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


Policy enforcement

SDP supports policy enforcement capabilities on both Access and Peering sides of the network. The policies are enforced at four levels:

Global Policies

These policies are enforced at a global level. Policy profiles can be created for Access as well as Peering side. The following policies can be provisioned in these profiles:

Access Policy Profiles

  • Are Registrations to be handled by SDP or passed through as intelligent proxy to core network while maintaining bindings for NAT traversals?
  • Is SIP digest Authentication via RADIUS enabled for Registrations?
  • Is Session Concurrency Authorization enabled for the client (based on its source IP address or username)?
  • Is Admission control enabled based on total Bandwidth quota per originating IP Address at the global access level?
  • Is user Authentication enabled based on source IP address?
  • Are Emergency calls to be handled?
  • Are any number translations to be applied according to given rules?
  • Are there any Header manipulation rules to be applied for Interoperability and SIP capability mismatch with core SIP servers?
  • Is RADIUS based Accounting enabled for sessions?
  • Is file based Accounting (CDR generation) enabled for sessions?
  • Is Media to be handled through relaying or trans-coding or only signaling is to be handled on access side in this core network while Media travels directly end to end without involving SDP?
  • Are any particular Media codecs to be filtered out before forwarding to core network?
  • Is Media Trans-coding enabled on Access Side on this core network?
  • Are there any service level policies defined?

Peering Policy Profiles

  • Is Media to be handled through relaying or trans-coding or only signaling is to be handled in this core network on Peering side i.e. when sending calls to other domains or PSTN terminators while Media travels directly end to end without involving SDP?
  • Is Media Trans-coding enabled on Access Side on this core network?
  • What types of Routing methods are to be invoked while Routing calls? Options include:
    • ENUM for toll bypass
    • External Routing query via SIP (302 Redirect)
    • Local LCR
    • RADIUS based Route Authorization (for Static Priority Routing and LCR override)
    • Local dial plan (based on JavaScript regular expression)
  • Are any number translations to be applied according to given rules before sending to terminating peer?
  • Is Lawful Intercept enabled for this session?
    • Does a special signaling CDR to be generated for Lawful Intercept purposes?
    • Does this call need to be recorded for Lawful Intercept purposes?
  • Are there any Header manipulation rules that should be applied for Interoperability and SIP capability mismatch with Peering SIP servers?
  • Is RADIUS based credit Authorization enabled before attempting SIP Sessions to Peers?
  • Is RADIUS based real-time Accounting enabled for sessions going to Peers?
  • Is file based Accounting (CDR generation) enabled for sessions going to Peers?

Service Level Policies

These policies are defined at the service level. Service profiles can be created on a per service type basis. The policies that are the same as on the global level are over-ridden by policies at this level since these are more specific than their global counterparts.
SDP is aware of several service specific parameters. It can also detect if a particular session request is incoming for the service subscriber or outgoing call made by the subscriber (mainly applies to retail services such as Residential VOIP or IP-PBX etc.). Please note that some of these policies are applied at Access level while others during Peering, depending upon the nature of the service.
The following policies can be provisioned in these profiles:

Service Policy Profiles

  • Is Session Concurrency Authorization enabled for the subscribers of this service?
  • Is Admission control enabled based on total Bandwidth quota for each subscriber in this service?
  • Is user Authentication enabled for subscriber’s outgoing calls based on username (SIP Digest) using RADIUS?
  • Is credit Authorization enabled for subscriber’s outgoing calls based on RADIUS (prepaid scenario)?
  • Is RADIUS based real-time Accounting enabled for service sessions?
  • Is file based Accounting (CDR generation) enabled for service sessions?
  • Are there any Header manipulation rules to be applied for Interoperability and SIP capability mismatch with this service’s SIP Application Server?
  • Is Media to be handled through relaying or trans-coding or only signaling is to be handled for this service while Media travels directly end to end without involving SDP?
  • Are any particular Media codecs to be filtered out or re-ordered for this service?
  • Is Media Trans-coding enabled for this particular service?
  • Are there any subscriber level policies defined for this service?
  • Is there any additional service orchestration and/or policy enforcement logic to be invoked for this service?


Subscriber level Policies

These policies are defined at the individual subscriber level. They are applied after recognizing the service and the subscriber. The policies that are the same as on the service level are over-ridden by policies at this level since these are more specific than their service level counterparts. Please note that some of these policies are applied at Access level while others during Peering, depending upon the nature of the service. The following policies can be provisioned in these profiles:

Subscriber Policy Profiles

  • Is Session Concurrency Authorization enabled for this subscriber?
  • Is Admission control enabled based on total Bandwidth quota for this subscriber?
  • Is user Authentication enabled for this subscriber’s outgoing calls based on username (SIP Digest) using RADIUS?
  • Is credit Authorization enabled for this subscriber’s outgoing calls based on RADIUS (prepaid scenario)?
  • Are any particular Media codecs to be filtered out or re-ordered for this subscriber?
  • Is there any additional service orchestration and/or policy enforcement logic to be invoked for this subscriber (for service feature extension, policy driven promotions, loyalty programs, streaming of specific media content e.g. announcements and advertisement for free users) ?

Peering partner level policies

These policies are defined for each terminating or Peering partner. These are independent of any service and applied while sending SIP calls to the terminating peer. These policies over-ride any global Peering side policies or specific service or subscriber level policies applicable to Peering (if defined). The following policies can be provisioned at this level:

