we are testing a SIP integration from UC7.x to CUCM 7.x with HA - we are forcing the secondary to stop taking calls. What should the user experience be in this scenario, we have to wait atleast 75 seconds before failover kicks in (i.e the primary starts taking the calls). Doing the same test using a sccp integration shows much better results i.e the failover is initiated within seconds. Any advise / previous experience of this would be appreciated...TIA, Jeff
Pressing the "stop taking calls" button isn't really a fair comparison. When you press that button with the SCCP integration, it unregisters its ports, so CUCM immediately can't route calls to it. If things go down where neither side is aware the failure occurred (e.g. pull the ethernet cable to the server), then times will be more similar.
That said, you may be able to improve things for SIP by tweaking the SIP trunk profile. You may try adjusting the SIP retry INVITE counter to 3 or other such timers.
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...