after you change the max retry number in the CRA script (yes that is the right place where you need to change it), you have to load the script so that the CRA understands the new script.. Reboot does not do this..
Try doing this. Then, look at MIVR traces. Check why it is going thru more than the configured retries.
1. Is it using a different script?
2. Is it not recognizing the change you made in the script?
3. Is it recognizing the change and just doing something wrong? If that is the case, call tac.
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...