SBC Apolocore · v3.3

Session Border Controller for secure VoIP networks

The solution that combines security, border, wholesale and billing. Apolocore sits at the edge of your network to interconnect customers and suppliers, protect every SIP session and keep traffic under control.

SBC Apolocore dashboard
10,000concurrent calls
300 CPSper node
10,000Concurrent calls
300Calls per second
300KSubscribers
100MCDR records
1+1High availability
Applications

One platform for operators and enterprises

Apolocore is installed at the edge of the operator network or in front of business PBXs, creating a secure border between networks.

Provider & operator border

Interconnect customers and suppliers through a single controlled border, hiding your internal topology.

Enterprise & remote users

Trunk connectivity for business PBXs and secure remote registration of users outside the office.

Traffic balancer

Absorb call center avalanches and distribute high-CPS traffic across several IP-SIP nodes.

Unified dial plans

Turn fragmented PBX and UC environments into one integrated system with unified dial plans and policies.

Wholesale & billing

Automatic billing, multi-currency, multi-vendor products and unlimited rates in the same platform.

High availability

Automatic 1+1 switching for SIP trunks and interconnections, with cluster and multi-balancer support.

Architecture

Border, balancer and gateway in one scenario

The Border Solution is designed for telecommunications operators. It creates a border between providers and the operator core, presenting to the networks only the SBC SIP headers and protecting the configuration of the operator core.

  • Balancer gateway with N routes or providers
  • Routing, priorities and channel limits
  • Border gateway to the PSTN for IN/OUT routing
  • Runs on VMware, KVM/OpenStack, AWS, Azure or physical servers
Apolocore border architecture diagram
Technical features

Built for carrier-grade traffic

General

  • UDP, TCP and TLS
  • IPv4 & IPv6
  • SNMP support
  • RTP management
  • SIP register client
  • Private & public SIP
  • Multi-networking
  • RTC support

Main modules

  • Dashboard & reports
  • Traffic balancer
  • Routing & priority
  • ANI random
  • Automatic billing
  • CDR reports
  • Performance module
  • IAMD for call centers

SIP security

  • User-Agent lists
  • GeoIP blocking
  • Security routing prefix
  • Traffic protection
  • ANI blocking
  • Automatic lock
  • Fraud detection
  • Transaction check

Capacities

  • CPS300
  • Concurrent calls10,000
  • Subscribers300,000
  • Group balancer20
  • RoutesUnlimited
  • CDR database100M
  • RatesUnlimited
  • Client managementYes
FAQ

Why your VoIP network needs an SBC

Why do I need a Session Border Controller?
VoIP traffic travels over IP networks, which makes it vulnerable to attacks such as denial of service (DoS). An SBC is the first line of defense between your network and untrusted IP networks, using intrusion detection and prevention, rate limiting, blacklists and advanced call control. It also handles codecs, protocol normalization and hides your internal topology.
What is an SBC and how does it work?
A session border controller regulates and protects IP communications. It sits on the frontier of your VoIP network and covers security, connectivity, quality of service and compliance, acting as a back-to-back user agent that splits SIP transactions into server and client parts.
How does Apolocore protect against attacks?
When SIP messages pass through the SBC it replaces the addresses of internal components, limits traffic to prevent DoS, rejects malicious or malformed SIP content and applies dynamic SIP firewall rules, GeoIP and User-Agent filtering.
  • DoS and DDoS protection
  • Topology hiding
  • Fraud and ANI blocking
Where can I deploy it?
On VMware, KVM/OpenStack, Amazon AWS, Microsoft Azure or physical servers, as a single node or in a high-availability cluster.
Contact

Talk to an SBC specialist

Tell us about your network and traffic volume. We will propose the right architecture and licensing.

  • Architecture sizing for your traffic
  • Online demo of the web interface
  • Cloud or on-premise licensing

Request information

Security code