The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.
RAINBOW OFFICE
Powered by RingCentral
Network Requirements
Edition 01 – May 2021
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 2
CONTENT
1. Introduction .................................................................................... 3
2. Reading Guidelines ............................................................................ 3
3. Acronyms ........................................................................................ 4
4. End-to-End Network Path Performance Requirements .................................. 6
5. Network Readiness Assessment .............................................................. 7
6. IP Supernets .................................................................................... 8
7. Networks ........................................................................................ 9
7.1. VLANs ................................................................................................... 9
7.2. SMB/SoHo Networks .................................................................................. 9
7.3. WiFi Networks ....................................................................................... 10
7.4. Wide-Area Networks (WANs) ...................................................................... 10
8. Network Components and Services ........................................................ 11
8.1. Enterprise Class Routers and Tested Routers .................................................. 11
8.2. Unsupported Devices and Configurations ....................................................... 11
8.3. Rainbow Office Soft-Client Endpoints ........................................................... 13
8.4. DNS .................................................................................................... 14
8.5. NAT ................................................................................................... 14
8.6. Firewall Control ..................................................................................... 14
8.6.1. TCP/IP Ports ................................................................................................. 14
8.6.2. Whitelisting of Domains, IP Addresses, and Ports ..................................................... 15
9. QoS Classification and Traffic Treatment Policies ...................................... 18
9.1. Traffic Classification ............................................................................... 18
9.2. Practical Constraints ............................................................................... 20
9.3. Traffic Classification Methods .................................................................... 20
9.4. Endpoint and Internet DSCP Traffic Marking Constraints ..................................... 21
9.5. DSCP Marking Policy ................................................................................ 22
9.6. Bandwidth Management Policy ................................................................... 23
9.7. Layer 2 WAN Interconnect Policy ................................................................ 23
10. Bandwidth and Network Capacity Assessment ........................................... 23
11. Appendix A. VLANs Configuration of Polycom / Poly Phones .......................... 24
12. Appendix B: TCP/IP Port Tables ............................................................ 27
13. Appendix C. Amazon CloudFront IP Address Range for Hard Phone Firmware, Soft
Client Software and Configuration Files Updates ....................................... 33
14. APPENDIX D. Rainbow Office Reference Architecture .................................. 34
14.1. Introduction ......................................................................................... 34
14.2. Acronyms ............................................................................................. 34
14.3. Reference Architecture Specification ........................................................... 36
14.4. Network Types ...................................................................................... 39
14.4.1. Small-Medium Businesses and Small Office - Home Office Networks ......................... 39
14.4.2. Mobile Networks ....................................................................................... 39
14.4.3. Wide-Area Networks .................................................................................. 39
14.4.4. CloudConnect .......................................................................................... 39
14.4.5. Software-Defined Networks and SD-WAN Networks .............................................. 39
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 3
1. INTRODUCTION
The purpose of this document is to provide customers with network requirements and
recommendations to ensure that cloud-based Unified Communication Services operate properly.
The network requirements must be followed without reservations, while recommendations are
advised to be followed.
This document covers network capacity, quality of service, firewall configuration, and
unsupported devices and configurations. The Rainbow Office Reference Architecture available in
Appendix D. can be used to understand the context of the end-to-end Quality of Service
requirements and the network specific requirements and recommendations describes the need
to perform Network Readiness Assessments to verify and ensure that the network meets the
stated requirements.
2. READING GUIDELINES
The following reading guidelines can be used:
• For Enterprise and SMB/SoHo environments, the network requirements and
recommendations are stated in Sections 6 through 9
• Section 6 specifies the RingCentral IP Supernets, which can be used to configure QoS
policies, firewall rules, and disable layer 7 functions.
• Section 7 specifies requirements and recommendations for specific types of enterprise and
wide-area networks.
• Section 8 provides network-specific NAT and firewall requirements.
• Section 9 specifies QoS requirements.
• Section 10 contains a description of LAN/WAN bandwidth and capacity requirements.
• The appendices contain detailed information, such as VLAN configuration of Polycom/Poly
phones, TCP/IP port tables, and IP Address Ranges for Phone Firmware upgrades.
• For some SMB routers, the Configuration Guides under the link provided in Section 8.1 on
Enterprise Class and Tested Routers can be used to configure QoS settings.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 4
3. ACRONYMS
Table 1 summarizes the acronyms used in this document:
Table 1. Acronyms
ACL
Access Control List
ms
Milliseconds
ALG
Application Layer Gateway
NAT
Network Address Translation
AP
Access Point
NTP
Network Time Protocol
ARP
Address Resolution Protocol
QoS
Quality of Service
BLA
Busy Lamp Appearance
RTP
Real-time Protocol
BW
Bandwidth
SBC
Session Border Controller
CoS
Class of Service
SIP
Session Initiation Protocol
DPI
Deep Packet Inspection
SMB
Small and Medium-sized
Business
DSCP
Differentiated Services Code
Point
SoHo
Small office - Home office
DSL
Digital Subscriber Line
SPI
Stateful Packet Inspection
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 5
Table 1. Acronyms
EF
Expedited Forwarding
SRTP
Secure Real-time Transport
Protocol
FQDN
Fully Qualified Domain Name
TCP
Transport Control Protocol
IDS
Intrusion Detection System
UDP
User Datagram Protocol
IP
Internet Protocol
VLAN
Virtual Local Area Network
IPS
Intrusion Prevention System
VoIP
Voice over IP
ISP
Internet Service Provider
WAN
Wide-Area Network
LAN
Local Area Network
WiFi
Set of standards for wireless
communication
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 6
4. END-TO-END NETWORK PATH PERFORMANCE REQUIREMENTS
The requirements stated in Table 2 below need to be satisfied to optimize the network path
for VoIP and Video media traffic (RTP) when using Rainbow Office services.
Table 2. End-to-End Network Path Performance Requirements
Network Property
Requirement
Link Capacity
Each link in the end-to-end path must have symmetric
(bidirectional) capacity which is larger than the maximum number
of simultaneous calls plus capacity added for other types of non-
real-time traffic and growth (Section 10)
Delay
< 150 ms (of one way latency)*
Packet Loss
< 1%
Jitter
< 30 ms
*https://www.itu.int/rec/T-REC-G.114-200305-I/en, Appendix II.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 7
5. NETWORK READINESS ASSESSMENT
The end-to-end QoS requirements stated in Section 4 can be validated by performing a Network
Readiness Assessment, which determines the quality of the LAN and the Service Provider
network. Two types of Network Readiness assessments can be performed to assess the ability of
the network path to support unified communication services:
• Snapshot Network Readiness Assessment - This assessment leverages the Capacity Test and
VoIP Quality Test tools at online. These tools provide an impression of network capacity
and quality in both directions of a given network path to the unified communication cloud
over a time interval of a few minutes.
• •Comprehensive Network Readiness Assessment - In this case, a probe is installed at the
local customer site. By running this probe over a longer time interval (e.g. a full business
week), a much better impression of the end-to-end quality as well as intermediate
network hop quality in both directions of the call is obtained. Detailed and targeted
network improvement recommendations can be provided based on the results of this type
of assessment.
The first type of assessment can be performed by the enterprise but provides minimal insight
into the end-to-end QoS over time. The second type of network assessment, which is
recommended to minimize the likelihood of user-perceived QoS issues, requires the involvement
of ALE or RingCentral Professional Services.
The requirements stated in the next sections must be implemented before a network assessment
is performed so that any major network issues are addressed beforehand.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 8
6. IP SUPERNETS
The following supernets (concatenated subnets) are used to support Rainbow Office Services:
Table 3. IP Supernets
66.81.240.0/20
80.81.128.0/20
103.44.68.0/22
104.245.56.0/21
185.23.248.0/22
192.209.24.0/21
199.68.212.0/22
199.255.120.0/22
208.87.40.0/22
These networks globally for call servers, media services, route announcements, and auxiliary
services, like telephone provisioning and network time. It is highly recommended to permit each
of these networks at all locations where unified communication services are used.
The supernets can be used to control the following features in local enterprise network devices
(see next section):
• Selectively disable layer 7 device functions such as Deep Packet Inspection (Section
8.2) for UDP traffic to/from unified communication cloud.
• Firewall TCP/IP Ports (Section 8.6.2).
• IP Layer DSCP packet markings (Section 9.5).
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 9
7. NETWORKS
This section covers high-level requirements and recommendations for specific types of enterprise
and wide-area networks. More details are provided in the subsequent sections for network
components, QoS handling, and bandwidth estimation.
7.1. VLANs
Virtual LANs (VLANs) can be used as follows with endpoints:
• Desk Phones and IP Speaker Phones - If VLANs are supported by network switches, it is
recommended to define a VLAN specifically for desk phones and IP speakerphones. This
will keep VoIP traffic of these types of endpoints logically separate from data traffic
and reduces broadcast domains. It also simplifies the management of these endpoints
because their IP addresses are VLAN-specific.
• Soft-Clients - Computers running soft-clients will usually run other applications as well.
For this reason, the computer is normally connected to the default VLAN, meaning VoIP
and video traffic for soft-clients does not reside on a dedicated VLAN.
The following recommendations and requirements should be followed for VLAN implementations:
• The VoIP solution must be put on a different VLAN and subnet than an already deployed
VoIP solution from a different vendor. Otherwise, the network routing of the existing
VoIP solution may inhibit VoIP phones from reaching out to cloud-based services.
• Recommended configuration to operate Polycom/Poly phones on VLANs is described in
Appendix A.
7.2. SMB/SoHo Networks
Small-Medium Businesses and Small Office - Home Office (SMB/SoHo) networks are mostly
connected to cable provider or Digital Subscriber Line (DSL) ISP networks. These local networks
may have lower quality equipment (such as all-in-one modems) than enterprise networks.
Frequently, the users on such networks also use WiFi. The combination of these factors makes it
more difficult to manage the end-to-end path impairments between endpoints and cloud
communications services. However, to maximize However, to minimize the impairments, it is
recommended to:
• Closely follow the network requirements in this document, including the WiFi network
requirements in Section 7.3.
• If an ISP provided modem is used with a separate router, the modem is configured in
bridge (also called passthru) mode, and the router is configured according to the
requirements in the following sections.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 10
7.3. WiFi Networks
The achievable network performance over a WiFi network depends on many factors. Chief among
them are:
• The capabilities, settings, and physical location of WiFi Access Points (APs)
• The location of users relative to Aps
• The number of users connecting to an AP
• Environmental conditions such as location, addition, and migration of objects and
furniture
• These factors may contribute to lower quality compared to wired network
implementations.
Soft-endpoints such as desktop softphones, mobile phone applications, and video applications
can be used on WiFi networks provided that network performance and configuration
requirements stated in this document are followed. To maximize network performance, it must
be ensured that:
• The wired network meets the network requirements
• The wired network plus the WiFi leg attached to the wired network also meets the
end-to-end requirements as stated in section 4
• The 5GHz band is used instead of the 2.4 Hz band since the former offers higher
bandwidth and less interference from other equipment due to non-overlapping
channels.
7.4. Wide-Area Networks (WANs)
Many technologies exist to implement WANs, including Internet, Ethernet Virtual Private Line,
MPLS, and SD-WAN. Each type of network technology has its own way of supporting. To ensure
that the end-to-end network performance QoS requirements and recommendations are met, it
is required that:
• Every traversed WAN network segment must have sufficient quality.
• Proper mapping of prioritization tags is performed between LAN and WAN networks
(Section 9.5).
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 11
8. NETWORK COMPONENTS AND SERVICES
To ensure high-quality communication service delivery, Rainbow Office requires that network
devices and endpoints support the feature requirements and follow the recommendations stated
in this section.
8.1. Enterprise Class Routers and Tested Routers
In general, enterprise class routers support most of the QoS capabilities and configuration options
described in the remainder of this document.
A set of SMB class WAN routers have been validated to work properly with the service. The list
of routers that have been tested can be found below (ringcentral.com/support/qos-router.html):
8.2. Unsupported Devices and Configurations
Some types of devices, device settings, and network configurations are not
supported/recommended in a Unified Communications solution as they are known to cause
continuous or intermittent voice quality issues (contributing to high latency, packet loss, or
jitter).
For proper support of Unified Communications services, the functions listed in Table 4 may need
to be disabled on IP devices (layer 3 switches, routers, firewalls), and Ethernet switches, or be
avoided. Disabling the mentioned functionality for the IP and higher layers can be limited to the
supernets listed in Section 6 by applying policy-based control. For example, WAN acceleration
can be configured to pass-through mode for UDP traffic originating and destined for the
supernets.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 12
Table 4. Functions which may impair SIP signaling and/or RTP media traffic
Layer
Function
Application
• SIP Application Layer Gateway (SIP ALG), also referred to as SIP
Transformations
• Deep Packet Inspection (DPI)
• Application Layer Access Control
• Stateful Packet Inspection (SPI), also called Dynamic Packet Filtering
• Intrusion Detection/Intrusion Prevention System (IDS/IPS)
• Web Proxy operation
• WAN Acceleration
Transport
• Port filtering
IP
• Packet-by-packet load balancing across multiple Service Providers links
IP & Data Link
• Auto-QoS, when used in combination with Polycom/Poly phones
• Dynamic ARP Inspection
Physical
• Energy Efficient Ethernet (a.k.a. Green Ethernet)
• Satellite (Ethernet over microwave) network connections
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 13
These items may result in intermittent call connectivity issues (phone registration or call feature
operation) and/or excessive voice quality impairments (increased latency and jitter),
specifically:
• For some of the functionality mentioned under Application Layer Functions, packet
content may traverse a separate processing engine, which may result in the mentioned
impairments. The impact may be minimal when using advanced networking devices
but could be substantial for SMB and SoHo devices.
• Enabling SIP ALG may cause signaling issues resulting in non- or partially functioning
call features and/or one-way or no-audio.
• IDS/IPS functions may limit packet streams to a certain bandwidth causing
intermittent audio issues across multiple calls when the number of calls exceeds a
certain volume. WAN accelerators use header compression to reduce bandwidth
consumption. For VoIP traffic, this can result in increased jitter.
• Web proxies typically do not support QoS so that VoIP and video traffic and may cause
an intermittent increase of latency and jitter.
• Port filtering, such as UDP flood protection, may limit bandwidth thereby causing
intermittent voice quality issues when many simultaneous calls occur.
• Packet-by-packet load balancing across multiple internet connections is not supported
because signaling and media for a single session must originate from the same IP
address.
• Use of Auto-QoS may cause voice quality issues (such as distortions or incorrect volume
levels) with older Polycom/Poly speakerphones and older versions of desk phones.
• Green Ethernet is used on switch ports to save energy by automatically setting them
into low power mode after they have not passed traffic for some time. This may also
cause intermittent signaling and media traffic issues.
• Satellite connections introduce delays much exceeding 150 ms in each direction and,
depending on the quality of the satellite connection, may also cause excessive jitter
and packet loss. It depends on end-user expectations whether this is acceptable.
8.3. Rainbow Office Soft-Client Endpoints
Endpoints used for soft-clients are recommended to be configured as follows:
In case of an endpoint with multiple network connections (wired or wireless) ensure that the
traffic uses only one connection.
From MS Windows, the WiFi metrics can be viewed by opening a command prompt window (CMD)
and entering netstat -rn. The Interface List indicates metrics in the left-hand column. The IPv4
Route Table shows the metric in the right-hand column. See
https://superuser.com/questions/708716/set-lan-to-take-network-priority-before-wi-fi-on-
windows-7 for more background.
Security Software:
Cloud-based security client software may need to be disabled when this interferes with soft-
client operation or presence status updates.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 14
8.4. DNS
All endpoints and services require internet-based DNS to function properly. In the case where
private DNS is used, it must perform forward-lookups to internet-based DNS.
For example, endpoints rely on a DNS service to resolve the provisioning service domain name.
8.5. NAT
Network Address Translation/Port Address Translation functionality (generically referred to as
NAT) is applied at the border between two networks to translate between address spaces or to
prevent collision of IP address spaces. More specifically, a NAT function translates a source (IP
address, port number) pair of outbound packets into a public source (IP address, port number)
pair and maintains table entries corresponding to this translation to allow inbound response
traffic to return to the proper host in the private network. This is required, for example, when
connecting: a) an enterprise IP network to the public Internet, or b) an enterprise network via
CloudConnect.
NAT is frequently implemented as part of firewall functionality but can also be implemented
stand-alone.
For proper operation of hard phones, a minimum Network Address Translation time out needs to
be configured. Cisco phones send a follow-up REGISTER refresh message every 4 minutes,
Polycom/Poly phones every 5 minutes. Therefore, NAT entry expiration timeout must be set to
greater than 5 minutes to cover all hard phones.
8.6. Firewall Control
For security purposes, a firewall is usually present at the border of an enterprise network. If no
egress filtering is performed in the network path to cloud-based communication services, then
the default firewall and NAT configuration for most enterprise-grade firewalls will be sufficient
to allow communication services to operate properly. However, if any egress filtering is applied
in the network where unified communication services are used from, then it needs to be ensured
that access is allowed based on the whitelisting Table 5 and Tables in Appendix B.
8.6.1. TCP/IP Ports
When using a firewall, use the tables in Appendix B to configure TCP/IP ports.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 15
8.6.2. Whitelisting of Domains, IP Addresses, and Ports
To allow the devices and applications indicated in Table 5 to access supporting cloud services,
Fully Qualified Domains Names (FQDNs), IP addresses, and associated ports must be whitelisted:
• Firmware updates for hard phones, software updates for soft-clients, and
configuration file updates for hard and soft-clients are supported by the CloudFront
service in the Amazon cloud.
• Softphones and mobile phones use Pubnub for presence status notifications.
• Premium and Ultimate plans provide the ability to archive softphone messages (text,
fax, and voicemail) and call recordings (automatic and on-demand) to the Box cloud
(www.box.com) or to an SFTP server.
• The port column indicates the port used by the respective unified communication
services.
Table 5. Whitelisting of Domains and IP Addresses
Endpoint
Cloud Service
To be whitelisted
Domain Name/IP Address
Port(s)
Rainbow Office login
page
Login Page
login.rainbowoffice.com
80.81.131.11
443
Rainbow Office
Service Web
Login Page
service.rainbowoffice.com
80.81.131.10
443
Rainbow Office
Analytics
Login Page
analytics.rainbowoffice.com
34.107.128.100
443
Rainbow Live Reports
Login Page
analytics.rainbowoffice.com/live-reports
443
Softphone Archiver
Box
It is assumed that the enterprise has already
whitelisted the appropriate domains to allow
access to Box
443
Secure File
Transfer
For archiving to an enterprise SFTP server, the
following SFTP client IP addresses in the
RingCentral cloud need to be whitelisted:
34.225.218.68
34.226.29.169
34.234.210.244
34.236.210.8
34.239.13.99
35.172.123.110
22
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 16
Table 5. Whitelisting of Domains and IP Addresses
Endpoint
Cloud Service
To be whitelisted
Domain Name/IP Address
Port(s)
52.87.7.127
54.80.51.95
Any of these IP addresses may dynamically be
selected by the RingCentral SFTP client to connect
to an enterprise SFTP server.
Telephony Client
Application using the
RingCentral Connect
Platform API
Production API
platform.ringcentral.com
443
Development API
platform.devtest.ringcentral.com
Rainbow Office Video
Login Page
video.rainbowoffice.com
80.81.131.12
443
Media Servers
*. video.rainbowoffice.com
443
Desktop Softphone
Application & Mobile
Application
Presence Status,
Call Log
Notifications, and
Voicemail
notifications
*.pubnub.com
*.pubnub.net
*.pndsn.com
ringcentral.pubnubapi.com (for newer endpoint
versions)
443
Google Chrome
Extension
Login Page
account.google.com
443
Chrome APIs for
plugin
apis.google.com
Fonts used by
Google Chrome
fonts.gstatic.com
SIP Registration
Server
sip.ringcentral.com
SIP Proxy Server
*.ringcentral.com
Hard Phones and Soft
Clients
Firmware,
Software and
Configuration
Updates**
*.cloudfront.net
443
Polycom/Poly Desk
Phones and
Conference Phones
Provisioning
pp.ringcentral.com
443
Firmware Update
pp.s3.ringcentral.com
Cisco Desk Phones
Provisioning
cp.ringcentral.com
443
Firmware Update
cp.s3.ringcentral.com
Yealink Desk Phones
Provisioning
yp.ringcentral.com
443
Firmware Update
yp.s3.ringcentral.com
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 17
Table 5. Whitelisting of Domains and IP Addresses
Endpoint
Cloud Service
To be whitelisted
Domain Name/IP Address
Port(s)
Alcatel-Lucent Desk
Phones
Provisioning
ale.ringcentral.com
443
Firmware Update
**See Appendix C. CloudFront IP Address Range for Phone Firmware Upgrades
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 18
9. QOS CLASSIFICATION AND TRAFFIC TREATMENT POLICIES
Traffic needs to be classified and treated properly in enterprise and service provider networks
to ensure that end-to-end QoS requirements are met for cloud-based communications services.
In terms of QoS, VoIP and video impose the most severe constraints on the network because
delay, packet loss, and jitter QoS requirements need to be met. Signaling traffic has lower QoS
requirements since real-time requirements do not apply and packets can be retransmitted when
lost. Other types of service traffic, such as messaging and directory services, can be treated
more like data traffic.
The next sections indicate how, ideally, communication services traffic should be classified and
treated in the context of the enterprise network and WAN. In practice, it may only be possible
to partially follow the QoS traffic class and treatment requirements due to limitations of
endpoints, network devices, and ISP and carrier networks. Recommendations to handle these
sub-optimal cases are provided as well.
• Outbound is away from the enterprise site or in the direction of the service provider
network.
• Inbound is to the enterprise site or from the service provider network into the local
enterprise network.
9.1. Traffic Classification
The left side of Table 6 indicates the traffic classes that are distinguished for unified
communication services, where the class requiring the highest priority treatment (VoIP Media) is
indicated at the top. At Layer 2, Class of Service (CoS) frame header tagging is indicated, while
DSCP packet marking is available in the IP header in Layer 3. In the next considerations, tagging
at Layer 2 and marking at Layer 2 is generically called marking.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 19
Table 6. Traffic Types and Classification
Traffic Class
CoS
Decimal
Value
DSCP
Decimal
Value
Name
Drop
Probability
VoIP Media - Real Time
5
46
EF
N/A
Video Media - Real Time
4
34
AF41
Low
SIP
3
26
AF31
Low
Transactional:
• Network Time Service
• Mobile App Data Sync
• LDAP Directory Service
2
18
AF21
Low
Best Effort: Phone Provisioning and
firmware update
0
0
BE
Undetermined
Layer 2
Layer 3
CoS is a 3-bit field in the Ethernet frame header with possible values ranging from 0 to 7. DSCP
is a 6-bit field in the IP packet header with possible values ranging from 0 to 63.
NOTE: Comprehensive security is implemented above the IP layer, e.g. secured VoIP media is
transported as SRTP/UDP/IP (SRTP is the secure version of RTP) so that security does not affect
CoS and DSCP values.
Network Requirements
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. 20
9.2. Practical Constraints
Ideally, the CoS tagging and DSCP marking values indicated in Table 6 are used across the entire
network between endpoints and cloud-based servers, and traffic is treated according to this
classification, which is referred to as honoring the marking. However, in practice this is often
not entirely possible because:
• Some network devices do not support sufficient QoS capabilities. Examples are low-
end routers.
• CoS values are often not managed in small networks.
• ISPs may change DSCP markings along the Internet path, e.g. from DSCP 46 to 0.
• In large corporate enterprise networks, with sites connected to an MPLS or Metro-
Ethernet network, a DSCP to CoS mapping must be performed by the WAN network
border devices. This mapping may not exactly maintain the CoS-DCSP values indicated
in Table 6. More details are provided in Section 9.7.
• Some endpoint types do not apply the CoS/DCSP value yet (Section 9.4).
Practical requirements and recommendations for traffic classification, DSCP marking, and a
description of Layer 2 WAN interconnections are provided in the next sections to address these
constraints.
9.3. Traffic Classification Methods
Depending on the QoS capabilities of the local network devices, one of two traffic classification
methods can be implemented to support unified communication services:
• Multi-Band Classification – Traffic to and from cloud servers is mapped according to
Table 6.
• Dual-Band Classification – Realtime voice and video UDP traffic and SIP TCP traffic
originating from or destined to cloud communication media servers are all classified as
DCSP 46. Other traffic is classified as unprioritized data traffic with DSCP and CoS
value equal to 0. The dual-band classification method is indicated in Table 7.
Multi-band classification offers the best way to handle QoS in large corporate networks and
whenever the network devices support this. Dual-band classification is relatively simple to
implement and works well in most SoHo and corporate environments with devices with limited
QoS capabilities. In some cases, when sufficient network capacity exists, some enterprises
choose to implement a variant of the dual-band classification illustrated in Table 7, where all
traffic (e.g. media, SIP, phone provisioning, and firmware update) is classified as DSCP 46.
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
Page is loading ...
/