Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!ira.uka.de!smurf!ipkama!freesid!nd495x!mamnix!mam
From: mam@mamnix.hamm.sub.org (Michael A. Meiszl)
Newsgroups: comp.dcom.modems
Subject: Re: Telebit V.32 problems
Keywords: V.32, Telebit, LAPM, MNP, disconnection
Message-ID: <112227@mamnix.hamm.sub.org>
Date: 14 Nov 90 21:55:34 GMT
References: <1990Nov8.180824.20867@Think.COM>
Organization: MaMniX!, Hamm, FRG
Lines: 22

bruce@think.com (Bruce Walker) writes:

>	1) Is this a Telebit implementation problem or a fundamental
>	   problem in the protocols involved?
>	2) Has anyone else seen it on Telebit or other hardware?
>	3) What can I do about it?
I have the same difficulties with my two TB2500. V42 does a better job as
MNP, but both of them resign after a hit by line noise.
I have contact with a manufacturer of V.32 modems here in germany and their
devolper tracked the problem quite down. He found that TBs generate a bogus
MNP/LAPM header on resynch. They just send a byte too much, so the other modem
can't resynch. This happens too often, the line is dropped by the other modem
after getting too much errors. The new Roms (GF7.00) behave a bit better, V42
can be resumed, MNP is still bad.
I personnally gave up on this error. PEP works fine and the next TB won't have
V.32 anymore. I save my money for other nice things..

cu mam
-- 
Michael A. Meiszl, Tomsonstr. 25, 4700 Hamm 1 Internet: mam@hamm.sub.org
Voice: 02381/889121   Fax   : 02381/880084    Fido    : NO FIDO ANYMORE
Data : 02381/880081   Traily: 02381/880082    Login   : box | uucp | nuucp