08-13-2007 07:32 AM - edited 03-14-2019 11:02 PM
Hi,
I have installed 2 2800 series with MGCP and Callmanager 5.1
The first one is connected to the PSTN (PRI)
The second is connected to a PBX (PRI)
the problem I have is when the second receive a call from the pstn, the isdn debug output is:
Aug 13 14:37:23.642: ISDN Se1/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0002
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA9838A
Exclusive, Channel 10
Calling Party Number i = 0x00A1, N/A
Plan:Unknown, Type:Unknown
Called Party Number i = 0x80, '5220'
Plan:Unknown, Type:Unknown
Aug 13 14:37:23.666: ISDN Se1/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8002
Channel ID i = 0xA9838A
Exclusive, Channel 10
Aug 13 14:37:31.734: ISDN Se1/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x0002
Cause i = 0x82AF - Resource unavailable, unspecified
12-06-2007 10:45 AM
hi,
did you solve this issue.if yes could you please share the solution.
i an facing the same problem
thanks in advance
Tom
12-14-2007 11:30 PM
It may not help here, but I use a demo version of a PRI Debugger program out there. go to pippinsoftware.com
I'm waiting for the full version to come out next month.
12-22-2007 10:00 AM
The first beta of this PRI debugger had some issues, there's a revised beta posted at pippinsoftware.com now.
01-03-2008 10:20 AM
Just FYI - you can grab the full version of a debug isdn q931 log analyzer dirt cheap at pippinsoftware.com It's alot easier than watching the logs scroll.
01-03-2008 02:39 PM
Q931 decoders are not going to help here. The debug traces clearly show an outgoing setup, the far end rings for 8 seconds and then the call is cleared from the gateway.
This means there is nothing wrong with the ISDN side of things.
Most common reason you see 'resource unavailable, unspecified' clear code is due to a codec mismatch on H323, or a lack of dsp resources on the router for either normal call processing or transcoding/conferencing/mtp. Since this is under MGCP control, the codecs are specified under the CCM control so there should be no mismatch.
Therefore we need to see what is happening at the MGCP side of things. Make a single test call and obtain the log from 'debug mgcp packet' , then turn this debug off and get a log from 'debug voip ccapi inout' for a similar test call. Make sure you do this when only one call is up (the debugs are too hard to follow otherwise)
Also attach a SH VER, SH RUN and SH DIAG output.
01-03-2008 11:18 PM
Post & Cameron,
I experienced the same behavior once I exhausted all my DSP Resources on my 2800's that hosted my Pri Trunks at a previous company. The solution was to purchase more PVDM's and calculate my DSP requirements more accurately. I recommend using the Cisco DSP Calculator that can be found here.
http://www.cisco.com/cgi-bin/Support/DSP/cisco_prodsel.pl
Remember the more complex the Codec the more DSP resources you will end up using.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: