cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
450
Views
0
Helpful
3
Replies

UC520 - Inbound Calls Issue

ReidJones
Level 1
Level 1

Hello,

I have a UC520 which I have just placed a Meraki MX64 security appliance in front of.  I'm now having issues with inbound calls.  Outbound calls work fine.  Please see the logs below and let me know if you can see what is causing the error.  The firewall has been disabled on the UC520 and we are using the Meraki appliance for the firewall.  The public WAN ip of the Meraki is 70.11.222.333, and the Meraki appliance has given the UC520 the IP address of 192.168.10.100.

006336: Mar 20 18:07:40.081: //-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=z9hG4bK1c87fa1f;rport
From: "OTTAWA, ON" <sip:6138881122@67.205.74.187>;tag=as1cfd8b2f
To: <sip:6137774444@70.11.222.333:55596>;tag=19A89B9C-1422
Date: Mon, 20 Mar 2017 22:07:40 GMT
Call-ID: 095fbd6618fa0b132a27c6134e42900f@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


006337: Mar 20 18:07:40.177: //-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=z9hG4bK1c87fa1f;rport
From: "OTTAWA, ON" <sip:6138881122@67.205.74.187>;tag=as1cfd8b2f
To: <sip:6137774444@70.11.222.333:55596>;tag=19A89B9C-1422
Call-ID: 095fbd6618fa0b132a27c6134e42900f@67.205.74.187:5060
CSeq: 102 INVITE
Reason: Q.850;cause=100
Content-Length: 0


006338: Mar 20 18:07:40.185: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
ACK sip:6137774444@70.11.222.333:55596 SIP/2.0
Via: SIP/2.0/UDP 67.205.74.187:5060;branch=z9hG4bK1c87fa1f;rport
Max-Forwards: 70
From: "OTTAWA, ON" <sip:6138881122@67.205.74.187>;tag=as1cfd8b2f
To: <sip:6137774444@70.11.222.333:55596>;tag=19A89B9C-1422
Contact: <sip:6138881122@67.205.74.187:5060>
Call-ID: 095fbd6618fa0b132a27c6134e42900f@67.205.74.187:5060
CSeq: 102 ACK
User-Agent: voip.ms
Content-Length: 0


006339: Mar 20 18:07:44.577: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:montreal2.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.100:5060;branch=z9hG4bK3AA3D36
From: <sip:174556_line@montreal2.voip.ms>;tag=19A8AD30-744
To: <sip:174556_line@montreal2.voip.ms>
Date: Mon, 20 Mar 2017 22:07:44 GMT
Call-ID: EEB4F152-CEE11E7-8CA1F5D5-939DC376
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1490047664
CSeq: 24 REGISTER
Contact: <sip:174556_line@192.168.10.100:5060>
Expires:  60
Supported: path
Content-Length: 0


006340: Mar 20 18:07:44.585: //12343/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.10.100:5060;branch=z9hG4bK3AA3D36;received=70.11.222.333;rport=55596
From: <sip:174556_line@montreal2.voip.ms>;tag=19A8AD30-744
To: <sip:174556_line@montreal2.voip.ms>;tag=as25c298a6
Call-ID: EEB4F152-CEE11E7-8CA1F5D5-939DC376
CSeq: 24 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="7dc89d09"
Content-Length: 0


006341: Mar 20 18:07:44.589: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:montreal2.voip.ms:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.10.100:5060;branch=z9hG4bK3AA419B5
From: <sip:174556_line@montreal2.voip.ms>;tag=19A8AD30-744
To: <sip:174556_line@montreal2.voip.ms>
Date: Mon, 20 Mar 2017 22:07:44 GMT
Call-ID: EEB4F152-CEE11E7-8CA1F5D5-939DC376
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1490047664
CSeq: 25 REGISTER
Contact: <sip:174556_line@192.168.10.100:5060>
Expires: 60
Authorization: Digest username="174556_line",realm="montreal2.voip.ms",uri="sip:montreal2.voip.ms:5060",response="a2b4a8e48af8905c751751ef744a5c17",nonce="7dc89d09",algorithm=MD5
Content-Length: 0


006342: Mar 20 18:07:44.593: //12343/000000000000/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.10.100:5060;branch=z9hG4bK3AA419B5;received=70.11.222.333;rport=55596
From: <sip:174556_line@montreal2.voip.ms>;tag=19A8AD30-744
To: <sip:174556_line@montreal2.voip.ms>;tag=as25c298a6
Call-ID: EEB4F152-CEE11E7-8CA1F5D5-939DC376
CSeq: 25 REGISTER
Server: voip.ms
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces, timer
Expires: 60
Contact: <sip:174556_line@192.168.10.100:5060>;expires=60
Date: Mon, 20 Mar 2017 22:08:05 GMT
Content-Length: 0
3 Replies 3

Provide the call flow with complete debugs for the failed call. 

Regards

Abhay

Regards
Abhay Singh Reyal
The Only Way To Do Great Work Is To Love What You Do. If You Haven’t Found It Yet, Keep Looking. Don’t Settle

I can do that.  Which debug command should I be using to get the logs requested.

Depending upon what the call flow is you can run below debugs

-debug ccsip messages [For SIP connectivity]

-debug voip ccapi inout

-debug isdn q931 [If there is a PRI connected on a SIP gateway or there is a TDM leg]

Run these debugs as per the set up you have, if you only have sip connectivity then run only 1st two debugs. 

Regards

Abhay

Regards
Abhay Singh Reyal
The Only Way To Do Great Work Is To Love What You Do. If You Haven’t Found It Yet, Keep Looking. Don’t Settle