04/05/19 22:33 PM  

Bandwidth and LAN / WAN Link Capacity Determination | RingCentral

« Go Back

Article

 
Summary
Details
Table of Contents

1. Introduction
2. Acronyms
3. Bandwidth and LAN / WAN Link Capacity Calculation
4. Endpoint Bandwidths
1. Introduction
RingCentral requires sufficient bandwidth allocation depending on your business requirements for your endpoint headcount and endpoint type. This article provides the guidelines on how to calculate your bandwidth requirement to adequately utilize RingCentral features on different endpoints. 

2. Acronyms 
The following acronyms are used in this document:
 

Acronyms

BW

Bandwidth

Mbps

Megabit per second

HD

High Definition

SUF

Simultaneous Use Factor

HQ

High Quality

TS-DATA-BW

Total data traffic bandwidth for a given site

IP

Internet Protocol

TS-RC-BW

Total RingCentral traffic bandwidth for a given site

ISP

Internet Service Provider

VoIP

Voice over IP

Kbps

Kilobit per second

WAN

Wide-Area Network

LAN

Local Area Network

WiFi

Set of standards for wireless communication


3. Bandwidth and LAN / WAN Link Capacity Calculation

Two methods can be used to determine the bandwidth produced by RingCentral traffic on LAN and WAN links and their capacity required to carry RingCentral unified communication traffic.

The preferred and most accurate method is to determine the peak traffic load from logs or network data extracted from a still deployed legacy voice/video system. Alternatively, the calculation method described below can be used.

Table 1 provides an example of a bandwidth calculation for a single enterprise site:

• For a given enterprise site, the numbers for the Number of Endpoints, Headroom for Growth, and Simultaneous Use Factor must be manually entered for each Endpoint Category and Use Case.

• The Endpoint Type Total Bandwidth is calculated from the combination of these numbers and the Bandwidth per Endpoint.

• The Number of Endpoints can be entered by using the Administrator tab in the RingCentral service portal. If a user has a desk phone and softphone (desktop or mobile), they are normally used one at a time and should not be double counted in the table.

• The Headroom for Growth column indicates how many extra endpoints will be activated soon after the first activation of RingCentral services. It is useful to take this number into account in the calculation to ensure that network capacity is sufficient to accommodate growth.

• The Simultaneous Use Factor (SUF), a number between 0 and 1, indicates the maximum number of simultaneously used endpoints. In call center deployments, this number must be set to 1.

• Since the bandwidth for Desk Phones using extension-to-extension video calls, RingCentral Meetings, RingCentral Rooms, and RingCentral Connector is much higher than for Desk and Softphones using audio, the SUF needs to be carefully selected. The SUF must be chosen so that, in all call scenarios, sufficient WAN link capacity is ensured. As an example, the SUF must be set to 1 for enterprises with a small number of users, where the total produced bandwidth is highly affected by the mentioned video applications.

• The Bandwidth for each endpoint types are obtained from bandwidth tables (Section 4) and are now stated in Mbps. Always the maximum number is used if transmit and receive bandwidth numbers are different. For VoIP, the bandwidths are rounded up to 0.1 Mbps.

• The calculated TS-RC-BW (Mbps) must be guaranteed in the local enterprise network and on the WAN link in each call direction (Transmit and Receive direction).

• The RingCentral Meetings bandwidth calculation must accommodate the RingCentral Office Edition and Meeting Add-on license since it has a significant impact on the bandwidth that needs to be supported by both the LAN network and WAN link. For example, with a Large Meeting Add-on, up to 200 people could simultaneously join an RC Meetings session using video, and multiple of those sessions may be held simultaneously. The Simultaneous Use Factor must be adjusted according to the expected use cases.

• The Total Site Bandwidth due to RingCentral traffic, TS-RC-BW is calculated as the sum of the Endpoint Type Total Bandwidth numbers:

TS-RC-BW = [(Number of Endpoints) + (Headroom for Growth)] x (Simultaneous Use Factor) x (Bandwidth per Endpoint)
 
Table 1. Transmit and Receive Bandwidth for Single Enterprise Site
Endpoint CategoryUse CaseNumber of EndpointsHeadroom for GrowthSimultaneous Use FactorBandwidth per Endpoint Type (Mbps)Endpoint Type Total Bandwidth (Mbps)
Desk and Soft PhonesHard phone10000.50.15
Hard phone - video2010.651.3
Speaker phone500.250.10.125
Softphone20010.12
Mobile phone on WiFi3010.13
RingCentral MeetingsGroup HQ video call501210
Two-party HD video call1001220
Two-party HQ video call10010.66
Group audio conference400.10.10.04
RingCentral RoomsTriple screen201612
Dual screen401416
Single screen10133
RingCentral Room ConnectorTriple screen401624
Dual screen601424
Single screen10133
 TS-RC-BW (Mbps) = 125.465

