Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

DSP error on a 3640

I am having problems with a gateway dropping calls. Someone calls an internal user. The user picks up. The call gets dropped.

I look in the logs and I see this error message.

%VTSP-3-DSP_TIMEOUT: DSP timeout on event 0x44: DSP ID=0x3: DSP error stats (call mode=1667152024), chnl info(1, 14, 2)

I am running H323 on a 3640 running 12.2(8)T1 with a PRI.

Any help would be appreciated.

4 REPLIES
Cisco Employee

Re: DSP error on a 3640

You may want to upgrade the IOS on this GW. 12.2(8)T1 has a software advisory notice. Possibly running into CSCin06601, which is a duplicate of CSCdw84078. The recommended version would be to go to 12.2(8)T4.

Hope this helps

Rob

New Member

Re: DSP error on a 3640

Brian,

The "DSP_TIMEOUT" message only means IOS lost connection with one of the DSPs. That may or may not require action.

Have a look at http://www.cisco.com/warp/customer/788/products/dsp-trbl.html

for more information.

HTH,

Stéphane

Re: DSP error on a 3640

I just got done fixing this on a clients router, it was an IOS bug and a IOS upgrade fixed it. They were running into bug CSCdu53333 which was fixed in 12.2(6a). According to the bug navigator, this was fixed in 12.2(6.7)T for the T train. You might be running into another issue however. My client was on 12.2(5) and we went to 12.2(12) but thats a different train. See the URL the other person posted for more details.

You can get around this issue by reloading the router, which brings the timed out DSPs back to life. the (1, 14, 2) middle # 14 is the Dsp Id. DSP 14 is one of the DSPs on the PVDM module in socket 0 on the NM-HDV. These were first ones to timeout for my client as well. It took on average of 14-20 hrs before they timed out.

You can do a test dsp (slot# of NM-HDV) and choose option 1 to query each DSP. They will come back as being ALIVE or NOT RESPONDING or might not respond at all. In my case the timed out ones didn't even respond.

If you have open voice-ports or channels, you can move the call to another voice-port which may provide a workaround. Each voice-port is bound to a different DSP. You can get the voice-port to DSP id mapping by choosing option 2 in the test dsp command above.

The VTSP-3-DSP_TIMEOUT will appear in logs or across console a few seconds after a call is made to one of the voice-ports tied to a DSP that is timed out. So, if you know that dial-peer # you can do 'csim start ###' at console/telnet and it should fail if DSP is sleeping and a few seconds later you'll see the error scroll by if you have term mon on or are on console.

HTH, Erick

New Member

Re: DSP error on a 3640

Well I upgraded the IOS to 12.2.(11)T So far no errors and no problems.

This gateway had been in production for several months with no problems. Not sure why it started to crop up now. I will definitely keep an eye on this guy.

105
Views
0
Helpful
4
Replies
CreatePlease login to create content