I've heard that a lot of people have experienced the same problem. In fact, I was told that it was a known issue after 3.5.12 was released and that was the reason for the 3.5.100 fix. 3.5.100 would be a good first move. I think you'll find that fixes your problem...for now. -Justin Kendall, NetEase, Inc.- jkendall@neteze.com ----- Original Message ----- From: "WebMaster" <webmaster@floodcity.net> To: <usr-tc@mailman.xmission.com> Sent: Monday, August 05, 2002 6:35 PM Subject: [USR-TC] HiperDSP and certain modem chipsets
Hi,
We're having handshaking issues with our HiperDSP (3.5.12) rack and
certain client
modem chipsets. Customers with Lucent WinModems and older USR Sportsters (x2) aren't finishing a handshake. The strange thing is that the same customers can connect fine onto our older Quad Modem racks. We've tried to reproduce the problem here with no success. I've tried Lucent drivers from 5.20 to 8.22 (newest), and they all connected fine. I've also tried older USR Sportsters with v.34, x2, and v.90 flash. They also connected fine, although the x2 flashes only connected at v.34. CommWorks support suggested I disable pcm upstream, and to try the 3.5.100 ER DSP code. I've also (as per the knowledge base) tried disabling v.92 altogether, and also V.FC Precoding. I even (on a whim) tried disabling V.44 and V.42. Nothing seems to have any effect. Has anyone else experienced similar problems, or have any ideas?
Thank you,
Allen Hebenthal
Systems Administrator FloodCity Internet (814) 288-3223 sysadmin@floodcity.net
_______________________________________________ USR-TC mailing list USR-TC@mailman.xmission.com http://mailman.xmission.com/cgi-bin/mailman/listinfo/usr-tc