Application Center Administration enables synchronization of the Avaya Experience Platform™ On-Prem entities such as Extensions, Agents, Reason Codes, and System parameter features from the Avaya Aura® systems that are on-premise to the cloud.
The following types of synchronizations are available in Application Center Administration: Manual full synchronization and Automated incremental synchronization.
Manual full synchronization:
In Application Center Administration, trigger a manual full synchronization to synchronize or resynchronize ranges of all the entities configured in the voice plans for Communication Manager.
Note:
Your system administrator must include your account in the Synchronization for Communication Manager feature toggle. Otherwise, you cannot perform manual full synchronization.
You must trigger a manual full synchronization when a Communication Manager server is set up for synchronization of voice plan ranges for different entities or when bulk changes are made to the entities on the on-premise server.
You must trigger a manual full resynchronization when bulk changes are made to voice plan definition, or a new big voice plan is added to a Communication Manager server that is already set up for manual full synchronization.
Automated incremental synchronization:
In Application Center Administration, automated incremental synchronization occurs automatically when an entity in the configured voice plan range is added, updated, or deleted in Avaya Experience Platform™ On-Prem for Communication Manager or System Manager.
Note:
Your system administrator must include your account in the Synchronization for Communication Manager and Auto-incremental Synchronization for Communication Manager feature toggles. Otherwise, you cannot enable automated incremental synchronization.
You can choose to enable or disable automated incremental synchronization for a Communication Manager element. If you choose to enable automated incremental synchronization, you must perform a minimum of one manual full synchronization of all the entities for the automated incremental synchronization to come into effect.
After you configure automated incremental synchronization, synchronization occurs every 5 minutes for any detected change in the voice plan range configured for Communication Manager.
Application Center Administration displays the date and time of the last change detected on on-premise after a minimum of one manual full synchronization is performed.
When you add a new voice plan range or update an existing voice plan range, perform a manual full synchronization to include the changes for automated incremental synchronization.
Note:
Application Center Administration maintains the history related to the following number of job details and the status details:
If the administrator configures the System Manager user with two Communication Manager profiles where one of the Communication Manager Endpoint Profile is set as Agent and the other Communication Manager Endpoint Profile is set as Endpoint, the user created in Application Center Administration synchronizes the following data:
First Name from System Manager
Last Name from System Manager
Login Name from System Manager
Email Address from System Manager
Extension from System Manager
Agent Login ID from Communication Manager
Agent Password from Communication Manager
Communication Address with Avaya SIP Handle and Domain from System Manager
Communication Profile Password from System Manager
User-Agent association from System Manager
User-Extension association from System Manager
Aux Work Reason Codes from Communication Manager
System parameter features entities such as Redirection on No Answer, ROOF, and IP Failure Reason Code Type from Communication Manager.
Application Center Administration applies the following business rules when dealing with multiple Communication Profile sets from System Manager:
If there are two CM endpoints, Application Center Administration selects one CM Endpoint Profile with Agent type and another CM Endpoint Profile with Endpoint type.
If multiple Communication Profile sets have CM Endpoint Profile with Endpoint type, Application Center Administration selects one from the Communication Profile Set marked as Primary. If no Communication Profile Set is marked as Primary, Application Center Administration selects the CM Endpoint Profile with Endpoint type from the first Communication Profile Set in the list.
If multiple Communication Profile sets have CM Endpoint Profile with Agent type, Application Center Administration selects the Communication Profile Set marked as Primary. If no Communication Profile Set is marked as Primary, Application Center Administration selects the CM Endpoint Profile with Agent type from the first Communication Profile Set in the list.
Application Center Administration applies the following business rules when dealing with multiple Communication Addresses from multiple Communication Profile sets from System Manager:
If there are two CM endpoints, Application Center Administration selects the Communication Profile Set containing the selected CM Endpoint Profile with Endpoint type.
If no Communication Profile Set contains CM Endpoint Profile with Endpoint type, Application Center Administration selects the Communication Profile Set containing the selected CM Endpoint Profile with Agent type.
Communication Addresses with the following types are supported: Avaya SIP and Avaya E.164.
If there is Avaya SIP and Avaya E.164, Application Center Administration prefers Avaya SIP over Avaya E.164.
If there are multiple Avaya SIPs, Application Center Administration chooses the one that matches the extension. Otherwise, Application Center Administration picks the first one.
If there are no Avaya SIPs but multiple Avaya E.164, Application Center Administration chooses the one matching the extension. Otherwise, Application Center Administration picks the first one.
