WAN based voice-call issues after 4520 MCU upgraded to v4.5
I upgraded out MCU last week and performed ( what I thought was ) sufficient testing including TMS scheduled conferences, ad-hoc conferences, video only, voice only calls. etc.. One thing I didn't test was inbound calls from field offices using the short dial (OnNet) to the bridge, whoops. I began getting emails from frustrated users in the middle of the night saying this was broken.
We're running Cisco call manager 8.5.
The users who dialed the full 10 digit pstn number got through fine but folks using on-net dialing got "unable to complete the call" messages.
The system log on the MCU shows the following entries for the failed calls including "Unable to establish call due to lack of matching media codecs"
My call manager guru says he believes it to be a transcoding issue g711/g729. All of the audio/video codecs to and from the MCU are enabled however.
I was able to roll back the upgrade to 4.4 and we're back up and running.
I thought I would throw this out to the community to see if anyone has any ideas before I open a TAC case
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...