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

Compare with Current View Page History

« Previous Version 19 Next »

In this section:

 

This page includes

Unable to show "metadata-from": No such page "_space_variables"
SIP and H.323 performance, registration and capacity metrics.

Pass-Through With/Without sRTP

Pass-Through without sRTP

 

Codec

Packet Size

10 ms

20 ms

30 ms

40 ms

G.711

75,000

99,000

112,000

119,000

G.726

85,000

150,000

150,000

150,000

G.729

85,000

150,000

150,000

150,000

G.722

75,000

99,000

112,000

119,000

AMR (12.2k) -BWE

 

150,000

 

150,000

AMR (12.2k) -OA

150,000

150,000

eVRC

150,000

150,000

eVRC-B

150,000

150,000

G.722.1

150,000

150,000

AMR-WB - BWE

150,000

150,000

AMR-WB-OA

150,000

150,000

iLBC - 20 ms

150,000

150,000

iLBC - 30 ms

 

150,000

 

G.723.1

150,000

Pass-Through with sRTP

 

Codec

Packet Size

10 ms

20 ms

40 ms

G.711

60,000

90,000

110,000

G.729

65,000

120,000

150,000

H.323 Performance Metrics

H.323 Performance Metrics

Specification

CategoryLimit
H.323 call set-up Call set-up rate300 cps
Call latency50 ms @ 300 cps
Fast Start or Tunneled H.245 calls

SIP-H.323 or GW-H.323

32,000
H.323-H.32316,000
Separate H.245 callsSIP-H.323 or GW-H.32316,000

Maximum Initial (challenged) REGISTER Rate with Background Load

Maximum Initial (challenged) REGISTER Rate with Background Load (SIP calls/second)

 

Initial SIP 
Registration/Sec

Number of 
Subscribers

Interval of Refresh
REGISTER (Seconds)


SIP Calls/Sec

UDP

1,500

450,000

30

250

2,500

600,000

60

350

TCP

2,000

850,000

300

500

TLS

1,500

750,000

300

420

SIP Session and Registration Capacity Limits

SIP Session and Registration Capacity Limits

 


Sessions


SIP Calls/Sec

Call Hold
(seconds)

Interval of Refresh
REGISTER (seconds)


Subscribers

Non-TLS peering

121,500

1,350

90

 

TLS peering

108,000

1,200

90

UDP

60,000

700

90

60

600,000

45,000

500

90

30

450,000

TCP

85,000

950

90

300

850,000

Note

In the current implementation, the “send” and “receive” buffer size for TCP packets is restricted to 64 kilobytes. Due to this limitation, the SBC cannot handle traffic where the product of the TCP packet size (measured in kilobytes) and the processor rate (measured in cycles per second) exceeds 64. For example, if the packet size is 3 kilobytes and the processor rate is 25 cycles per second, the product is 75 - which is greater than the TCP buffer size. If the TCP buffer overflows, the SBC resets the connection. This is particularly important when the packet sizes are large, as in case of packets containing the INFO header that bloats the packet sizes.

Video Calls Metrics

Video Calls Metrics

SpecificationLimit 

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).

25,000
SIP-SIP conference sessions with direct media25,000
SIP-SIP conference sessions600 cps
H.323-H.323 video sessions (media anchored) comprising up to two media streams (one audio, one video)16,000
H.323-H.323 video sessions90 cps

SUBSCRIBE/NOTIFY Benchmark for SBC 7000 (with ERE)

SUBSCRIBE/NOTIFY Benchmark for SBC 7000 (with ERE)

Scenario

SUBSCRIBEREGISTERCallsSUBSCRIBEs/SecREGISTRATIONs/SecCalls/Sec

SUBSCRIBE From Unregistered user

6,000,000

 

 

 1,000

 

 

SUBSCRIBE with 100,000 Calls

3,000,000

 

100,000

 1,000

 

1,000

SUBSCRIBE with 75,000 calls and 1 million Registrations (Calls from Registered user)

3,000,000

1,000,000

75,000

 1,000

1,500

1,000

SUBSCRIBE with 1.2 million Registrations (subscribe from registered user)

4,000,000

1,200,000

 

 1,000

1,500

 


  • No labels