Audiocodes SBC Resilliency
DC Separation
Here the SBCs are separate installations that are not linked, this provides geographic redundancy. TPO controls the failover between SBCSs through the in SIP Private wire gateways "Proxies" or PBX cluster "node addresses".
Upon failover the TPO will restore to the secondary SBC. For PWs the TPO will attempt to keep the call alive on the turret whilst it fails over. For DDIs the call will be lost during the transition.
HA Pair
The Audiocodes SBC can be deployed as a HA pair for additional resiliency. Here the SBCs in a HA pair are linked together with a separate management network interface, each device then has a unique IP on this interface and call state and configuration is passed between the devices. SBCs in a HA pair must be in the same geographic location but HA pairing can be comined with DC separation.
The IP address of other interfaces then is only used by the active SBC in the pair. This way devices such as TPO are not even aware of the failover between the active and passive SBC in the pair and as such all calls are held up with a very short audio blip during transition.
|
|
|
|
|
|
There is an additonal cost to licensing when required for use on a HA pair
|
|
|
|
|
|
The HA status can be viewed under Monitor-> Monitor
You can enact a HA Pair failover manually by setup-> Administation -> Maintenance -> High availability Maintenance
|
|
|
|
|
|
In Azure it is not recommended as gives little benefit
|
|
|
|
|
|
|
