You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

In this section:

 

Key Features

The following table lists the key features of 

Unable to show "metadata-from": No such page "_space_variables"
.

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)
  • Transparency Profile (refer to SBC SIP Transparency Implementation Guide)

Routing/Policy

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

(refer to 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

(refer to Managing Security for security best practices)

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

Lawful InterceptRefer to Lawful Intercept for additional information.

 

Functional Differences

The following table lists the primary functional differences between the

Unable to show "metadata-from": No such page "_space_variables"
models in this release.

(tick) = Supported
(error) = Not supported

SBC Core Functional Differences

Feature

SBC 51x0/52x0

SBC 5400SBC 7000 SeriesSBC SWeReference
  • G.711–T.38 (V0) fax transcoded calls
  • G.711–T.38 (V3) fax transcoded calls
  • T.38 (V0)–T.38 (V0) fax transcoded calls
  • T.38 (V3)–T.38 (V3) fax transcoded calls
(tick)(tick)(tick)(error) Refer to Fax Over IP. 
GW-GW signaling(tick)(tick)(tick)(error)Refer to Configuring Gateways (Features Guide), Zone - Gw Trunk Group (EMA), Zone - GW Trunk Group - CLI.

Link Detection:

Physical link detection
ICMP Ping
ARP Probing

 

(tick)
(tick)
(error)

 

(tick)
(tick)
(error)

 

(tick)
(tick)
(tick)

 

(tick)
(tick)
(error)

Refer to SBC Redundancy for details.

Maximum number of call legs

1/2 of UDP media port range1/2 of UDP media port range

Determined by:

  • number of IP addresses per interface
  • UDP media port range

 

(Refer to 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

(Refer to SBC Provisioning Limits for details).

SIP Trunk Group profiles:

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

 

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

 

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

 

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

 

(Refer to SBC Provisioning Limits)

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

Refer to SBC Provisioning Limits for details.

Standby packet port support

(error)(error)(tick)(error)Refer to SBC Redundancy for details.
KPML DTMF support(tick)(tick)(tick)(error) 

 

  • No labels