Skip to end of metadata
Go to start of metadata

In this section:

Key Features

The following table lists the key features of SBC Core.

Table : SBC Portfolio Key Features





  • Stand alone system
  • Optional HA system support
  • Includes an Embedded Routing Engine (ERE), performs DNS, ENUM lookups
  • Supports IPv4, IPv6, IPv4/IPv6 interworking, SIP, H.323, GW-GW, SSH, SNMP, NTP, RTP/RTCP, FTP, UDP, TCP, DNS, and ENUM.
  • Packet-to-packet call flows (B2B UA)
  • Extensive SIP signaling and session handling
  • Media relay and transcoding with pinhole control
  • Local storage
  • DoS protection
  • Crypto functions (IPsec, TLS, SRTP)
  • Integrated routing capabilities

Routing/ Policy

  • Embedded Routing Engine (ERE)
  • Standalone ePSX
  • Replica ePSX to an external PSX
  • DIAMETER+ queries to optional external centralized PSX Policy/ Route Server with or without internal ERE fallback

Robust Security

  • Topology hiding
  • DoS/ DDoS, Rogue RTP protection
  • Line rate malformed packet protection
  • TLS, IPsec (IKEv1 or IKEv2 for peering) for signaling encryption
  • Secure RTP for media encryption

Media Services

  • Audio codecs (see Audio Support)
  • Video codecs (see Video Support)
  • T.38 compliant relay or fall back to G.711, Dynamic Jitter Buffer, Fax/ Modem Detection, DTMF/Tone Relay/RFC2833/ RFC4733,
  • BFCP, FECC, H.239, Presentation



Functional Differences

The following table lists the primary functional differences between the SBC Core models in this release.

(tick) = Supported
(error) = Not supported

Table : SBC Portfolio Functional Differences


SBC 5000 Series

SBC 7000 SeriesSBC SWeReference
DTMF detection (NP-based)(tick)(tick)(error)See DTMF and RTP Relay.
ePSX integration(tick)(tick)(error)See Routing and Policy Management,
EVRC-B codecs(tick)(tick)(error)See Audio Support.
Fax/T.38 transcoding(tick)(tick)(error)This feature involves taking a G.711 call with FAX tones and transcoding to T.38, and T.38 to G.711 FAX in reverse direction. See Fax Over IP.
Fax/Modem fallback(tick)(tick)(error)This feature involves allowing a compressed call to switch to G.711 mid call for FAX transmission.
GW-GW signaling(tick)(tick)(error)See Configuring Gateways (Features Guide), Zone - Gw Trunk Group (EMA), zone gwTrunkGroup (CLI).

See IPSEC for Signaling for feature description. See Ipsec - Peer (EMA) or IPSEC Peer - CLI for configuration details.

SBC SWe supports IKEv2 as of 04.02.01R0 release.

Link Detection:

Physical link detection
ARP Probing







See SBC Core Redundancy for details.

Maximum number of call legs

1/2 of UDP media port rangeBased on number of IP addresses per interface and UDP media port rangeSee SBC SWe Performance Metrics

Two examples assuming 64,000 media port range:

  • SBC 5000 series number of call legs = 32,000
  • SBC 7000 series number of IP addresses = 6 / number of call legs = 110,000

See SBC 5000 and 7000 Series Provisioning Limits for details.

Multiple IP Addresses per interface

(error)(tick)(error)See SBC 7000 Alternate Media Addresses Support for details.

See MSRP Support for feature description. For configuration details, see:

Opus codec support(tick)(tick)(error)

See Opus Codec Support for feature description. For configuration details, see:

SIPRec, NICE, MCT and LI(tick)(tick)(error)See Session Recording Support for details.

SIP Trunk Group profiles:






Maximum number varies based on server hardware where VM is deployed and VM vCPUs / memory configuration

For example, SBC 7000 4K/40K profile is comprised of:

  • 4,000 instances each of Address Contexts, Zones, IP Interface Groups, IP Interfaces, Signaling Ports;
  • 40,000 Trunk Groups

See SBC 5000 and 7000 Series Provisioning Limits for details.

Standby packet port support

(error)(tick)(error)See SBC Core Redundancy for details.