Ppm Synchronization; Failover/Failback Behavior - Avaya 9601 Administering

PPM synchronization

As part of PPM synchronization the deskphone performs a getAllEndpointConfiguration request.
This request contains the following EndpointConfigurationFields:
• VolumeSettings
• LinePreferenceInfo
• ListOfOneTouchDialData
• ListOfButtonAssignments
• SoftMenuKeyList
• DialPlanData
• ListOfSpeedDialData
• ListOfMaintenanceData
• ListOfTimers
• VMONInfo
• ListOfRingerOnOffData
• ListOfNumberFormatRules - applies only when registered to a Session Manager (SM)
• ListOfIdentities - only when registered to a SM
• MWExt - applies only when registered to an SM
• VMNumber - applies only when registered to an SM
If the getAllEndpointConfiguration request fails, the phone does not continue with the other PPM
requests. In this case the getContactList request doesn't occur causing no contacts and no "New"
softkey to be displayed in the Contact list.
Related Links
Controller Determination and Survivability Activity

Failover/failback behavior

Related Links
Controller Determination and Survivability Activity
System performance
Deskphone behavior during failover
System performance
The survivability characteristics of the system as a whole are dependant 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
August 2015 Administering Avaya 9601/9608/9611G/9621G/9641G/9641GS IP Deskphones SIP
on page 131
on page 132
Comments on this document? infodev@avaya.com
Controller Determination and Survivability Activity
on page 127
on page 127
131