...
| Add_workflow_for_techpubs |
|---|
...
Key Features
| AUTH2 | UserResourceIdentifier{userKey=8a00a0c85652e4980156d51e50b20014, userName='null'} |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'} |
|---|
| REV5 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'} |
|---|
| REV6 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'} |
|---|
| REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd700a1f, userName='null'} |
|---|
| REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c90501d8, userName='null'} |
|---|
| REV2 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99d02be, userName='null'} |
|---|
|
The following table lists the key
...
features.| 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 Profile (
|
|
...
| Routing/Policy | - Integrated routing
- Embedded Routing Engine (ERE)
|
|
...
...
- DIAMETER+ queries to optional external centralized PSX Policy/Route Server with or without internal ERE fallback
( |
|
...
...
...
...
...
) | Media/Multimedia Services | |
|
...
...
- Refer to Video Codecs, Video Support)
- Text codecs (Refer to Text Codecs)
- 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 (
|
|
...
...
...
...
Back to Top
Functional Differences
The following table lists the primary functional differences between the
models in this release.
= Supported
= Not supported
| Caption |
|---|
| 0 | Table |
|---|
| 1 | SBC Core Functional Differences |
|---|
|
| Feature | SBC 5000 Series | SBC 7000 Series | SBC SWe | Reference |
|---|
| ePSX integration | | | | See Routing and Policy Management, | - T.38 (V3/V0) pass-through fax calls
- G.711–T.38 (V3) fax transcoded calls
- T.38 (V3)–T.38 (V3) fax transcoded calls
| | | | See Fax Over IP. | | GW-GW signaling | | | | See Configuring Gateways (Features Guide), Zone - Gw Trunk Group (EMA), zone gwTrunkGroup - CLI. | Link Detection: Physical link detection
ICMP Ping
ARP Probing |
|
|
| See SBC Redundancy for details. | Maximum number of call legs | 1/2 of UDP media port range | Based on number of IP addresses per interface and UDP media port range | See 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. | SIP Trunk Group profiles: 1K
4K
4K/10K
4K/40K |
|
| Maximum number varies based on - server hardware where VM is deployed
- 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 | | | | See SBC Redundancy for details. |
|
...