Anyone running Unity 5.0 and with Failover? I noticed this the other day. In CUCM, I see my voicemail ports all registered, even the Failover ports. When I failover to Unity failover server, my primary unity server voicemail ports go unregistered (which they should) But when I failover to the primary, the failover ports stay registered.
Is this new Unity 5.0? Because in Unity 4.x, this was not the case. Unity Failover voicemail ports would "unregister" when you saw the status of them.
No, I'm pretty sure this has always been the case. This is what allows for automatic failover. The secondary server needs to keep its ports registered so that CUCM can route calls to it immediately when the primary server is unavailable or unresponsive. Conversely, the primary MUST unregister when it is inactive so that CUCM will not attempt routing calls to this in active server. Remember, all the ports are in the same Hunt List, with the primary's Line Group listed first.
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...