cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2218
Views
19
Helpful
17
Replies

MGCP Controlled Gateway Call Drops

sarwarm123
Level 1
Level 1

I am trying to configure MGCP controlled gateway but experiencing a call drop issue. A gateway has BRI card installed, when I try to make a call it rings but as soon as I receive call it just drop. I gathered some debug logs (Debug ISDNQ931). I have replaced DSP but still no luck.

When I ring first time after restart Gateway

Oct 31 16:04:23.730: ISDN BR0/1/0 Q931: RX <- RELEASE_COMP pd = 8  callref = 0x01

2951-rtr1#

Oct 31 16:04:32.423: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8  callref = 0x01

        Sending Complete

        Bearer Capability i = 0x9090A3

                Standard = CCITT

                Transfer Capability = 3.1kHz Audio

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0x89

                Exclusive, B1

        Calling Party Number i = 0x2183, '7776137568'

                Plan:ISDN, Type:National

        Called Party Number i = 0x81, '306892'

                Plan:ISDN, Type:Unknown

Oct 31 16:04:32.435: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8  callref = 0x81

        Channel ID i = 0x89

                Exclusive, B1

Willenhall-2951-rtr1#

Oct 31 16:04:32.463: ISDN BR0/1/0 Q931: TX -> ALERTING pd = 8  callref = 0x81

        Progress Ind i = 0x8088 - In-band info or appropriate now available

Willenhall-2951-rtr1#

Oct 31 16:04:34.487: ISDN BR0/1/0 Q931: TX -> CONNECT pd = 8  callref = 0x81

Oct 31 16:04:34.511: ISDN BR0/1/0 Q931: TX -> DISCONNECT pd = 8  callref = 0x81

       Cause i = 0x80AF - Resource unavailable, unspecified

Oct 31 16:04:34.539: ISDN BR0/1/0 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x01

Oct 31 16:04:34.551: ISDN BR0/1/0 Q931: TX -> STATUS pd = 8  callref = 0x81

       Cause i = 0x80E2 - Message not compatible with call state or not implemented

        Call State i = 0x0B

Oct 31 16:04:34.703: ISDN BR0/1/0 Q931: RX <- RELEASE pd = 8  callref = 0x01

Oct 31 16:04:34.707: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x81

When I ring second time, it just beep and give this error message

Oct 31 16:05:40.233: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8  callref = 0x01

        Sending Complete

        Bearer Capability i = 0x9090A3

                Standard = CCITT

                Transfer Capability = 3.1kHz Audio

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0x89

                Exclusive, B1

        Calling Party Number i = 0x2183, '7776137568'

                Plan:ISDN, Type:National

        Called Party Number i = 0x81, '306892'

                Plan:ISDN, Type:Unknown

Willenhall-2951-rtr1#

Oct 31 16:05:44.225: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8  callref = 0x01

        Sending Complete

        Bearer Capability i = 0x9090A3

                Standard = CCITT

                Transfer Capability = 3.1kHz Audio

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0x89

                Exclusive, B1

        Calling Party Number i = 0x2183, '7776137568'

                Plan:ISDN, Type:National

        Called Party Number i = 0x81, '306892'

                Plan:ISDN, Type:Unknown

Willenhall-2951-rtr1#

Oct 31 16:05:48.194: ISDN BR0/1/0 Q931: RX <- DISCONNECT pd = 8  callref = 0x01

        Cause i = 0x82E6 - Recovery on timer expiry

Oct 31 16:05:48.198: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x81

       Cause i = 0x80D1 - Invalid call reference value

17 Replies 17

Two more SDI log files attached

I have looked at the trace and I can see that the gateway is sending error code 510 to CUCM during the CRCX phase of the negotiation..

11/08/2012 18:09:32.286 CCM|MGCPHandler received msg from: 10.88.48.3

510 7337 fx: setting cannot be supported

|<:STANDALONECLUSTER><:10.102.243.13><:2><:10.88.48.3><:><:SIGNIFICANT><:2000>

11/08/2012 18:09:32.286 CCM|MGCPHandler received RESP header w/ transId= 7337|<:STANDALONECLUSTER><:10.102.243.13><:2><:10.88.48.3><:><:DETAILED><:2000>

11/08/2012 18:09:32.286 CCM|<:STANDALONECLUSTER><:10.102.243.13><:2><:MGCPENDPOINT><:>BRI/S0/SU1/P1/1@BellGreen-2851-rtr1.cwss.nhs.uk><:BRI><:ALL><:FFFF>

11/08/2012 18:09:32.286 CCM|MGCPHandler received RESP header w/ transId= 7337 FOUND a match with ERROR RETURN CODE|<:STANDALONECLUSTER><:10.102.243.13><:2><:10.88.48.3><:BRI><:SIGNIFICANT><:2000>

11/08/2012 18:09:32.286 CCM|MGCP Protocol Error - VERB:CRCX, transId: 7337, return_code: 510

11/08/2012 18:09:32.286 CCM|MGCPHandler received msg from: 10.88.48.3

510 7337 fx: setting cannot be supported

|<:STANDALONECLUSTER><:10.102.243.13><:2><:10.88.48.3><:><:SIGNIFICANT><:2000>

11/08/2012 18:09:32.286 CCM|MGCPHandler received RESP header w/ transId= 7337|<:STANDALONECLUSTER><:10.102.243.13><:2><:10.88.48.3><:><:DETAILED><:2000>

11/08/2012 18:09:32.286 CCM|<:STANDALONECLUSTER><:10.102.243.13><:2><:MGCPENDPOINT><:>BRI/S0/SU1/P1/1@BellGreen-2851-rtr1.cwss.nhs.uk><:BRI><:ALL><:FFFF>

11/08/2012 18:09:32.286 CCM|MGCPHandler received RESP header w/ transId= 7337 FOUND a match with ERROR RETURN CODE|<:STANDALONECLUSTER><:10.102.243.13><:2><:10.88.48.3><:BRI><:SIGNIFICANT><:2000>

11/08/2012 18:09:32.286 CCM|MGCP Protocol Error - VERB:CRCX, transId: 7337, return_code: 510

Can you send me your sh run and also please enable the ff debug

debug mgcp packet

then do a test..pleae send the debug

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

Please rate all useful posts

Thanks Aokanlawon, I'll be out all day today. But will upload sh run and mgcp debug output tomorrow. Thank you very much once again to being looking at this issue