During the OVA deployment

Using the CLI command EASGManage after deployment

Open a ticket to Avaya services and request to enable it

Using SMGR web GUI, check the "Enable EASG" check box on the desired component in the Inventory/Manage Elements screen

Using the SDM after the deployment

Network Address Translation (NAT)

Avaya Session Border Controller for Enterprise (SBCE) public IP-address

Split Horizon DNS with FQDN

Virtual Private Network (VPN)

Two-party calls originated by SIP stations or trunks, and terminated by H.323 trunks, media gateways, or other vendors' H.323 stations, will typically shuffle if CM is configured to do so.

Two-party calls originated by H.323 stations, trunks, or media gateways, and terminated by SIP stations or trunks, cannot shuffle.

SIP-SIP two-party calls will always use SIP Direct Media if Communication Manager (CM) is configured to do so.

H.323-H.323 two-party calls will always shuffle to establish a direct media path if CM is configured to do so.

If a direct media path cannot be established between two IP endpoints the call will fail from release 7.0.