If the customer implements Avaya Experience Platform™ Public Cloud orchestration with Avaya Experience Platform™ (On-Prem + Connect) and if all the following conditions occur, the call redirects to on-premise, the media anchor releases from Media Processing Core (MPC), and the audio path does not loop through the cloud:
As an account administrator, enable the voice feature Remote Party ID SIP Header in transfer on the Account page in Application Center Administration.
The system administrator must select the Release media anchor during transfer check box on the Element Inventory page in Application Center Administration.
As an account administrator, validate that the feature of releasing MPC anchor is enabled and effective. Ensure that the BYOC-H trunks for the Voice channel display Yes in the Release media anchor during transfer column in Application Center Administration.
Note:
Application Center Administration and MPC for Avaya Experience Platform™ Public Cloud must use identical naming conventions for BYOC-H trunks.
The Avaya Session Border Controller administrator must enable the SIP REFER feature for the tenant on Avaya Session Border Controller. The administrator must perform the following tasks:
Create a Server Profile with SIP REFER Handling Enabled.
Attach the Server Profile to Session Manager that handles SIP calls from the MPC of Avaya Experience Platform™ Public Cloud.
Create a Rule to route SIP REFER calls to Session Manager.
Apply the Routing Rule to the Call Flow from the MPC of Avaya Experience Platform™ Public Cloud to Session Manager.
Avaya Experience Platform™ Public Cloud orchestration receives an incoming end user interaction from on-premise through BYOC-H.
The end user goes through the IVR and makes a selection that requires Redirect to External to on-premise through the same BYOC-H trunk.
The end user and agent can talk to each other.
The system administrator must validate that SIP REFER on the same trunk is working by checking the MPC trace.
