...
Add_workflow_for_techpubs |
---|
|
Key Features
The following table lists the key features of
. Caption |
---|
0 | Table |
---|
1 | 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 (see SBC SIP Transparency Implementation Guide)
| 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 | |
|
...
...
Back to Top
Functional Differences
The following table lists the primary functional differences between the
models in this release. = Supported
= Not supported
Div |
---|
|
Caption |
---|
0 | Table |
---|
1 | SBC Core Functional Differences |
---|
| |
|
...
...
Refer to Fax Over IP. | - 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
| | | | |
|
|
...
...
...
Refer to SBC Redundancy for details. | Maximum number of call legs | 1/2 of UDP media port range | 1/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
( |
|
|
...
Maximum number varies based on:
...
...
| 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
|
|
|
...
...
...
...