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

Overview
Features
Policies
Programmability
Modules
Appliances

Policy enforcement

SBC 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?

 

  


Copyright All Rights Reserved 2006 to 2013 @ Media Routes Inc