Peering Partner Policy Profiles

  • Is there a specific code to be pre-fixed before the called destination (Technical Prefix) for this terminator? This code can be over-ridden by Route Authorization.
  • Are there any Header Manipulation rules that should be applied for Interoperability and SIP capability mismatch while Peering with this particular terminator?
  • Are any particular Media codecs to be filtered out while Peering with this terminator?
  • Does the Peering partner require Authentication when sending INVITES based on username/password i.e. SIP Digest?

Service Orchestration & Mediation

SDP is a programmable SIP server. It is a scalable and high performance service orchestration engine that enables fine-grained and advanced control of SIP Sessions. It can be used to:

  • Create new SIP based services
  • Extend, enhance and manipulate the functionality of existing SIP servers
  • Enforce fine-grained policy decisions for service monetization
  • Add new policies and service logic on the fly via simple JavaScript based scripting without modifying source code
  • Perform deep packet inspection and SIP header manipulation via simple scripting
  • Create complex services from other SIP Application Servers as building blocks acting as a SCIM
Mediate between multiple Enterprise systems using their exposed API to create powerful, telephony enhanced business applications



Use cases of SCIM

Convert any post-paid service into pre-paid

Many Service Providers offer multi-media services that are currently being charged in a post-paid fashion for subscribers. They want to add the prepaid charging option for any specific services to expand the subscriber base as well as create further service differentiation by defining flexible prepaid, post-paid service bundles and packages combining multiple applications and services for monetization.
SCIM and service orchestration capability enables such powerful offerings for Service Providers. With SCIM, they can insert the SDP as a probe and implement service logic for prepaid charging for incoming and outgoing calls. Several integrations and mediations are required for this use case, some of which may include Integration with:

    • Online charging systems via RADIUS for credit Authorization and Accounting
    • Payment gateways
    • Order Management and Provisioning
    • Subscriber self-care portals for personalized service management

            In addition, unit reservation and quota management is an essential requirement for the SIP
Application to realize this use case in order to prevent the subscriber balance from going into
negative.


Federated IP PBX across geographical locations with centralized dial and route plan management

Enterprises have separate and isolated, on-premises IP PBX systems installed in different branch offices. Also, these days, several Enterprises are shifting to hosted IP-PBX solutions with IP Telephony Service Providers. Unification and integration of these systems is usually an extremely cumbersome exercise at best, and many a times not even technically possible. Enterprises therefore are forced to continue with non-unified PBX systems because of the heavy costs and technical difficulties involved.
SCIM and service orchestration capability can enhance the SBC functionality to realize the use cases of a federated IP-PBX. Several use cases can be realized in this regard some of which include:

    • Centralized Dial Plan management
    • Centralized Routing Plan management
    • Application of additional service logic to handle calls between different geographical locations e.g. centralized company directory and Auto-Attendant

Extending PBX, UC and Call Center functionality across geographical locations in a unified manner

Similar to the federated IP-PBX use case above, enterprises also face a different challenge when dealing with different isolated, on-premises IP-PBX, Unified Communication servers and Call Center solutions. Since these on-premises PBX systems may have been from different vendors at different times, there could be gaps and differences in functionality and features. An enterprise faces a tough challenge when trying to standardize on a feature across the enterprise campuses and branch offices but not all installed PBXes support it. For example, an enterprise wants to provide Fixed Mobile Convergence throughout the enterprise but many legacy PBX systems installed in different campuses do not support it.
SCIM and service orchestration can be a highly valuable tool in such cases. Fixed mobile convergence application can be used with enhanced service logic to provide the functionality to all branch offices in a unified manner. Some of the other services that can be provided through SCIM in a unified and centralized manner include:

    • Call Recording
    • Mid-Call Announcements
    • Multiple, Rule-based Auto-Attendants
    • Company Directory
    • Call Parking Server
    • Music On Hold Server
    • Personalized Ring-Back Tones Server
    • Content Streaming Server
    • Voice broadcasting Server
    • Bulk Auto-dial out server
    • IVR Consolidation Server

Convert off-the-shelf non-multitenant PBX, UC and Call Center Application Servers into multi-tenant systems

Service Providers want to monetize SIP applications such as PBX, Unified Communication servers and Call Centers. If they buy normal, off the shelf systems for this purpose, these systems are usually for a single enterprise and do not support multiple corporate accounts with isolation and confinement of interfaces and subscriber management. They have to install separate instances of these Application Servers for each such corporate account, usually on separate hardware. This increases cost substantially when dealing with hundreds, even thousands of enterprise accounts.
SCIM and service orchestration layer, coupled with subscriber and order management, quota manager module and self-care portals can provide all the essential use cases for a multi-tenant SIP Applications environment where each enterprise operates in an isolated virtualized partition on the same SBC system and uses the SIP service realized on a third party product that is not aware of multiple enterprises.

Policy based service monetization

Service Providers want to monetize individual services based on policy driven control of services. This can be achieved by creating service differentiation based on features and class of service e.g. video versus audio only, premium HD voice versus normal voice, bulk messaging, Quality of Service Control for Premium accounts and different Service Level Agreements for different service levels. In addition, they require support of feature and bonus Add-Ons, promotions, loyalty programs etc. such as Free minutes and Friend and Family numbers etc. Usually, such monetization features are available only through advanced billing and Pre-paid Management systems.
SCIM functionality, coupled with PCRF, Quota Manager and Subscriber and Order Management modules can provide several such use cases including:

    • Differentiated service offerings
    • Differentiated CDRs for extensive monetization granularity
    • Prepaid Authorization
    • Subscriptions and Add-Ons with Authorizations
    • Promotions, loyalty programs and free minutes

Commercial Offering Models

  • Entry Level
  • Enterprise Edition
  • Carrier Edition



 
 
Contact Now!



Tel: +1 (416) 900 5593

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