Solved: It is a CUCM with a SIP trunk

Cameron Whitehead · ‎05-20-2014

Hi,

We are having an issue where calls made to a disconnected numbers are giving users issues. Rather then getting a reorder tone or a message saying the number does not exist the phone just plays dead air and shows "Call Proceed" on the screen. I have done an ISDN q931 debug and I get the following.

005846: May 20 13:56:57 PDT: ISDN Se0/0/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x84FE
        Cause i = 0x8090 - Normal call clearing
005847: May 20 13:56:57 PDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x04FE
005848: May 20 13:56:57 PDT: ISDN Se0/0/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x84FE
005849: May 20 13:56:57 PDT: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0xD is 0x0 0x0, Calling num 5555
005850: May 20 13:56:57 PDT: ISDN Se0/0/0:23 Q931: Sending SETUP callref = 0x457D callID = 0xC4FE switch = primary-ni interface = User
005851: May 20 13:56:57 PDT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x457D
        Bearer Capability i = 0x8090A2
                Standard = CCITT
                Transfer Capability = Speech
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA98395
                Exclusive, Channel 21
        Facility i = 0x9F8B0100A10C020167020100800454657374
                Protocol Profile = Networking Extensions
                0xA10C020167020100800454657374
                Component = Invoke component
                        Invoke Id = 103
                        Operation = CallingName
                                Name Presentation Allowed Extended
                                Name = Test
        Calling Party Number i = 0x0081, '5555'
                Plan:Unknown, Type:Unknown
        Called Party Number i = 0xA1, '7784296802'
                Plan:ISDN, Type:National
005852: May 20 13:56:57 PDT: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8 callref = 0xC57D
        Channel ID i = 0xA98395
                Exclusive, Channel 21
005853: May 20 13:56:58 PDT: ISDN Se0/0/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0xC57D
        Cause i = 0x8081 - Unallocated/unassigned number
        Progress Ind i = 0x8088 - In-band info or appropriate now available
005854: May 20 13:57:14 PDT: ISDN Se0/0/0:23 Q931: RX <- PROGRESS pd = 8 callref = 0xC57D
        Cause i = 0x8081 - Unallocated/unassigned number
        Progress Ind i = 0x8088 - In-band info or appropriate now available
005855: May 20 13:57:17 PDT: ISDN Se0/0/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x457D
        Cause i = 0x8090 - Normal call clearing
005856: May 20 13:57:17 PDT: ISDN Se0/0/0:23 Q931: RX <- RELEASE pd = 8 callref = 0xC57D
005857: May 20 13:57:17 PDT: ISDN Se0/0/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x457D

I can see the Progress Message over and over again saying that the number is "Unallocated/unassigned" but the user doesn't know that so they just sit on the line.

Thanks,

Cameron

Brian Meade · ‎05-21-2014

So looks like the problem is on the CUCM side not responding to the 183 Session Progress. Try changing the SIP Profile on the SIP Trunk to have SIP Rel1XX Options set to "Send Prack if 1XX contains SDP".

Edit: The trunk has to be reset after the change so that needs to be done after hours.

View solution in original post

George Thomas · ‎05-20-2014

/Is this a CM or CME environment, what kind of gateway is this? SIP/MGCP/H323?

Please rate useful posts.

Cameron Whitehead · ‎05-21-2014

It is a CUCM with a SIP trunk to the gateway.

Brian Meade · ‎05-21-2014

Get a "debug ccsip messages" so we can see how it's getting converted to SIP. It should be sending a 183 Session Progress to pass through the recording to the phone.

Cameron Whitehead · ‎05-21-2014

Hi Brian,

Here is the output from the debug ccsip messages.

006461: May 21 12:31:30 PDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:97785551234@<Gateway ip>:5060 SIP/2.0
Via: SIP/2.0/TCP <CUCM ip>:5060;branch=z9hG4bK2264d597b4bba
From: "Test" <sip:5555@<CUCM ip>>;tag=852701~3fecf685-a77c-4687-a8b6-306635a9b4c0-18134622
To: <sip:97785551234@<Gateway ip>>
Date: Wed, 21 May 2014 19:31:30 GMT
Call-ID: 80ed5a80-37c1ff12-9141-1e32a8c0@<CUCM ip>
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:<CUCM ip>:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 2163038848-0000065536-0000017152-0506636480
Session-Expires: 1800
P-Asserted-Identity: "Test" <sip:5555@<CUCM ip>>
Remote-Party-ID: "Test" <sip:5555@<CUCM ip>>;party=calling;screen=yes;privacy=off
Contact: <sip:5555@<CUCM ip>:5060;transport=tcp>
Max-Forwards: 70
Content-Length: 0

006462: May 21 12:31:30 PDT: //73331/80ED5A800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP <CUCM ip>:5060;branch=z9hG4bK2264d597b4bba
From: "Test" <sip:5555@<CUCM ip>>;tag=852701~3fecf685-a77c-4687-a8b6-306635a9b4c0-18134622
To: <sip:97785551234@<Gateway ip>>
Date: Wed, 21 May 2014 19:31:30 GMT
Call-ID: 80ed5a80-37c1ff12-9141-1e32a8c0@<CUCM ip>
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Length: 0

006463: May 21 12:31:30 PDT: //73331/80ED5A800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP <CUCM ip>:5060;branch=z9hG4bK2264d597b4bba
From: "Test" <sip:5555@<CUCM ip>>;tag=852701~3fecf685-a77c-4687-a8b6-306635a9b4c0-18134622
To: <sip:97785551234@<Gateway ip>>;tag=E69CF0E4-1C0A
Date: Wed, 21 May 2014 19:31:30 GMT
Call-ID: 80ed5a80-37c1ff12-9141-1e32a8c0@<CUCM ip>
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:7785551234@<Gateway ip>>;party=called;screen=no;privacy=off
Contact: <sip:97785551234@<Gateway ip>:5060;transport=tcp>
Supported: sdp-anat
Reason: Q.850;cause=1
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 428

v=0
o=CiscoSystemsSIP-GW-UserAgent 448 422 IN IP4 <Gateway ip>
s=SIP Call
c=IN IP4 <Gateway ip>
t=0 0
m=audio 31074 RTP/AVP 18 0 8 9 4 96 15 19
c=IN IP4 <Gateway ip>
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=fmtp:9 bitrate=64
a=rtpmap:4 G723/8000
a=fmtp:4 bitrate=6.3;annexa=no
a=rtpmap:96 G726-32/8000
a=rtpmap:15 G728/8000
a=rtpmap:19 CN/8000

006464: May 21 12:31:40 PDT: //73331/80ED5A800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 183 Session Progress
Via: SIP/2.0/TCP <CUCM ip>:5060;branch=z9hG4bK2264d597b4bba
From: "Test" <sip:5555@<CUCM ip>>;tag=852701~3fecf685-a77c-4687-a8b6-306635a9b4c0-18134622
To: <sip:97785551234@<Gateway ip>>;tag=E69CF0E4-1C0A
Date: Wed, 21 May 2014 19:31:30 GMT
Call-ID: 80ed5a80-37c1ff12-9141-1e32a8c0@<CUCM ip>
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Remote-Party-ID: <sip:7785551234@<Gateway ip>>;party=called;screen=no;privacy=off
Contact: <sip:97785551234@<Gateway ip>:5060;transport=tcp>
Supported: sdp-anat
Reason: Q.850;cause=1
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 428

v=0
o=CiscoSystemsSIP-GW-UserAgent 448 422 IN IP4 <Gateway ip>
s=SIP Call
c=IN IP4 <Gateway ip>
t=0 0
m=audio 31074 RTP/AVP 18 0 8 9 4 96 15 19
c=IN IP4 <Gateway ip>
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=fmtp:9 bitrate=64
a=rtpmap:4 G723/8000
a=fmtp:4 bitrate=6.3;annexa=no
a=rtpmap:96 G726-32/8000
a=rtpmap:15 G728/8000
a=rtpmap:19 CN/8000

006472: May 21 12:32:40 PDT: //73331/80ED5A800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/TCP <CUCM ip>:5060;branch=z9hG4bK2264d597b4bba
From: "Test" <sip:5555@<CUCM ip>>;tag=852701~3fecf685-a77c-4687-a8b6-306635a9b4c0-18134622
To: <sip:97785551234@<Gateway ip>>;tag=E69CF0E4-1C0A
Date: Wed, 21 May 2014 19:31:30 GMT
Call-ID: 80ed5a80-37c1ff12-9141-1e32a8c0@<CUCM ip>
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-15.2.4.M5
Reason: Q.850;cause=127
Content-Length: 0

006473: May 21 12:32:40 PDT: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:97785551234@<Gateway ip>:5060 SIP/2.0
Via: SIP/2.0/TCP <CUCM ip>:5060;branch=z9hG4bK2264d597b4bba
From: "Test" <sip:5555@<CUCM ip>>;tag=852701~3fecf685-a77c-4687-a8b6-306635a9b4c0-18134622
To: <sip:97785551234@<Gateway ip>>;tag=E69CF0E4-1C0A
Date: Wed, 21 May 2014 19:31:30 GMT
Call-ID: 80ed5a80-37c1ff12-9141-1e32a8c0@<CUCM ip>
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0

Brian Meade · ‎05-21-2014

So looks like the problem is on the CUCM side not responding to the 183 Session Progress. Try changing the SIP Profile on the SIP Trunk to have SIP Rel1XX Options set to "Send Prack if 1XX contains SDP".

Edit: The trunk has to be reset after the change so that needs to be done after hours.

Cameron Whitehead · ‎05-21-2014

Thanks a ton Brian. I have not been using SIP gateways all that long, all my previous positions we used h323 so good to start learning a bit more about the SIP ones.

Call stuck in "Call Proceed"