This is ecu 3.24 modified to work with Linux.

There are several files in this distribution.
ecu3.24src.tgz	- Source of ecu
ecu3.24bin.tgz	- Binaries of ecu compiled using gcc 2.4.3 shared libs 4.4.1
ecu.patch	- patch to original sources to make it work correctly under
		  Linux.

Here is an excerpt from the README:

ECU (Extended Call Utility) is a research and engineering
communications program originally written for users of SCO UNIX
V.3.2/386 and XENIX V on 80286 and 80386 systems.  Support for
other systems has been added and further porting is possible with
"minor" effort to other systems based on or similar to UNIX
System V.

ECU provides the classic terminal communications facility of
passing keyboard data to a serial line and incoming data to the
computer video display.  In addition, a dialing directory, a
function key mapping feature, session logging, and other
basic features are available.  

ECU presents to the host a flexible "ANSI" terminal type,
accepting any valid video control sequences from MS-DOS or SCO
documentation as of late 1990.  It also fares well, though
imperfectly, with Sun and VT-100 in-band video control sequences.
Standards are great: everybody should have one, especially if
they call it "ANSI". For more information, refer to the manual
section titled "ANSI Filter."

Support for arbitrary video consoles is included.  I use ECU
(almost exclusively now) with an X11R4 xterm.  This release has
been tested extensively with xterms (particularly Metro Link
X11R5, SCO ODT 2.0 X11R4, SunOS 4.1 MIT standard distribution,
OpenWindows 2.0, and Roell's X386 1.1b).  Your terminal must be
fairly "smart", with insert/delete-line features,
erase-to-end-of-line, etc..  See "Supported Terminals" in the
manual.  Also check the note below named "KBDTEST3".

ECU supports numerous file transfer protocols: as of this
writing, XMODEM, XMODEM/CRC, XMODEM-1K, YMODEM/CRC Batch,
ZMODEM/CRC-16, ZMODEM/CRC-32, C-Kermit 5 and SEAlink are
supported.  For more information, refer to the manual sections
describing the individual interactive and procedure file transfer
commands.

A very flexible procedure (script) language is also incorporated
to automate many communications tasks.  In addition to augmenting
interactive tasks, by using shell scripts and ECU procedures, ECU
can perform batch-style communications sessions in an entirely
"unattended" fashion.

For applications too unwieldy for the procedure language,
"ecufriend" programs are supported.  Friends are spawned by ECU
having access to the shared memory segment containing an
ECU-managed "screen image" and other data and having use of the
attached communications line.

--------------------------------------------------

The Linux port of ECU 3.24 was done by Jeremy Bettis
Contact ME for Linux specific problems, not the author.  Contact the author
for general ECU problems, not me.

I can be emailed at:  jbettis@cse.unl.edu - or - jerbo@tddi.UUCP