I have an auto attendant with menu options 0, 1-4, and the ability to press # to transfer to another extension.
Very frequently people are trying to access an internal extension and ending up at the wrong place, which happens to be one of the menu options. I feel there is a possibility of user error, but have no way of proving it without a log of what was pressed to get to the extension.
Is there any way to trace this in the Unity call handler?
You can go into Unity, go to System Reports and run a Call Handler Traffic report.
What you may also want to do to avoid misdials is "unlock" the number for the menu option that overlaps your extensions. Most likely you have the key set to "Lock this key to this action". That could save you years of headaches and complaints!
I went ahead and unlocked the keys so they wouldn't instantly dial, and also exposed the error messages as well so I could redirect incorrect key presses back to the same call handler. I think this will solve my issues.
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...