Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
5088
Views
0
Helpful
15
Replies

CME, SIP-UA, IOS upgrade problem.

Go to solution
Utair Corporation
Level 3
Level 3

‎02-17-2013 08:26 PM - edited ‎03-16-2019 03:46 PM

Hi.

There is a 2811 ISR router with CME 7.0 onboard.

It has SIP-UA based trunk to service provider.

It has 12.4T IOS and all working fine. Since we need to add support for 6921 phones i have upgraded it with 15.1 IOS.

I turned "Toll fraud prevent" feature off.

But sip-ua trunk stopped working. I've debugged with debug ccsip messages, but it seems that they are identical, but appears like remote party do not receive our TRYING and RINGING messages and keep spamming with INVITEs.

Problems with inbound calls only.

Configs almost identical except for tftp-bindings and toll fraud commands.

Here is SIP log from 12.4T:

*Feb 17 05:41:46.189: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:73952486173@172.24.4.14:5060 SIP/2.0
Via:SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-861278493-511748539-1361079706169-
From:<sip:73452298489@172.30.252.1;user=phone>;tag=511748539-1361079706169-
To:"OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Call-ID:BW1441461691702131647371913@172.30.252.1
CSeq:861278493 INVITE
Contact:<sip:172.30.252.1:5060>
Remote-Party-ID:<sip:73452298489@172.30.252.1;user=phone>;screen=yes;party=calling;privacy=off;id-type=subscriber
RPID-Privacy:party=calling;id-type=subscriber;privacy=off
Proxy-Require:privacy
Supported:100rel,timer
Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept:multipart/mixed,application/media_control+xml,application/sdp
Min-SE:60
Max-Forwards:10
Content-Type:application/sdp
Content-Length:366
v=0
o=BroadWorks 92296329 1 IN IP4 172.30.253.225
s=-
c=IN IP4 172.30.253.225
t=0 0
m=audio 19284 RTP/AVP 8 0 18 100 101
c=IN IP4 172.30.253.225
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=bsoft: 1 image udptl t38
*Feb 17 05:41:46.217: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-861278493-511748539-1361079706169-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=511748539-1361079706169-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Date: Sun, 17 Feb 2013 05:41:46 GMT
Call-ID: BW1441461691702131647371913@172.30.252.1
CSeq: 861278493 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
*Feb 17 05:41:46.261: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-861278493-511748539-1361079706169-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=511748539-1361079706169-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=5D510-1AB1
Date: Sun, 17 Feb 2013 05:41:46 GMT
Call-ID: BW1441461691702131647371913@172.30.252.1
CSeq: 861278493 INVITE
Require: 100rel
RSeq: 6130
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:73952486173@172.24.4.14:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
*Feb 17 05:41:46.269: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
PRACK sip:73952486173@172.24.4.14:5060 SIP/2.0
Via:SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-861278494-511748539-1361079706169-
From:<sip:73452298489@172.30.252.1;user=phone>;tag=511748539-1361079706169-
To:"OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=5D510-1AB1
Call-ID:BW1441461691702131647371913@172.30.252.1
CSeq:861278494 PRACK
RAck:6130 861278493 INVITE
Max-Forwards:10
Content-Length:0
*Feb 17 05:41:46.277: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
irkutsk-2811#SIP/2.0 200 OK
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-861278494-511748539-1361079706169-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=511748539-1361079706169-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=5D510-1AB1
Date: Sun, 17 Feb 2013 05:41:46 GMT
Call-ID: BW1441461691702131647371913@172.30.252.1
Server: Cisco-SIPGateway/IOS-12.x
CSeq: 861278494 PRACK
Content-Length: 0

And here is SIP log from 15.1:

