X Series Technical Requirements

Document History

	Update Contact Center Mail Server Addresses, minor corrections, and/or clarifications for Contact
	Center.
March 9th,	Browser and TLS requirements added/updated
2021
	CORRECTION in United States Quality Management SUBNETS 2.35.50.242/32 was
	corrected to be 52.35.50.242/32
February 22nd,	Additional Clarity on FTP and Email Requirements
2021
	8x8 is expanding geo-routing capabilities on April 2nd, 2021.
February 10th,	•	Montreal: 168.138.74.128/26
		•	Toronto: 140.238.129.0/26
2021
		•	Cardiff: 129.151.79.0/24
	•	Hyderabad: 152.67.181.0/26

January 27th,	For converged networks, a link to recommendation for setting up VLANs for Poly was provided.
2021
January 13th,	Add WorkW WebRTC Ports
2021

Older Updates

8x8 is expanding geo-routing capabilities on January 25, 2021.

November	•	Amsterdam: 158.101.200.0/26
21st, 2020	•	Ashburn: 129.159.80.0/24
	•	Sao Paulo: 168.138.245.128/25

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements

Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by

1

1. Frankfurt: 130.61.163.0/25
   

2. London: 152.67.145.0/24
   

3. Phoenix: 158.101.41.0/24
   

November 5th, 2020

October 26th, 2020

October 16th, 2020

September 24th, 2020

Additionally added 8x8's Maestro Gateway IPs (for use when restricting access to your CRM from 8x8).

New Domain Table format with filtering and export capability added

New Subnet Table format with filtering and export capability added

1. Add callstats ports
   

2. 66.81.220.0/24: UK Data Center Added
   

3. 66.81.216.0/24: AU Data Center Added
   

Change the format of the IP Range table to make it easier to read/use, added new IPs for Quality Management Service.

New 3rd party domain walkme.com added

New 8x8 domain added 8x8cloud.com added

August	ADD the following SUBNET for Australia 168.138.20.0/25
17th, 2020	India had the following CHANGE of SUBNETS 152.67.22.0/26 REPLACED	124.124.82.224/28
November
		New Domain Table format with filtering and export capability added
5th, 2020
October	New Subnet Table format with filtering and export capability added
26th, 2020
October	•  Add callstats ports
		•  66.81.220.0/24: UK Data Center Added
16th, 2020
		•  66.81.216.0/24: AU Data Center Added

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

2

July 31st, 2020

Added the following Subnets UK: 109.70.59.0/24

Update of 8x8 Meet IP subnets. New Ranges:

130.61.162.0/24

168.138.245.0/25

152.67.144.0/24

193.122.184.0/24

152.67.21.0/24

158.101.40.0/25

129.146.204.128/27

129.146.205.0/27

129.146.205.96/27

129.146.206.64/27

168.138.111.128/25

130.61.64.185

193.122.11.14

168.138.236.29

168.138.229.53

140.238.95.196

152.67.128.56

193.122.177.113

193.122.167.175

152.67.14.48

152.67.30.22

129.146.227.2

129.146.219.44

168.138.110.244

168.138.110.59

140.238.148.121

140.238.148.27

168.138.216.49

168.138.223.155

158.101.192.6

193.123.38.193

193.122.64.56

158.101.224.215

Update product names to reflect Work for Desktop and Work for Mobile

Remove range 50000-65535 UDP for RTP (Overlap)

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

3

July 20th, 2020

June 4th, 2020

Add *.amazonaws.com for storing and downloading Call Center Analytic reports via S3 Signed URLs.

Correction on Softphone Ports, removed 5443.

Added the following Subnets UK: 185.173.48.64/26 and China: 101.227.59.128/27. *.callstats.io moved to 8x8 Core Domains from 3rd Party Domains. Add "Additional Resources" links for customers that are mixing both 8x8 and other Brands owned by 8x8.

Overview

This document provides a comprehensive guide to the network requirements necessary to enable 8x8 X Series services (Including Unified Communications, Contact Center Applications, Work for Desktop and Work for Mobile, UCaaS clients, Video Meetings, and current hardware offerings).

Note: This document should supersede any other documentation that references IP's, Subnets or Ports used by 8x8.

Applies To

1. X Series Platforms
   

2. Technical Requirements
   

Abbreviations

Abbreviation Meaning

8x8 8x8, Inc.

ALG Application Layer Gateway

DNS Domain Name System

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

4

Abbreviation Meaning

DPI Deep Packet Inspection

