H.248 Proxy server

Avaya Aura® solution allows its components (Communication Manager, Session Manager, Session Border Controller, Media Gateways, and IP Phones) to be deployed in a distributed architecture. With the Edge Gateway feature, endpoints and gateways can operate in local NAT address domains at the branch office sites, while the Avaya server products remain in the data centers. The data centers operate in a private address space as well. The Avaya Session Border Controller (ASBCE) is the conversion element that supports end-to-end communication from the data centers to public service provider networks and the branch office sites.

The G4xx gateways operating as an Edge Gateway is on the public network side of the firewall from the ASBCE. Avaya products within the data center can communicate with IP Addresses whereas, the Edge gateway communicates within a NAT address space. The Edge gateway tunnels H.248 signaling into a TCP/TLS connection towards port 2944 on the ASBCE. The ASBCE acts as an H.248 Proxy server to modify the address fields and forward these messages to TCP port 2944 on Communication Manager.

Edge Gateway to SBC management link

Edge Gateway supports a new management link (MGSBC) with the Session Border Controller. The link is required to support the following:

• SNMP TRAP messages that are sent up a link to UDP port 162 on the host Communication Manager.

• The transport of SSH maintenance messages between a Communication Manager and an Edge gateway.

The Edge gateway establishes a TLS/TCP connection with the TCP port 2946 on the ASBCE when the gateway finishes booting up. This connection occurs before the establishment of the H.248 registration to expand the window of diagnostic capability for the service personnel.

Enabling Edge Gateway mode

To enable Edge mode, use the ‘SBC@ip’ address in the set mgc list gateway CLI command. For more details on enabling the Edge mode, see the Avaya Branch Gateway G450 CLI Reference guide.