Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!revell From: revell@uunet.UU.NET (James R Revell Jr) Newsgroups: comp.dcom.modems Subject: Re: echo cancellation & Telebits (WAS: tb2500 to tb+ connect problem) Summary: MCI starting echo cancelation ? Message-ID: <116057@uunet.UU.NET> Date: 28 Dec 90 23:52:31 GMT References: <1990Dec28.045029.9006@bilver.uucp> Reply-To: revell@uunet.uu.net (James R Revell Jr) Organization: UUNET Communications Services, Falls Church, VA Lines: 31 In article <1990Dec28.045029.9006@bilver.uucp> bill@bilver.uucp (Bill Vermillion) writes: } I have a T2500 rev 7 roms, he's using a tb+ rev 4 roms. I can call } him, and uucp transfers do fine. } } He calls me, and the modems seem to train forever, the normal low } speed gets going, then the moose calls start, they talk a bit, and } then I seem to send some tones and it starts again with the PEP } calls. It continues for about 15 seconds until he times out. Are you calling long distance and using different LD carriers (my bet is he uses MCI, maybe Sprint, and you don't)? Do you also have S120 set to 16 or 28, thus disabling the fix for echo cancellation in your T2500? Based on problems I've dealt with over the last 10 days I am getting the impression that MCI may have started the same echo cancellation deal that Sprint did late last winter. There are other symptoms caused by this problem I haven't noticed yet, but the long retraining at start of call is the first symptom I saw last time too. If I'm right this is going to be a big problem for lots of people soon. I encourage any UUNET subscriber who experiences similar problems to send mail to uunet!postmaster. I'm particularly interested in whether you use MCI when seeing this problem. Other symptoms of this problem may include extremely low throughput and a dramatic increase in failed connections. } Bill Vermillion - UUCP: uunet!tarpit!bilver!bill -- James Revell senior uunet postmaster /8^{~