I have approximately 16 remote sites, each with their own local PRI (some with multiple PRIs) - we are just starting to receive complaints of crackling on the IP phones when initiating outbound calls to the PSTN. Internal calls are fine as well as PSTN calls into IP phones. This is happening at multiple locations therefore I beleieve we have a CUCM issue somewhere and not relatedto gateways/PRIs/slips as they all look clean. I can duplicate the issue on my IP Phone as well - when dialing there is no crackling but as soon as the call begins to connect and ring the crackling appears and is appearing more frequently on more phones at more locations.
we are running CUCM 8.6(2a) and the issues with quality have appeared and are occuring more frequently since we upgraded to 8.6(2a) aprrox 3 weeks ago (bug issue maybe??). Our phones (mainly 791x and 794x versions) are running sccp 9-2-1s. Is anybody running this version of CUCM and/or phone load and if so have you experienced similar issue with call quality? Our UC environment has been rock solid for years until this issue appeared
Yes,it is the duration of the call - the callers on the remote side cannot hear the static/crackling, just our employees, if that helps. i plan to reboot the cluster (3 CUCM) this evening anyway but do not anticipate that resolving it
We were running CUCM 8.0(2c)SU1 prior and were issue free. I am curious to know if it could be the new firmware - we definitely had a different version on the older CUCM, i beleive it was SCCP 8-3-2. can i back down a version or two on the phone firmware?
It could be the firmware but since it's only affecting outbound calls I think it's unlikely (but not impossible).
I'd like to get some info on the gateways. What protocol is CUCM using to communicate to the gateways? h323, MGCP, SIP?
Are MTPs required on your gateway/trunk configurations?
If so, do you have MTPs configured on each gateway or are you just using CUCM? If they're on the gateways are they registering properly?
If your gateways are set to require an MTP and the only MTP configured is the CUCM server then the RTP stream would flow through CUCM and that would be the common demoninator. But, if that were the case it should afftect all calls, not just outbound.
As an FYI on the issue - on Thursday evening I wound up rolling the phones back to sccp 9-0-3 from 9-2-1s, rebooted the cluster to have the phones downgrade their firmware and have not heard a complaint since.
In addition to what protocol and firmware version is being used, it would be interesting to see what codec is being used. I was using 9-2-1S and was having trouble with internal calls using G.722. Basically as soon as a call was connected with that codec being used both parties received a busy signal.
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...