Last night in my initial testing of our new PM3, I kept getting
disconnected whenever my connection saw any kind of increased activity.
I posted a message earlier about the bad FCS messages.
Today I had my home machine call in and I started a pingflood to it.
Sure enough, about 30 seconds later, it disconnected with the following
information for M0:
M0 S0 ACTIVE 31200 V42BIS LAPM 65 0 CIRCUIT DISCONNECT
Session termination history for the port:
0 min - User Request - Call Circuit Closed
2 min - User Request - Normal Modem Disconnect
This doesn't happen with the PM2e, and I'm certain that my system did not
request the disconnection, and I'm sure that the previous disconnect,
under similar circumstances, was not normal.
The ComOS version is 3.7. The same behavior happened with the 3.5c6 that
the box was shipped with. Modems that I've tested with this are the
Supra Faxmodem 288, Supra Express, and Boca 28.8. I've found the Supra
Faxmodem to be totally reliable until I started calling this PM3 with it.
So what's going on here? This is a fairly major problem.
Nick
--- Nick Johnson, writer of code, fixer of modems, administrator of pops Gulf Coast Internet Network Engineering Team Check the web: http://www.gulf.net/support/network_status/