User failed over, manual failback mode

Last Updated : Dec 11, 2012 |

This event occurs when one or more users fail over to their nonprimary, redundant Session Manager and the Global failback policy is set to manual.

Manual failback policy means that without manual intervention, the failed over users stays on this nonprimary Session Manager forever. This event reflects a notification of a potential problem and not loss in service.

You can find the primary Session Manager defined on the User administration page in Communication Profile and Session Manager Profile section as the first drop-down menu.

The possible causes for this event are:

  • The primary Session Manager is not running.

  • The user lost connectivity with the primary Session Manager due to network issues or any other reason.

  • The primary Session Manager is currently in the Deny New Service state.

  • The primary Session Manager is currently overloaded.

  • The primary Session Manager is in an error state which is preventing the user from receiving service from it.

Troubleshooting User failed over, manual failback mode

Procedure

  1. Make sure the Session Manager is up and running.
  2. Verify the Session Manager is in the Accept New Service state.
  3. Check the SIP Entity Monitoring page to see if there are any network connectivity problems to the primary Session Manager.
  4. Using the User Registration page:
    1. Find the affected users.
    2. Select the affected users.
    3. Click the Failback button.
  5. Change the Global Failback Policy on the Session Manager Administration screen from Manual to Auto.
  6. If none of these steps work, contact your Avaya support representative.