NAT IP Address Per SBC Device

Live Platform now supports NAT configuration at the SBC device level, making it easier to manage environments that use multiple layers of NAT.

Previously, NAT IP addresses could only be set at the Tenant (Service Provider) level, mainly to support customers connecting to Live Platform through VPN where Local Load Balancer limitations required a Tenant-level NAT. However, when customers host their own SBC and use a shared User Management Pack 365 or floating license server, they often connect through VPN with an additional NAT on their side. In these cases, the Tenant NAT IP is already in use by the Local Load Balancer, preventing Live Platform from correctly discovering the SBC devices located behind the customer’s NAT.

To address this, you can now configure a NAT IP per SBC device. This is done using the new 'NAT IP Address' field in the AC Device Details dialog box when adding a device (Topology > Devices).

When NAT is configured on various levels in Live Platform, the following NAT priority is used:

■

WebSocket tunnel

■

Device NAT IP

■

Tenant NAT IP