The Avaya Ready Now® is a cloud-based service offer that requires Avaya products to be deployed in a distributed architecture. The endpoints and gateways operate in local NAT address domains at the branch office sites, while the Avaya server products remain in the data centers. The data centers also operates in a private address space. The Avaya SBC supports end-to-end communication from the data centers to reach out across public service provider networks and ultimately serve the branch office sites.

You can use Avaya SBC to access PRI trunk, DCP phones, Analog phones from branch to One Cloud Private core through public internet or SD-WAN. The feature should keep media optimized and local to branch for all cases of PRI trunk. DCP phones, Analog phones, and SIP phones from within the same branch or across branches with a common NAT. Avaya SBC provides media access to the One Cloud Private core if any media treatment is required from the One Cloud Private data center.

The G4xx gateways operating as an Edge Gateway are on the public network side of the Firewall from the Avaya SBC. While Avaya Products within the Data Center communicates with IP Addresses. The Edge Gateway tunnels H248 signaling into a TCP/TLS connection toward port 2944 on the Avaya SBC. The Avaya SBC acts as H248 Proxy server to modify the address fields and forward these messages on toward TCP port 2944 on the Communication Manager.

The Single IP support mechanism is developed to ensure that the same listen IP can talk to a unique connect IP towards Avaya Aura®Communication Manager. To identify each gateway uniquely, Avaya SBC is provisioned with a unique gateway serial ID. This gateway serial ID is configured from H248 Servers. The existing real IP of the gateway is replaced with the gateway serial ID. This support essentially allows all gateways to talk to one public IP of Avaya SBC on the public side. On the internal side, the feature has two functionality based on:

• If multiple private IPs are used for gateway registration on Avaya Aura®Communication Manager, then the Avaya SBC must perform multiplexing and de-multiplexing.
• If a single IP is used that requires changes on Avaya Aura®Communication Manager side to manage the gateway registrations using media gateway ID. The gateway sends TPKT0 packet with gateway serial ID, which Avaya SBC uses to identify connect interface towards Avaya Aura®Communication Manager. On each relay, there must be a unique gateway attached.