In CallManager, "CallWaitingEnable" is set to false. A majority of the phones are configured with "Call Waiting" set to default.
Yet, we still get the call waiting beeps when a second call is received on the phone. By setting the "CallWaitingEnabled" parameter to false, and the default setting on the phone call waiting should be off.
Is this a glitch/bug, or am I interpreting the information incorrectly?
If you have more than one line on the phone and you have the first line configured to forward busy to the second line then you are probably hearing the toneoncallforward and not the call waiting tone. If you look down at the phone is the call coming in on the first line or the second?
You can set it to false. The only problem is this is a per call manager parameter. So what ever you set it to per call manager is how all the phones registered to that call manager will react. If you do set it false then you will not know when you have a second call ringing in unless you are looking down at the phone.
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...