...
Noprint | |||||||||
---|---|---|---|---|---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
In this section:
|
To understand the role of a Session Border Controller, let us break the term down to its basic elements:
Table of Contents | ||||
---|---|---|---|---|
|
Div | ||
---|---|---|
| ||
|
A call leg is defined as a single connection between the SBC and another device. So a session between two devices includes a call leg between device A and the SBC, and a call leg between the SBC and device B.
A call may require a single session or it may require multiple sessions resulting from call forking, conference call, call transfer, call recording or other mechanisms. For example, a call between two registered users through a feature server consumes two sessions: one session from User A to the Feature Server and one session from the Feature Server to User B.
The total number of concurrent sessions supported on the SBC platform may be limited by different factors, including:
...
A customer has purchased a 5,000 package of licenses, calls are coming in and egressing the SBC with no call forking – so each ingress and egress is one session. The maximum number of active calls is 5,000.
Caption | ||||
---|---|---|---|---|
| ||||
A customer has purchase a 5,000 package of licenses. Calls are coming in and getting transferred back through the SBC. Each call consists of two sessions, so the maximum number of simultaneous active calls is 2,500.
Caption | ||||
---|---|---|---|---|
| ||||
...
Info |
---|
...
| ||
For multiple transfers, each new GCID and SIP REFER is considered a session. |
Typically, these sessions will traverse one or more IP networks, whether on an enterprise network or multiple service provider networks. The SBC sits at the border of each network in order to control the amount and type of sessions, as well as the type of data that can be used during these sessions. In this sense the SBC is part firewall, protecting the network from malicious IP traffic, and part traffic cop, policing how much traffic can enter the network in order to prevent overloads.
The SBC is a controller, which means it controls not only whether traffic can enter the network, but where it should be sent (referred to as session routing) and what type of modifications should be made to the traffic (example, transforming a SIP message header into an H.323 message header or downgrading an HD voice call to a compatible voice codec).
Noprint |
---|
...
The Sonus
Spacevars | ||
---|---|---|
|
Sonus SBC Edge
Sonus SBC Core
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Info |
---|
The focus of this documentation space is on the SBC Core platforms. To view SBC 1000/2000 product documentation, |
...
navigate to https://doc.rbbn.com/display/ALLDOC/SBC+1000-2000+Documentation. |
The
Spacevars | ||
---|---|---|
|
The
Spacevars | ||
---|---|---|
|
The
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
...
Noprint |
---|
...
Pagebreak |
---|
Caption | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
|
...
|
...
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
The following table lists the number of ports and storage capacities of the various
Spacevars | ||
---|---|---|
|
Caption | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
...
|
...
...
Pagebreak |
---|