.Feb 15 10:20:38.905: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:73952486173@172.24.4.14:5060 SIP/2.0
Via:SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From:<sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To:"OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Call-ID:BW192038902150213-125121960@172.30.252.1
CSeq:783244860 INVITE
Contact:<sip:172.30.252.1:5060>
Remote-Party-ID:<sip:73452298489@172.30.252.1;user=phone>;screen=yes;party=calling;privacy=off;id-type=subscriber
RPID-Privacy:party=calling;id-type=subscriber;privacy=off
Proxy-Require:privacy
Supported:100rel,timer
Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept:multipart/mixed,application/media_control+xml,application/sdp
Min-SE:60
Max-Forwards:10
Content-Type:application/sdp
Content-Length:366
v=0
o=BroadWorks 91986713 1 IN IP4 172.30.253.225
s=-
c=IN IP4 172.30.253.225
t=0 0
m=audio 17622 RTP/AVP 8 0 18 100 101
c=IN IP4 172.30.253.225
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=bsoft: 1 image udptl t38
.Feb 15 10:20:38.953: //12841/2DBA559C8E5D/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Date: Fri, 15 Feb 2013 10:20:38 GMT
Call-ID: BW192038902150213-125121960@172.30.252.1
CSeq: 783244860 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
.Feb 15 10:20:38.965: //12841/2DBA559C8E5D/SIP/Msg/ccsipDisplayMsg:
Sent:
irkutsk-2811#SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=55E926C-135E
Date: Fri, 15 Feb 2013 10:20:38 GMT
Call-ID: BW192038902150213-125121960@172.30.252.1
CSeq: 783244860 INVITE
Require: 100rel
RSeq: 8755
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:73952486173@172.24.4.14:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
.Feb 15 10:20:39.409: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:73952486173@172.24.4.14:5060 SIP/2.0
Via:SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From:<sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To:"OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Call-ID:BW192038902150213-125121960@172.30.252.1
CSeq:783244860 INVITE
Contact:<sip:172.30.252.1:5060>
Remote-Party-ID:<sip:73452298489@172.30.252.1;user=phone>;screen=yes;party=calling;privacy=off;id-type=subscriber
RPID-Privacy:party=calling;id-type=subscriber;privacy=off
Proxy-Require:privacy
Supported:100rel,timer
Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept:multipart/mixed,application/media_control+xml,application/sdp
Min-SE:60
Max-Forwards:10
Content-Type:application/sdp
Content-Length:366
v=0
o=BroadWorks 91986713 1 IN IP4 172.30.253.225
s=-
c=IN IP4 172.30.253.225
t=0 0
m=audio 17622 RTP/AVP 8 0 18 100 101
c=IN IP4 172.30.253.225
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=bsoft: 1 image udptl t38
.Feb 15 10:20:39.413: //12841/2DBA559C8E5D/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=55E926C-135E
Date: Fri, 15 Feb 2013 10:20:39 GMT
Call-ID: BW192038902150213-125121960@172.30.252.1
CSeq: 783244860 INVITE
Require: 100rel
RSeq: 8755
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:73952486173@172.24.4.14:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
.Feb 15 10:20:39.461: //12841/2DBA559C8E5D/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=55E926C-135E
Date: Fri, 15 Feb 2013 10:20:39 GMT
Call-ID: BW192038902150213-125121960@172.30.252.1
CSeq: 783244860 INVITE
Require: 100rel
RSeq: 8755
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
irkutsk-2811#SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:73952486173@172.24.4.14:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
.Feb 15 10:20:40.409: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:73952486173@172.24.4.14:5060 SIP/2.0
Via:SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From:<sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To:"OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Call-ID:BW192038902150213-125121960@172.30.252.1
CSeq:783244860 INVITE
Contact:<sip:172.30.252.1:5060>
Remote-Party-ID:<sip:73452298489@172.30.252.1;user=phone>;screen=yes;party=calling;privacy=off;id-type=subscriber
RPID-Privacy:party=calling;id-type=subscriber;privacy=off
Proxy-Require:privacy
Supported:100rel,timer
Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept:multipart/mixed,application/media_control+xml,application/sdp
Min-SE:60
Max-Forwards:10
Content-Type:application/sdp
Content-Length:366
v=0
o=BroadWorks 91986713 1 IN IP4 172.30.253.225
s=-
c=IN IP4 172.30.253.225
t=0 0
m=audio 17622 RTP/AVP 8 0 18 100 101
c=IN IP4 172.30.253.225
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=bsoft: 1 image udptl t38
.Feb 15 10:20:40.417: //12841/2DBA559C8E5D/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=55E926C-135E
Date: Fri, 15 Feb 2013 10:20:40 GMT
Call-ID: BW192038902150213-125121960@172.30.252.1
CSeq: 783244860 INVITE
Require: 100rel
RSeq: 8755
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:73952486173@172.24.4.14:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
.Feb 15 10:20:40.461: //12841/2DBA559C8E5D/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=55E926C-135E
Date: Fri, 15 Feb 2013 10:20:40 GMT
Call-ID: BW192038902150213-125121960@172.30.252.1
CSeq: 783244860 INVITE
Require: 100rel
RSeq: 8755
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
irkutsk-2811#SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:73952486173@172.24.4.14:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
irkutsk-2811#
.Feb 15 10:20:42.413: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:73952486173@172.24.4.14:5060 SIP/2.0
Via:SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From:<sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To:"OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Call-ID:BW192038902150213-125121960@172.30.252.1
CSeq:783244860 INVITE
Contact:<sip:172.30.252.1:5060>
Remote-Party-ID:<sip:73452298489@172.30.252.1;user=phone>;screen=yes;party=calling;privacy=off;id-type=subscriber
RPID-Privacy:party=calling;id-type=subscriber;privacy=off
Proxy-Require:privacy
Supported:100rel,timer
Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept:multipart/mixed,application/media_control+xml,application/sdp
Min-SE:60
Max-Forwards:10
Content-Type:application/sdp
Content-Length:366
v=0
o=BroadWorks 91986713 1 IN IP4 172.30.253.225
s=-
c=IN IP4 172.30.253.225
t=0 0
m=audio 17622 RTP/AVP 8 0 18 100 101
c=IN IP4 172.30.253.225
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=bsoft: 1 image udptl t38
.Feb 15 10:20:42.417: //12841/2DBA559C8E5D/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=55E926C-135E
Date: Fri, 15 Feb 2013 10:20:42 GMT
Call-ID: BW192038902150213-125121960@172.30.252.1
CSeq: 783244860 INVITE
Require: 100rel
RSeq: 8755
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:73952486173@172.24.4.14:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
.Feb 15 10:20:42.485: //12841/2DBA559C8E5D/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783244860-1321215410-1360923638902-
From: <sip:73452298489@172.30.252.1;user=phone>;tag=1321215410-1360923638902-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=55E926C-135E
Date: Fri, 15 Feb 2013 10:20:42 GMT
Call-ID: BW192038902150213-125121960@172.30.252.1
CSeq: 783244860 INVITE
Require: 100rel
RSeq: 8755
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
irkutsk-2811#SUBSCRIBE, NOTIFY, INFO, REGISTER
Allow-Events: telephone-event
Contact: <sip:73952486173@172.24.4.14:5060>
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
irkutsk-2811#
.Feb 15 10:20:44.917: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:73952486173@172.24.4.14:5060 SIP/2.0
Via:SIP/2.0/UDP 172.30.252.17;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783247866-1489923946-1360923644915-
From:<sip:73452298489@172.30.252.17;user=phone>;tag=1489923946-1360923644915-
To:"OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Call-ID:BW192044915150213-457531721@172.30.252.17
CSeq:783247866 INVITE
Contact:<sip:172.30.252.17:5060>
Remote-Party-ID:<sip:73452298489@172.30.252.17;user=phone>;screen=yes;party=calling;privacy=off;id-type=subscriber
RPID-Privacy:party=calling;id-type=subscriber;privacy=off
Proxy-Require:privacy
Supported:100rel,timer
Allow:ACK,BYE,CANCEL,INFO,INVITE,OPTIONS,PRACK,REFER,NOTIFY
Accept:multipart/mixed,application/media_control+xml,application/sdp
Min-SE:60
Max-Forwards:10
Content-Type:application/sdp
Content-Length:365
v=0
o=BroadWorks 4063973 1 IN IP4 172.30.253.225
s=-
c=IN IP4 172.30.253.225
t=0 0
m=audio 17622 RTP/AVP 8 0 18 100 101
c=IN IP4 172.30.253.225
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=yes
a=rtpmap:100 X-NSE/8000
a=fmtp:100 192-194
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=bsoft: 1 image udptl t38
.Feb 15 10:20:44.953: //12844/314FB40F8E66/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.30.252.17;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783247866-1489923946-1360923644915-
From: <sip:73452298489@172.30.252.17;user=phone>;tag=1489923946-1360923644915-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>
Date: Fri, 15 Feb 2013 10:20:44 GMT
Call-ID: BW192044915150213-457531721@172.30.252.17
CSeq: 783247866 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
.Feb 15 10:20:44.953: //12844/314FB40F8E66/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 486 Busy here
Via: SIP/2.0/UDP 172.30.252.17;branch=z9hG4bK-BroadWorks.172.30.252.1-172.24.4.14V5060-0-783247866-1489923946-1360923644915-
From: <sip:73452298489@172.30.252.17;user=phone>;tag=1489923946-1360923644915-
To: "OAO Aviakompaniya UTair"<sip:73952486173@irk.voice.dsi.ru>;tag=55EA9D0-975
Date: Fri, 15 Feb 2013 10:20:44 GMT
Call-ID: BW192044915150213-457531721@172.30.252.17
CSeq: 783247866 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=17
Content-Length: 0

