01-20-2012 05:02 AM - edited 03-21-2019 05:13 AM
Hi,
Can anyone help? I'm not incredibly technical but have a vague understanding... using the CCA to setup, I know how to telnet into CLI but not confident on the commands to use after that so don't generally touch it so I don't break anything.
I've set up a SIP trunk on a UC540 from VOIP-Unlimited. The outgoing calls work fine, and have even set up the outbound DID mapping.
However can't get incoming calls to connect. I've checked that the IP addresses from the ITSP are all set to be allowed, and I've mapped the inbound DID to an extension. The error log includes the number formatted as both +44845.... and 0845.... so I've tried both on the inbound mapping but neither work.
The error code is 127, but after reading the Cisco document on incoming call problems can't work out what else to do?
Oh and I do have a Dynamic Public IP address which is being changed to a Static IP in the next few weeks if that makes a difference - but the error log shows the correct public IP address for my connection.
The error log is (I've starred out my phone numbers and public IP address):
Frame 4 (624 bytes on wire, 624 bytes captured)
Arrival Time: Jan 20, 2012 12:18:40.027551000
Internet Protocol, Src: [MYPUBLICIP] ([MYPUBLICIP]), Dst: 91.151.2.130 (91.151.2.130)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 500 Internal Server Error
Status-Code: 500
[Resent Packet: False]
Message Header
Reason: Q.850;cause=127
Reason Protocols: Q.850
Cause: 127(0x7f)[Internetworking, unspecified]
Date: Fri, 20 Jan 2012 12:29:40 GMT
From: <sip:07525******@91.151.11.20>;tag=3536050719-942236
SIP from address: sip:07525******@91.151.11.20
SIP from address User Part: 07525******
SIP from address Host Part: 91.151.11.20
SIP tag: 3536050719-942236
Allow-Events: telephone-event
Content-Length: 0
To: +44845******* <sip:0845*******@91.151.2.130;user=phone>;tag=1E8224-1038
SIP Display info: +44845*******
SIP to address: sip:0845*******@91.151.2.130
SIP to address User Part: 0845*******
SIP to address Host Part: 91.151.2.130
SIP tag: 1E8224-1038
Call-ID:
14384647-3536050719-942229@msx1-voip-unlimited-net.mydomain.com
Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bKf438.ad3a8dc1.0,SIP/2.0/UDP 91.151.11.20:5060;rport=5060;received=91.151.11.20;branch=z9hG4bK03c5a15cdfb692caf9f5d370fad8dd48
Transport: UDP
Sent-by Address: 91.151.2.130
Branch: z9hG4bKf438.ad3a8dc1.0
Transport: UDP
Sent-by Address: 91.151.11.20
Sent-by port: 5060
RPort: 5060
Received: 91.151.11.20
Branch: z9hG4bK03c5a15cdfb692caf9f5d370fad8dd48
CSeq: 1 INVITE
Sequence Number: 1
Method: INVITE
Server: Cisco-SIPGateway/IOS-12.x
01-23-2012 03:56 AM
UC_540#show ip interface brief
Interface IP-Address OK? Method Status Protocol
FastEthernet0/0 82.38.242.91 YES DHCP up up
In0/0 10.1.10.2 YES TFTP up up
FastEthernet0/1/0 unassigned YES unset up up
FastEthernet0/1/1 unassigned YES unset up down
FastEthernet0/1/2 unassigned YES unset up up
FastEthernet0/1/3 unassigned YES unset up down
FastEthernet0/1/4 unassigned YES unset up up
FastEthernet0/1/5 unassigned YES unset up up
FastEthernet0/1/6 unassigned YES unset up up
FastEthernet0/1/7 unassigned YES unset up up
FastEthernet0/1/8 unassigned YES unset up down
Dot11Radio0/5/0 unassigned YES NVRAM up up
Dot11Radio0/5/0.1 unassigned YES unset up up
Dot11Radio0/5/0.100 unassigned YES unset up up
Vlan1 unassigned YES NVRAM up up
Vlan100 unassigned YES NVRAM up up
NVI0 10.1.10.2 YES unset up up
BVI1 10.0.1.1 YES NVRAM up up
BVI100 10.1.1.1 YES NVRAM up up
Loopback0 10.1.10.2 YES NVRAM up up
UC_540#
01-23-2012 04:00 AM
OK.
Please now capture an incoming SIP Invite
Were looking for something like this:
INVITE sip:0845*******@82.38.242.91:5060 SIP/2.0
Please can your post your invite ?
thanks
01-23-2012 04:10 AM
This is the SIP invite provided by the ITSP, after which is returned the 500 Server Error:
Frame 3 (1320 bytes on wire, 1320 bytes captured) Arrival Time: Jan 23, 2012 12:02:55.904806000 Internet Protocol, Src: 91.151.2.130 (91.151.2.130), Dst: 82.38.242.91 (82.38.242.91) User Datagram Protocol, Src Port: sip (5060), Dst Port: 60589 (60589) Session Initiation Protocol Request-Line: INVITE sip:08455240241@82.38.242.91:60589 SIP/2.0 Method: INVITE Request-URI: sip:08455240241@82.38.242.91:60589 Request-URI User Part: 08455240241 Request-URI Host Part: 82.38.242.91 Request-URI Host Port: 60589 [Resent Packet: False] Message Header Record-Route: <91.151.2.130> Max-Forwards: 66 Session-Expires: 3600;refresher=uac Min-SE: 600 Supported: timer, 100rel To: +448455240241 <08455240241> SIP Display info: +448455240241 SIP to address: sip:08455240241@91.151.2.130 SIP to address User Part: 08455240241 SIP to address Host Part: 91.151.2.130 From: <07525632279>;tag=3536308975-891968 SIP from address: sip:07525632279@91.151.11.20 SIP from address User Part: 07525632279 SIP from address Host Part: 91.151.11.20 SIP tag: 3536308975-891968 Call-ID: 14496129-3536308975-891962@msx1-voip-unlimited-net.mydomain.com CSeq: 1 INVITE Sequence Number: 1 Method: INVITE Allow: INVITE, BYE, OPTIONS, CANCEL, ACK, REGISTER, NOTIFY, INFO, REFER, SUBSCRIBE, PRACK, UPDATE, MESSAGE, PUBLISH Via: SIP/2.0/UDP 91.151.2.130;branch=z9hG4bK582c.805a1bc4.0 Transport: UDP Sent-by Address: 91.151.2.130 Branch: z9hG4bK582c.805a1bc4.0 Via: SIP/2.0/UDP 91.151.11.20:5060;rport=5060;received=91.151.11.20;branch=z9hG4bKfe30ece2448733d40223daff4c162902 Transport: UDP Sent-by Address: 91.151.11.20 Sent-by port: 5060 RPort: 5060 Received: 91.151.11.20 Branch: z9hG4bKfe30ece2448733d40223daff4c162902 Contact: <07525632279> Contact Binding: <07525632279> URI: <07525632279> SIP contact address: sip:07525632279@91.151.11.20:5060 Content-Type: application/sdp Content-Length: 448 Message Body Session Description Protocol Session Description Protocol Version (v): 0 Owner/Creator, Session Id (o): msx1-voip-unlimited-net 3066282 0 IN IP4 91.151.11.20 Owner Username: msx1-voip-unlimited-net Session ID: 3066282 Session Version: 0 Owner Network Type: IN Owner Address Type: IP4 Owner Address: 91.151.11.20 Session Name (s): sip call Connection Information (c): IN IP4 91.151.8.181 Connection Network Type: IN Connection Address Type: IP4 Connection Address: 91.151.8.181 Time Description, active time (t): 0 0 Session Start Time: 0 Session Stop Time: 0 Media Description, name and address (m): audio 58760 RTP/AVP 8 18 0 101 Media Type: audio Media Port: 58760 Media Protocol: RTP/AVP Media Format: ITU-T G.711 PCMA Media Format: ITU-T G.729 Media Format: ITU-T G.711 PCMU Media Format: DynamicRTP-Type-101 Media Attribute (a): rtpmap:101 telephone-event/8000 Media Attribute Fieldname: rtpmap Media Format: 101 MIME Type: telephone-event Sample Rate: 8000 Media Attribute (a): fmtp:101 0-15 Media Attribute Fieldname: fmtp Media Format: 101 [telephone-event] Media format specific parameters: 0-15 Media Attribute (a): sqn:0 Media Attribute Fieldname: sqn Media Attribute Value: 0 Media Attribute (a): cdsc: 1 audio RTP/AVP 8 18 0 101 Media Attribute Fieldname: cdsc Media Attribute Value: 1 audio RTP/AVP 8 18 0 101 Media Attribute (a): cdsc: 5 image udptl t38 Media Attribute Fieldname: cdsc Media Attribute Value: 5 image udptl t38 Media Attribute (a): cpar: a=T38FaxVersion:0 Media Attribute Fieldname: cpar Media Attribute Value: a=T38FaxVersion:0 Media Attribute (a): cpar: a=T38FaxRateManagement:transferredTCF Media Attribute Fieldname: cpar Media Attribute Value: a=T38FaxRateManagement:transferredTCF Media Attribute (a): cpar: a=T38FaxMaxDatagram:160 Media Attribute Fieldname: cpar Media Attribute Value: a=T38FaxMaxDatagram:160 Media Attribute (a): cpar: a=T38FaxUdpEC:t38UDPRedundancy Media Attribute Fieldname: cpar Media Attribute Value: a=T38FaxUdpEC:t38UDPRedundancy Media Attribute (a): X-sqn:0 Media Attribute Fieldname: X-sqn Media Attribute Value: 0 Media Attribute (a): X-cap: 1 image udptl t38 Media Attribute Fieldname: X-cap Media Attribute Value: 1 image udptl t38 07525632279>07525632279>07525632279>07525632279>08455240241>91.151.2.130>
01-23-2012 04:18 AM
No that's OK.
Your router is registering on their SIP network.
I'll PM you
01-23-2012 04:11 AM
They look to be sending it to port 60589, not 5060? that right?
01-23-2012 04:29 AM
Can you post another debug?
debug ccsip all
debug voice ccapi inout
These are not user friendly but very complete. We will look for sip negotiation issues, acl issues, dial-peer config issues, and so on.
Regards.
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