Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c86e9b2550016ec54396b5000a, userName='null'}
JIRAIDAUTHSBX-108268
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cdb30a83, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a0c85652e498015697f3e3b3000b, userName='null'}


Panel

In this section:

Table of Contents
maxLevel4


This page includes

Spacevars
0model5
performance metrics.

Provisioning Capacities

Caption
0Table
1SBC 5400 Performance and Capacity


SpecificationCategorySBC 5400 Platform

SIP/GW Call Set-up

Call set-up rate700 cps
Call latency30ms @ 700cps
Sessions by Signaling Protocols*SIP75,000
Sessions by Codec*G.729 (20 ms)75,000
G.711 (20 ms)75,000
RTCP Sessions Scale
1:1 with RTP sessions
RegistrationsInitial register rate with no calls, in registers per second
(Includes initial Register Authentication)		1250
SecurityTLS connections set-up rate
(without mutual authentication)		750
Maximum number of IPSec tunnels2,048 (4,096 IPSec SAs)
IPSEC (IKE) setup rate150
Maximum number of SRTP sessions75,000
Maximum number of registered subscribers on IMS AKA256,000
Subscribers




Over UDP with an interval refresh REGISTER of 1800 sec.600,000
Over UDP/NAT with an interval refresh REGISTER of 30 sec.225,000
Over UDP/NAT with an interval refresh REGISTER of 60 sec.300,000
Over TCP with an interval refresh REGISTER of 300 sec.425,000
Over TLS with an interval refresh REGISTER of 300 sec.375,000

* The session count represents the aggregate number of sessions on one system.

Info
titleNote
  • The SBC 5400 supports 75K passthrough calls standalone.
  • The recommended peak capacity in HA systems is 68.5K calls.


Pass-Through With/Without sRTP


Caption
0Table
1Pass-Through with sRTP
3Pass-Through with sRTP


Codec

Packet Size

10 ms

20 ms

40 ms

G.711

28,000

50,00075,000

G.729

32,000

64,00075,000




Caption
0Table
1Pass-Through Without sRTP
3Pass-Through without sRTP


Codec

Packet Size 

 

10 ms

20 ms

30 ms

40 ms

G.711

50,000

75,000

75,000

75,000

G.726

50,000

75,000

75,000

75,000

G.729

50,000

75,000

75,000

75,000

G.722

50,000

75,000

75,000

75,000

AMR (12.2k) -BWE

N/A

75,000

N/A

75,000

AMR (12.2k) -OA

N/A

75,000

N/A

75,000

eVRC

N/A

75,000

N/A

75,000

eVRC-B

N/A

75,000

N/A

75,000

G.722.1

N/A

75,000

N/A

75,000

AMR-WB - BWE

N/A

75,000

N/A

75,000

AMR-WB-OA

N/A

75,000

N/A

75,000

iLBC - 20 ms

N/A

75,000

N/A

75,000

iLBC - 30 ms

N/A

N/A

75,000

N/A

G.723.1

N/A

N/A

75,000

N/A




H.323 Performance Metrics


Caption
0Table
1SBC 5400 H.323 Performance Metrics


Specification

CategoryLimit
H.323 Call setup Call setup rate250 cps
Call latency50 ms @ 250 cps
Fast start or tunneled H.245 calls

SIP-H.323 or GW-H.323

30,000
H.323-H.32315,000
Separate H.245 calls (50 ms @ 200 CPS)SIP-H.323 or GW-H.3234,000


 


Maximum Initial (challenged) REGISTER Rate with Background Load


Caption
0Table
1Maximum Initial (challenged) REGISTER Rate with Background Load (SIP calls/second)
3Maximum Initial (challenged) REGISTER Rate with Background Load



Initial SIP 
Registration/Sec

Number of 
Subscribers

Interval of Refresh
REGISTER
(seconds)

SIP Calls/Sec

UDP

800225,00030200

1,500

300,00060300

TCP

1,000425,000300300
TLS750375,000300300


 


SIP Session and Registration Capacity Limits


Caption
0Table
1SIP Session and Registration Capacity Limits
3SIP Session and Registration Capacity Limits



SessionsSIP Calls/SecCall Hold
(seconds)		Refresh REGISTER
Interval (seconds)		Subscribers

Non-TLS Peering

75,000

700

107


TLS Peering

74,400

600

124

UDP

72,000

40018030225,000

72,000

50014460300,000

TCP

54,000500108300425,000


Include Page
_TCP_Buffer_Size_64KB_Limitation
_TCP_Buffer_Size_64KB_Limitation


Video Calls Metrics


Caption
0Table
1Video Calls Metrics
3Video Calls Metrics


Specification
Limit

SIP-SIP conference sessions (media anchored) consisting of five streams: audio, main video, content share video, far end camera control (FECC), and floor control (BFCP)

20,000
SIP-SIP conference sessions with direct media20,000
SIP-SIP conference sessions500 cps
H.323-H.323 video sessions (media anchored) comprising up to two media streams (one audio, one video)4,000
H.323-H.323 video sessions40 cps


 


SUBSCRIBE/NOTIFY Benchmark for SBC 5400 (with ERE)

SUBSCRIBE/NOTIFY benchmarking metrics for

Spacevars
0model5
are provided below.

Caption
0Table
1SUBSCRIBE/NOTIFY Benchmark for SBC 5400 (with ERE)


Scenario

SUBSCRIBE

REGISTER

Calls

SUBSCRIBE /Sec

REGISTRATION/sec

CALLS/Sec

SUBSCRIBE From Unregistered user

1,500,000



300



SUBSCRIBE with 50,000 Calls

500,000


50,000

300


600

SUBSCRIBE with 40,000 calls and 128,000 Registrations (Calls from Registered user)

400,000

128,000

40,000

300

600

600

SUBSCRIBE with 256,000 Registrations (subscribe from registered user)

1,000,000

256,000


300

600




Dynamic Capacities

The SBC 5400 can support up to 75,000 simultaneous calls.

  • Combination of RTP and RTCP calls.
  • SRTCP and SRTP with 40 ms or larger packets.
Note

The SBC 5400 can be subject to bandwidth limitations that prevent the total call count from reaching 75,000.

Sessions

The following table lists the SBC 5400 session limits:

Caption
0Table
1Sessions


Functionality
SBC 5400
Call recording sessions (NICE/SIPREC)32,000
Lawful Intercept Sessions2048
Media capture tool (MCT) sessions10

NP-based DTMF detection (simultaneous digits)

1,024
NP-based DTMF insertion (simultaneous digits)1,024

Pagebreak