I can't tell any difference in initial replys, but in latter case it seems like remote party does not receive any of them.

Pinging remote party IPs, telnetting them to 5060 ports works without any problem.

Don't know what to do..

Here is cut down config:

voice service voip
 ip address trusted list
  ipv4 10.0.0.0 255.0.0.0
  ipv4 172.16.0.0 255.240.0.0
 allow-connections h323 to h323
 allow-connections h323 to sip
 allow-connections sip to h323
 allow-connections sip to sip
 no supplementary-service sip moved-temporarily
 no supplementary-service sip refer
 fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw
 h323
 sip
  transport switch udp tcp
  localhost dns:irk.voice.dsi.ru
!
!
interface FastEthernet0/1.10
 description DSI-SIP
 encapsulation dot1Q 10
 ip address 172.24.4.14 255.255.255.0
!
ip route 172.24.0.0 255.254.0.0 172.24.4.254 name DSI-4
ip route 172.30.0.0 255.255.0.0 172.24.4.254 name DSI-3
ip route 172.31.0.0 255.255.0.0 172.24.4.254 name DSI-5
!
!
dial-peer voice 3 voip
 translation-profile incoming 1
 session protocol sipv2
 session target sip-server
 incoming called-number 73952.T
 voice-class codec 752
 dtmf-relay rtp-nte
