Dialing an "Invalid Number" produces a fast busy on CCME
Calling an number that doesn't exist (an "invalid number") on our CCME system produces a fast busy signal.
On our CM system, it results in a "Your call cannot be completed as dialed..." message.
I have an auto-attendant script on our CCME system that I wish to perform tasks upon attempting to transfer a call to an "invalid number". Problem is it is reporting to the script as 'busy' and not performing the correct tasks.
Is there a way to get a call to a non-existent number on our CCME system to give a system message or report differently than a fast busy so that the script will detect it properly and run the right code?
Re: Dialing an "Invalid Number" produces a fast busy on CCME
when you are writing your script you collect the digits then you use the extension to user statement, if that is unsuccessful you can put the play prompt you have reached an invalid extension there, then redirect them back to main menu. let me know if you would like a copy of this
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...