System failover and survivability
158 Administering Avaya 9601/9608/9608G/9611G/9621G/9641G IP Deskphones SIP
Comments? infodev@avaya.com
● ListOfMaintenanceData
● ListOfTimers
● VMONInfo
● ListOfRingerOnOffData
● ListOfNumberFormatRules
● ListOfIdentities
● MWExt
● VMNumber
If the getAllEndpointConfiguration request fails, the deskphone does not continue with the other
Session Manager requests. In this case, the getContactList request doesn't occur causing no
contacts and no "New" softkey to be displayed in the Contact list.
Failover/failback behavior
System performance
The survivability characteristics of the system as a whole are dependent on the configuration
and behaviors of all the SIP network elements such as phones and proxy servers as well as the
traditional network elements like routers and DNS servers. The endpoint detects a failure within
approximately 90 seconds of the time the failure occurs when TCP or TLS connections are
used. Once a failure has been detected, the endpoint completes its selection of an ‘Active’
controller within approximately 5 seconds.
With simultaneous registration, available in a multiple Session Manager environment with SIP
software Release 2.6, both failover/failback transition time and behavior is minimized.
Deskphone behavior during failover
During failover, 9600 Series SIP IP Deskphones will:
● Locate multiple controller addresses in priority order,
● Detect the availability of each controller,
● Transition automatically to lower priority controllers whenever a high priority controller fails
or becomes unreachable (automatic failover),
● Transition from lower priority controllers to a high priority controller (failback) either
automatically or as a result of explicit administrator activity,
● Preserve active calls to the greatest extent possible in the event of a transition, and
● Preserve as many call and system features as possible when operating under failure
conditions.
To Next Page
Loading...