The WAN link may be shared for RingCentral and Data Traffic. In that case, the bandwidth for data traffic, TS-DATA-BW, needs to be added to the TS-RC-BW number to get the total bandwidth for the site. The TS-DATA-BW must be determined during a busy time and include headroom for data spikes and growth.

The following capacity condition must be met to ensure that the WAN link capacity is sufficient to transport RingCentral Unified Communication traffic:
(TS-RC-BW + TS-DATA-BW) < (Enterprise Site Provisioned WAN link Capacity)

If this condition is not met, then the WAN link capacity needs to be increased. The provisioned capacity is the capacity available on the WAN link. This may be lower than the physical capacity. As an example, a 1 Gbps fiber WAN link may be connecting to the enterprise but only a capacity of 100 Mbps may actually be provisioned.

Additional capacity constraints:
• The stated capacity condition must be met for the inbound (Receive) and outbound (Transmit) direction.

• Similar capacity conditions must be met for any of the internal LAN links and deeper in the ISP network.

• For RingCentral CloudConnect, also the aggregate bandwidth of all sites together and the provisioned capacities of data center links and ports needs to be considered for capacity determination.

• Bandwidth calculators for ISP WAN link connected sites and CloudConnect scenarios can be obtained upon request via email to ben.baten@ringcentral.com
 

 4. Endpoint Bandwidths 
The next sections summarize bandwidths produced and consumed by each of the RingCentral endpoint types. The bandwidth numbers can be used to calculate the capacity needed for the LAN links and ISP WAN link. 
 

4.1. VoIP Endpoint Bandwidth

Table 2 states the bandwidth numbers for both the receive and transmit traffic of hard and softphones. As indicated, the numbers depend on the endpoints and the administrative codec settings enabled in the RingCentral cloud. The numbers include packetization and Ethernet framing.

Table 2 - Transmit and Receive Bandwidth for Hard Phones and Soft Phones Use Cases

Endpoint

Codec

Transmit and Receive Bandwidth (Kbps)

Desk phone and IP Conference phone

G.711

87

G.729

31

G.722

87

Opus

60 - 80

Video*

616

Softphone

Opus

60 - 80

Mobile phone

Opus

60 - 80

*For some account tiers, 2-party extension-to-extension video calls for Polycom VVX 601/600 and 501/500 with detachable cameras are supported. This is an on-demand feature, which must be enabled by RingCentral Administration. A video call can be activated one-way or in both call directions. 
 

4.2. RingCentral Meetings Bandwidth

Table 3 states the bandwidth numbers for both the receive and transmit traffic of RingCentral Meetings. As indicated, the numbers depend on the use case. 

Table 3 - Per Endpoint Transmit and Receive Bandwidth for RingCentral Meetings Use Cases

Use Case

Meetings Login Panel and Login Panel Setting

Transmit Bandwidth (Kbps)

Receive Bandwidth (Kbps)

Group HQ video call

Settings, Video, Capture HD video not checked

600

2000

Two-party HD video call

Settings, Video, Capture HD video checked

2000

2000

Two-party HQ video call

Settings, Video, Capture HD video not checked

600

600

Group audio conference

Start without video on RingCentral Meeting

60 - 80

60 - 80


If a user does not join the audio portion of a RingCentral Meetings session on a computer but calls in via a separate phone connection, then no audio is transferred (transmitted/received) on the user’s computer but video is still transferred to the computer.

As indicated in Table 4, RingCentral Office Editions offer different audio and video capacities for RingCentral Meetings sessions.
 

Table 4 - RingCentral Office Editions vs RingCentral Meetings Audio and Video Capacities

RingCentral Office Edition

Max. Number of Audio Participants

Max. Number of Video Participants

Without Large Meetings License

With Large Meetings License

Standard

999

4

100 or 200

Premium

999

50

100 or 200

Ultimate

999

75

100 or 200

 

4.3 RingCentral Rooms Bandwidth

Table 5 states the bandwidth numbers for both the receive and transmit traffic of RingCentral Rooms. The transmit and receive bandwidths depend on the use case. The receive bandwidth for video operation depends on the number of screens. The transmit bandwidth is always 2 Mbps because a single camera is used.
 

Table 5 - Transmit and Receive Bandwidth for RingCentral Room Use Cases

Use Case

Transmit Bandwidth (Kbps)

Receive Bandwidth (Kbps)

Triple Screen

2000

6000

Dual Screen

2000

4000

Single Screen

2000

2000

Screen sharing only

150 - 300

150 - 300

Audio-only

60 - 80

60 - 80

 

Ranking
Was this information helpful?
Yes
No
Somewhat

Tell us why and what can we do to improve this information