I am working with a Call Manager Cluster running 8.6.2. I am testing outbound calls from the Call Manager to an Acme SBC and then out to our provider via SIP trunks. Our provider is sending a 180 RINGING message with SDP. There doesn't seem to be any RTP traffic for the ringing, so on our SIP Profile I have the "Disable Early Media on 180" check box checked.
This is the crazy part. Whenever I reset and restart the SIP Trunks, the outbound call will have ringback. Any calls after that will not have ringback until the SIP Trunks are reset and restarted once again. Has anybody seen something like this before?
Instead of a gateway router we have an Acme SBC. I took Brian's advice and looked at the SIP messaging and nothing was different between the two call-legs. While testing some more, I noticed that the phone displayed "Ring Out" when the phone had ringback, and did not display anything when there was no ringback. I think something got hosed up with the SIP Trunk itself to where it didn't know to have the phone play ringback once a 180 was recieved. I deleted the trunk this morning and rebuilt it just as it was, and I have ringback on every call. I was using the trunk for testing a new provider as well as a new DSP farm. I was making quite a few changes quite often and I guess something was hung with all the changes.
Thanks for the feeback, everybody! I really appreciate everyone's advice.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...