AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
Administering the Avaya Aura® Web Gateway
Signaling and media path topology when clients are located in or near different data centers
In the following topology example, there are two data centers with one Avaya Aura® Web Gateway in each data center. Clients are located in different data centers outside of the firewall and registered on the Avaya Aura® Web Gateway to receive calls. When one client makes a call to the other, the call follows the following flow:
Both clients log in to the corresponding Avaya Aura® Web Gateway and activate the call service.
A client in data center 1 (DC1) gets the address of the DC1 load balancer and communicates with the Avaya Aura® Web Gateway deployed on that data center. The Avaya Aura® Web Gateway registers the client to the corresponding Session Manager deployed on DC1.
A client in data center 2 (DC2) gets the address of the DC2 load balancer and communicates with the Avaya Aura® Web Gateway deployed on that data center. The Avaya Aura® Web Gateway registers the client to the corresponding Session Manager deployed on DC2.
The DC1 Avaya Aura® Web Gateway initiates the call. To route the media, the Avaya Aura® Web Gateway uses the Session Border Controller and Avaya Aura® Media Server deployed on DC1.
The Avaya Aura® Web Gateway sends the SIP call to Session Manager deployed on DC1.
Session Manager deployed on DC1 forwards the call to Session Manager deployed on DC2.
Session Manager deployed on DC2 forwards the SIP invite to the Avaya Aura® Web Gateway from DC2, where the second client is logged in.
The Avaya Aura® Web Gateway from DC2 uses the Session Border Controller and Avaya Aura® Media Server deployed on DC2 to pass the media through the firewall to the second client.
