Re: Outgoing calls to ITSP (BT) via CUBE and SIP trunk doesn't work

pajacek · ‎10-22-2020

Hello All,

Because BT upgrades of thier SIP Platform, I needed to reconfigure my CUBE. Right now I still in testing phase, because it doesn't work. Trunk from CUBE to BT SIP Platform is registered, but I cannot make outgoing calls. BT SIP Platform sends to me SIP 491 Request Pending message.

When I back with CUBE configuration to old BT platform, calls works fine, and I recieve SIP 183 Session Progress message instead SIP 491 Request Pending.

In attachments you can find:

- success SIP call flow to old BT Platform,

- failed SIP call flow to new BT platform

And here you are debug of failed call from CUBE (real DN numbers are changed).

_______________________________________

*Oct 22 00:44:09.200: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:0048602602602@10.152.17.6:5060 SIP/2.0
Via: SIP/2.0/UDP 10.152.243.12:5060;branch=z9hG4bK70e96d68dc7814
From: "Jack" <sip:442076441234@10.152.243.12>;tag=62967327~f9be96dd-55e1-494e-b666-13aeaade7f41-44017607
To: <sip:0048602602602@10.152.17.6>
Date: Thu, 22 Oct 2020 00:43:51 GMT
Call-ID: a61ec300-f901d5c7-6c6b8c-cf3980a@10.152.243.12
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Session-ID: 8bce30cfbb390640742ff8096a4b2ba0;remote=00000000000000000000000000000000
Cisco-Guid: 2787033856-0000065536-0000025414-0217290762
Session-Expires: 14400
Diversion: <sip:48602602602@10.152.243.12>;reason=unknown;privacy=off;screen=yes
P-Asserted-Identity: "Jack" <sip:442076441234@10.152.243.12>
Remote-Party-ID: "Jack" <sip:442076441234@10.152.243.12>;party=calling;screen=yes;privacy=off
Contact: <sip:442076441234@10.152.243.12:5060>
Max-Forwards: 70
Content-Type: application/sdp
Content-Length: 204

v=0
o=CiscoSystemsCCM-SIP 62967327 1 IN IP4 10.152.243.12
s=SIP Call
c=IN IP4 10.152.17.6
t=0 0
m=audio 19302 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

*Oct 22 00:44:09.224: //54/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.152.243.12:5060;branch=z9hG4bK70e96d68dc7814
From: "Jack" <sip:442076441234@10.152.243.12>;tag=62967327~f9be96dd-55e1-494e-b666-13aeaade7f41-44017607
To: <sip:0048602602602@10.152.17.6>
Date: Thu, 22 Oct 2020 00:44:09 GMT
Call-ID: a61ec300-f901d5c7-6c6b8c-cf3980a@10.152.243.12
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0

*Oct 22 00:44:09.228: //55/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0048602602602@uk.networks.com:5060 SIP/2.0
Via: SIP/2.0/UDP 109.231.203.7:5060;branch=z9hG4bK15CD6
From: <sip:442076441234@uk.networks.com>;tag=E32D0-1BDB
To: <sip:0048602602602@uk.networks.com>
Date: Thu, 22 Oct 2020 00:44:09 GMT
Call-ID: 87C8A7E1-133611EB-804D90D9-85413BB6@109.231.203.7
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2787033856-0000065536-0000025414-0217290762
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Timestamp: 1603327449
Contact: <sip:442076441234@109.231.203.7:5060>
Expires: 300
Allow-Events: telephone-event
Max-Forwards: 69
Diversion: <sip:442035420430@uk.networks.com>;privacy=off;reason=unknown;screen=yes
P-Asserted-Identity: "Jack" <sip:442076441234@109.231.203.7>

Session-Expires: 14400
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 206

v=0
o=CiscoSystemsCCM-SIP 62967327 1 IN IP4 10.152.243.12
s=SIP Call
c=IN IP4 109.231.203.7
t=0 0
m=audio 19346 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

