My Unity has failed over from the Primary to the Secondary but I cannot see any logs of it in the Event viewer. I checked all the CiscoUnity_NodeMgr logs but it does not show when and why it failed over.
Port 1 typically means a normal failover but it's still worth investigation. If a call comes in on an odd port like something beyond the first few, I would check your Calling Search Space and Partitions on callmanager and make sure no phones have access to the voice port phone numbers for dialing. Sometimes people don't do this and someone fat fingers an internal extension that dials a port on the secondary and triggers failover. Yours looks like it either hit RNA or NA on the primary and went direct to the failover. Again, this is assumption without proper logs. If you have the right logs enabled to investigate this, open a TAC case. If this is occuring often, again, open a TAC case so appropriate logs can be enabled for next failure and gathered after for analysis.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...