Re: [NTISP] Rockwell

Youssef A. Rahman ( (no email) )
Tue, 09 Mar 1999 22:04:18 +0200

We have upgradede the OS to 7.0.1 but the same problem still exist, and we found
that 6.1.3 is the most stable OS and has the least communication bugs.

Josh Hillman wrote:

> From: Youssef A. Rahman <>
> >We had the same problem with the Ascend Max, and the following
> >initialization string stopped it
> >+ms=k56,1,75,33600,75,5600
> You might consider upgrading your Max to the latest OS (or at least 7.0.1--I
> just now realized that 7.0.3 and 7.0.4 have been released, but I haven't
> looked into them yet). There's only a single modem that I've come across
> that has a problem dialing into our Max 40xx machines and that's a modem
> built into a Compaq Presario 5204 or something. Althouth that modem is
> already V.90, there's something screwy about it that's preventing it from
> linking up with us (CDC never detected, then hangs up). That modem also
> doesn't comply with the standard AT commands that work with other Rockwell
> HFC-type modems, so we could never figure out how to disable the V.90
> (forcing it to V.34 or maybe K56Flex to see if that'd take care of it until
> a newer firmware release is avalailable for that modem).
> On a rare occasion, we come across a modem that won't connect unless 4
> commas are appended to the end of the dial-up number--this forces the modem
> to wait 8 seconds before doing anything because that modem doesn't recognize
> the ITU-T V.8bis (I think that's the number) fax tone that the NAS issues.
> Although that V.8bis is a standard and has been for quite some time, some
> modems don't know what to do with it.
> Actually, now that I think of it, I think IBM MWave modems have always had
> problems dialing into us (at least most of them).
> Josh Hillman
> Max 4004 and 4048 units, each running 7.0.1
> Sig Mode=Inband
> Rob Ctl=Inc-W-200
> Framing Mode=ESF
> Encoding=B8ZS
> >"Geoffrey L. Scully" wrote:
> >
> >> I am having problems with Rockwell V.90's and most Win Modems with the
> >> 3COM Hiper DSP's. They sit there continuing to handshake and then
> >> eventually timeout. Anyone else having this problem? Anyone figure out
> >> the fix?
> >>
> >> For more information about this list, including removal,
> >> see this url:
> >
> >
> >For more information about this list, including removal,
> >see this url:
> For more information about this list, including removal,
> see this url:

For more information about this list, including removal,
see this url: