Information Necessary to perform Root Cause Analysis on Unity Failover
The Information needed to troubleshoot why a Unity server running versions 4.x, 5.x, and 7.x failed over:
Mandatory: Should be Included when Opening TAC SR Desired: Follow up Information that should be collected once Mandatory Information has been collected.
Unity failover normally occurs for a few possible reasons:
Call received on the secondary server
The secondary server loses communication with the primary server (primary does not respond for 30 seconds)
Failover is manually initiated using Failover Monitor
SQL replication failures
Slow MAPI interaction with exchange
Mandatory information to get:
GUSI Cab files from both servers. This will tell us why it failed over.
For full root cause analysis, the CCM and SDL Traces from all the nodes in the cluster are necessary.(if Unity is integrated with CM). Traces should span at least 30 minutes prior to the failure. Refer to this link for CM trace collection -
I have the need to share content using a switch between a laptop, desktop and microscope, all over HDMI into a WebEx Room Kit. I used an el-cheapo Cables To Go $100 switch and it worked fine, but had a crazy lag between switching. (around...
Hello, I installed CMS 2.5.2 and I want to edit the invitation_template.txt contained in the call_branding.zip to show special character (specially accented letters). I realized they are not shown when the invitation is sent. Is there some way to include ...
Hi, good afternoon.We had a some disconnect calls incoming from PSTN with cause code 16, the calls dropped when going off-hook. The current version of CUCM is 22.214.171.124900-10, gateway H323 with E1 R2-digital. We tried a check/unchecked MTP of gateway,...
I have a small office that we have implemented SIP trunks with Centurylink and a broadband circuit. For their call volume it works great. We are looking for a failover or HA solution because the main circuit has gone out a couple of times...