Depending on the network size and service requirement, you can deploy Avaya SBC in one of the following configurations:
Standalone configuration: In the standalone configuration, the SBC and EMS coreside in the same server. In this deployment, the phones maintain two separate socket connections to the SBC, at two different IP addresses hosted by the SBC.
Multiple server configuration: A multiple server configuration requires the EMS and the SBC to be deployed on different servers.
High availability (HA) configuration: A High availability (HA) configuration requires a separate EMS server. SBC HA pairs can be deployed in an enterprise in a parallel mode configuration. In the parallel configuration, the signaling packets are routed only to the active or primary SBC, which performs all data processing. The interface ports on the standby SBC do not process any traffic. The Management interfaces on the SBC appliances have different IP addresses, but the signaling or media interfaces have the same IP address. Upon failover, the standby SBC advertises its new MAC as the L2 address for the common IP address. The SBC devices are synchronized via the heartbeat on the dedicated interfaces, and both SBC devices are in continuous communication with the EMS.
These configurations are also available with deployment in the virtualized environment.
Avaya SBC is packaged as a vAppliance (OVA) ready for deployment on VMware certified hardware to run in VMware environment. Avaya SBC is also delivered in vAppliance (OVA) format for VMware based deployments. Avaya SBC has a single OVA file for EMS, SBC+EMS, and Avaya SBC only deployment. The .ova file is available in PLDS. This configuration supports VMware features, such as vMotion, HA across datacenters, and mixed hardware configuration.
For more information about virtualization, see Deploying Avaya Session Border Controller on a Virtualized Environment Platform.
