AVAYA DOCUMENTATION CENTER
Find answers to your technical questions and learn how to use our products
Administering Avaya Session Border Controller
Media unanchoring scenarios
Avaya SBC can release media when:
-
Both endpoints or ends of the call pass through the same Avaya SBC
-
Both end points can negotiate with the same media format, SRTP or RTP
This section covers a few scenarios in which Media unanchoring can be used.
Remote workers in the same subnet
As the endpoints are in the same subnet, the Avaya SBC can be configured to flow the media directly between the endpoints.
Remote workers in two different subnets
Avaya SBC can be configured to release the media between two different subnets. The subnets must be reachable to flow the media.
Remote workers behind the same NAT
When Avaya SBC detects that both remote workers in the call are behind the same NAT device, Avaya SBC can enable media flow directly between the remote workers.
Remote branch office with Avaya SBC
In this scenario, the endpoints belong to two different subnets. However, one of the endpoints is behind a NAT device, and the other subnet has remote Avaya SBC. The Core Avaya SBC can be configured to release the calls between these subnets by using the remote Avaya SBC. To release the media from core Avaya SBC, enable the has remote sbc flag during Session Flow configuration.
Remote branch office with Avaya SBC
In this scenario, the endpoints belong to two different subnets, and one of the subnets has remote Avaya SBC. The Core Avaya SBC can be configured to release the calls between these subnets.
Calls between remote workers and Trunk users with same Avaya SBC
In this scenario, a call is established between remote worker from one subnet to the trunk subnet user. As these endpoints pass through the same Avaya SBC, the Avaya SBC device can be configured to release media between these endpoints. Both subnets must be reachable.
Calls between two trunks with the same Avaya SBC
In this scenario, a call is established between two different trunk subnet users. As the endpoints pass through the same Avaya SBC, the Avaya SBC device can be configured to release media between these endpoints. Both subnets must be reachable.
Trunk behind firewall and Remote branch office with Avaya SBC
In this scenario, one subnet belongs to the trunk connected to Avaya SBC, and the other subnet has a remote worker connected to Avaya SBC with remote Avaya SBC. The core Avaya SBC can be configured to release calls between these subnets, by using the remote Avaya SBC. To release the media from core Avaya SBC, enable the has remote sbc flag during Session Flow configuration.
Back-to-back Avaya SBC deployment
In this scenario, core and DMZ Avaya SBC devices can be configured to release the media between the endpoints. For more information, see the section for back-to-back Avaya SBC deployment.
Back-to-back-to-back Avaya SBC deployment
In this scenario Remote, DMZ, and core Avaya SBC devices can be configured to release the media between the endpoints. For more information, see the section for back-to-back-to-back Avaya SBC deployment.