LibreSBC is a Session Border Controller, a network function which secures voice over IP (VoIP) infrastructures while providing interworking between incompatible signaling messages and media flows (sessions) from end devices or application servers. LibreSBC designed to employed in Enterprise infrastructures or any carrier network delivering commercial residential, or typically deployed at both the network edge and at carrier interconnects, the demarcation points (borders) between private production environment and other service providers.
SBCs commonly maintain full session state and offer the following functions:
Allow multiple networks to communicate through the use of a variety of techniques such as:
- Advanced NAT Traversal Capabilities
- SIP normalization via SIP message and header manipulation
- Call Party Translatation
- VPN connectivity
- Protocol translations between UDP, TCP & TLS
- Built-in Powerful routing module.
- Allowing control routing by 3rd-party software with via HTTP
- Dynamic Load Balancing, Failover, Distribution
Protect the network and other devices from:
- Malicious attacks such as a denial-of-service attack (DoS) or distributed DoS
- Toll fraud via rogue media streams
- SIP Malformed Packet Protection
- Topology hiding by back to back user agent (B2BUA)
- Malformed packet protection
- Encryption of signaling (via TLS) and media (SRTP)
- Access Control List
- Smart IP Firewall
The QoS policy of a network and prioritization of flows is usually implemented by the SBC. It can include such functions as:
- Resource allocation
- Rate limiting include call per second (cps), concurrent calls (ccs)
- Traffic Optimization by token bucket and leaky bucket
- ToS/DSCP bit setting
Offer border-based media control and services such as:
- Media encoding/decoding (SRTP/RTP)
- DTMF relay and interworking
- Media Codec transcoding: G711, G729, OPUS.
- Tones and announcements
- Data and fax interworking
Support to intergrate with 3rd-party system or customer function easily
- Flexible JSON Call Detail Record (CDR), Send CDR to Webhook or Database server
- Customization routing mechanism via HTTP API
- Network capture support: Live Capture and Intergrated with Homer
- SNMP and/or Prometheus monitoring
- Distributed System
- Active-Active Cluster Concept
- Healthcheck and Failure Autodetect
- System Under Test
- OS: Debian 4.19.132-1 x86_64 (10.6)
- CPU: Intel(R) Xeon(R) CPU X5670 @ 2.93GHz
- RAM: 8GB; SSD: 128GB
- Result:
- 50 call per second, 1000 concurent call
- Used Memory: 1730M, CPU Load: 26%, Call Duration: 600 seconds