DSCP Differentiated Services Code Point

EF Expedited Forwarding

FTPS FTP Secure (FTP over TLS)

GTM Global Traffic Manager (8x8 DNS)

HTTP(s) HyperText Transfer Protocol (Secure)

IMAP Internet Message Access Protocol

IP Internet Protocol

KB Knowledge Base System

LAN Local Area Network

LDAP(S) Lightweight Directory Access Protocol (Secure)

NTP Network Time Protocol

POP3 Post Office Protocol version 3

QoS Quality of Service

SIP(S) Session Initiation Protocol (Secure)

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements

Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by

5

Abbreviation	Meaning
SPI	Stateful Packet Inspection
(S)RTP	(Secure) Real-Time Protocol
TCP	Transport Control Protocol
TLS	Transport Layer Security
UDP	User Datagram Protocol
CC	8x8	Contact Center
VLAN	Virtual Local Area Network
Work for Desktop	8x8	Work for Desktop Application (8x8 UC Client for desktop)
Work for Mobile	8x8	Work for Mobile Application (8x8 UC Client for mobile devices)
WAN	Wide Area Network
ZTP	Poly Zero Touch Provisioning

Terminology

The following terms are essential in understanding your network requirements for 8x8:

1. Jitter: A measure of the time interval between data packets as they reach their destination. A low degree of jitter indicates a relatively steady stream of data packets.
   

2. Packet loss: Data, such as a VoIP transmission, is sent over the Internet in the form of packets. Packet loss occurs when some of these packets do not arrive at their destination. For each packet loss, a small amount of speech is cut out. If the degree of packet loss is high, conversation audio can sound very choppy, delayed, or unclear.
   

3. MOS score: The higher your MOS score, the better your VoIP experience will be. A MOS score is measured on a scale of 1 to 5, in which 5 represents the best possible call quality, and 1 represents the worst possible call quality.
   

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

6

The range is subjective and based on normative data collected from experimental trials.

Firewall Guidelines

With regards to Firewall guidelines, It is advisable to either exempt 8x8 traffic from Deep Packet Inspection (DPI) and Intrusion Protection or ensure that appliances performing these operations can inspect the traffic without inducing measurable delay.

Default Recommendations

DNS

When using a Voice Only VLAN (a Virtual LAN with only Hard Phones, and no computers on it), 8x8 recommends that you set the 8x8 GTMs, 8.28.0.9 and 192.84.18.11 as the Primary and Secondary DNS servers in the VLANs DHCP Scope. An alternate option is to implement conditional forwarding of 8x8.com and packet8.net on your local DNS servers to 8.28.0.9 and 192.84.18.11, which are 8x8's DNS servers. It is not recommended to set conditional forwarding on your Data VLAN, and/or if you have only one network. If your network only consists of a single LAN (you are not using VLANs), 8x8 can set the DNS of your hard phones to the GTMs. This ensures proper Geo Routing of your 8x8 traffic to the closest 8x8 data center for each location.

8x8 UCasS Clients use the 8x8 GTMs directly (with a fall back of the local DNS); thus, no additional work is needed to ensure proper routing of the traffic for UCaaS Clients.

NTP

8x8's recommendation for NTP is to allow the default NTP setting of pool.ntp.org through the firewall. If your internal security requirements do not allow for external NTP, our advice is to use Option 42 in your DHCP scope to override the NTP setting to an NTP server of your choice. Should you not have an internal NTP server, please use ntp2.packet8.net.

SIP-Application Level Gateway (ALG)

By default, 8x8 enables SRTP, which supersedes SIP-ALG functionality for a list of equipment that supports SRTP see our list of SRTP Compatible Equipment. 8x8 recommends for NON-SRTP Users that SIP-ALG be disabled on all your Layer 3 Network equipment, as SIP-ALG can cause issues with SIP messages. Please review and test to ensure that disabling SIP-ALG on your networking equipment will not impact other existing services on their network. For more information on SIP-ALG and possible solutions for disabling please see our SIP-ALG documentation, click here.

SIP-ALG (Application Level Gateway) is a feature in which the layer three network equipment can manipulate the payload section of a SIP Packet to change the private addressing to be public address. As the phone or Work for Desktop/Work for Mobile is not aware of the public address, all payload information references private addressing. Edge devices attempt to "correct" this by opening all SIP packets and manipulating the payload (body) of the packets by

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

7

replacing private addresses with the public IP of the edge device and the Natted port. Unfortunately, many devices do not adequately manipulate these packets causing them to be invalid or contain incorrect information. For this reason, 8x8 recommends that this function be disabled for non-SRTP users.

Firewall Rules

Our recommendation is to create an OUTBOUND Policy "Internal to 8x8" rule in your firewall. This is a highly secure action as it is only opening outbound traffic towards a known destination (8x8 data center(s)). The list of 8x8 subnets (or Domains) is later in the document.

We recommend setting firewall session timers as follows to prevent premature NAT session changes that can cause de-registration, intermittent one-way audio, and phones not to pick up or ring when using certain firewalls:

1. UDP session timer: 300 seconds
   

2. TCP session timer (TLS connections only, port 5443): 300 - 700 seconds
   

Application and Browser-Based Interfaces

All 8x8 services are deployed within the IP address spaces listed in this document and identified by one of the domains listed in this document. Outbound requests made to these ranges on port 80 (HTTP) will be redirected to port 443 (HTTPS) and customers should allow both outbound ports to the IP/Domains.

To ensure the utmost security as you use your 8x8 services, beginning Contact Center Configuration Manager, Agent Desktop, along with API web browsers or libraries compliant with TLS 1.2 or better:

February 28, 2021, access to the 8x8 Virtual calls to these systems, will require up-to-date

The following browsers have been verified by 8x8 QA to support the changes occurring February 28, 2021:

1. Google Chrome version 70 or later
   

2. Mozilla Firefox version 48 or later
   

3. Microsoft Internet Explorer 11 on Windows 10
   

4. Microsoft Edge (any)
   

5. Apple Safari version 9 or later
   

You can also click here to test your current browser’s security standard compatibility.

Proxy Server

8x8 ONLY supports using a proxy for TCP port 80 and 443 (HTTP/HTTPS) traffic, all other traffic (Video and Audio) should bypass your proxy. 8x8 has made every attempt to ensure that Work for Desktop application will respect the proxy settings of the system Work for Desktop is running on. 8x8's web applications (Contact Center Agent Interface, Configuration managers, Analytics, and so forth) are, by nature, proxy aware and will respect the proxy setting of the system/browser.

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

8

Physical Instruments

For all approved telephony devices (endpoints), Outbound requests made via HTTP over TLS (HTTPS) on port TCP 443 to all 8x8 domains listed in the Domains section of this document without restriction to specific IP address ranges.

Provisioning Note: Poly devices can make use of Poly Zero Touch Provisioning (ZTP) and Poly PDMS service. Each of these services require HTTPS traffic to be allowed to Poly. For more details see How do I Whitelist Zero Touch Provisioning Services for Obihai and Polycom Devices. Device Access to Poly’s IPs is NOT required for 8x8 services, it will assist/speed deployment for new devices.

Network Considerations and Recommendations

Below are Network considerations and recommendations that customers should review and adapt as appropriate, as they may not ally to all installations.

Parameters

Poly Zero Touch Provisioning (ZTP)

TLS

Wiring

WiFi

PoE (recommended)

Requirements

Allow Poly Zero Touch Provisioning, alternative options can be found in Setting up ZTP Override

TLS 1.2 support is mandatory

At least Cat 5 (preferably Cat 6) wiring for networking devices, and IP phones that use a wired connection.

Strong and consistent WiFi connection for networking devices, and IP phones that use WiFi.

See Device Manufacturer Data Sheets

Packet loss	0% packet loss
Jitter	<20 ms jitter
	https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements
	Updated: Mon, 15 Mar 2021 19:46:08 GMT
	Powered by

9

Parameters

Network latency

Bandwidth requirement

Requirements

<100 ms latency to 8x8 data centers. VoIP services are known to work even in higher latency conditions up to 150-200 milliseconds. However, this must be maintained consistently with no packet loss.

Voice UCaaS and CCaaS:

1. G711 Codec: 90 kbps symmetric/call
   

2. G722 Codec: 90 kbps symmetric/call (UC Calls Only)
   

3. G729 Codec: 35 kbps symmetric/call
   

4. CCaaS add an additional 30kbps symmetric/call
   

Video Meetings Upstream:

1. Up to 3Mbps for video
   

2. 40kbps for audio
   

Video Meetings Downstream:

1. 2.5 Mbps for "On Stage" video in high quality
   

2. At least 500kbps for one incoming stream at the lowest quality
   

3. 200kbps per thumbnail stream (excluding on-stage)
   

4. 40kbps for audio
   

