Re: PM3 digital modem problems

Sherwood Pekelo (spekelo@iav.com)
Fri, 16 May 1997 07:01:48 -1000 (HST)

First,

take pity on us 'poor' UNIX users and wordwrap...not to mention send in
ASCII with NO attachments, like that HTML crap...now onto your grief...

On Fri, 16 May 1997, Greg Watkins wrote:

> Hi all. We just recently switched over from a PM2E to a PM3 running
channelized T1 with 24 modems and we are having lots of problems. From
the messages I see here there are some others of you out there taht have
this setup working well and I am frustrated with tech support as they
have been slow to respond and as of yet have no answers. Here are the
problems:

Typically, give ComOS version. You ARE using the newest public beta
right? You should also cc questions of this nature to
support@livingston.com, in addition, CALL Livingston and open a
trouble-ticket. The mail list is an informal service by Livingston and as
such does not officially track individual customer's difficulties.

> 1. We have many users that cannot conect at all that could connect fine
before we switched to the digital modems. Most of them get an error such
as "The machine is not answering" or Cannot establish a dialup
connection" even though they hear the modem tones. It just can't
negociate a connection anymore. Sometimes if they change their modem from
whatever type it is in WIN 95 to a "standard modem" type then it will
connect ok.

What types of modems do the users have? Have you gone through all the
Win95 fixes? Have you looked through the digests/archives of this mail
list for answers for particular problems? Upgrade your users with the
kernal patch and the service pack. Have them disable IPX/SPX and NetBeui.

Occasionally, disabling hardware flow control works and/or software
compression.

If the user has a 56K modem, it current must be set to:

at+ms=11,1,14400,33600

for rockwell chipsets...

for USR 56K there is another init string, which I hope someone will post
again... was it atw95?

> 2. Another problem is that with most of the other users that
can connect, they are not getting on a full speed, i.e. it will connect at
24000 or 26400 but they have 28800 or 33.6 modems. Some will even connect
at 14400 or slower.

This is well known. Modems will connect at what the PM3 considers to be
the best current rate, but will actually transmit at a higher rate than
the initial connection in many instances. Take off the blinders and do
throughput tests rather than believing what the M$ DUN tells you. I've
had customers with 14.4Kbps modems say that they've never seen faster
throughputs than when they connect to our PM3. Again, some modems may
connect at 21600 or 24000 etc, but actually retrain to a higher speed.

As for connects at 14.4Kbps, what modems are doing this? Realize
Non-standards are NOT supported, such as V.Fast, V.FC, HST...

> 3. Last but not least, it appears that sometimes the ports will
show idle but when I call the number of that port I get a busy signal.
Resetting the port does not clear it, I have to reboot the portmaster or
if I wait long enough they will clear eventually.

Are you resetting the T1 channel or the modem? Relooking at your setup,
are you trunk-side terminated? It could be the telco is not giving you
the cleanest connection possible. The rebooting of the PM3 does not
conclusive indicate that it is the problem with your non-connections, it
could be the CT1. If possible, please look through the archives as this
was explained by someone in the near past.

> Has anyone else had these same symptoms or is it just something on our
end?

Yes, these symptoms occur, just seems you got hit with all of them at
once. Perhaps, if possible, sales or support should compile a list/FAQ to
be distributed regarding these issues.

Let the list AND support know your ComOS, User modem types, etc... then
progress can be made towards solving these difficulties.

When we first setup our PM3 with 2 PRI, we did experience some problems,
but by tracking down exactly what modem types, we have been able to get
98% of our users converted over. Though I'm still curious why we
initially would get no answers on a nearly idle box, but now haven't had
a problem with this....I'm guessing the telco did a few tweaks.... ;)

Take this constructively and not as an attack. Many have asked the same
questions and support has answered them...Now it remains for you to do a
little sleuthing so that all the clues are in place for the final
solution.

I wonder how the new DSPs will be when they're dropped in.... heheh I hope
the break-in time is much quicker... 8)

Just a thought...

--
Aloha,

Sherwood