You require Avaya Aura® Device Services to search for corporate contacts in Avaya Aura®, Avaya Experience Platform™ On-Prem, and enterprise directory sources to transfer or consult. Without Avaya Aura® Device Services, the agent needs to know the number to transfer the call. This applies even if the number to transfer the call belongs to another Avaya Experience Platform™ (On-Prem + Connect) agent. Hence, you must configure Avaya Experience Platform™ (On-Prem + Connect) with Avaya Aura® Device Services for an optimal agent experience.

Avaya Aura® Device Services also provides dialing rules support for outgoing calls. On the original number that an agent dials from Avaya Workspaces, dialing rules are automatically applied and prefixed with different codes as applicable. Avaya Aura® uses the newly formed number to evaluate how to route the call.

For detailed instructions on deployment of the supported Avaya Aura® Device Services version, see https://documentation.avaya.com/bundle/DeployingAvayaDeviceServices_R10.1.1/page/Avaya_Aura_Device_Services_overview.html.

• In networks where connections to an Avaya Aura® Device Services instance go through Avaya SBC placed in a DMZ, you must perform additional configurations for the reverse proxy. For complete information about reverse proxy configuration, see https://documentation.avaya.com/bundle/DeployingAvayaDeviceServices_R10.1.1/page/Checklist_for_reverse_proxy_configuration.html.

• You can configure Avaya Aura® Device Services to be accessible to remote workers using Avaya Workspaces from outside the enterprise network. For specific information about remote access configuration, see https://documentation.avaya.com/bundle/DeployingAvayaDeviceServices_R10.1.1/page/Remote_access_configuration.html.