Downstream max bandwidth in a conference of n people would be 2.5Mbps + (n-2)*200kbps + 40kbps

Please make sure you have 50% of your available bandwidth free to accommodate any spike in usage. Always assume that at least 35% of your users are on call at any time. However, depending on your company's use case, you may have a higher percentage.

Note: When setting up devices to use an uncompressed voice CODEC, enable both G.711a law and G.711μ law capabilities available on the device. This prevents call quality loss by eliminating transcoding of international VoIP calls. This has no impact on bandwidth requirements, as either choice uses 80 Kbps per call. Transcoding does increase latency.

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

10

Parameters Requirements

• Agents require a personal computer and a high-speed

Internet connection capable of running currently supported

browsers.

•  If an agent uses a Voice over IP (VoIP) softphone provided

Contact Center hardware by 8x8, then the agent's computer and Internet connection

requirements must consistently perform well while processing all other

desktop applications required for the agent's tasks.

•  Agent screens must support a resolution of no less than

1200 x 900 pixels. If available, a higher screen resolution is

recommended.

Parameters Considerations

If running a converged network for voice and data

DHCP scope

Maximum Transmission Unit (MTU)

WAN failover

Configure VLANs to separate the traffic. Please ensure that the

Phone VLAN has the following DNS and NTP in its DHCP scope:

1. Use 8x8 DNS (Global Traffic Managers) servers 192.84.18.11 and 8.28.0.9
   

2. Use 8x8 NTP server ntp2.packet8.net
   

Note: The recommended DNS does not resolve any other domain except 8x8.com and packet8.net. For more information

on Poly and VLANs see https://support.8x8.com/equipment-devices/phones/polycom/polycom-devices-vlan-overview-and-recommendations

Ensure that there are no rules specified to force any provisioning server or NTP server to deviate from default 8x8 values. For provisioning servers, you must disable Option 66/160.

The network must support an MTU of 1500 bytes per packet. The MTU is the size of the largest protocol data unit that the layer can pass onwards. This is for Non-SRTP Communications only.

We highly recommend that you use dual WAN connections in a

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

11

Parameters

VPN use cases

Internet Access Requirements

NAT Requirements

Considerations

failover state by using WAN link redundancy (Active / Standby). Dual WAN connections in load balancing (Active / Active) may not be supported due to the multiple ways to implement, speak to your 8x8 engineer for supported options and/or recommendations.

If your remote users or Internet egress use a VPN tunnel, please make sure that the 8x8 traffic does not traverse it. Consider a Split Tunnel to have local Internet egress for 8x8 traffic. In addition, split DNS to resolve 8x8 domain queries locally. Speak to your 8x8 engineer for more information.

1. All 8x8 UC and Contact Center agents, supervisors, and administrators must have high-speed Internet access. Examples of high-speed Internet include DSL, Cable, or most corporate LANs.
   

2. Although 8x8 UC and Contact Center can interoperate with high-speed satellite connections, the round-trip transmission delay inherent in all satellite connections is likely to result in an undesirable degradation in performance.
   

3. Note: Dial-up Internet connections are not supported.
   

4. 8x8 UC and Contact Center works with typical default stateful inspection firewall settings.
   

5. 8x8 Contact Center requires standard NAT with any VoIP Application Layer Gateway (ALG) address fix up features disabled when using Bria.
   

6. The 8x8 Contact Center browser and VoIP phone sessions periodically generate activity to keep stateful inspection ports open.
   

7. 8x8 Contact Center Agents using Counterpath software-based softphones (such as eyeBeam and Bria) may need to configure any firewall products (for example, Windows firewall, Symantec, or Trend Micro) to allow the softphones to receive calls.
   

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

12

QoS / Priority

The basic approach of handling QoS for 8x8 traffic within your network is by DSCP markings as provided by the applications and approved devices. When configuring QoS, on circuits that support QoS, external to your network 8x8's recommendation is to identify 8x8 traffic based on source/destination network, (i.e., not by DSCP markings, ports, channels, etc.). RTP will make up 90+% of your traffic. That way, any of your traffic that is sourced/destined to any of the 8x8 networks should be treated with the highest priority.

If the majority of your users are on Wi-Fi rather than Ethernet, please make sure you follow the best practices in Wi-Fi deployment to ensure plenty of coverage.

8x8 Meetings does not currently mark the meetings traffic; our recommendation is to set priority (EF) on the predictable port of UDP 10000.

8x8 DSCP / CoS Values Applied

