02-07-2017 08:28 AM - edited 03-17-2019 09:26 AM
We are in the midst of switching from one ISP to another. I received the router and need to put it in front of the UC520. My only problem is that inbound calls aren't working. I ran the logs and found the following error. Is there an easy way to fix this?
Thanks!
508123: Feb 6 21:27:39.083: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Via: SIP/2.0/UDP 67.205.74.187:5060;branch=z9hG4bK1b465d94;rport
From: "OTTAWA, ON" <sip:9051234444@67.205.74.187>;tag=as114d9064
To: <sip:4161234567@70.11.54.125>;tag=AC65B1A0-959
Date: Tue, 07 Feb 2017 02:27:39 GMT
Call-ID: 3c38a49e18e06e726292e7631d3d900f@67.205.74.187:5060
CSeq: 102 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=100
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
508124: Feb 6 21:27:39.183: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Via: SIP/2.0/UDP 67.205.74.187:5060;branch=z9hG4bK1b465d94;rport
From: "OTTAWA, ON" <sip:9051234444@67.205.74.187>;tag=as114d9064
To: <sip:4161234567@70.11.54.125>;tag=AC65B1A0-959
Call-ID: 3c38a49e18e06e726292e7631d3d900f@67.205.74.187:5060
CSeq: 102 INVITE
Reason: Q.850;cause=100
Content-Length: 0
508125: Feb 6 21:27:39.187: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:4161234567@70.11.54.125 SIP/2.0
Via: SIP/2.0/UDP 67.205.74.187:5060;branch=z9hG4bK1b465d94;rport
Max-Forwards: 70
From: "OTTAWA, ON" <sip:9051234444@67.205.74.187>;tag=as114d9064
To: <sip:4161234567@70.11.54.125>;tag=AC65B1A0-959
Contact: <sip:9051234444@67.205.74.187:5060>
Call-ID: 3c38a49e18e06e726292e7631d3d900f@67.205.74.187:5060
CSeq: 102 ACK
User-Agent: voip.ms
Content-Length: 0
508126: Feb 6 21:27:57.092: //130325/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:montreal2.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.13:5060;branch=z9hG4bK36BB411EF
From: <sip:montreal2.voip.ms>;tag=AC65F7F8-1C3B
To: <sip:montreal2.voip.ms>
Date: Tue, 07 Feb 2017 02:27:57 GMT
Call-ID: DEFAB269-EC1311E6-99CDB6DD-2E5C7378@montreal2.voip.ms
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:192.168.2.13:5060>
Content-Length: 0
508127: Feb 6 21:27:57.100: //130325/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.13:5060;branch=z9hG4bK36BB411EF;received=70.11.54.125;rport=60527
From: <sip:montreal2.voip.ms>;tag=AC65F7F8-1C3B
To: <sip:montreal2.voip.ms>;tag=as62836686
Call-ID: DEFAB269-EC1311E6-99CDB6DD-2E5C7378@montreal2.voip.ms
CSeq: 101 OPTIONS
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:67.205.74.187:5060>
Accept: application/sdp
Content-Length: 0
02-07-2017 11:05 AM
What version of IOS? Check the following link regarding toll fraud prevention.
http://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/112083-tollfraud-ios.html
Try adding the following commands to allow this host:
voice service voip
ip address trusted list
ipv4 67.205.74.187
Brandon
02-07-2017 11:43 AM
The IOS Version is 15.1(4)M5-ADV-IP-SERV-CRYPTO.
I checked the config and am already showing that command is entered. Should I be adding 70.11.54.125 to the trusted list?
voice service voip ip address trusted list ipv4 67.205.74.187
02-07-2017 11:55 AM
Yes, add this address as well. Is this the address of your ISP's edge router?
02-07-2017 11:58 AM
Thats the IP address of the router supplied to by the ISP (in front of UC520).
02-07-2017 12:25 PM
Reid,
From the logs it appears that the IP address
70.11.54.125)
that the inbound call is sent to doesnt not exist on the router.
Do you have this host IP configued on any of your interface? Are you using NAT? Pleas epost the full debug ccsip message
02-07-2017 01:15 PM
I have a Bell / Sagecom router hooked up to our new Fiber connection. Behind that I have our UC520 that we've used for years. I changed the internet configuration on the UC520 from pppoe to DCHP.
The full debug is below:
--------------------------show logging--------------------------
Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 10 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: disabled
Monitor logging: disabled
Buffer logging: level debugging, 66 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled
No active filter modules.
Trap logging: level informational, 9617 message lines logged
Logging Source-Interface: VRF Name:
Log Buffer (1000000 bytes):
010403: Feb 7 16:11:31.636: %SEC-6-IPACCESSLOGP: list 105 denied tcp 220.162.92.43(49132) -> 169.1.1.1(6789), 1 packet
010404: Feb 7 16:11:32.196: %SYS-5-CONFIG_I: Configured from console by Reid on vty0 (192.168.10.33)
010405: Feb 7 16:11:41.429: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:6131234567@70.11.54.125 SIP/2.0
Via: SIP/2.0/UDP 67.205.74.187:5060;branch=z9hG4bK3298a5e1;rport
Max-Forwards: 70
From: "OTTAWA, ON" <sip:6139876543@67.205.74.187>;tag=as10f6ebf2
To: <sip:6131234567@70.11.54.125>
Contact: <sip:6139876543@67.205.74.187:5060>
Call-ID: 3ec7e39d6a494433647ff4161b9dbc90@67.205.74.187:5060
CSeq: 102 INVITE
User-Agent: voip.ms
Date: Tue, 07 Feb 2017 21:12:15 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Remote-Party-ID: "OTTAWA, ON" <sip:6139876543@67.205.74.187>;party=calling;privacy=off;screen=no
Content-Type: application/sdp
Content-Length: 223
v=0
o=root 877975709 877975709 IN IP4 67.205.74.187
s=voip.ms
c=IN IP4 67.205.74.187
t=0 0
m=audio 19694 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv
010406: Feb 7 16:11:41.433: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Calling Number=6131234567, Called Number=6131234567, Peer Info Type=DIALPEER_INFO_SPEECH
010407: Feb 7 16:11:41.433: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Match Rule=DP_MATCH_DEST; Called Number=6131234567
010408: Feb 7 16:11:41.433: //-1/xxxxxxxxxxxx/DPM/dpMatchCore:
Dial String=6131234567, Expanded String=6131234567, Calling Number=6131234567T
Timeout=TRUE, Is Incoming=FALSE, Peer Info Type=DIALPEER_INFO_SPEECH
010409: Feb 7 16:11:41.433: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
OutboundSearch=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH, Current Peer(Tag=1800,Peer Info Type=DIALPEER_INFO_FAX)
010410: Feb 7 16:11:41.433: //-1/xxxxxxxxxxxx/DPM/MatchNextPeer:
Result=Success(0); Outgoing Dial-peer=20012 Is Matched
010411: Feb 7 16:11:41.433: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
Result=Success(0) after DP_MATCH_DEST
010412: Feb 7 16:11:41.433: //-1/xxxxxxxxxxxx/DPM/dpMatchSafModulePlugin:
dialstring=6131234567, saf_enabled=1, saf_dndb_lookup=1, dp_result=0
010413: Feb 7 16:11:41.433: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
Result=SUCCESS(0)
List of Matched Outgoing Dial-peer(s):
1: Dial-peer Tag=20012
010414: Feb 7 16:11:41.437: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Via: SIP/2.0/UDP 67.205.74.187:5060;branch=z9hG4bK3298a5e1;rport
From: "OTTAWA, ON" <sip:6139876543@67.205.74.187>;tag=as10f6ebf2
To: <sip:6131234567@70.11.54.125>;tag=3FC274C-14C2
Date: Tue, 07 Feb 2017 21:11:41 GMT
Call-ID: 3ec7e39d6a494433647ff4161b9dbc90@67.205.74.187:5060
CSeq: 102 INVITE
Allow-Events: telephone-event
Reason: Q.850;cause=100
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
010415: Feb 7 16:11:41.533: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Via: SIP/2.0/UDP 67.205.74.187:5060;branch=z9hG4bK3298a5e1;rport
From: "OTTAWA, ON" <sip:6139876543@67.205.74.187>;tag=as10f6ebf2
To: <sip:6131234567@70.11.54.125>;tag=3FC274C-14C2
Call-ID: 3ec7e39d6a494433647ff4161b9dbc90@67.205.74.187:5060
CSeq: 102 INVITE
Reason: Q.850;cause=100
Content-Length: 0
010416: Feb 7 16:11:41.537: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:6131234567@70.11.54.125 SIP/2.0
Via: SIP/2.0/UDP 67.205.74.187:5060;branch=z9hG4bK3298a5e1;rport
Max-Forwards: 70
From: "OTTAWA, ON" <sip:6139876543@67.205.74.187>;tag=as10f6ebf2
To: <sip:6131234567@70.11.54.125>;tag=3FC274C-14C2
Contact: <sip:6139876543@67.205.74.187:5060>
Call-ID: 3ec7e39d6a494433647ff4161b9dbc90@67.205.74.187:5060
CSeq: 102 ACK
User-Agent: voip.ms
Content-Length: 0
010417: Feb 7 16:11:59.033: %SEC-6-IPACCESSLOGP: list 105 denied udp 17.173.254.223(16387) -> 169.1.1.1(60025), 11 packets
010418: Feb 7 16:12:05.409: //3072/000000000000/SIP/Msg/ccsipDisplayMsg:
Sent:
OPTIONS sip:montreal2.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.13:5060;branch=z9hG4bK143B9FE
From: <sip:montreal2.voip.ms>;tag=3FC84F4-156A
To: <sip:montreal2.voip.ms>
Date: Tue, 07 Feb 2017 21:12:05 GMT
Call-ID: E94FCED8-ECB011E6-841BEC0A-4794616F@montreal2.voip.ms
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
CSeq: 101 OPTIONS
Contact: <sip:192.168.2.13:5060>
Content-Length: 0
010419: Feb 7 16:12:05.418: //3072/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.13:5060;branch=z9hG4bK143B9FE;received=70.11.54.125;rport=60110
From: <sip:montreal2.voip.ms>;tag=3FC84F4-156A
To: <sip:montreal2.voip.ms>;tag=as33c892c1
Call-ID: E94FCED8-ECB011E6-841BEC0A-4794616F@montreal2.voip.ms
CSeq: 101 OPTIONS
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Contact: <sip:67.205.74.187:5060>
Accept: application/sdp
Content-Length: 0
010420: Feb 7 16:12:09.998: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:montreal2.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.13:5060;branch=z9hG4bK143CD54
From: <sip:123456_line@montreal2.voip.ms>;tag=3FC96E0-C9A
To: <sip:123456_line@montreal2.voip.ms>
Date: Tue, 07 Feb 2017 21:12:09 GMT
Call-ID: 3F49BED6-ECAC11E6-83F3EC0A-4794616F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1486501929
CSeq: 55 REGISTER
Contact: <sip:123456_line@192.168.2.13:5060>
Expires: 60
Supported: path
Content-Length: 0
010421: Feb 7 16:12:10.006: //3073/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.2.13:5060;branch=z9hG4bK143CD54;received=70.11.54.125;rport=60110
From: <sip:123456_line@montreal2.voip.ms>;tag=3FC96E0-C9A
To: <sip:123456_line@montreal2.voip.ms>;tag=as3e14e196
Call-ID: 3F49BED6-ECAC11E6-83F3EC0A-4794616F
CSeq: 55 REGISTER
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="montreal2.voip.ms", nonce="0b96b19c"
Content-Length: 0
010422: Feb 7 16:12:10.010: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:montreal2.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.13:5060;branch=z9hG4bK143D22DD
From: <sip:123456_line@montreal2.voip.ms>;tag=3FC96E0-C9A
To: <sip:123456_line@montreal2.voip.ms>
Date: Tue, 07 Feb 2017 21:12:10 GMT
Call-ID: 3F49BED6-ECAC11E6-83F3EC0A-4794616F
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1486501930
CSeq: 56 REGISTER
Contact: <sip:123456_line@192.168.2.13:5060>
Expires: 60
Authorization: Digest username="123456_line",realm="montreal2.voip.ms",uri="sip:montreal2.voip.ms:5060",response="5a7ad20ce76a778a823851ccbebaa962",nonce="0b96b19c",algorithm=MD5
Content-Length: 0
010423: Feb 7 16:12:10.018: //3073/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.2.13:5060;branch=z9hG4bK143D22DD;received=70.11.54.125;rport=60110
From: <sip:123456_line@montreal2.voip.ms>;tag=3FC96E0-C9A
To: <sip:123456_line@montreal2.voip.ms>;tag=as3e14e196
Call-ID: 3F49BED6-ECAC11E6-83F3EC0A-4794616F
CSeq: 56 REGISTER
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 60
Contact: <sip:123456_line@192.168.2.13:5060>;expires=60
Date: Tue, 07 Feb 2017 21:12:44 GMT
Content-Length: 0
010424: Feb 7 16:12:11.706: //6/850BEB228005/DSM:(50/0/9):-1/dsp_stream_mgr_get_levels_sync: .
010425: Feb 7 16:12:11.706: //6/850BEB228005/DSPAPI/[]/dsp_query_info:
Request ID=6, Reset Flag=FALSE Q:TX RX Levels
010426: Feb 7 16:12:11.706: //6/850BEB228005/DSPAPI/[]/dsp_tx_stats:
Request ID=6, Packets: Voice=0, Signaling=0, ComfortNoise=0
TX duration=0(ms): Voice=0(ms), FAX=0(ms)
010427: Feb 7 16:12:11.706: //6/850BEB228005/DSPAPI/[]/dsp_rx_stats:
Request ID=6, Packets: Voice=0, Signalling=0, ComfortNoise=0
RX duration=0(ms): Voice=0(ms), FAX=0(ms)
Packets: Bad Sequence=0, Bad Protocol=0, Late=0, Early=0
010428: Feb 7 16:12:11.706: //6/850BEB228005/DSPAPI/[]/dsp_level_stats:
Request ID=6, TX: power=0.0(dBm0), mean=0.0(linear PCM), RX: power=0.0(dBm0), mean=0.0(linear PCM)
Background Noise=0.0(dBm0), ERL level=0.0(dB)
ACOM level=0.0(dB), Current TX act=2, Current RX act=2
Reflector locations: 19586(ms) 12361(ms) 513(ms), MAX reflector=4(ms)
2 ECAN control words: 670 7562, ECAN Version=6C69.63A4(na)
010429: Feb 7 16:12:11.706: //6/850BEB228005/DSM:(50/0/9):-1/dsmp_dsmapi_stats_cb: .
010430: Feb 7 16:12:11.706: //7/850BEB228005/DSM:(0/4/0):-1/dsp_stream_mgr_get_levels_sync: .
010431: Feb 7 16:12:11.706: //7/850BEB228005/DSPAPI/[0/1:1]/dsp_query_info:
Request ID=6, Reset Flag=FALSE Q:TX RX Levels
010432: Feb 7 16:12:11.710: //7/850BEB228005/DSPAPI/[0/1:1]/dsp_tx_stats:
Request ID=6, Packets: Voice=3340182, Signaling=0, ComfortNoise=0
TX duration=66803650(ms): Voice=66803650(ms), FAX=0(ms)
010433: Feb 7 16:12:11.710: //7/850BEB228005/DSPAPI/[0/1:1]/dsp_rx_stats:
Request ID=6, Packets: Voice=0, Signalling=0, ComfortNoise=0
RX duration=66803650(ms): Voice=0(ms), FAX=0(ms)
Packets: Bad Sequence=0, Bad Protocol=0, Late=0, Early=0
010434: Feb 7 16:12:11.710: //7/850BEB228005/DSPAPI/[0/1:1]/dsp_level_stats:
02-07-2017 03:29 PM
So here is the host portion of the request URI (70.11.54.125). Like I said earlier, do you have this IP on the UC520? If you dont, then your NAT is not working correctly. The gateway will not process any request for an IP that is not its own
Received:
INVITE sip:6131234567@70.11.54.125 SIP/2.0
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide