The deadline to register with TCR has been extended. To continue or start using SMS, please register your company with TCR through your Admin Portal now to avoid delays or blocked messages. Learn more
Access, service, and grow your account from here.
US
Australia En
Canada En
Canada Fr
France Fr
Germany De
Italy It
Singapore En
Spain Es
Portugal Pt
United Kingdom En
United States En
Search
Contact us
Recommended
Save time by chatting with RChee, available online 24/7.
Submit a case
The most direct way to match you to the right expert on your issue. Responses within 48 hours.
Contact us
FOR SALES
1 (888) 898-4591
FOR SUPPORT
1 (888) 898-4591
Search resources
Submit a case
Contact us
FOR SALES
FOR SUPPORT
Welcome to MyRingCentral
Hi, ${extension.contact.firstName}!
Account overview
Account
Support resources
Support
Analytics
Welcome to MyRingCentral
Hi, ${extension.contact.firstName}!
Home > Network and system requirements > Network requirements > Network requirements | Engage Voice

Network requirements | Engage Voice

Table of contents

To use RingCentral Engage Voice services, you must meet certain network requirements.

1. Connectivity and bandwidth requirements

  • A connection of at least 10/100 Mbps over wired Ethernet is required. Wireless connectivity is not recommended.
  • You must disable the IPv6 protocol on any applicable network interfaces.
  • For voice traffic, you must allocate at least 128 Kbps of dedicated bandwidth per agent in both outbound and inbound directions. This requirement doesn’t account for the extra bandwidth for enterprise data traffic.
  • All customer sites and points of network connectivity must use enterprise-grade network circuits with associated service-level agreements and support contracts from the relevant Internet Service Providers (ISPs). RingCentral doesn’t recommend using residential-grade network circuits or circuits without support contracts.

2. Whitelisting of domains, IP addresses, and ports

The following tables specify outbound and inbound whitelisting rules for domain names and IP addresses. Outbound rules pertain to traffic initiated from a RingCentral endpoint to the Engage Voice service in the RingCentral cloud. Inbound traffic rules for RingCentral Engage Voice need only be configured when you’re using web services, SIP trunks, or FTP jobs.

To support Engage Voice, you must whitelist the domains, IP addresses, and TCP/IP ports listed in Table 2.1.1, Table 2.1.2, Table 2.2.1, and Table 2.2.2 in your enterprise firewalls.
  • Table entries marked as deprecated are only relevant for legacy Engage Voice services, and should be ignored for new deployments.
  • Unless otherwise specified, all IP addresses correspond to Engage Voice cloud service addresses.
  • There are several differences between the domain names and IP addresses for Engage Voice cluster C01 (aws80, vacd.biz) and cluster C02 (aws82, virtualacd.biz).
  • The port tables indicate which enterprise firewall ports must be opened to allow enterprise clients to receive and transmit traffic between the client and the Engage Voice cloud.
  • In Outbound Rules tables, destination ports refers to port outbound firewall ports that are used for communication with cloud servers.
  • In Inbound Rules tables, destination ports refers to inbound firewall ports.
  • For Inbound Rules tables, we recommend opening only those ports needed for a specific Engage Voice deployment. For example, if you’re not using inbound webhooks from RingCentral, you need not open the corresponding ports.
  • Contact RingCentral Support if you need to determine which cluster or ports to use for a specific deployment.

2.1 Platform: AWS80 / vacd.biz / engage.ringcentral.com

Table 2.1.1 - AWS80 Outbound rules

Purpose

Application protocol

Domain name

IP address

Destination ports

General access to the platform

HTTPS

portal.vacd.biz

engage.ringcentral.com

-

TCP\443
TCP\8081

Agent connectivity to the platform

Websocket

c01-con1.vacd.biz (52.43.198.0)

c01-con2.vacd.biz (52.25.215.69)

c01-con3.vacd.biz (52.88.95.144)

c01-con4.vacd.biz (52.34.108.236)  

c01-con5.vacd.biz (52.42.74.173)

c01-con6.vacd.biz (54.185.237.43)

TCP\8080

WebRTC telephony - RingCentral MVP login

HTTP(S)

-

Supernets in Section 6 of Network Requirements and Recommendations

TCP\8083

UDP\20000-64999

WebRTC telephony - legacy login

DTLS / WSS / SRTP 

c01-aorga-reg1.vacd.biz (54.213.242.35)

c01-aorgb-reg2.vacd.biz (52.10.253.130)

c01-aorga-reg3.vacd.biz (54.213.242.2)

c01-aorgb-reg5.vacd.biz (54.71.172.105)

c01-aorgc-reg6.vacd.biz (52.38.78.182)

c01-aorga-reg11.vacd.biz (35.165.57.28)

c01-aorga-reg12.vacd.biz (35.166.199.109)

c01-aorga-reg13.vacd.biz (44.224.213.125)

c01-aorga-reg14.vacd.biz (44.226.30.248)

c01-aorga-reg15.vacd.biz (44.229.187.129)

c01-aorga-reg16.vacd.biz (52.40.232.195)

c01-aorga-reg17.vacd.biz (44.242.127.106)

c01-aorga-reg18.vacd.biz (54.185.126.252)

c01-aorga-reg19.vacd.biz (54.71.30.126)

c01-aorga-reg20.vacd.biz (44.235.170.250)

s01-aorgc-reg1.vacd.biz (50.112.71.165) (see Note a)

s01-aorgb-reg2.vacd.biz (34.212.55.129) (see Note a)

s01-aorga-reg3.vacd.biz (52.25.189.52) (see Note a)

TCP\8089

UDP\ 10000-20000

Required for STUN protocol
(see Note b)

