Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site felix.UUCP
Path: utzoo!linus!decvax!ittvax!dcdwest!sdcsvax!bmcg!felix!zemon
From: zemon@felix.UUCP
Newsgroups: net.unix-wizards
Subject: Re: TELEX and UNIX
Message-ID: <315@felix.UUCP>
Date: Mon, 2-Jul-84 10:06:55 EDT
Article-I.D.: felix.315
Posted: Mon Jul  2 10:06:55 1984
Date-Received: Wed, 4-Jul-84 05:05:29 EDT
References: <12431@arizona.UUCP>
Organization: FileNet Corp., Costa Mesa, Ca.
Lines: 31

The easiest way to let your Unix system communicate with
Telex terminals is to subscribe to Western Union
Telegraph's EasyLink system.  I just spent a couple of
months learning that this is virtually the only way to do
it effectively (unless you want to lease your own Telex
line and adaptor hardware -- modems won't do it).

If you want to communicate with USA Telex terminals, then I
strongly recommend EasyLink.  For international
communication, any of the competitors will probably do just
as well.  We have used MCI Mail (alias Western Union
International -- no relation to WU Telegraph) successfully
for international traffic but are very dissatisfied with
the domestic service.

The basic problem is that there are a number of competing
telex communication networks.  If you attempt to send mail
to a Telex number, almost everybody *assumes* that the
number is on the Western Union Telegraph network.  Routing
messages across networks requires explicit action on the
operator's part and may not work.  For instance, Western
Union Telegraph ("real" Telex) subscribers have a lot of
trouble sending messages to MCI Mail (domestically located
Western Union International) telex numbers because the
numbers are too long.

    Art Zemon
    FileNet Corp.
    714/966-2344
    ...!{ucbvax,decvax}!trwrb!felix!zemon
    Telex I: 383902 FILENET CM