When integrating the Avaya Aura Web Gateway (AAWG) to support Avaya Spaces Calling, the Avaya Aura Media Server (AAMS) plays a persistent role in the media path.
WebRTC Translation: Avaya Spaces Calling utilizes WebRTC technology. Because standard telephony components (like Avaya Communication Manager or traditional deskphones) often use different codecs or signaling methods than web-based clients, the AAMS acts as the media anchor.
Media Processing: Unlike traditional SIP-to-SIP calls where media can often be "shuffled" (Direct IP-to-IP) to save bandwidth, calls involving the Web Gateway generally require the AAMS to stay in the loop to manage the transcoding and media relay between the WebRTC world and the Aura core.
Duration: The AAMS remains in the signaling and media path for the entire length of the call to ensure stability and compatibility between the web-based caller and the telephony destination.

BD: Administering Entity Link between Presence Services Cluster SIP Entity and Session Manager Procedure
1. On the System Manager web console, navigate to Elements > Routing > Entity Links.
2. In the Name field, enter a name for Entity Link.
3. In the SIP Entity 1 field, select the Session Manager instance.
4. In the Protocol field, select TLS.
5. In the Port field, type 5062.
Note: Note that this port number cannot be the same as the port number administered in
"Administering Entity Link between Avaya Breeze and Session Manager".
CD: Administering Entity Link between Avaya Breeze and Session Manager.
About this task
Create an En2tity Link to connect Session Manager to Avaya Breeze. You must administer separate Entity Links for Avaya Breeze servers in order to open SIP listeners on the designated ports.
Session Manager requires a Listen Port with the Listen Port as 5061, Protocol as TLS, and Default Domain as the login domain of endpoint devices. Without this, PPM will fail for SIP endpoints.
https://downloads.avaya.com/css/P8/documents/101013646