>> >what I am getting is all seem to be happy, but after a few calls, connect
>> >rates start being 9600 rather than 24,600, 28,800, etc. . .
We've been using Supras for over a year and have not observed this problem.
The init string we use is straight out of a modem table listing posted by
Livingston's Brian Rice: AT&F&D3&K3&Q5S0=1
Then we write it to both NVRAM loactions with AT&W0&W1
(For the sake of honesty, Bri also had the command M0 to shut off
the speaker in his init string...)
We're running both a recent shipping version of firmware, as well as
the beta known as 1.440-16 which we've found to be stable and offer good
connect rates. Only bug noted is that on aborted login attempts or voice
calls being received by the modems that cause the modems to hear dialtone
during handshaking will sometimes cause the modems to lock at 300 baud and
not reset in response to the PortMaster dropping DTR.
>> I have this same problem....
>>
>> I changed my init string to AT&F2&D3&S0=1&W this helped a lot. Even so
>> after a few days a few of the modems started going back to the 9600 connects.
This init string looks like it does the same thing as described above, which
is interesting.
Assuming your PortMaster async ports are all locked at 115,200 (or 57,600) for
all three possibilities (ie speed 1, speed 2, speed 3) the only other thing I
can think of is heat. We bought a large fan and installed a dedicated A/C in
the NOC because the room gets quite warm. The Supras were the only devices
that seemed to get temperamental over heat, but our problems manifested itself
as an inibility to handshake properly at call setup. Customers just had a bitch
of a time getting connected.
At this point, we're transitioning most of the dial-ups to the new Microcom
ISPorte
rackmount modem product, knowing that in the future we'll probably bring our
dialups in via channelized T-1.
If you solve your modem problems, and want to buy some more Supras, let me
know <g>!
Damien