*Oct 22 00:44:09.232: //55/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 109.231.203.7:5060;branch=z9hG4bK15CD6
From: <sip:442076441234@uk.networks.com>;tag=E32D0-1BDB
To: <sip:0048602602602@uk.networks.com>
Call-ID: 87C8A7E1-133611EB-804D90D9-85413BB6@109.231.203.7
CSeq: 101 INVITE
Timestamp: 1603327449
Content-Length: 0

*Oct 22 00:44:09.256: //55/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 109.231.203.7:5060;branch=z9hG4bK15CD6
WWW-Authenticate: DIGEST realm="uk.networks.com",qop="auth",nonce="BroadWorksXkgk3r80sTepz378BW",algorithm=MD5
To: <sip:0048602602602@uk.networks.com>;tag=3812316231-233913900
From: <sip:442076441234@uk.networks.com>;tag=E32D0-1BDB
Call-ID: 87C8A7E1-133611EB-804D90D9-85413BB6@109.231.203.7
CSeq: 101 INVITE
Contact: <sip:0048602602602@62.7.201.137:5060>

Content-Length: 0

*Oct 22 00:44:09.260: //55/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:0048602602602@uk.networks.com:5060 SIP/2.0
Via: SIP/2.0/UDP 109.231.203.7:5060;branch=z9hG4bK15CD6
From: "Jack" <sip:442076441234@uk.networks.com>;tag=E32D0-1BDB
To: <sip:0048602602602@uk.networks.com>;tag=3812316231-233913900
Date: Thu, 22 Oct 2020 00:44:09 GMT
Call-ID: 87C8A7E1-133611EB-804D90D9-85413BB6@109.231.203.7
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0

*Oct 22 00:44:09.260: //55/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:0048602602602@uk.networks.com:5060 SIP/2.0
Via: SIP/2.0/UDP 109.231.203.7:5060;branch=z9hG4bK16222B
From: <sip:442076441234@uk.networks.com>;tag=E32D0-1BDB
To: <sip:0048602602602@uk.networks.com>
Date: Thu, 22 Oct 2020 00:44:09 GMT
Call-ID: 87C8A7E1-133611EB-804D90D9-85413BB6@109.231.203.7
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE: 1800
Cisco-Guid: 2787033856-0000065536-0000025414-0217290762
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Timestamp: 1603327449
Contact: <sip:442076441234@109.231.203.7:5060>
Expires: 300
Allow-Events: telephone-event
Authorization: Digest username="442035420430",realm="uk.networks.com",uri="sip:0048602602602@sipt-dynamic-bslnws09.yourwhc.co.uk:5060",response="4c767a9cfe987302659c566a08277330",nonce="BroadWorksXkgk3r80sTepz378BW",cnonce="AE8AA0C4",qop=auth,algorithm=MD5,nc=00000001

Max-Forwards: 69
Diversion: <sip:442035420430@uk.networks.com>;privacy=off;reason=unknown;screen=yes
P-Asserted-Identity: "Jack" <sip:442076441234@109.231.203.7>
Session-Expires: 14400
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 206

v=0
o=CiscoSystemsCCM-SIP 62967327 1 IN IP4 10.152.243.12
s=SIP Call
c=IN IP4 109.231.203.7
t=0 0
m=audio 19346 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

*Oct 22 00:44:09.268: //55/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 109.231.203.7:5060;branch=z9hG4bK16222B
From: <sip:442076441234@uk.networks.com>;tag=E32D0-1BDB
To: <sip:0048602602602@uk.networks.com>
Call-ID: 87C8A7E1-133611EB-804D90D9-85413BB6@109.231.203.7
CSeq: 102 INVITE
Timestamp: 1603327449
Content-Length: 0

*Oct 22 00:44:09.268: //55/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 491 Request Pending
Via: SIP/2.0/UDP 109.231.203.7:5060;branch=z9hG4bK16222B
To: <sip:0048602602602@uk.networks.com>
From: <sip:442076441234@uk.networks.com>;tag=E32D0-1BDB
Call-ID: 87C8A7E1-133611EB-804D90D9-85413BB6@109.231.203.7
CSeq: 102 INVITE

