cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1383
Views
5
Helpful
3
Replies

Incoming sip calls have stopped working outgoing still works CME stumped

craigtewsley
Level 1
Level 1

A little background.  I have a 2811 at a client site setup with a single sip trunk.  It worked at the client's old site.  It no longer accepts inbound calls  Nothing has been changed in terms of the config.  I have a 2851 at home as a lab.  I had it as a mirror with my own SIP account.  It too was working.  It no longer receives calls after been stood up again to troubleshoot the client.  Behind the main internet connection at the lab are an SPA112 which receives calls just fine from the same server and voip provider.  A soft phone is also able to receive calls using the same account as is configured on the 2851.  It leads me to think that I have missed something on the 2811 and the 2851 I could really us a hand please and thank you:

 

SHOW RUN for the SIP section sanitized:

voice service voip

 ip address trusted list

  ipv4 184.75.215.146

  ipv4 10.10.153.1

 ip address trusted call-block cause not-in-cug

 gcid

 clid substitute name

 allow-connections sip to sip

 no supplementary-service sip moved-temporarily

 no supplementary-service sip refer

 sip

  session refresh

  e911

  transport switch udp tcp

  asserted-id ppi

  localhost dns:phones.iisottawa.ca

  midcall-signaling passthru

  no call service stop

!

!

dial-peer voice 2 voip

 destination-pattern [2-9]..[2-9]......

 session protocol sipv2

 session target ipv4:184.75.215.146

 dtmf-relay rtp-nte cisco-rtp sip-kpml sip-notify

 codec g711ulaw

 no vad

!

dial-peer voice 3 voip

 destination-pattern 1[2-9]..[2-9]......

 session protocol sipv2

 session target ipv4:184.75.215.146

 dtmf-relay rtp-nte cisco-rtp sip-kpml sip-notify

 codec g711ulaw

 no vad

!

dial-peer voice 4 voip

 session protocol sipv2

 session target ipv4:184.75.215.146

 incoming called-number .

 dtmf-relay cisco-rtp rtp-nte

 codec g711ulaw

!

dial-peer voice 1 voip

 destination-pattern *97

 session protocol sipv2

 session target ipv4:184.75.215.146

 dtmf-relay rtp-nte cisco-rtp sip-kpml sip-notify

 codec g711ulaw

 no vad

!

dial-peer voice 98 voip

 destination-pattern *98

 session protocol sipv2

 session target ipv4:184.75.215.146

 dtmf-relay rtp-nte cisco-rtp sip-kpml sip-notify

 codec g711ulaw

 no vad

!

dial-peer voice 56 voip

 huntstop

 destination-pattern 6135182156

 session protocol sipv2

 session target ipv4:10.10.153.1:2000

 dtmf-relay rtp-nte cisco-rtp sip-kpml sip-notify

 codec g711ulaw

 no vad

!

dial-peer voice 57 voip

 huntstop

 destination-pattern 6135182157

 session protocol sipv2

 session target ipv4:10.10.153.1:2000

 dtmf-relay rtp-nte cisco-rtp sip-kpml sip-notify

 codec g711ulaw

 no vad

!

!

sip-ua

 credentials username 218332_main password 7 xyz realm toronto7.voip.ms

 authentication username 218332_main password 7 xyz realm toronto7.voip.ms

 mwi-server dns:toronto7.voip.ms expires 160 port 5060 transport udp unsolicited

 registrar dns:toronto7.voip.ms expires 300

!

!

telephony-service

 max-ephones 42

 max-dn 144

 ip source-address 10.10.153.1 port 2000

 service dss

 cnf-file location flash:

 load 7914 S00105000400

 load 7915-12 cmterm-7915.1-0-4-2

 load 7915-24 cmterm-7915.1-0-4-2

 load 7941 SCCP41.9-4-2SR3-1S

 load 7961 SCCP41.9-3-1SR4-1S

 load 7962 cmterm-7942_7962-sccp.8-5-2

 time-zone 12

 voicemail *97

 mwi relay

 max-conferences 8 gain -6

 transfer-system full-consult

 create cnf-files version-stamp Jan 01 2002 00:00:00

!

!

