We have a DN configed to Call Forward on No Answer to another DN. If this second DN is busy, then the caller hears ringing for the "Ring No Answer timeout" duration, and then hears busy. Therefore it seems it should be doing what it should, but is there a way to prevent the divert occurring if the ultimate destination is busy, and therefore keep ringing the original destination (this seems to be what happens in our PBX).
For normal CFNA and CFB scenarios you will not be able to do this. In this case CCM will ring the first phone then when the CFNA timer expires CCM will stop this call and initiate a new call to the CFNA destination. The forwarding rules for this device will take affect if appropriate.
You might be able to accomplish something simialr with Attendant Console hunt groups. The config will depend on the version of CCM you have. You can use AC without having to use the GUI.
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...