Allow: PUBLISH,UPDATE,PRACK,SUBSCRIBE,REFER,INFO,NOTIFY,REGISTER,OPTIONS,BYE,INVITE,ACK,CANCEL
Content-Length: 0

*Oct 22 00:44:09.280: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:0048602602602@uk.networks.com:5060 SIP/2.0
Via: SIP/2.0/UDP 109.231.203.7:5060;branch=z9hG4bK16222B
From: "Jack" <sip:442076441234@uk.networks.com>;tag=E32D0-1BDB
To: <sip:0048602602602@uk.networks.com>
Date: Thu, 22 Oct 2020 00:44:09 GMT
Call-ID: 87C8A7E1-133611EB-804D90D9-85413BB6@109.231.203.7
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Content-Length: 0

*Oct 22 00:44:09.280: //54/A61EC3000000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 500 Internal Server Error
Via: SIP/2.0/UDP 10.152.243.12:5060;branch=z9hG4bK70e96d68dc7814
From: "Jack" <sip:442076441234@10.152.243.12>;tag=62967327~f9be96dd-55e1-494e-b666-13aeaade7f41-44017607
To: <sip:0048602602602@10.152.17.6>;tag=E3308-E31
Date: Thu, 22 Oct 2020 00:44:09 GMT
Call-ID: a61ec300-f901d5c7-6c6b8c-cf3980a@10.152.243.12
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=127
Content-Length: 0

*Oct 22 00:44:09.288: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:0048602602602@10.152.17.6:5060 SIP/2.0
Via: SIP/2.0/UDP 10.152.243.12:5060;branch=z9hG4bK70e96d68dc7814

From: "Jack" <sip:442076441234@10.152.243.12>;tag=62967327~f9be96dd-55e1-494e-b666-13aeaade7f41-44017607
To: <sip:0048602602602@10.152.17.6>;tag=E3308-E31
Date: Thu, 22 Oct 2020 00:43:51 GMT
Call-ID: a61ec300-f901d5c7-6c6b8c-cf3980a@10.152.243.12
User-Agent: Cisco-CUCM11.5
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence
Content-Length: 0

_______________________________________

If someone could help me will be great!

Please let me know, if you've got any suggestion..

Thank you!

Mohammed al Baqari · ‎10-22-2020

Hi

Try to enable 100rel in your cube and on cucm sip trunk enable prack
response for 183 messages.

dial-peer voice XXX voip
voice-class sip rel1xx require 100rel

On CUCM SIP profile applied to your CUBE. Change this parameter: Send PRACK
if 1XX contains SDP

**** please remember to rate useful posts

pajacek · ‎10-25-2020

Hello Mohammed al Baqari,

Thank you for help... Unfortunately your solution cannot solve this issue. PRACK is sent when 18X SIP message is recieved. In this case is recieved 491 SIP message.

Regards,
Jacek

pajacek · ‎10-29-2020

Hello All,

Issue from this topic is still not solved. But... I've got one more question.

As a reminder what's the situation. There is a SIP trunk between our CUBE and ITSP (BT). Trunk is registered, which is confirmed by the command sh sip-ua register status.. But we cannot make outgoing calls. ITSP sends back SIP 491 Request Pending and finish process (please look at debug above).

I still try to investigate this issue, and... ITSP informs me about out-of-sequence incoming SIP signaling by their site, so this is a reason why process is ended.

But.. looking at SIP debug above... and I even did SIP packet capture from CUBE outgoing interface... in both traces I see correct sequence of SIP process... but ITSP sends me different. Please look at attachments to compare.

Is possible situation like that??? From CUBE perspective whole process regarding SIP outgoing and incoming signaling is in proper order, and there is a small difference on the other end of trunk??

Best Regards,

Jacek