Endpoint Type	Traffic Type /	COS Value	DSCP	Name
		Application	(Decimal)		(Decimal)
Windows / Non-	Voice Media -	CS7	DSCP 56
Admin	Real-Time
Windows / Non-	SIP Signalling	CS5	DSCP 40
Admin
Windows /	Voice Media -	EF	DSCP 46	Expedited
Admin	Real-Time					Forwarding
Windows /	SIP Signalling	AF31	DSCP 26	Assured
Admin							Forwarding
Mac / iOS	Voice Media -	EF	DSCP 46	Expedited
				Real-Time			Forwarding
Mac / iOS	SIP Signalling	AF31	DSCP 26	Assured
								Forwarding

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

13

Endpoint Type	Traffic Type /	COS Value	DSCP	Name
		Application	(Decimal)		(Decimal)
Android	Voice Media -	EF	DSCP 46	Expedited
				Real-Time			Forwarding
Android	SIP Signalling	AF31	DSCP 26	Assured
								Forwarding
Poly	Voice Media -	EF	DSCP 46	Expedited
				Real-Time			Forwarding
Poly	SIP Signalling	AF31	DSCP 26	Assured
								Forwarding

8x8 Outbound Datacenter Ports

Traffic Requiring Outbound Connections from within the customer network to the 8x8 Cloud.

Traffic Source &			Applies To	Protocol(s)			Destination Port(s)
Purpose
Device
•	Provisioning	All Certified	•	HTTP
				Physical Phones &	•	HTTPS	TCP 80, 443
•	Configuration
				ATAs
•	Software Update
Device			All Certified	SIPS
Secure SIP Signalling			Physical Phones &	(Secure SIP)			TCP 5443
						ATAs
Device			Certified Physical	LDAPS			TCP 636
Corporate Directory			Phones

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

14

Traffic Source &	Applies To	Protocol(s)	Destination Port(s)
Purpose
			•  UDP

Device

Network Time

Device

Domain Name System

Device

1. SIP Activation
   

2. SIP Signalling
   

Softphone Application

1. Browser
   

1. Authorization
   

2. Messaging
   

3. Presence
   

4. Configuration
   

5. Administration
   

6. Reporting
   

7. Quality Management
   

8. Microservices
   

All Certified Physical Phones & ATAs

All Certified Physical Phones & ATAs

All Certified Physical Phones & ATAs

1. Work for Desktop & Work for Mobile
   

2. 8x8 Admin Console
   

3. Analytics
   

4. Contact Center Agent, Supervisor
   

5. Quality mgmt
   

NTP

DNS

SIP

HTTPS

•  TCP 123

Can be provided locally via

DHCP Option 42

1. UDP 53
   

2. TCP 53
   

Can be provided locally via

DHCP Option

1. UDP 5060 (Activation only)
   

2. UDP 5199,5299,5399
   

TCP 443

Softphone Application	•	Work for	SIPS
				Desktop
			TCP: 5401
	•	Work for
Secure SIP Signalling					(Secure SIP)

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

15

Traffic Source &

Purpose

Applies To

(Default)

Mobile

Softphone Application

SIP Signalling (Optional)

Real-Time Audio

Voice Call Audio

Real-Time Audio

8x8 Meet

callstats

1. Work for Desktop
   

2. Work for Mobile
   

3. Physical Phones
   

4. Work for Desktop & Work for Mobile
   

5. WorkW
   

6. Work for Desktop
   

7. Work for Mobile
   

8. Browser
   

9. Call Analytics
   

10. Meeting Analytics
    

11. Smart Connectivity Tests
    

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

16

Traffic Source &	Applies To			Protocol(s)	Destination Port(s)
Purpose
	•	Smart
Smart Connectivity Tests		Connectivity	•  WebRTC	•  UDP 1024 - 65000
		Tests

Optional Services

Applications Requiring Outbound Connections

The following are optional items that may not be required. Consult your 8x8 team to validate whether these scenarios are applicable to your specific use cases.

Traffic Source &	Applies To	Protocol(s)	Destination Port(s)
Purpose
Quality Management	Screen Recording
Screen Recording
		Client in Quality	HTTPS	TCP 443
Streaming screens	Management
			•  Control Connection:

Downloads of

contact center call

VCC FTPS Call

recordings using

Recording Download

FTP over TLS

(FTPS).

Standalone contact

Bria Softphone

center softphone

FTPS

Note: FTPS is not the same as SFTP (SSH Based).

1. SIP
   

