Skip to end of metadata
Go to start of metadata

In this section:

Modified: for 5.0.1

 

Key Features

The following table lists the key features of  SBC Core.

Table : SBC Core Key Features

Features

Description

General

  • Stand-alone system platforms
  • HA system platforms
  • 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)

Routing/Policy

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

(see Routing and Policy Management)

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

(see Security)

Media/Multimedia 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
  • ICE (see SDP Support)
  • WebRTC (see SBC for WRTC)

Management

Billing

 

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 Core Functional Differences

Feature

SBC 5000 Series

SBC 7000 SeriesSBC SWeReference
ePSX integration(tick)(tick)(error)See Routing and Policy Management,

T.38 (V3/V0) pass-through fax calls

(tick)(tick)(tick)See Fax Over IP.

Fax transcoding:

  • G.711–T.38 (V3) fax transcoded calls
  • T.38 (V3)–T.38 (V3) fax transcoded calls
(tick)(tick)(error)See Fax Over IP.
DTMF detection (NP-based)(tick)(tick)(error)See DTMF and RTP Relay.
EVRC-B codecs(tick)(tick)(error)See Audio Support.
GW-GW signaling(tick)(tick)(error)See Configuring Gateways (Features Guide), Zone - Gw Trunk Group (EMA), zone gwTrunkGroup - CLI.

Link Detection:

Physical link detection
ICMP Ping
ARP Probing

 

(tick)
(tick)
(error)

 

(tick)
(tick)
(tick)

 

(tick)
(tick)
(error)

See SBC 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 Provisioning Limits for details.

MSRP(tick)(tick)(error)

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

SIP Trunk Group profiles:

1K
4K
4K/10K
4K/40K

 

(tick)
(tick)
(tick)
(error)

 

(tick)
(tick)
(tick)
(tick)

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 Provisioning Limits for details.

Standby packet port support

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