Products -> Service Delivery -> Session Border Controller
AdvOSS SBC (Session Border Controller) provides powerful border control functionality by allowing control and manipulation of signaling and media packets for secure VoIP communication.
Overview
Features
Technical Use Cases
Business Use Cases
Modules
Appliances

Business Use Cases


AdvOSS SBC supports and enables several important business use cases for Service Providers. Some of the major use cases include but not limited to the following:

  • Terminator Network Management
    SBC provides a Vendor Management Module that allows an operator to define terminators, their trunk groups and their IP addresses. More advanced use cases include defining the capability set of the trunks specially the codecs supported by it and the capacity available on the IP.

  • Incoming Calls
    Incoming calls to subscribers require their CPEs (Customer Premises Equipment) to register with a SIP registrar so that the SBC can locate the endpoint through its registered IP address when an incoming call comes in. For this purpose, AdvOSS SBC provides a SIP registrar that takes registration requests from endpoints, authenticates them through any of the supported means and keep registrations alive waiting for incoming calls.

  • Connection to Radius Server
    Most real-time systems including Charging and Rating Engines, different types of User Identity Repositories, Authorization servers, accounting system etc. are integrated behind a Radius AAA Server. AdvOSS SBC comes with a Radius client that allows to connect to any external Radius server which is then used to fulfill multiple use cases.

  • User Authentication
    User Authentication is the process of identifying the user behind any incoming request. Depending on the security framework used, different variations are used for this purpose. AdvOSS SBC supports new request authentication using Radius AAA client or can also query a locally attached database or a text file.

  • Prepaid
    Running a prepaid network requires that each session be authorized before it is allowed to commence. AdvOSS SBC provides interface to a Radius AAA server that allows for Authorization of the session before it starts. The AAA Server returns a permission to start the call after looking at the available credit as well as the rate for the destination called and gives the total amount of time allowed for the call. AdvOSS SBC then disconnects the call when the allotted time expires. In more advanced use cases where a single customer may be doing multiple concurrent calls, AdvOSS SBC provides a client to an online charging system that issues small amounts of units periodically and then AdvOSS SBC goes back to the online charging system to issue more time for each ongoing session. This allows more granular prepaid control over the ongoing sessions

  • Accounting Interface
    When the sessions terminate, Accounting needs to be done. AdvOSS SBC can write completed sessions CDRs into a text file or into a locally attached database. It can also write CDRs over the accounting interface to an external Radius Server.

  • Connection to Least Cost Router
    Least Cost Routing servers like AdvOSS LCR have all the rate sheets from the terminators stored in them and have the capacity to look up the least cost route for any session that is about to start. They then need to communicate the details of the selected Terminator back to the SBC which is responsible for call completion. AdvOSS SBC offers different ways to connect to an external LCR. If the LCR supports SIP signalling as AdvOSS LCR does, then the SBC sends the call to the LCR and the LCR sends back a SIP 302 redirect message that indicates to the SBC who the selected terminator is. If the external LCR does not have SIP interface, then AdvOSS SBC supports Radius based interface overloading the Authorization request to get least cost route information or also has the support to call any external API through multiple provided interfaces.

  • NAT Traversal
    When the endpoints are behind NAT, then the SBC needs to have arrangement to traverse the NAT to reach the endpoints behind NAT. AdvOSS SBC supports different ways to do this. The most fail-proof way of achieving this is to do full media proxy on both sides and AdvOSS SBC through its attached media server is fully capable of doing it.

  • Media Transcoding
    When the sender wants to use a codec not supported by the receiver, transcoding between codecs is needed. Transcoding requires full media proxy and is a CPU intensive process. AdvOSS SBC through its attached media server fully supports media transcoding between most common codecs. To save on the CPU, some operators use external hardware based or even cloud based transcoding servers. AdvOSS SBC fully supports both models and can forward media streams to external transcoders and manage them accordingly.

  • Simultaneous Ringing
    Simultaneous Ringing is a process where a single call is sent to multiple endpoints and the user can pick up the call from any of the endpoints and the calls to the rest of the endpoints are cancelled. AdvOSS SBC through its forking proxy, allows to send requests to multiple endpoints at the same time and when one of them is answered, it cancels the others.

  • Multiple Private IDs
    Customers may like to have multiple devices attached to a single Public ID. When the call comes to their Public ID, they want it to ring on all the devices simultaneously. AdvOSS SBC registrar allows users to register using multiple Private IDs against the same Public ID. This way when an incoming call comes, the registrar returns multiple endpoints and SBC through its forking proxy forks calls to all of them simultaneously. Once the user answers through any of the IDs, the calls to other IDs are cancelled.

  • Topology Hiding
    Topology Hiding involves hiding the topology of the core network from external entities and also hiding the IP addresses of the originator from the terminator and vice versa. To achieve this, AdvOSS SBC works as a B2BUA (Back to Back User Agent) which means that it terminates the incoming calls onto itself and then originates a fresh call towards the terminator. The two call legs belong to the same session but do not share any information of one party with the other. To complete topology hiding even of the media streams, AdvOSS SBC comes with full media proxy functionality.

  • Multiple Application Servers Support
    When offering services through application servers, the SBC is put on the border and the application servers are put inside the core network. AdvOSS SBC through its IFC module allows to define multiple Application Servers and to define Initial Filter Criteria which is evaluated on each incoming call from the outside and the call is then forwarded to the configured Application Server inside the core

  • Multiple Service Support
    Operators providing multiple services over SIP / IMS have multiple application servers in the core serving those services. AdvOSS SBC offers IFC module which is fully aware of multiple services and allows to evaluate the correct service asked by the originator and forwards the call to the configured application server.

  • Real-Time monitoring
    AdvOSS SBC comes with Session Management module that inserts each session into a database as it is authorized and then removes it from there when the session terminates. A GUI provides real-time view into the sessions and any other mechanism can be established to view ongoing sessions.

  • 10 or 7 digit dialing
    10 digit dialing requires that users within the same country can dial within the country without first dialing the country code. 7 Digit dialing requires an awareness of the caller’s area code and it then allows users to call within their area code only by dialing the last seven digits. AdvOSS SBC comes with a number translation module that allows multiple configurations and can even append the caller’s area code behind the called digits if it finds only seven digits in the called number. Digit length for countries with other lengths can be adjusted as per configuration.

  • E911 Support
    Most retail services would need support for E911 or other emergency numbers. This requires that calls to such emergency numbers are not sent for any Authentication or Authorization. AdvOSS SBC is fully aware of such emergency numbers and provides different ways to reach E911 provides when such calls come including failover mechanisms to PSTN breakout numbers in case the IP links cannot be established.

  • Recharge DIDs
    Recharge DIDs are special phone numbers which are running a recharge IVR hosted by the operator. Customers who have run out of credit may have their services suspended and to allow them to charge through such special DIDs require that SBC sitting on the border be aware of those numbers and if any call comes to those numbers, then it would not authorize the caller but would not send the call for Authorization as the authorization would be denied by the credit control application. AdvOSS SBC comes with a special numbers module that allows an operator to define its Recharge DID numbers as exceptions where the Authorization is skipped

  • Secure Communications
    Secure communications require all SIP messages to be encrypted by the sender before they are sent. This requires SBC to decrypt the messages when they arrive. To provide secure communications on both legs, SBC requires to encrypt the signal again before sending to the terminator. AdvOSS SBC support TLS encryption on both legs for this purpose.

  • Congestion Control
    All elements in a system have limits on the number of requests that they can process in a given time window like a second. When originators are allowed to send multiple concurrent calls, they may cause congestion by sends requests in bursts. Even if SBC can handle the burst, there may be other elements inside the core or behind AAA Servers or even on terminator networks that may not sustain such bursts. In such situations it is important to control such bursts and the process is called Congestion Control. AdvOSS SBC provides two modules for this purpose. Admission Control offers a limit on the number of requests that an endpoint can send in a period of time. Once this limit is exceeded, any further requests are not entered into the core and are sent appropriate congestion messages. If an endpoint exceeds an even higher burst rate, further requests from the said endpoint are discarded without a reply. This protects the core network from messages that it cannot handle. Other than admission control AdvOSS SBC also offers Rate Limiting which means that it throttles the requests going out to Application Servers in the core or onto terminators which they cannot handle.

  • DOS / DDOS Prevention
    DOS (Denial of Service) attacks are illegitimate requests coming in large bursts from an identified endpoint with the purpose to overload the system and make it unavailable for legitimate users. AdvOSS SBC provides Admission Control that allows such endpoints to be blocked although for such endpoints a layer 4 restriction in the firewall may be a better alternative. A DDOS (Distributed Denial of Service) attack sends a large number of illegitimate requests but all of them appear to be coming from different sources. If layer 4 techniques fail in such situations, AdvOSS SBC uses advanced layer 7 techniques to mitigate such attacks. Details of such behavior depends on the overall deployment and business model.

  • Incompatibility Removal
    With different network elements outside communicating with others in the Operator’s core network, incompatibilities may arise at times when some of them do not conform to the details of the SIP protocol. In such situations, AdvOSS SBC sitting at the border provides means through its protocol correction module to fix such errors.

  • Terminator Capacity Control
    AdvOSS SBC provides Session Management which provides a real-time view of all ongoing sessions. This module together with Vendor Concurrency Management module provides a way for SBC to know available capacity on all routes and discard the routes on which the capacity has met its limit. This improves the overall call completion rate and post dial delay

  • Terminator Failover
    AdvOSS SBC provides failover mechanisms to secondary terminators in case the primary terminator fails the connection. It has the ability to figure out if the call was rejected because of congestion reasons and it will give them another try through other sources.

  • Classes of Service
    AdvOSS SBC supports TechPrefixes which are extra digits which are issued to originators that they can append behind dialed digits to indicate the class of service that they need. AdvOSS SBC removes those digits and sends the actual dialed digits to other network elements. It can also be configured to send the TechPrefix separately into any request which can then be consumed by other network elements for their configured purposes.

  • Outgoing Toll Bypass
    Provided ENUM based look ups to directly communicate to service providers over IP that have exposed their networks over ENUM protocol. Saves all toll charges paid to terminators for such calls and most of the times improves the voice quality as well.
  • Incoming Toll Bypass
    Allows the Service Provider to expose its support DIDs over ENUM protocol so that other service providers can connect to it bypassing their toll charges.



Other Industry Names for This Product:


- Session Border Controller
- B2BUA (Back to Back User Agent)
- Media Proxy Server



 
 
Contact Now!



Tel: +1 (416) 900 5593

E-mail: sales@AdvOSS.com
Address:
Suite 401, 50 Burnhamthorpe Road W.
Mississauga, ON L5B 3C2, Canada