• Programmable-sbc
  • sip-routing
  • SBC-Policy
Programmable-sbc1 sip-routing2 SBC-Policy3

Overview
Features
Policies
Programmability
Modules
Appliances

Service Orchestration & Programmability

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 Programmability and Service Orchestration

Policy based Monetization

Service Providers want to monetize individual service infrastructure features that are considered as resources shared by all applications rather than part of individual applications. This gives them fine-grained, policy driven control of services.

 

SBC enables infrastructure monetization through its awareness of several infrastructure features by providing quota and concurrency limits for these features. These include:

  • Voice Calls
  • Video Calls
  • Multi-Party Audio Conferencing (Bridges)
  • Trans-Coding among different codecs
  • Call Recording
  • Pre-Paid Online Charging with unit reservation via RADIUS
  • Diameter based client with Pre-paid or Post-Paid Charging scenarios

 Programmability of SBC enables further monetization 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.

 

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 systems 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.

 

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 in a unified and centralized manner include:

    • Call Recording
    • Mid-Call Announcements
    • Company Directory
    • Call Parking Server
    • Music On Hold Server
    • Personalized Ring-Back Tones Server
    • Content Streaming Server
    • Voice broadcasting 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 accounts, usually on separate hardware. This increases cost substantially when dealing with hundreds, even thousands of enterprise accounts.

 

Service orchestration layer, coupled with Media Routes Application Delivery Platform 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.

  


Copyright All Rights Reserved 2006 to 2013 @ Media Routes Inc