Yes I believe so but there is something wrong with it as far as stalling connections goes. The DSP's we were having this problem with have PRI's coming from a GTE GTD5 switch. We have DSP's at another POP that is Ameritech using a 5ESS switch and running 2.0.51 with no problems. When we were using 2.0.51 on the GTD5 switch we started noticing an increase to the point of 10 to 15 complaints a day of stalling connections, I spoke with 3 Com and another ISP having similar problems and the consensus was to go back to 2.0.60 which we did and all of the sudden no more stalling complaints. We did nothing more that go back to 2.0.60 and we did not change any settings in the DSP cards. It is strange I will grant you but it worked for us and our customers quit having problems and were happy again so that was enough for me and we have not noticed any other problems with 2.0.60. Clint R. Sparks ComQuest Internet Services csparks@cqc.com ----- Original Message ----- From: "Paul Farber" <farber@admin.f-tech.net> To: <usr-tc@lists.xmission.com> Sent: Saturday, May 27, 2000 11:59 AM Subject: Re: (usr-tc) TCPIP Stall
Wasn't .51 just an engineering patch to correct a bad batch of DSP's?
Paul Farber Farber Technology farber@admin.f-tech.net Ph 570-628-5303 Fax 570-628-5545
On Fri, 26 May 2000, Clint R. Sparks wrote:
I disagree it does have to do with the DSP code 2.0.51 on certain telco switch equipment as we were having similar problems and went back to 2.0.60 and no more stalling, all the customers that were complaining about it said it was then fine and none have complained about it since, and the only thing we switched was the Hiper DSP code from 2.0.51 to 2.0.60. We are running Hiper ARC code 4.1.59-6. Also 3 Com has told me that they are seeing complaints specifically from those running 2.0.51 and customers complaining about stalling, they were not sure what was causing it when I spoke to them but they did say it was related to DSP code 2.0.51.
Clint R. Sparks ComQuest Internet Services csparks@cqc.com
----- Original Message ----- From: "V" <ved@iyka.com> To: <usr-tc@lists.xmission.com> Sent: Friday, May 26, 2000 5:03 PM Subject: RE: (usr-tc) TCPIP Stall
The problem has nothing to do with DSP code, need to know the version of Hiper arc code, and also would need traces. Mon PPP on the user when connected will show some info to begin with.
-V
->-----Original Message----- ->From: owner-usr-tc@lists.xmission.com ->[mailto:owner-usr-tc@lists.xmission.com]On Behalf Of Scot Desort ->Sent: Friday, May 26, 2000 4:44 PM ->To: usr-tc@lists.xmission.com ->Subject: (usr-tc) TCPIP Stall -> -> ->We are running DSP's with 2.0.51 software. We have had 2 customers in the ->past 3 weeks with this issue. They connect to us just fine. If they simply ->connect and do nothing else, their connection is stable. We can ping back ->and forth. They then launch a TCPIP application like IE. Sometimes ->immediately, other times after several minutes, their connection simply ->stalls. All data traffic stops. They can no longer ping. Even if ->they close ->the app, the ability to send traffic does not return. -> ->Happens with IE, netscape, OE. Installed latest IE5 and reset all browser ->defaults. -> ->Customers both have different modems. One runs Win98, the other Win98SE. -> ->One has AOL5, the other doesn't. Tried disabling AOL Dialup ->Adapter. Removed ->extra occurences of wsock.vxd in the AOL directories. Removed ->TCPIP and DUN ->and reinstalled. Cannot pin this problem down. -> ->Might now be related to the DSP's at all, but I figured I'd give ->this list a ->shot. Maybe someone else has run across this problem. Any ideas? -> ->-- ->Regards, -> ->Scot -> -> -> -> ->- -> To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" -> with "unsubscribe usr-tc" in the body of the message. -> For information on digests or retrieving files and old messages send -> "help" to the same address. Do not use quotes in your message. ->
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.