I have created a new call handler for the main greeting of the company.
I have pointed the error handler to that call handler instead of the default opening greeting. We now get blank messages from time to time in the mailbox linked to that call handler. Some of them are 5 minutes long which is the limit on recordings. The user that the message is coming from never called that call handler.
This is what they said happen.
-They called their VM when another call came in. They took the other call without hanging up the VM call. When They got back to the VM call, they didn't hear anything and then hang up.
-They called VM and didn't hear anything back so they hanged up.
If I call my Voice mailbox, and don't do anything, the call is sent to the call handler in the end. I don't understand why the system doesn't detect that the message is blank and keeps recording nothing.
Also I need the error handler to go to my new call handler for when somebody press the wrong key. Is there a way to differenciate the error when somebody doesn't press anything.
Actually... You CAN edit this from the SA but you have to make a registry hack for the error greeting to be exposed... you can find this in the AdvancedSettings tool if you want to do that.
Also, I normally reccomend folks look at AnswerMonkey.net for the latest versions of the tools (including BulkEdit). It's much "fresher" since updating it takes me just a few minutes as opposed to submitting update requests to CCO and then waiting 5 days or so before they show up - I know, I know... I need to keep both updated but you can always be sure the lastest is on AnswerMonkey. It also lets you see the version history and help files (and in some cases training videos) which are not available on CCO due to the restrictions on the way I can post info there.
you mean the Advanced Settings Tool "Expose the error greeting" option... yeah, I think you're right. It might have slipped in there in a later 2.4.6 build but I don't have one handy to test against - probably best to use BulkEdit unless you're at 3.0(1) or later...
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...
[toc:faq]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 discusse...