home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!ira.uka.de!smurf.sub.org!flatlin!pilhuhn!senga.ka.sub.org!chr
- From: chr@senga.ka.sub.org (Christian Riede)
- Newsgroups: comp.dcom.modems
- Subject: Re: How to get Supra 9600 to talk V.32 to Telebit Worldblazer?
- Message-ID: <xxPYr*Sl0@senga.ka.sub.org>
- Date: Tue, 10 Nov 1992 06:48:33 GMT
- FollowUp-To: poster
- References: <BxF7D6.MEq@hico2.westmark.com>
- Organization: Private UUCP site
- X-Newsreader: Arn V1.00 pre
- Lines: 33
-
- In article <BxF7D6.MEq@hico2.westmark.com>, Kris A. Kugel writes:
-
- >
- > My brother out in California has a Supra 9600 modem.
- > I have a Worldblazer here.
- >
- > When he calls my machine, the only way he's been able
- > to successfully connect is when he sets it to accept
- > 2400 baud connections ONLY. If he does not do that,
- > the Supra identifies something in the PEP answer sequence
- > as being something else, and puts out a solid tone until
- > it hangs up.
- >
- > Can anybody who has dealt with this problem give me some
- > suggestions? I'd prefer a solution which affects
- > just the Supra, as I've got my uucp connections
- > running smoothly, and for various reasons I don't want
- > to turn the worldblazer answer sequence to answer PEP last.
-
- Make Supra skip PEP carriers by adding commas (can be up to 10) after the
- number (assuming that PEP carrier comes first).
-
- BTW, I had this kind of behaviour with my old 2400 Modem connecting to a
- TB2500 and solved it the above way. My Supra V.32bis connects just fine to
- TB2500s. What's different with Worldblazers and TB2500?
-
- Gruss, Christian
-
- --
- Christian Riede, Lange Strasse 88, D-W7500 Karlsruhe 51, Germany
- Tel. (+49) 721 {886091 | 608-4487 | 608-2749} | iso-8859-1:
- EMail: chr@senga.ka.sub.org, riede@ira.uka.de | Σ÷ⁿ▀==aeoeuess
- War das 'ne Landung --- oder hast du den Globus gerammt?
-