Businesses must register their text usage as soon as possible, or outbound texting will be blocked.
Register now
Access, service, and grow your account from here.
CA
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, 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
Call support
Contact sales
Search resources
Submit a case
Contact us
My next steps
0
Action required
Your credit card on file is about to expire. Update now
Great job!
You're all caught up.
Check back here to make the most of your RingCentral plan.
Home > Network and system requirements > Network requirements > Network requirements | Engage Voice

Network requirements | Engage Voice

Table of contents

For the successful implementation of RingCentral Engage Voice services, the network requirements must be followed without reservations, while recommendations are advised to be followed.

1. Connectivity and bandwidth requirements

  • At least 10/100 Mbps wired ethernet connection is required. Wireless connectivity is not recommended.
  • IPv6 protocol must be disabled on any applicable network interfaces.
  • For voice traffic, at least 128 Kbps of dedicated bandwidth per agent must be allocated, both in the outbound and inbound direction relative to the enterprise network. This requirement does not account for any extra bandwidth for enterprise data traffic.
  • All customer sites and points of network connectivity must utilize enterprise-grade network circuits with an associated Service Level Agreement and Support Contract from the ISP (Internet Service Provider). Residential grade network circuits and circuits without a support contract are not supported.

2. Whitelisting of domains, IP addresses, and ports

The next set of tables specify outbound and inbound rules of whitelisting 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 with RingCentral Engage Voice only need to be configured when web services, SIP trunks, or FTP jobs are used.
 
Table 1 through Table 4 indicate the domains, IP addresses, and TCP/IP ports that must be whitelisted in enterprise firewalls to support Engage Voice.
  • Table entries marked as deprecated are only relevant for earlier deployed Engage Voice services and should be ignored for new deployments.
  • Unless otherwise specified, all IP addresses correspond to Engage Voice cloud service addresses.
  • Several of the domain names and IP addresses are different between Engage Voice clusters C01 (aws80, vacd.biz) and C02 (aws82, virtualacd.biz)
  • The port tables indicate which enterprise firewall ports must be opened for an enterprise client to receive/transmit traffic between a client and cloud-based Engage Voice.
  • Two types of port tables are distinguished (see table header):
    • Outbound Rules tables: destination ports refer to port outbound firewall ports used for communication with cloud servers. 
    • Inbound Rules tables: destination ports refer to inbound firewall ports.
  • For Inbound Rules tables, it is recommended to open only those ports that are needed for a specific Engage Voice deployment. For example, if Inbound Webhooks from RingCentral is not used, then the corresponding ports do not need to be opened. 
  • Please consult RingCentral to determine which cluster is used and the ports that are relevant for a specific deployment.

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

Table 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 - RingEX Login

HTTP(S)

-

Supernets in Network Requirements

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)* (1)

s01-aorgb-reg2.vacd.biz (34.212.55.129)* (1)

s01-aorga-reg3.vacd.biz (52.25.189.52)* (1)

TCP\8089

UDP\ 10000-20000

Required for STUN protocol (2)

STUN

-

x.x.x.x

UDP\3478 UDP\19302

(1) PCI enabled customers only
(2) RingCentral utilizes 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 ensure these ports are opened for all IP addresses (generally indicated as x.x.x.x).

Table 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 from RingCentral. Inbound SIP termination from RingCentral SIP network. These should only be whitelisted if the customer is receiving SIP termination from RingCentral to an external SIP endpoint

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

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

Table 3. 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 - RingEX Login

HTTP(S)

-

Supernets in Network Requirements

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 (3)

STUN

-

x.x.x.x

UDP\3478

UDP\19302

(3) RingCentral utilizes 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 ensure these ports are opened for all IP addresses (generally indicated as x.x.x.x).

Table 4. 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 from RingCentral.  Inbound SIP termination from RingCentral SIP network. These should only be whitelisted if the customer is receiving SIP termination from RingCentral to an external SIP endpoint

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

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.