ephone-dn  56  dual-line

 number 6135182156 secondary 56

 mwi-type both

!

!

ephone-dn  57  dual-line

 number 6135182157 secondary 57

 mwi-type both

!

!

ephone  56

 mac-address 0000.0000.0000

 mwi-line 1

 button  1:56

!

!

!

ephone  57

 mac-address 0000.0000.0000

 mwi-line 1

 button  1:57

!

Router#show sip register status
Line                             peer       expires(sec) registered P-Associ-URI
================================ ========== ============ ========== ============
218332_main                      -1         180          yes
56                                       20002      69           no
57                                       20004      98           no
6135182156                       20001      67           no
6135182157                       20003      98           no

 

Router#debug ccsip error
SIP Call error tracing is enabled
Router#
*Jan 10 02:34:53.091: //389/000000000000/SIP/Error/ccsip_api_register_result_ind: Message Cod e Class 4xx Method Code 100 received for REGISTER
*Jan 10 02:34:53.091: //389/000000000000/SIP/Error/sipSPIRegPthruProcessResponse: Error NO RP CB

 

Router#debug ccsip messages
SIP Call messages tracing is enabled
Router#
*Jan 10 02:37:24.991: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:toronto7.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK31221BC
From: <sip:57@toronto7.voip.ms>;tag=9F2674-1D5C
To: <sip:57@toronto7.voip.ms>
Date: Wed, 10 Jan 2018 02:37:24 GMT
Call-ID: D81E7D81-F4CD11E7-8006F9D3-51DFE151
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1515551844
CSeq: 174 REGISTER
Contact: <sip:57@192.168.1.30:5060>
Expires: 300
Supported: path
Content-Length: 0


*Jan 10 02:37:25.015: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:toronto7.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK313244D
From: <sip:6135182157@toronto7.voip.ms>;tag=9F268C-1C97
To: <sip:6135182157@toronto7.voip.ms>
Date: Wed, 10 Jan 2018 02:37:25 GMT
Call-ID: D7D98654-F4CD11E7-8005F9D3-51DFE151
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1515551845
CSeq: 174 REGISTER
Contact: <sip:6135182157@192.168.1.30:5060>
Expires: 300
Supported: path
Content-Length: 0


*Jan 10 02:37:25.035: //395/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK31221BC;received=23.233.25.247;rport=56623
From: <sip:57@toronto7.voip.ms>;tag=9F2674-1D5C
To: <sip:57@toronto7.voip.ms>;tag=as494c8bb2
Call-ID: D81E7D81-F4CD11E7-8006F9D3-51DFE151
CSeq: 174 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="toronto7.voip.ms", nonce="1b827133"
Content-Length: 0


*Jan 10 02:37:25.039: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:toronto7.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK3141FB9
From: <sip:57@toronto7.voip.ms>;tag=9F2674-1D5C
To: <sip:57@toronto7.voip.ms>
Date: Wed, 10 Jan 2018 02:37:25 GMT
Call-ID: D81E7D81-F4CD11E7-8006F9D3-51DFE151
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1515551845
CSeq: 175 REGISTER
Contact: <sip:57@192.168.1.30:5060>
Expires: 300
Authorization: Digest username="218332_main",realm="toronto7.voip.ms",uri="sip:toronto7.voip.ms:5060",response="717b01f4041b2e04c7f60216c621cf02",nonce="1b827133",algorithm=MD5
Content-Length: 0


*Jan 10 02:37:25.047: //396/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK313244D;received=23.233.25.247;rport=56623
From: <sip:6135182157@toronto7.voip.ms>;tag=9F268C-1C97
To: <sip:6135182157@toronto7.voip.ms>;tag=as195bacdf
Call-ID: D7D98654-F4CD11E7-8005F9D3-51DFE151
CSeq: 174 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="toronto7.voip.ms", nonce="6950e0a7"
Content-Length: 0