!
!
sip-ua
 credentials username username password 7 password realm BroadWorks
 keepalive target dns:as1.voice.dsi.ru
 keepalive target dns:as2.voice.dsi.ru secondary
 authentication username username password 7 password
 no remote-party-id
 retry invite 2
 retry response 3
 retry bye 3
 retry prack 6
 retry register 3
 timers expires 300000
 timers connection aging 300
 sip-server dns:irk.voice.dsi.ru
 connection-reuse
 host-registrar

Labels:
0 Helpful
2 Accepted Solutions

Accepted Solutions

Go to solution
Tim Smith
Level 4
Level 4
In response to Utair Corporation

‎02-19-2013 03:09 AM

Interesting!

I read that via only needs port if it is not default.

I didn't see anything on source ports except for this..

http://www.ietf.org/rfc/rfc3581.txt

That seems to say that with UDP, it is expected that you would reply to the Via port (in broadsoft case, not specified, so assuming 5060) - so it seems 12.4 would be in line with this.

Did you check bug toolkit? It seems like something that would appear. Or maybe as a changed behaviour in release notes?

There is the connection-reuse command. My understanding is this one should ensure the CUBE sends the replies from source port 5060. I cant find any docco about what it does to destination. I think this command is on in both your configs, as source is 5060. But it may also be interesting to see what wireshark says with this off.

i.e. if it wasn't re-using a connection, maybe it would just send the reply straight to 5060.

Sorry that probably doesn't really help too much.

Cheers,

Tim.

View solution in original post

0 Helpful

Go to solution
semyon.taskin
Level 1
Level 1
In response to Utair Corporation

‎02-19-2013 02:07 PM

I would think you do need to have connection-reuse under sip-ua. I have a client with Broadworks who uses 2900 series with 15.2 with connection-reuse. (it didnt work without connection-reuse and invites were ignored by provider - similar to what you see)

!

voice service voip

address-hiding

dtmf-interworking rtp-nte

allow-connections sip to sip

no supplementary-service sip moved-temporarily

no supplementary-service sip refer

sip

  localhost dns:siptrunk.provider

!

sip-ua

no remote-party-id

retry invite 2

sip-server dns:siptrunk.provider

connection-reuse

!

On 15.1 I would try going connection-reuse - no connection-reuse - connection-reuse. If that doesnt help power cycle the router with connection-reuse on (make sure you got your config saved )

Semyon

View solution in original post

0 Helpful
15 Replies 15

Go to solution
Tim Smith
Level 4
Level 4

‎02-17-2013 09:15 PM

Hey mate,

I think if toll fraud prevention was the issue, you could see it kicking in by debugging ccapi voip inout

But you are receiving the INVITE from the far end, so I dont think that is the issue.

I've seen fragmentation problems with UDP

Your SIP message looks the same, so that shouldn't be the change

But perhaps the way IOS is handling the packet could be an issue

Exactly what IOS are you running?

Check out this article (search for IP CEF) and you will see a couple of recommendations.

https://supportforums.cisco.com/thread/2154873

I think in most of these cases it is a good idea to open a ticket with the carrier as well. Ask them to check their logs and see if they are receiving your messages (and responding)

External wireshark cap is always nice as well, if you havent tried this.

Cheers,

Tim

0 Helpful

Go to solution
Utair Corporation
Level 3
Level 3
In response to Tim Smith

‎02-17-2013 09:30 PM

First it was c2800nm-adventerprisek9_ivs-mz.151-4.M4.bin

Next i tried c2800nm-adventerprisek9_ivs-mz.151-4.M5.bin

Used capture on router itself, there were packets generated by CPU at least.

But perhaps the way IOS is handling the packet could be an issue
Exactly what IOS are you running?
0 Helpful

Go to solution
Tagir Temirgaliyev
Spotlight
Spotlight
In response to Utair Corporation

‎02-17-2013 09:52 PM

Hi, try this

voice service voip

ip address trusted list

  ipv4 0.0.0.0 0.0.0.0

allow-connections h323 to h323

allow-connections h323 to sip

allow-connections sip to h323

allow-connections sip to sip

fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none

h323

  call start slow

  h245 passthru all

sip

  bind control source-interface GigabitEthernet0/0.62

  bind media source-interface GigabitEthernet0/0.62

0 Helpful

Go to solution
Utair Corporation
Level 3
Level 3
In response to Tagir Temirgaliyev

‎02-17-2013 11:49 PM 

ttemirgaliyev wrote:
Hi, try this
voice service voip
 ip address trusted list
  ipv4 0.0.0.0 0.0.0.0

I did, also tried disabling at all, by the book.

Did not help. Also, router would not answer at first place.

0 Helpful

Go to solution
Tim Smith
Level 4
Level 4
In response to Utair Corporation

‎02-17-2013 10:02 PM

I think I'd be tempted to just try the work around:

configure "no ip cef" in the router, see if it will help

configure " ip virtual-reassembly" on the interface which will have the incoming SIP INVITE

If that works you know it is a fragmentation problem.

I think in our case we upgraded to 15.2.1 T2.

Sorry I dont have bug ID or more details.

Cheers,

Tim.

0 Helpful

Go to solution
Utair Corporation
Level 3
Level 3
In response to Tim Smith

‎02-17-2013 11:50 PM 

Tim Smith wrote:
I think I'd be tempted to just try the work around:
configure "no ip cef" in the router, see if it will help
configure " ip virtual-reassembly" on the interface which will have the incoming SIP INVITE
If that works you know it is a fragmentation problem.
I think in our case we upgraded to 15.2.1 T2. 
Sorry I dont have bug ID or more details.
Cheers,
Tim.

I will, just need to wait people go home.

0 Helpful

Go to solution
Utair Corporation
Level 3
Level 3
In response to Utair Corporation

‎02-18-2013 07:25 PM

Playing with ip cef anf virtual reassembly did not hepl and actually was not the case.

After some wiresharking and swapping IOSes i've found the reason:

Here is message flow in 12.4T IOS:

Service Provider -> Our router

INVITE: UDP src port: random X dst port: 5060

Our Router->Service Provider

Trying: UDP src port: 5060 dst port: 5060

