| Event Id | 1049 |
| Source | CiscoUnity_NodeMgr |
| Description | Service 1: Failback from partner server 2. |
| Event Information | According To Cisco: This occurs when a failback event is initiated from the secondary server. In other words, the secondary Unity server was active and processing all calls and either the Failback button was pressed from the Failover Monitor tool on the secondary server or a scheduled failback occurred (as configured in the Failover Monitor tool). The primary server will now assume the role of the active Unity server. You will see event IDs 1033, 1029, and in a Cisco CallManager integration you will see the TSP ports re-register with event IDs 110, 103, and 101. You will then see an event 1051 from the CiscoUnity_Notifier source and an MWI resynch is initiated (Event ID 1063). The process is complete when you see an event ID 1047 from CiscoUnity_NodeMgr. |
| Reference Links | Cisco Events Guide |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.