Xref: utzoo comp.sys.att:2370 comp.dcom.modems:1352
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ptsfa!ihnp4!ttrdc!ttrde!stox
From: stox@ttrde.UUCP (Kenneth P. Stox)
Newsgroups: comp.sys.att,comp.dcom.modems
Subject: Re: Trailblazer gets mad at AT&T 3b1 OBM (on board modem)
Message-ID: <327@ttrde.UUCP>
Date: 2 Feb 88 15:14:26 GMT
References: <986@neoucom.UUCP> <362@dmk3b1.UUCP>
Organization: AT&T, Skokie, IL
Lines: 20
Keywords: thinks 3b1 has MNP protocol
Summary: 3B1 OBM <==> MNP

In article <986@neoucom.UUCP> wtm@neoucom.UUCP (Bill Mayhew) writes:
>. . .  When the trailblazer placed the data call at
>1200 baud into the 3b1 OBM, it thought that the 3b1 had MNP
>protocol, as reported by the Telebit's "CONNECT 1200/REL".  At that
>point, the Trailblazer locked up, and I had to drop the DTR lead to
>get it to disconnect. . . .
>So the question is, is the 3b1's OBM really supposed to be an MNP
>modem, and this 3b1 is sick?

I have had the exact same experience using the MicroCom 9424C. The
only solution was to disable the "Auto-Reliable" mode on the 
MicroCom. Apparently, something about the OBM on the 3B1 convinces
the MNP modem that it is also a MNP modem. 

So, to answer your question, your OBM is fine, your 3B1 probably
healthy. If someone out there in netland has a copy of the MNP
specification, maybe you can let us in on why it behaves this
way.

-Ken Stox