01-05-2022 12:30 PM
We just migrated from E1 to Sip but, we cannot make or receive calls
Incoming calls ring on our extension, when you answer the call it will not connect and it will continue to ring at the other end. I reported this to the provider, they said no acknowledgment is not received at their end that we should check our config.
Also, they said sip was configured as interworking at their end., so credentials are not required.
Have tried all I can with no success. I will appreciate any help I can get.
See attachments for logs.
01-05-2022 07:43 PM
incoming calls ring on our extension, when you answer the call it will not connect and it will continue to ring at the other end. I reported this to the provider, they said no acknowledgment is not received at their end that we should check our config.:- is there a firewall some where in between the gateway and CUCM ?
01-05-2022 11:23 PM
No firewall. the VoIP in running on a CME
01-05-2022 10:11 PM
01-06-2022 12:55 AM - edited 01-06-2022 12:58 AM
Please share your running configuration for us to verify it. Also please share the output from both debug ccsip message and debug voip ccapi inout in the same file, one per direction of the call, ie one file for inbound and another for outbound.
01-06-2022 01:29 AM
01-06-2022 01:42 AM
01-06-2022 05:56 AM
Looks like you did not have both debugs active at the same time. Can you please redo the calls and repost?
01-06-2022 05:57 AM
Looks like you’re running config is incomplete. Can you please repost the entire configuration?
01-06-2022 09:41 AM
01-06-2022 10:51 AM - edited 01-08-2022 01:14 AM
I would recommend you to clean up your configuration of dial peers, from what I can make out you should only need to keep 1111 and 1000. For dial peer 1000 your missing the bind statement and it has a session target definition, that’s not needed on an inbound dial peer as that’s an outbound option. Also your SIP-UA configuration should be altered to cater for the need of SIP CME phones, the sip server command is not required. SIP CME phones need the gateway to act as a SIP registrar. Search for this on the community and I’m sure you’ll find what you need.
For inbound VOIP dial peers my general advise is to if possible use information in the VIA header to match the dial peer. Information on this and many more tidbits on dial peer configuration can be found in this superb document. https://www.cisco.com/c/en/us/support/docs/voice/ip-telephony-voice-over-ip-voip/211306-In-Depth-Explanation-of-Cisco-IOS-and-IO.html
01-07-2022 06:56 AM
I'm yet to resolve this.
iI saw this in the log "resending 180 response due to no PRACK"
what is the meaning
3: //37125/F5C5069A9EB1/SIP/Info/info/4096/sipSPIResendInviteResponse: resending 180 response due to no PRACK
01-07-2022 09:55 AM
You got an answer from @Mohammed al Baqari with details about PRACK. Suggest that you read that and use the information provided. Once done and if it still does not work please repost the debugs as requested earlier, with both of them running simultaneously.
01-09-2022 04:32 AM
The issue has been resolved
The problem was the port I'm using to connect to the provider, my nat was applying dynamic port, they advised I to connect to them using port 5060
Adding this to my config solved the problem
registrar ipv4:xx.xx.xx.xx:5060
sip-server ipv4:xx.xx.xx.xx:5060
connection-reuse
Thank you, guys. I really appreciate your help
01-09-2022 05:38 AM
Glad to hear that you have solved your problem. FYI Adding :5060 after the FQDN on these commands has the actual effect in IOS to stop the router from trying to do an SRV DNS lookup. Not saying that it wasn’t your NAT configuration that was at fault with this, only to provide you with the complete details on what your changes does.
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