2. RTP
   

1. TCP: 21 Explicit
   

2. TCP: 2121 Explicit
   

3. TCP: 990 Implicit
   

2. Data XFER Ports: UDP:30000-30999
   

List of Platform URLs

1. UDP: 5060 Default
   

2. UDP: 5061 Alternate/ Optional
   

3. UDP High Ports (1024 - 65535)
   

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

17

Traffic Source & Purpose

Zoiper Softphone

Network Utility

1. Media Tests
   

2. Fragmentation Test
   

3. BufferBloat Test
   

Wavecell API

SIP Trunks

1. SIP(S) Signalling
   

2. (S)RTP
   

Applies To	Protocol(s)			Destination Port(s)
Standalone contact	•	SIP	•	UDP 5060, 5061
						•	UDP High Ports
		•	RTP
center softphone
							(32000 - 65535)

Network •  RTP •  UDP 3478-3480

Assessment

	•	HTTP
Video API	•	HTTPS	•  UDP 10000 - 20000
		•	WSS

See customized Statement of Work for the unique implementation

Applications Requiring Incoming Connections

Traffic Source & Purpose

Contact Center Email

POP3/IMAP email access

Destination Port(s)	Source IPs
•  For POP3 email support, enable port TCP 110.	•	US-West: 8.21.164.0/24
•  For POP3 SSL, enable port TCP 995.	•  US-East: 8.28.3.0/24
•  For IMAP email support, enable port TCP 143.	•	Brazil: 168.90.173.112/28
•  For IMAP SSL, enable port TCP 993.	•	Canada: 142.165.219.0/24
•  For SMTP email support, enable port TCP 25.	•	Europe2: 217.163.57.0/24
•  For SMTP TLS email support, enable port TCP	•	Europe3: 109.70.58.0/24

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

18

Traffic Source & Purpose

Destination Port(s)

587.

1. For SMTP SSL email support, enable port TCP 465.
   

Note: custom ports can be configured.

Source IPs

1. Hong Kong:
   

103.252.162.0/24

2. Australia: 103.239.164.0/ 24
   

3. Bell Canada: 50.100.15.0/ 24
   

SIP Trunks

•  SIP(S) Signaling See customized Statement of Work for the unique implementation

•  (S)RTP

8x8 Datacenter IP Ranges & Domains

Note: In the process of connecting to Secure HTTP servers and setting up TLS connections, the certificates used in the connections will be validated by the issuing authority. Ensure you allow access to any/all issuing authorities.

Provisioning Note: Poly devices can make use of Poly Zero Touch Provisioning (ZTP) and Poly PDMS service. Each of these services require HTTPS traffic to be allowed to Poly. For more details see How do I Whitelist Zero Touch Provisioning Services for Obihai and Polycom Devices. Device Access to Poly’s IPs is NOT required for 8x8 services, it will assist/speed deployment for new devices.

IP Ranges

Below is a list of IP Ranges that are used by 8x8 products and applications. Access Control List (ACL) and Quality of Service (QoS) flags indicate if the subnet should be included in your ACL and/or QoS Lists. There is an export option at the top of the list. When a Port range of * is referenced it refers to All Ports listed above in the Data Center Ports

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

19

section.

Media, iframe, embed and object tags are not supported inside of a PDF.

Domains

Below is a list of domains that are used by 8x8 products and applications. There is an export option at the top of the list. When a Port Used range of * is referenced it refers to All Ports listed above in the Data Center Ports section.

Media, iframe, embed and object tags are not supported inside of a PDF.

Additional Resources

The following resources are intended for customers who are using Jitsi, Callstats, Wavecell, Sameroom or other companies/brands owned by 8x8 outside of their 8x8 resources/applications.

1. Oracle IP ranges (full): https://docs.cloud.oracle.com/en-us/iaas/tools/public_ip_ranges.json
   

2. Jitsi IP ranges (full): https://go.8x8.vc/ranges
   

The following resources are intended for customers who are using 8x8 Voice + Microsoft Teams. There are no 8x8 specific network requirements for these users. The Teams applications (mobile, desktop, browser) and any Teams certified phones communicate directly with Microsoft and do not communicate directly with 8x8.

1. Microsoft Teams: https://docs.microsoft.com/en-us/microsoftteams/prepare-network
   

https://support.8x8.com/cloud-phone-service/voice/network-setup-voice/x-series-technical-requirements Updated: Mon, 15 Mar 2021 19:46:08 GMT

Powered by 

20