SBC Features

Owned by Nathaniel Halbrooks
Nov 15, 2023
2 min read

 

Simple Licensing

  • Sangoma has very intuitive licensing model.

  • Product is licensed based on number of calls.

  • A SIP Session is considered a single leg of the call. Thus two sessions are needed to complete a full duplex call.

  • Example: 8000 SIP Sessions on SBC can provide a 4000 call paths capacity

  • SBC's are licensed based on Call Paths

Simple and Predictable

  • Aside from sessions licensing there are NO

  • Per feature licensing

  • Per user licensing

  • Per codec licensing

  • All features, codecs are included in the license.

  • Sangoma only counts INVITE as a session.

This allows a network planner a predictable SBC capacity in every situation.

Other vendors use draconian licensing schemes 
Example: Phone “Registration” counts as a session when the call is made In this SBC case capacity is reduced further due to the licensing model.

 

 

Media Anchoring and Complex Calls

  • Proxy based PBXs require Sangoma SBC when connected to a SIP trunk.

  • PBX needs an SBCs in order to perform complex  call functions such as blind transfers and call forking.

PBX Isolation

  • Sangoma SBC is able to isolate the enterprise PBX from the ITSP and provide rich media functions.

  • Without the Sangoma SBC acting as the demarcation point between the PBX and ITSP, unwanted SIP messages such as REFER would reach the ITSP.

  • In such cases ITSP would simply reject such messages causing call failures.

  • In other cases ITSP has strict rules as to which call flows are supported and allowed.

 

SIP-XandeZuce

  • Sangoma full interoperates with SIP-X based PBXs and facilitates secure demarcation point.

  • While offering media anchoring support to the PBX.

Advanced XML Routing and Database Support

  • Sangoma SBC’s have SoftSwitch style routing plans.

  • Users can configure an unlimited number of dial plans/routing rules per sip profile.

  • All routing plans can be applied live without system interruption.

  • The rules can be very simple or very complex.

  • They support complex syntax for advanced logic and customization.

Database Support

  • Complex routing rules, DIDs, and ACL lists are usually stored in internal or external Databases.

  • Sangoma SBC supports external database access via HTTP requests.

  • For each routing table entry an HTTP request to an external DB can be used to fetch routing information.

  • Sangoma SBC support internal database via mysql for routing plans, ACL lists and etc.

  • For each routing table entry an HTTP request to an internal DB can be used to fetch routing information.

  • HTTP access allows user to map any DB info into the Sangoma SBC routing logic.

Per Message Routing and Header Manipulation

  • Routing rules are executed for each SIP message.

  • Actions can be taken based on any SIP message that flows through the SBC.

  • SIP Headers can be modified using regular expressions for each SIP message.

Advanced Networking

  • Most large networks require complex networking support.

  • Sangoma SBC supports: VLAN, DiffServ, QOS, Firewall, etc.

 

Load Balancing and Least Cost Routing

  • Sangoma SBC offers carrier features to the Enterprise SBC.

    • Load Balancing allows Sangoma SBC to distribute the call load to the number of ITSP providers.

  • In case of ITSP failure, the call load can be re-routed to other ITSPs.

  • Least Cost Routing tables can be used to route calls based on route costs.

  • Take advantage of favorable rates.

Media Server and Trasncoding

Sangoma SBCs offer rich media services along with full featured: 

  • Transcoding.

  • VQE Features

  • Echo Cancellation, Noise Reduction, AGC,etc…

  • Codecs

  • G729, G722, AMR,etc…

  • Fax (FoIP)

  • T.38 Pass-Through

  • T.38 Relay (roadmap)

  • T.38 SRTP (roadmap)

 

Some codes such as AMR-WB will reduce session capacity in certain scenarios.

 

 

Configurable Load Limit Messages

  • What separates the Sangoma SBC from others is that when this threshold is reached the

  • SBC will reply with a SIP 503 Service Unavailable message which tells the originator to try an alternate destination.

  • In other SIP appliances once the CPU threshold reaches a certain point the traffic is disrupted by means of calls

  • Dropping, loss of RTP (ifmedia is flowing through), or registrations becoming corrupted.

Configurable Load Limit Message

  • Sangoma SBC allows one to configure the load limit message: 501, 403etc…

  • This allows greater flexibility and customization to custom network needs.

 

 Yes   No

 

Return to Documentation Home I Return to Sangoma Support