STUN

-

x.x.x.x

UDP\3478 UDP\19302

Notes:
(a) Only needed for PCI-enabled customers.
(b) RingCentral uses publicly available STUN servers with public IP addresses that can change over time. STUN runs on publicly accessible servers at ports 19302 and 3478. Please make sure these ports are opened for all IP addresses (generally indicated as x.x.x.x).

Table 2.1.2 - AWS80 inbound rules

Purpose

Application protocol

Domain name

IP address

Destination ports

Inbound WebService / webhook calls from RingCentral

HTTP(S)/SOAP

-

35.174.82.125

52.70.185.69

52.88.123.24

TCP\80 and TCP\443

Call recording transfers to customer hosted storage

FTP

SFTP

-

34.214.85.33

34.211.88.180

52.26.76.93

TCP\22

Reporting delivery to FTP

FTP/SFTP

FTP/SFTP

-

34.214.85.33

34.211.88.180

52.26.76.93

UDP\20-22
TCP\20-22

Reporting delivery to FTP

FTP

SFTP

Reporting.studio (Deprecated)

54.148.108.169

TCP\20, 21 and TCP\990

SIP termination
(see Note c) 

SIP

RTP

(Deprecated)

18.204.31.132

34.232.93.194

52.25.227.140

169.46.33.86

169.46.49.64

169.44.167.196

169.45.81.0

SIP: TCP\5060

UDP\5060

RTP:
UDP\10000-20000

Note:
(c) These IP addresses and ports should only be whitelisted if the customer receives SIP termination from RingCentral to an external SIP endpoint.

2.2 Platform: AWS82 / virtualacd.biz / engage.ringcentral.com

Table 2.2.1 - AWS82 outbound rules

Purpose

Application protocol

Domain name

IP address

Destination ports

General access to the platform

HTTP(S)

portal.virtualacd.biz

engage.ringcentral.com

-

TCP\443

TCP\8081

Agent connectivity to the platform

Websocket

c02-con1.virtualacd.biz (52.44.217.101)

c02-con2.virtualacd.biz (52.45.102.24)

c02-con3.virtualacd.biz (52.45.36.231)

c02-con4.virtualacd.biz (54.89.31.228) 

c02-con5.virtualacd.biz (184.73.182.89) 

c02-con6.virtualacd.biz (107.23.35.52) 

TCP\8080

WebRTC telephony - RingCentral MVP login

HTTP(S)

-

Supernets in Section 6 of Network Requirements and Recommendations

TCP\8083

UDP\ 20000-64999

WebRTC telephony - legacy login

DTLS / WSS / SRTP 

c02-anvga-reg1.virtualacd.biz (52.6.196.60)

c02-anvgb-reg2.virtualacd.biz (3.92.254.243)

c02-anvga-reg3.virtualacd.biz (34.199.42.79)

c02-anvgb-reg4.virtualacd.biz (34.196.255.210)

c02-anvgd-reg5.virtualacd.biz (34.203.130.137)

c02-anvga-reg11.virtualacd.biz (23.21.209.77)

c02-anvga-reg12.virtualacd.biz (3.233.136.218)

c02-anvga-reg13.virtualacd.biz (35.172.47.196)

c02-anvga-reg14.virtualacd.biz (52.202.202.98)

c02-anvga-reg15.virtualacd.biz (54.147.128.66)

c02-anvga-reg16.virtualacd.biz (34.233.42.49)

c02-anvga-reg17.virtualacd.biz (34.239.210.196) 

c02-anvga-reg18.virtualacd.biz (35.170.222.98)

c02-anvga-reg19.virtualacd.biz (54.157.53.60)

c02-anvga-reg20.virtualacd.biz (54.167.2.61)

TCP\8089

UDP\ 10000-20000

Required for STUN protocol
(see Note d)

STUN

-

x.x.x.x

UDP\3478

UDP\19302

Note:
(d) RingCentral uses publicly available STUN servers with public IP addresses that can change over time. STUN runs on publicly accessible servers at ports 19302 and 3478. Please make sure these ports are opened for all IP addresses (generally indicated as x.x.x.x).

Table 2.2.2 - AWS82 inbound rules

Purpose

Application protocol

Domain name

IP address

Destination ports

Inbound WebService / webhook calls from RingCentral

HTTP(S)

c00-prx.connectfirst.com

52.88.123.249

52.70.185.69

35.174.82.125

TCP\80

TCP\443

Call recording transfers to customer hosted storage

FTP

SFTP

-

34.198.187.185

54.87.111.82

34.227.42.48

52.22.161.8

54.210.62.149

TCP\22

Reporting delivery to FTP

FTP

SFTP

-

34.198.187.185

54.87.111.82

34.227.42.48

52.22.161.8

54.210.62.149

TCP\20-22

Reporting delivery to FTP

FTP

SFTP

Reporting.studio (Deprecated)

54.148.108.169

TCP\20, 21, and TCP\990

SIP Termination

(see  Note e) 

SIP

RTP

(Deprecated)

18.204.31.132

34.232.93.194

52.25.227.140

169.46.33.86

169.46.49.64

169.44.167.196

169.45.81.0

SIP: TCP\5060

UDP\5060

RTP: UDP\10000-20000

Note:
(e) These IP addresses and ports should only be whitelisted if the customer receives SIP termination from RingCentral to an external SIP endpoint.
System Status
Legal
Cookie preferences
Privacy Notice
Contact us
© 2022 RingCentral, Inc. All rights reserved.
Thanks!
We've sent you a link, please check your phone!
Please allow a full minute between phone number submissions.
There was an issue with SMS sending. Please try again. If the issue persists, please contact support.