*Jan 10 02:37:25.051: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:toronto7.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK31511A3
From: <sip:6135182157@toronto7.voip.ms>;tag=9F268C-1C97
To: <sip:6135182157@toronto7.voip.ms>
Date: Wed, 10 Jan 2018 02:37:25 GMT
Call-ID: D7D98654-F4CD11E7-8005F9D3-51DFE151
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1515551845
CSeq: 175 REGISTER
Contact: <sip:6135182157@192.168.1.30:5060>
Expires: 300
Authorization: Digest username="218332_main",realm="toronto7.voip.ms",uri="sip:toronto7.voip.ms:5060",response="35caef264994ae2c46363f633b8b2e56",nonce="6950e0a7",algorithm=MD5
Content-Length: 0


*Jan 10 02:37:25.067: //395/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK3141FB9;received=23.233.25.247;rport=56623
From: <sip:57@toronto7.voip.ms>;tag=9F2674-1D5C
To: <sip:57@toronto7.voip.ms>;tag=as494c8bb2
Call-ID: D81E7D81-F4CD11E7-8006F9D3-51DFE151
CSeq: 175 REGISTER
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0


*Jan 10 02:37:25.083: //396/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Forbidden
Via: SIP/2.0/UDP 192.168.1.30:5060;branch=z9hG4bK31511A3;received=23.233.25.247;rport=56623
From: <sip:6135182157@toronto7.voip.ms>;tag=9F268C-1C97
To: <sip:6135182157@toronto7.voip.ms>;tag=as195bacdf
Call-ID: D7D98654-F4CD11E7-8005F9D3-51DFE151
CSeq: 175 REGISTER
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Content-Length: 0

 

1 Accepted Solution

Accepted Solutions

Issue is related to NAT please check your firewall or NAT device.

 

Received:
INVITE sip:6135180480@198.251.62.14:57276 SIP/2.0
Via: SIP/2.0/UDP 184.75.215.146:5060;branch=z9hG4bK70f089fb;rport
Max-Forwards: 70
From: "OTTAWA, ON" <sip:6135588702@184.75.215.146>;tag=as7c72a645
To: <sip:6135180480@198.251.62.14:57276>

Contact: <sip:6135588702@184.75.215.146:5060>

 

INVITE is being received from public IP to private IP and router is not able to handle it.

 

Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Via: SIP/2.0/UDP 184.75.215.146:5060;branch=z9hG4bK70f089fb;rport
From: "OTTAWA, ON" <sip:6135588702@184.75.215.146>;tag=as7c72a645
To: <sip:6135180480@198.251.62.14:57276>;tag=6C4831CC-72D
Date: Sat, 13 Jan 2018 16:34:44 GMT

 

Please work with your network team to configure the correct NATing.

 

Regards,

Balram


Please rate if you find this helpful
Thank You
Balram

View solution in original post

3 Replies 3

Hello,

Make incoming test call and collect following debugs.

debug voip ccap inout
debug ccsip message
debug voip translation
debug sccp packet
debug sccp events

Share both calling and called number.


Please rate if you find this helpful
Thank You
Balram

Thank you so much for looking at this,

Attached is the trace with the following enabled:

debug voip ccap inout
debug ccsip message
debug voip translation
debug sccp packet
debug sccp events

I called in from 6135588702 to 6135180480 I got no ring through the 7941g

Issue is related to NAT please check your firewall or NAT device.

 

Received:
INVITE sip:6135180480@198.251.62.14:57276 SIP/2.0
Via: SIP/2.0/UDP 184.75.215.146:5060;branch=z9hG4bK70f089fb;rport
Max-Forwards: 70
From: "OTTAWA, ON" <sip:6135588702@184.75.215.146>;tag=as7c72a645
To: <sip:6135180480@198.251.62.14:57276>

Contact: <sip:6135588702@184.75.215.146:5060>

 

INVITE is being received from public IP to private IP and router is not able to handle it.

 

Sent:
SIP/2.0 400 Bad Request - 'Invalid Host'
Via: SIP/2.0/UDP 184.75.215.146:5060;branch=z9hG4bK70f089fb;rport
From: "OTTAWA, ON" <sip:6135588702@184.75.215.146>;tag=as7c72a645
To: <sip:6135180480@198.251.62.14:57276>;tag=6C4831CC-72D
Date: Sat, 13 Jan 2018 16:34:44 GMT

 

Please work with your network team to configure the correct NATing.

 

Regards,

Balram


Please rate if you find this helpful
Thank You
Balram
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: