This sounds very strange, the first thing I would do is double check the scripts. Actually, have someone besides the author check the scripts. If that turns out to not be the issue ensure you're running the latest version of the IP IVR. In addition, you can turn up app tracing on the MIVR logs.
I have tripple checked the scripts and i am the author. When writing the scripts i do a deburg and all steps is working fine. even after calling in live to the scripts working fine and suddenly i get calls stating that the ToD is not working.
I then goes into the script and debugs and there it is. When hitting the ToD variable it jumps over all times and moves on to next variable.
I will have to remove the existing ToD and add it again and then it works just fine. Very very strange problem. The problem is that i dont know what to look for in the MIVR logs and also i dont know exactly when this happens.
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...