08-26-2013 12:29 PM - edited 03-16-2019 07:02 PM
Hello, we are installing a new SIP trunk from our ISP to replace our PRI. With the setup the way we have it we are getting ring no answer on inbound calls and fast busy on outbound calls. The ISP has a Cisco 2900 router that is NATing over to our Cisco 2851 with advipservices firmware. Behind our Cisco 2851 we have CUCM 8.0. What could be causing our issues? Attached is the configuration in the voice gateway. The ISP Router has the public IP and is NATing the traffic across to 130.0.100.1. Then there is an outbound dial-peer going to the call manager. The phone will ring, but the calling party just hears endless ringing even if the called party picks up the phone. I've only been testing one number since we don't have all of the numbers ported over, i have it translated with a num-exp value. Also, it works with a phone plugged directly into an FXS port.
Solved! Go to Solution.
09-04-2013 06:43 AM
09-04-2013 09:41 AM
It's just sending UDP invites out over and never gets a response. Are you sure you have the IP address right? Also, do they expect TCP or UDP?
09-04-2013 10:24 AM
I believe I do have the IP addresses correct for their equipment. I'm not onsite, I'm checking now to make sure everything is powered up since this isn't running live.
Thanks
09-04-2013 01:35 PM
Attached is the latest debug I ran. The cabling to the Telco Router had been unplugged for some reason so that's why it wasn't communicating before on my previous debug. I'm still getting a fast busy on outbound calls but it waits a few seconds before it gives the fast busy
09-04-2013 02:07 PM
The debug is incomplete. We only see the outbound INVITE...Pls post the full debugs
Please rate all useful posts
"opportunity is a haughty goddess who waste no time with those who are unprepared"
09-04-2013 03:24 PM
I'm testing on the live network now so please disregard the prevoius post. I am getting a 503 service unavailable. A fastbusy on outbound calls and I see no SIP traffic between my CUBE and the telco's equipment. Below is the debug in it's entirety for the call
Sep 4 22:22:20.198: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
INVITE sip:92566138703@130.0.100.1:5060 SIP/2.0
Via: SIP/2.0/TCP 130.0.100.146:5060;branch=z9hG4bK4051db5294
From: <2565476386>;tag=1f4823e6-e05d-4f53-ab96-a322c4ecf282-272565476386>
142664
To: <92566138703>92566138703>
Date: Wed, 04 Sep 2013 22:22:20 GMT
Call-ID: 7569fb80-2271b29c-2b-92640082@130.0.100.146
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM8.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE,
NOTIFY
CSeq: 101 INVITE
Contact: <2565476386>2565476386>
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: <130.0.100.146:5060>;method="NOTIFY;Event=telephone-event;Duratio130.0.100.146:5060>
n=500"
Cisco-Guid: 1969879936-0000065536-0000000043-2456027266
Session-Expires: 1800
P-Asserted-Identity: <2565476386>2565476386>
Remote-Party-ID: <2565476386>;party=calling;screen=yes;privacy2565476386>
=off
Max-Forwards: 70
Content-Length: 0
Sep 4 22:22:20.214: //39335/7569FB800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 100 Trying
Via: SIP/2.0/TCP 130.0.100.146:5060;branch=z9hG4bK4051db5294
From: <2565476386>;tag=1f4823e6-e05d-4f53-ab96-a322c4ecf282-272565476386>
142664
To: <92566138703>92566138703>
Date: Wed, 04 Sep 2013 22:22:20 GMT
Call-ID: 7569fb80-2271b29c-2b-92640082@130.0.100.146
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Content-Length: 0
Sep 4 22:22:20.226: //39335/7569FB800000/SIP/Msg/ccsipDisplayMsg:
Sent:
SIP/2.0 503 Service Unavailable
Via: SIP/2.0/TCP 130.0.100.146:5060;branch=z9hG4bK4051db5294
From: <2565476386>;tag=1f4823e6-e05d-4f53-ab96-a322c4ecf282-272565476386>
142664
To: <92566138703>;tag=32D99D64-5B592566138703>
Date: Wed, 04 Sep 2013 22:22:20 GMT
Call-ID: 7569fb80-2271b29c-2b-92640082@130.0.100.146
CSeq: 101 INVITE
Allow-Events: telephone-event
Server: Cisco-SIPGateway/IOS-12.x
Reason: Q.850;cause=38
Content-Length: 0
Sep 4 22:22:20.226: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
McCartney_R1#ACK sip:92566138703@130.0.100.1:5060 SIP/2.0
Via: SIP/2.0/TCP 130.0.100.146:5060;branch=z9hG4bK4051db5294
From: <2565476386>;tag=1f4823e6-e05d-4f53-ab96-a322c4ecf282-272565476386>
142664
To: <92566138703>;tag=32D99D64-5B592566138703>
Date: Wed, 04 Sep 2013 22:22:20 GMT
Call-ID: 7569fb80-2271b29c-2b-92640082@130.0.100.146
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: presence, kpml
Content-Length: 0
09-04-2013 09:53 PM
After looking at this closer, the ISP had given me an incorrect IP address. I corrected this and made a few dial-peer changes and calls are now completing outbound.
Thanks all for your help with these issues.
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