Ringing: UDP src port: 5060 dst port: 5060

Here is message flow in 15.1 IOS:

Service Provider -> Our router

INVITE: UDP src port: random X dst port: 5060

Our Router->Service Provider

Trying: UDP src port: 5060 dst port: X

Ringing: UDP src port: 5060 dst port: X

In 15.1 IOS, router uses the same socket for sending replies.

SP support team claims that their Boradworks device does not support this behavior and expects replies on 5060 port.

Is there an option to switch to old behavior in 15.1 IOS?

0 Helpful

Go to solution
Utair Corporation
Level 3
Level 3
In response to Utair Corporation

‎02-18-2013 08:27 PM

Another difference in behavior found:

Broadworks switch sends INVITE requests with VIA header without port:

INVITE sip:73952486173@172.24.4.14:5060 SIP/2.0

Via:SIP/2.0/UDP 172.30.252.1;branch=z9hG4bK-

Comparing with Cisco's INVITE:

INVITE sip:74113698212@irk.voice.dsi.ru:5060 SIP/2.0

Via: SIP/2.0/UDP 172.24.4.14:5060;branch=z9hG4bK18EA255C

there is port field.

Wich port should be used for sending 100 replies? Which IOS is more correct?

I was trying to read SIP RFC, but they are not specific on that case.

0 Helpful

Go to solution
Tim Smith
Level 4
Level 4
In response to Utair Corporation

‎02-19-2013 03:09 AM

Interesting!

I read that via only needs port if it is not default.

I didn't see anything on source ports except for this..

http://www.ietf.org/rfc/rfc3581.txt

That seems to say that with UDP, it is expected that you would reply to the Via port (in broadsoft case, not specified, so assuming 5060) - so it seems 12.4 would be in line with this.

Did you check bug toolkit? It seems like something that would appear. Or maybe as a changed behaviour in release notes?

There is the connection-reuse command. My understanding is this one should ensure the CUBE sends the replies from source port 5060. I cant find any docco about what it does to destination. I think this command is on in both your configs, as source is 5060. But it may also be interesting to see what wireshark says with this off.

i.e. if it wasn't re-using a connection, maybe it would just send the reply straight to 5060.

Sorry that probably doesn't really help too much.

Cheers,

Tim.

0 Helpful

Go to solution
Utair Corporation
Level 3
Level 3
In response to Tim Smith

‎02-19-2013 03:54 AM

Do you propose to issue:

sip-ua

  no connection-reuse

?

I tried searching Bug toolkit, but did not find anythig usefull.

0 Helpful

Go to solution
Utair Corporation
Level 3
Level 3
In response to Utair Corporation

‎02-19-2013 04:01 AM

playing with connection-reuse on 12.4T did not change anything, at least broadworks can see messages.

0 Helpful

Go to solution
semyon.taskin
Level 1
Level 1
In response to Utair Corporation

‎02-19-2013 02:07 PM

I would think you do need to have connection-reuse under sip-ua. I have a client with Broadworks who uses 2900 series with 15.2 with connection-reuse. (it didnt work without connection-reuse and invites were ignored by provider - similar to what you see)

!

voice service voip

address-hiding

dtmf-interworking rtp-nte

allow-connections sip to sip

no supplementary-service sip moved-temporarily

no supplementary-service sip refer

sip

  localhost dns:siptrunk.provider

!

sip-ua

no remote-party-id

retry invite 2

sip-server dns:siptrunk.provider

connection-reuse

!

On 15.1 I would try going connection-reuse - no connection-reuse - connection-reuse. If that doesnt help power cycle the router with connection-reuse on (make sure you got your config saved )

Semyon

0 Helpful

Go to solution
Utair Corporation
Level 3
Level 3
In response to semyon.taskin

‎02-20-2013 02:14 AM

connection-reuse via-port helped

0 Helpful

Go to solution
Tim Smith
Level 4
Level 4
In response to Utair Corporation

‎02-20-2013 12:20 PM

Hey good stuff.

Where did you get the via-port part? Just from cli or did you find some more info on connection-reuse command?

Cheers,

Tim

Sent from Cisco Technical Support iPhone App

0 Helpful
Getting Started

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:

Customers Also Viewed These Support Documents