Overview
The options and port settings listed in the linked Technical Requirements documents are typically available in your router/firewall's web interface (GUI) and are generally required to ensure quality 8x8 service. (Not every setting will be available in every router.) Consult your network administrator and or your manufacturer's documentation for more details on setting up your router for optimal Quality of Service (QoS).
Note: We highly recommend consulting an IT or network professional when configuring advanced network settings or devices.
Technical Requirements
Zero Touch Provisioning
Information on Zero Touch Provisioning IP's and Ports can be found in Whitelist Zero Touch Provisioning Services for Obihai and Poly Devices.
For Quick Testing with an issue present (Audio issues are occurring right now)
- Download and run WinMTR. See Download WinMTR Ping and Traceroute Tool .
- Run two simultaneous tests, one to google.com and one to the closest media server:
- India: 124.124.82.233
- Amsterdam: 64.95.100.100
- Brazil: 168.90.173.118
- Singapore: 117.20.40.201
- West Coast US: 192.84.16.2
- East Coast US: 8.28.0.2
- United Kingdom: 217.163.57.2
- Australia: 103.239.164.2
- Hong Kong: 103.252.162.2
- Run test for a minimum of 2 minutes and a maximum of 5 minutes.
- Stop the test and review the results.
- The latency and/or packet loss issue should be visible on both results.
- After interpreting the results, if the problem is outside the LAN, contact the ISP and report the latency and/or packet loss issue from the issue hop.
- If there is packet loss or high latency only to the 8x8 Data center the fragmentation test will need to be run from the Network Utility Download .
- If fragmentation fails the MTU may need to be adjusted on the LAN or the ISP is not supporting fragmentation on the route to 8x8. If the ISP is not supporting fragmentation on the route they will need to be contacted.
Example Bad WinMTR, issue from hop 2. Latency passes from hop 2 to destination (Google):
Longer-term Testing for Intermittent Issues
Download and run Pingplotter. See How to Use Ping Plotter for Network Troubleshooting .
Definitions and Tolerance Levels
Latency
This is the time it takes to move voice packets from the phone to 8x8 (and back). In general, this should not exceed 150ms in one direction to prevent deterioration of voice quality. NOTE: When part of the call travels over the public Internet (which introduces its own latency), the organization's internal network latency should be significantly less than 100ms.
Compensating for Latency
In most cases, latency is introduced by a congested network or a carrier issue. 8x8 suggests that you run PingPlotter or WinMTR (free 3rd party utilities) to get a better overall view of your network as well as a Buffer Bloat Test.
Jitter
Jitter is a variation in packet transit delay caused by queuing, contention and serialization effects on the path through the network. In general, higher levels of jitter are more likely to occur on either slow or heavily congested links. This is the variations in packet delay. As far as the source endpoint is concerned, the packets would be sent in a continuous stream. But since each packet may take a different route to its destination, network congestion or improper configuration can result in variations in packet delay. If the packets are not received in the same order or were dropped entirely on the way, this results in Jitter. Jitter that exceeds 40ms will cause severe voice quality issues. High levels of jitter is usually a consequence of slow speeds or congested networks.
Jitter Measurements
Jitter may be measured in a number of different ways, several of which are detailed in various IETF standards for RTP such as RFC 3550 and RFC 3611. Some of these methods are Mean packet to packet delay variation, Mean absolute packet delay variation, Packet delay variation histograms and Y.1541 IPDV Parameter.
Compensating for Jitter
The first thing to check is to verify the QoS settings of the company network. It is expected that the increasing use of "QoS" control mechanisms such as class-based queuing, bandwidth reservation and usage of higher speed links. If the QoS has not been configured or improperly set up, voice packets will not be receiving the proper priority. This will result in missed or discarded packets. Audio calls will then be subjected to high levels of jitter, degrading the voice quality. If the QoS settings are correct and network traffic is at its usual levels, there should not be any significant jitter.
Jitter buffers are not recommended, Although the size can be increased up to a point. Generally, they are only effective for delay variations of less than 100 ms and even then, deterioration in quality may be easily noticeable to users. There are various tools available that can be used by experts to isolate jitter sources and remove them. Therefore organizations should try to identify the sources of jitter on their networks instead of relying on jitter buffers.
Fragmentation
Fragmentation is a technique that divides a data packet into smaller data packets so that they can be sent through a network that can only transfer small data packets. Fragmentation occurs during network transmission. When these packets are received at their destination, they are reassembled to their original data packet size.
Supporting Fragmentation
In rare situations, signaling packets may become extremely large and require to be fragmented. If fragmentation is not supported there will be a loss of audio. 8x8 Recommends that Fragmentation be supported by all network equipment, including routers.
Packet Loss
Packet Loss is caused within routers. Errors in routers can, and will, occur if a router is overloaded. This will result in the router dropping packets; in IP telephony Packet loss is unacceptable. The performance of an IP call will suffer if a packet loss reaches more than 0.3 percent. Packet Delay can wreak havoc in a latency-sensitive application such as VoIP. Delays can be introduced in the data network due to router configuration, network capacity and performance and load on the equipment.
Tolerance Levels:
- Packet Loss: Less than 0.3
- Jitter Rate: Less than 20
- Latency: Less than 120 ms
Additional Information
What is Fragmentation?
Overview
It is best practice to first set up the DNS with the DNS from the Internet Service Provider (ISP). However, if issues still arise you can set the 8x8 GTM on the phones. Below is a list of DNS servers for multiple common ISPs.
It is not recommended to use Google DNS, as this will likely cause geo-routing issues.
Note: If you are setting up custom DNS on the phone, you have to set static IP first. See Set a Static IP on a Poly Phone .
ISP DNS List
Comcast DNS
- 75.75.75.75
- 75.75.76.76
Time Warner DNS
- 209.18.47.61
- 209.18.47.62
Brighthouse DNS
- 65.32.1.65
- 65.32.1.70
ATT DNS
- Primary DNS: 68.94.156.1
- Secondary DNS: 68.94.157.1
Century Link DNS
- Primary DNS: 205.171.3.65
- Secondary DNS: 205.171.2.65
COX DNS
- Primary DNS: 68.1.16.107
- East Coast DNS: 68.1.16.108
- West Coast DNS: 68.111.106.68
Sudden Link DNS
- Primary DNS: 208.180.42.100
- Secondary DNS: 66.76.175.100
Frontier DNS
- Primary DNS: 74.40.74.40
- Secondary DNS: 74.40.74.41
8x8 GTM
- 8.28.0.9
- 192.84.18.11
Note: Do not set 8x8 GTM servers as the DNS for your LAN. This will cause your computers to lose internet connectivity.
Revision History
Change Log
Dec, 14th 2022 |
The following callstats.io subnets and ports are no longer used as of Jan 2023. Subnets: 132.226.0.0/26, 168.138.100.0/26, 140.238.129.64/26, 130.61.163.128/26, 158.101.200.64/26, 152.67.22.64/26, 193.122.65.0/26, 168.138.245.192/26, 152.67.146.0/26, 129.159.81.0/26, 158.101.40.128/26 Ports: UDP 1024 - 65000 (Smart Connectivity Tests) |
Oct, 21st 2022 |
Further clarification on UDP ports 3478-3480 and add recommendation to allow always |
Aug, 17th 2022 |
8x8 Meet Anycast Subnets 13.248.132.124/32, 13.248.142.92/32,76.223.3.109/32,76.223.9.91/32 TCP:443 have been REMOVED. For proper functionality of 8x8 Meet it is recommended to place NO RESTRICTIONS ON OUTBOUND TCP Port 443 (HTTPS) traffic. |
Aug, 6th 2022 |
Add reference that AnyCast DNS Servers are not recommended |
June, 22nd 2022 |
Clarification on when NOT using SRTP for softphone (Work for Desktop/Work for Mobile) TCP Port 5199 is required |
June, 8th 2022 |
Add link to Citrix Integration Documentation/Recommendations |
May, 11th 2022 |
Update Activation ports for Audio Codes to include UDP 5499 |
May, 4th 2022 |
Add UK (152.67.137.148/32) and US (132.226.123.231/32) Customer Experience Subnets |
Feb, 14th 2022 |
Updates to Filtering functions for Subnets |
Nov, 30th 2021 |
Correction/clarification Nomadic 911 is communicating over HTTPS (TCP 443) not HTTP. |
Nov, 19th 2021 |
New Meetings Subnet in Japan. 155.248.191.0/24 UDP 10000. It will go into effect Dec 17th,2021 -- UPDATED |
Oct, 14th 2021 |
Add additional dedicated sections for Contact Center as a Stand-Alone Service |
Aug 18th, 2021 |
Added the following subnet: Canada (SaskTel): 207.195.32.64/27 |
May 19th, 2021 |
Removed the following subnets for 8x8 Meetings
|
May 7th, 2021 |
Add 35.182.82.252/32 and 15.222.42.21/32 for Quality Management as REQUIRED when using the service/application. |
April 28th, 2021 |
Updated Meetings Domains, better clarified required vs optional vs analytics, and removed outdated domains (for Meetings only) |
March 18-19th, 2021 |
|
March 9th, 2021 |
Update Contact Center Mail Server Addresses, minor corrections, and/or clarifications for Contact Center. Browser and TLS requirements added/updated CORRECTION in the United States Quality Management SUBNETS 2.35.50.242/32 was corrected to be 52.35.50.242/32 |
February 22nd, 2021 |
Additional Clarity on FTP and Email Requirements |
February 10th, 2021 |
8x8 is expanding geo-routing capabilities on April 2nd, 2021.
|
January 27th, 2021 |
For converged networks, a link to recommendation for setting up VLANs for Poly was provided. |
January 13th, 2021 |
Add WorkW WebRTC Ports |
November 21st, 2020 |
8x8 is expanding geo-routing capabilities on January 25, 2021.
Additionally added 8x8's Maestro Gateway IPs (for use when restricting access to your CRM from 8x8). |
November 5th, 2020 |
New Domain Table format with filtering and export capability added |
October 26th, 2020 |
New Subnet Table format with filtering and export capability added |
October 16th, 2020 |
|
September 24th, 2020 |
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 17th, 2020 |
ADD the following SUBNET for Australia 168.138.20.0/25 India had the following CHANGE of SUBNETS 152.67.22.0/26 REPLACED |
November 5th, 2020 |
New Domain Table format with filtering and export capability added |
October 26th, 2020 |
New Subnet Table format with filtering and export capability added |
October 16th, 2020 |
|
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) |
July 20th, 2020 |
Add *.amazonaws.com for storing and downloading Call Center Analytic reports via S3 Signed URLs. Correction on Softphone Ports, removed 5443. |
June 4th, 2020 |
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. |
Dec, 14th 2022 | The following callstats.io subnets and ports are no longer used as of Jan 2023. Subnets: 132.226.0.0/26, 168.138.100.0/26, 140.238.129.64/26, 130.61.163.128/26, 158.101.200.64/26, 152.67.22.64/26, 193.122.65.0/26, 168.138.245.192/26, 152.67.146.0/26, 129.159.81.0/26, 158.101.40.128/26 Ports: UDP 1024 - 65000 (Smart Connectivity Tests) |
Oct, 21st 2022 | Further clarification on UDP ports 3478-3480 and add recommendation to allow always |
Aug, 17th 2022 | 8x8 Meet Anycast Subnets 13.248.132.124/32, 13.248.142.92/32,76.223.3.109/32,76.223.9.91/32 TCP:443 have been REMOVED. For proper functionality of 8x8 Meet it is recommended to place NO RESTRICTIONS ON OUTBOUND TCP Port 443 (HTTPS) traffic. |
Aug, 6th 2022 | Add reference that AnyCast DNS Servers are not recommended |
June, 22nd 2022 | Clarification on when NOT using SRTP for softphone (8x8 Work for Desktop/8x8 Work for Mobile) TCP Port 5199 is required |
June, 8th 2022 | Add link to Citrix Integration Documentation/Recommendations |
May, 11th 2022 | Update Activation ports for Audio Codes to include UDP 5499 |
May, 4th 2022 | Add UK ( 152.67.137.148/32 ) and US ( 132.226.123.231/32) Customer Experience Subnets |
Feb, 14th 2022 | Updates to Filtering functions for Subnets |
Nov, 30th 2021 | Correction/clarification Nomadic 911 is communicating over HTTPS (TCP 443) not HTTP. |
Nov, 19th 2021 | New Meetings Subnet in Japan. 155.248.191.0/24 UDP 10000. It will go into effect Dec 17th,2021 -- UPDATED |
Oct, 14th 2021 | Add additional dedicated sections for Contact Center as a Stand-Alone Service |
Aug 18th, 2021 | Added the following subnet: Canada (SaskTel): 207.195.32.64/27 |
May 19th, 2021 | Removed the following subnets for 8x8 Meetings
|
May 7th, 2021 | Add 35.182.82.252/32 and 15.222.42.21/32 for Quality Management as required when using the service/application. |
April 28th, 2021 | Updated Meetings Domains, better clarified required vs optional vs analytics, and removed outdated domains (for Meetings only) |
March 18-19th, 2021 |
|
March 9th, 2021 | Update Contact Center Mail Server Addresses, minor corrections, and/or clarifications for Contact Center. Browser and TLS requirements added/updated CORRECTION in the United States Quality Management SUBNETS 2.35.50.242/32 was corrected to be 52.35.50.242/32 |
February 22nd, 2021 | Additional Clarity on FTP and Email Requirements |
February 10th, 2021 | 8x8 is expanding geo-routing capabilities on April 2nd, 2021.
|
January 27th, 2021 | For converged networks, a link to recommendation for setting up VLANs for Poly was provided. |
January 13th, 2021 | Add WorkW WebRTC Ports |
November 21st, 2020 | 8x8 is expanding geo-routing capabilities on January 25, 2021.
Additionally added 8x8's Maestro Gateway IPs (for use when restricting access to your CRM from 8x8). |
November 5th, 2020 | New Domain Table format with filtering and export capability added |
October 26th, 2020 | New Subnet Table format with filtering and export capability added |
October 16th, 2020 |
|
September 24th, 2020 | 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 17th, 2020 | ADD the following SUBNET for Australia 168.138.20.0/25 India had the following CHANGE of SUBNETS 152.67.22.0/26 REPLACED |
November 5th, 2020 | New Domain Table format with filtering and export capability added |
October 26th, 2020 | New Subnet Table format with filtering and export capability added |
October 16th, 2020 |
|
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 8x8 Work for Desktop and 8x8 Work for Mobile Remove range 50000-65535 UDP for RTP (Overlap) |
July 20th, 2020 | Add *.amazonaws.com for storing and downloading Call Center Analytic reports via S3 Signed URLs. Correction on Softphone Ports, removed 5443. |
June 4th, 2020 | 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, 8x8 Work for Desktop and 8x8 Work for Mobile, UCaaS clients, Video Meetings, and current hardware offerings).
Note: This document should supersede any other documentation that references IPs, Subnets, or Ports used by 8x8.
Applies To
- X Series Platforms
- Technical Requirements
Abbreviations
Abbreviation | Meaning |
---|---|
8x8 | 8x8, Inc. |
ALG | Application Layer Gateway |
DNS | Domain Name System |
DPI | Deep Packet Inspection |
DSCP | Differentiated Services Code Point |
EF | Expedited Forwarding |
FTPS | FTP Secure (FTP over TLS) |
GTM | Global Traffic Manager (8x8 DNS) |
HTTPs | HyperText Transfer Protocol (Secure) |
IMAP | Internet Message Access Protocol |
IP | Internet Protocol |
KB | Knowledge Base System |
LAN | Local Area Network |
LDAPs | Lightweight Directory Access Protocol (Secure) |
NTP | Network Time Protocol |
POP3 | Post Office Protocol version 3 |
QoS | Quality of Service |
SIPs | Session Initiation Protocol (Secure) |
SPI | Stateful Packet Inspection |
sRTP | (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 |
8x8 Work for Desktop | 8x8 Work for Desktop Application (8x8 UC Client for desktop) |
8x8 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:
- 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.
- 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.
- 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. 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 8x8 Work for Mobile and 8x8 Work for Desktop Clients use the 8x8 GTMs directly (with a fallback of the local DNS); thus, no additional work is needed to ensure proper routing of the traffic for UCaaS Clients.
8x8 does not recommend the use of DNS servers that make use of AnyCast, as the Geo Location can be unpredictable.
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, 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, see Disabling SIP-ALG in Your Router or Firewall.
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 8x8 Work for Desktop/8x8 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 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 centers). 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:
- UDP session timer: 660 seconds
- 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 February 28, 2021, access to the 8x8 Configuration Manager for Contact Center, Agent Desktop, along with API calls to these systems, will require up-to-date web browsers or libraries compliant with TLS 1.2 or better:
The following browsers have been verified by 8x8 QA to support the changes occurring February 28, 2021:
- Google Chrome version 70 or later
- Mozilla Firefox version 48 or later
- Microsoft Edge (any)
- Apple Safari version 9 or later
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 8x8 Work for Desktop application will respect the proxy settings of the system 8x8 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.
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 Whitelist Zero Touch Provisioning Services for Obihai and Poly Devices. Device Access to Poly’s IPs is not required for 8x8 services, it will assist/speed deployment for new devices.
Citrix
Customers using 8x8 Work for Desktop should refer to Citrix VDI Integration with 8x8 Work for Desktop & Web for more details.
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.
Requirements
Parameters | Requirements |
---|---|
Poly Zero Touch Provisioning (ZTP) | Allow Poly Zero Touch Provisioning, alternative options can be found in Setting Up ZTP Override. |
TLS | TLS 1.2 support is mandatory. |
Wiring | At least Cat 5 (preferably Cat 6) wiring for networking devices, and IP phones that use a wired connection. |
WiFi | Strong and consistent WiFi connection for networking devices, and IP phones that use WiFi. |
PoE (recommended) | See Device Manufacturer Data Sheets. |
Packet loss | 0% packet loss |
Jitter | <20 ms jitter |
Network latency | <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. |
Bandwidth requirement | Voice UCaaS and CCaaS:
Video Meetings Upstream:
Video Meetings Downstream:
Downstream max bandwidth in a conference of n people would be 2.5Mbps + (n-2)*200kbps + 40kbps 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. To estimate the network bandwidth required to support a VoIP station:
When calculating total network load, be sure to include all applications that use the network, especially applications with high bandwidth requirements (such as video conferencing). |
Contact Center hardware requirements |
|
SoHo (small office/home office) suggestions | For information on setting up SoHo networks see SoHo Networking Design Best Practices. |
Considerations
Parameters | Considerations |
---|---|
If running a converged network for voice and data | Configure VLANs to separate the traffic. Ensure that the Phone VLAN has the following DNS and NTP in its DHCP scope:
Note: The recommended DNS does not resolve any other domain except 8x8.com and packet8.net. For more information on Poly and VLANs see Poly Devices VLAN Recommendations. |
DHCP scope | 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. |
Maximum Transmission Unit (MTU) | 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. |
WAN failover | We highly recommend that you use dual WAN connections in a 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. |
VPN use cases | If your remote users or Internet egress use a VPN tunnel, 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. |
Internet Access Requirements |
|
NAT Requirements |
|
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, 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 / Application | COS Value (Decimal) | DSCP (Decimal) | Name |
---|---|---|---|---|
Windows / Non-Admin | Voice Media - Real-Time | CS7 | DSCP 56 | |
Windows / Non-Admin | SIP Signalling | CS5 | DSCP 40 | |
Windows / Admin | Voice Media - Real-Time | EF | DSCP 46 | Expedited Forwarding |
Windows / Admin | SIP Signalling | AF31 | DSCP 26 | Assured Forwarding |
Mac / iOS | Voice Media - Real-Time | EF | DSCP 46 | Expedited Forwarding |
Mac / iOS | SIP Signalling | AF31 | DSCP 26 | Assured Forwarding |
Android | Voice Media - Real-Time | EF | DSCP 46 | Expedited Forwarding |
Android | SIP Signalling | AF31 | DSCP 26 | Assured Forwarding |
Poly | Voice Media - Real-Time | EF | DSCP 46 | Expedited 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 & Purpose |
Applies To |
Protocols |
Destination Ports |
---|---|---|---|
Device
|
All Certified Physical Phones & ATAs |
|
TCP 80, 443 |
Device Secure SIP Signalling |
All Certified Physical Phones & ATAs |
SIPS (Secure SIP) |
TCP 5443 |
Device Corporate Directory |
Certified Physical Phones |
LDAPS |
TCP 636 |
Device Network Time |
All Certified Physical Phones & ATAs |
NTP |
Can be provided locally via DHCP Option 42 |
Device Domain Name System |
All Certified Physical Phones & ATAs |
DNS |
Can be provided locally via DHCP Option |
Device SIP Signalling |
All Certified Physical Phones & ATAs |
SIP |
|
Device SIP Activation |
All Certified Physical Phones & ATAs |
SIP |
|
Softphone Application & Browser
|
|
HTTPS |
TCP 443 |
Softphone Application Secure SIP Signalling (Default) |
|
SIPS (Secure SIP) |
TCP: 5401 |
Softphone Application SIP Signalling (When SRTP is Disabled this port is required. If you are using SRTP, the default setting, it is optional) |
|
SIP |
TCP: 5199 |
Real-Time Audio Voice Call Audio |
|
SRTP (Secure RTP) |
|
Real-Time Audio |
|
|
|
8x8 Meet |
|
|
|
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 & Purpose |
Applies To |
Protocols |
Destination Ports |
---|---|---|---|
Nomadic 911 Location Management | Location Manager Application (also referred to as ERS Server communications) | HTTPS |
|
Nomadic 911 Location Management | Physical Phone (also referred to as HELD Server communications) | HTTPS |
|
Quality Management Screen Recording Streaming screens |
Screen Recording Client in Quality Management |
HTTPS |
TCP 443 |
VCC FTPS Call Recording Download |
Downloads of contact center call recordings using FTP over TLS (FTPS). |
FTPS Note: FTPS is not the same as SFTP (SSH Based). |
|
Bria Softphone |
Standalone contact center softphone |
|
|
Zoiper Softphone |
Standalone contact center softphone |
|
|
Network Utility*
|
Network Assessment *8x8's recommendation is to always allow these ports |
|
|
Wavecell API |
Video API |
|
|
SIP Trunks / TIE Trunks
|
See customized Statement of Work for the unique implementation |
Applications Requiring Incoming Connections
Traffic Source & Purpose |
Destination Ports |
Source IPs |
---|---|---|
Contact Center Email POP3/IMAP email access |
Note: custom ports can be configured. |
|
SIP Trunks
|
See customized Statement of Work for the unique implementation. |
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 Whitelist Zero Touch Provisioning Services for Obihai and Poly Devices. Device Access to Poly’s IPs is not required for 8x8 services, it will 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 section.
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.
Contact Center as a Stand Alone Service
When using Contact Center as a stand-alone service (not using 8x8 UC as a voice path/answering point). If you are using 8x8's XCaaS services, this section does not apply.
Computer hardware |
|
Firewall and Network Address Translation (NAT) Requirements |
|
Additional Resources
The following resources are intended for customers who are using Jitsi, Wavecell, or other companies/brands owned by 8x8 outside of their 8x8 resources/applications.
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.
Question
How do I interpret MTR and Traceroute results?
Applies To
- WinMTR
- Networking
- Windows
Answer
MTR (My Traceroute, and originally called Matt's Traceroute) is a Linux/Unix utility that combines Ping and Traceroute functions into one easy-to-use program. WinMTR is a Windows clone of MTR. MTR is run on a computer to provide detailed hop test data (a series of brief measurements). MTR does not require installation or system admin rights.
What does MTR do?
MTR provides test results that are a combination of ping and Traceroute. Where Traceroute makes three ping tests to each hop, MTR continuously sends ping requests to each hop until you stop the test. For each hop in the path, MTR displays the:
- Average % of packet loss.
- Total packets sent and received.
- Best, average, worst and last latency test result.
There are options to copy or export the results as plain text or HTML.
How do I interpret MTR results? What do they mean?
Like a normal Traceroute, we are looking for something that replicates down the route list, through to the end. A single hop with high latency isn’t a problem—unless it’s the last one.
If a hop introduces latency, or packet loss, and that continues through the remaining hops, we have identified a problem.
In this first example, we see one hop with 23% packet loss, and one with a worst-case latency of 52ms. Neither of them is a problem since they don’t continue to the next hop in the list.
In another case, we see poor results starting at hop 11, and replicating through to the destination host. If the host was in the US and not Australia, this would be a concern.
One other thing to note is the variation in latency–jitter. There is a small amount of jitter in hop 12 (above), but it does not continue through. Even though we have higher latency in the final six hops, jitter is very good and not a concern.
Additional Information
Overview
The Smart Connectivity Test (SCT) performs active network tests both before each 8x8 Work call (pre-call tests) and in the background during a call. The aim of SCT alerts is to provide continuous diagnostics and active monitoring to help users detect and even predict bad call quality before actually experiencing it. This article provides some tips for quickly resolving the issues, and how to prevent them from occurring again based on the alerts that the user receives.
Recommended Setup
We encourage you to get familiar with network standards, and learn best practices for setting up a proper home or small area network by reviewing the SoHo Networking Design Best Practices.
Quick tips for deployment setup
- Ethernet connection is almost always faster than wireless networks. It provides the best connectivity, because it’s protected from wireless interference. The main factor that might impact connectivity over Ethernet is when another application takes over the capacity or old cables and connectors have been used (e.g., Cat3 or below) .
- Wifi is preferred over cellular networks at work or home locations. However, in public spaces where wifi networks may have capacity or connectivity restrictions, you might consider using cellular internet. In the case of using cellular data, LTE/5G is especially preferred in public locations.
- VPN servers may have capacity limitations that may slow down your internet speed. Either turn off the VPN or consider VPN split tunneling. Split tunneling provides two connections at the same time. A secure connection and an open connection to the internet. It enables you to decide which apps are routed through your VPN while others send the data through a regular network. You can ask your IT administrator for a split-tunnel set up.
Number of connections to your network
Sharing your home/office (workspace) internet network with others may cause other applications in your network to use the available capacity. Be mindful of the number of users and devices that get connected to your network. Pay attention to the apps being used while you’re making a video call, as those other streaming, gaming apps take bandwidth away from your audio and video apps. For example, Netflix at 4K streaming may use 10-30 Mbps of your bandwidth.
Reducing wireless interference
Many devices at home, e.g., microwave ovens or cordless phones, can interfere with your wifi network. If your wifi is set up at 2.4 GHz frequency band, it is more likely that your wifi is interfered with because the majority of the appliances interfere with the 2.4 GHz frequency. If your wifi router is dual-band, switching from 2.4 GHz to 5 GHz band might resolve the issue. However, while the 5 GHz frequency band provides faster speeds with less congestion, it outperforms 2.4 GHz band if you are located near the wifi router with less obstacles between your device and the wifi router.
Physical connectivity
Defective cables or bad connections may result in bad connectivity. Make sure that cables are healthy and connections (LAN, fiber-optic cables) are not damaged. Make sure that cable connectors are properly connected to your wifi, PC or laptop. If you are on a LAN network and connectors are properly setup, and still having problems, probably other apps are taking away bandwidth.
SCT Notifications and Alerts
During active monitoring, the SCT may provide a message in the 8x8 application interface indicating one or more of the issues below. Read on to see how to address each one.
Insufficient Bandwidth issue
When you’re getting an intermittent bandwidth alert, it’s likely that some other application in your workspace is consuming the capacity and very little is available to the 8x8 application. In these cases the other apps are monopolizing the connection and therefore resulting in lower quality audio and video. Consider closing other applications that may be taking bandwidth: like streaming apps, file downloads, system updates, etc.
When you’re getting a persistent alert about insufficient bandwidth over several hours or days it’s likely that the connectivity at your workspace is limited. Old Wifi routers (802.11a/b) may not have sufficient capacity to sustain multi participant video calls. Our personal recommendation is to upgrade the old router and then consider upgrading the internet connection. Consider talking to your internet service provider about upgrading your wifi router to new versions like 802.11g/n/ac.
Lossy network or high latency
A lossy network happens when the audio/video packets are not delivered to the receiver. Packet loss in VoIP is typically a slowly degrading impact on Voice Quality. The human ear is very good at handling short gaps that are typical of packet loss. So it may take a significant amount of packet loss for the user community to be annoyed enough to report it. High packet loss will cause choppy or poor-quality audio and video experiences.
High latency occurs when the data from the sender is delivered to the receiver with unnatural delays (latency). Consistent high latency can slow down conversations and also lead to the dreaded 'talk over' effect where one speaker interrupts the other unknowingly. Latency can also cause echoes making it hard for the listener to distinguish between spoken words. High latency can cause severe problems in normal one-to-one calls but these issues can be exacerbated during multiparty video or conference calls. It can cause the audio to be out of sync with the video which can quickly derail project meetings. If the latency becomes too high, you might experience times when you don't have any audio or video.
There are several reasons for lossy networks and high latency. Persistent issues over multiple days are likely due to your home/office network. VPNs are especially known to cause issues with audio and video calls too. So, consider the recommendations given in the ”Quick tips for deployment setup” section above.
Intermittent issues may be due to a change in location, gaming/streaming apps, running out of battery, or a CPU-hungry application running in the background:
- Check if you’re on the correct connection. See preference order in the Quick tips for deployment setup section.
- Check if there’s direct line of sight between your device and the wifi router, and consider moving closer. Walls, microwave ovens and other heavy duty electro-magnetic devices can interfere with your connection.
- Check if there is another application (like video streaming or gaming) running in your workspace. If your workspace doesn’t have sufficient capacity to handle several high performance applications, gaming and streaming applications can interfere with the 8x8 application. Consider closing these other applications.
Additional Resources
For additional resources or more information about 8x8 recommendations and network setup, see the following articles:
Overview
The term disconnect here is defined as you are talking on an active call (meaning you have not put it on hold, parked the call, are in the process of picking up, etc.) and the call ends. You no longer see the call on your display with the call timer incrementing. If you do see the call on your display with the timer incrementing, that means the call is still continuing and has lost audio, which is a different topic (but may be related).
Reasons
The below top ten are listed in order of probability (from most to least likely). Refer to X Series Technical Requirements for best practices. This covers both 8x8 Work and 8x8 Contact Center calls.
1. Public IP Changed
Where to look for a fix: Usually related to multi-path, load balancing, failover, redundancy actions of a router with 2 or more WAN ports or a SDWAN device.
2. NAT Port Changed
Where to look for a fix:
- TCP timer is less than 300 - 700 seconds (TLS connections only, port 5443)
- UDP timer is less than 300 seconds
- Ensure all devices have a unique NAT Assignment (for example each device has a unique IP:Port combination)
- General NAT assignment/session issue with Edge: When making corrections to timers, make sure you apply to all layer 2 or 3 devices as some networks may have multiple firewalls and access points in line.
3. Device has lost registration with 8x8
Where to look for a fix: See the suggestions for Reasons 1 and 2 above.
4. Issues with SIP Signaling or Session Timers
Potentially, SIP signaling (such as Keep-Alive/ACK communication) is blocked, or Session Timers are interrupted on your network.
Where to look for a fix: Ensure over protective security practices are not causing the issue, such as DPI, SSL Decryption etc.
5. Incorrect Call Control
Where to look for a fix:
- For Contact Center customers: Rather than attempting to use the call control (park, hold, transfer, etc) from your physical device or the 8x8 Work application, call control must be done from the Contact Center Agent Workspace interface. 8x8 Contact Center should be set up where Work applications do not present call control features.
- When the 8x8 Work for Desktop application is set to Call Using Deskphone, you must use the desk phone for call control options.
6. Remote side disconnected unexpectedly
This may include cellular drops due to poor coverage (tunnels, building restrictions, network overload).
7. Wireless Headset Disconnects
Where to look for a fix:
- Check battery
- Check within range
- Update Firmware or OS on device
8. Loss of Internet
Where to look for a fix:
- Check internet connection
- Check Wi-Fi status (See also SoHo Networking Design Best Practices
9. Loss of Power
Where to look for a fix: Restore Power
10. Carrier Issue
8x8 will manage communications in this situation and release notifications as appropriate via the 8x8 Status Page.
Getting Help from 8x8 Support
When reporting issues to 8x8 Support, having the right details to share is key to assisting 8x8 in identifying the cause of the call drop. It is critical to report as soon as you can due to the length of time logs are available.
Important information to have available
- If you have an open ticket provide the ticket number, or reference that there was an open ticket for this previously
- What was the exact representation/experience when this happened
- Example: I was on the call for 1 min talking and then the call dropped, caller called back and said they could not hear me.
- Example: I was on the call for 45 seconds and then could not hear anything, eventually the call ended.
- Example: Call was very choppy, very hard to understand, audio cutting in and out and then it was gone.
- Were you on a hard phone, Work for desktop, or Work for Mobile
- Were you In the office, at home, or "on the road"
- Do you have more than 1 WAN link?
- If yes, how is load balancing, load sharing, failover, SDWAN implemented?
- Were you on WiFi or Hard Wired?
- What was the time & date of the call along with the Caller ID (Inbound) or Number Dialed (Outbound) as well as your extension number
- Approximately how many times has this happened to you previously, and does it happen to others in the organization
Network Utility and MOS Score are not usually necessary
It is important to note that the Network Utility or Network Assessment tool will provide little to no assistance in resolving this issue due to the tool is designed to identify issues in Setting up a call or registration issues not identifying issues of an ongoing call. Nor will the MOS score of the call/past calls in most cases, MOS is related to the RTP stream also known as "Voice Quality" For example the call was choppy. This information is always welcomed but may yield little help.
Overview
This page provides details on the parts of your 8x8 system—particularly in your new administration portal, Admin Console —that you can expect to see changes in following your X Series upgrade.
Before and During Your Upgrade
Account Manager vs Admin Console
Admin Console may look different, but all the functionality you had before is still present. As before, administrators control the account and all onboarding and offboarding tasks, and determine what actions individual users can take, such as dialing internationally, recording calls, and making account changes.
In Admin Console, we have moved away from extension configuration to a user-based model for both ease of use and efficient user management. User profiles are created first, then services and phone numbers are assigned to them on the Users page. This creates an easy workflow for setting up all of your users before assigning extension services and phone numbers via your new X licenses.
You can easily navigate to settings for users, services, and sites by clicking the corresponding icon on the Admin Console home page.
Training & Helpful Links
Comprehensive information on 8x8 Admin Console can be found in:
- Work Admin & Configuration Training - Self-paced training courses providing administrators with the ability to perform common 8x8 Work administrative tasks.
- 8x8 Admin Console Web Guide - The complete administrative user guide.
- 8x8 University 8x8 Admin Console Training - Get to know the basics of of using 8x8 Admin Console in this free online course.
X Series Upgrade Impact
The below sections cover details and system changes related to your upgrade from Account Manager to Admin Console.
8x8 Configuration Manager for Contact Center
8x8 Contact Center Administrator Permissions
- The primary and secondary admins username and password will remain the same after the upgrade.
- Admins assigned granular admin access prior to the upgrade will have full user administrative privileges after the upgrade, such as create, edit, view, and delete users. Permissions can be removed after your account is upgraded.
- Further admin permission details:
- Admins that have access to Virtual & Toll Free Numbers and Number Transfer Requests in Account Manager will be given access to Virtual Contact Center Channels after the upgrade.
- Admins that have access to Channel Rerouting in Account Manager will be given access to VCC Routing Plans after the upgrade.
- Admins that have access to Contact Center Calling Plans in Account Manager will not be given any certain admin access to VCC.
- After your account upgrade, if newly created Virtual Contact Center admins do not have the Virtual Contact Center Config Mgr icon in their Application Panel there are two options to resolve:
(1) Assign the VCC Admin (default) and Company Admin (default) roles to the newly created user
- OR -
(2) Assign a VCC or VO license and the VCC Admin (default) role to the newly created user
See also: Viewing and Creating X Series User Roles |
Channel Routing Plans
- After your account upgrade only the latest version of your Alternate routing plan will be available, and any additional Alternate plans will be lost.
- The Normal routing plan will remain the same.
Creating Contact Center Users In The 8x8 Admin Console
- After your upgrade, if you need to create new 8x8 Contact Center agents, this will need to be created in the 8x8 Admin Console. The process to configure the user in Configuration Manager for Contact Center will be the same after your upgrade.
- For details on this process see links below.
See also: |
Password Policy Support
- Your current password policy settings will remain the same after your account upgrade.
- You will not have the ability to edit these password policy settings after your account is upgraded.
- At this time there is no option available in the 8x8 Admin Console or Configuration Manager for Contact Center to edit password policy settings.
- The ability to edit password policy settings will be available in the Admin Console in the coming months.
- To modify your password policy settings after your account is upgraded reach out to Support for assistance to make adjustments.
8x8 Admin Console
Adjunct Lines
- While only the primary extension of adjunct lines is included in the upgrade, all lines tied to the primary will continue to work as normal after the upgrade.
- Any changes attempted to be made to the primary user profile after the upgrade will not actually push to either the primary or the other lines.
Advanced Call Forwarding
- Advanced call forwarding rules are not visible in 8x8 Admin Console, however, these rules will still function as expected after the upgrade.
Advanced call forwarding rules will continue to work until any change is made to the user profile. These rules will be removed and will need to be reset again in the 8x8 Admin Console.
Auto Attendants
- All your Auto Attendant profiles from Account Manager (both active and inactive) are included in your system upgrade.
- After the upgrade, submenus that are shared between Auto Attendant main menus (BH/AH) will not be visible in 8x8 Admin Console until the Monday following the upgrade. This is a display issue only, calls to these Auto Attendants will continue to route as expected and will not be impacted.
- When this display issue is resolved on Monday, Auto Attendants main menu that shared a submenu in Account Manager will each have their own submenu.
- Admin Console supports the ability to create one Auto Attendant schedule and apply it to multiple Auto Attendants on your account.
- Auto Attendants included in the upgrade that have never been turned on before can only be turned on by support after the upgrade.
- After the upgrade all Auto Attendant profiles will continue to work as expected, but in order to make changes to the Default Auto Attendant (extension 444) in Admin Console you will need to edit and save changes to the (extension 445) Auto Attendant instead. Any changes made to the (ext 445) Auto Attendant will reflect for the Default Auto Attendant (ext 444).
- This will not cause any changes to your current call routing setup for the Default Auto Attendant (ext 444). Calls routing to the Default Auto Attendant (ext 444) will still route as expected.
- Admins can remove the phone numbers from the Default Auto Attendant (ext 444), but if the phone numbers are not promptly reassigned to another service this will cause downtime until the numbers are reassigned.
- Avoid deleting the (ext 445) Auto Attendant, as it will disconnect the two Auto Attendants and calls to the Default Auto Attendant (ext 444) will no longer route correctly.
- When in edit mode for these Auto Attendants, yellow banners will display at the top of the page with further details. (See screenshots below)
- If you have issues with your Auto Attendant(s) after your account upgrade reach out to support.
Default Auto Attendant (x444) Preview
Auto Attendant (x445) Preview
See also:
Set up an Auto Attendant in 8x8 Admin Console
Billing & Licenses
- Billing settings have been moved to the My 8x8 Support Portal. See How do I use the 8x8 Support Portal (My 8x8)?
- Your bill will be shorter and easier to read as individual service lines are now packaged into bundled services called Licenses.
- After your account upgrade there will be a slight difference with how phone numbers are listed in your billing statement. Phone numbers that are assigned to a users profile with an extension (X Series service) will have more than one listing in your billing statement (as listed and shown below) :
- Additional Local Numbers are priced based on the contract price
- Numbers assigned to a user profile with an extension (X Series service) are priced at 0
- This is expected behavior and does not indicate a discrepancy in your bill.
See also:
Checking Billing Statements in the 8x8 Support Portal
Call Logs & Reports - Analytics
- Ongoing reports for billing call logs will continue to work after the upgrade.
- Any scheduled reports created before the upgrade will not be available after the upgrade and will need to be recreated after the upgrade. To save these reports we recommend downloading your scheduled reports before your upgrade date.
- For assistance navigating to the Analytics section in the 8x8 Admin Console see the documentation linked below.
Call Queues
- Users listed in both the primary and secondary member groups will be included only in the primary member group after the upgrade.
- Admin Console supports users to be added to either the primary or secondary member groups, but not both.
Communication Preferences
- Management of communication preferences with regard to 8x8 e-newsletter, satisfaction survey, and product trial or promotional emails is not supported in Admin Console.
Contact Center Multiple Tenant
- Contact Center Multiple Tenant customers' admins that are not Super Admin or Company Admin, will have read-only view access to the tenant list in Admin Console. They will not be able to edit any tenant in Admin Console unless another admin which has RBAC permissions, assigns them the tenant's permission.
- Role-based access control (RBAC) is not available for call recordings for Contact Center customers in X series. All admins will see all call recordings for all contact center tenants linked to the PBX.
- New Tenant creation is currently not available.
- Add-on licenses need to be manually assigned to respective tenant in Admin Console.
- CC Analytics will still not support multiple tenant
Conference Bridge
- Individual conference bridges and their dedicated numbers will be replaced with 8x8 Meetings.
- 8x8 Meetings will include a list of domestic and international dial-in numbers for participants that would prefer to dial into the meeting as opposed to joining online.
- The conference bridge extension, 556, is not available to be assigned to users.
Cost Centers
- Existing Cost Centers are included in your account upgrade, and your current setup will not change.
- Cost Centers will be located in the M8x8 Customer Portal under the Billing tab labeled “Cost Center Management”.
- Admins with the Billing or My8x8 role assigned will have access to Cost Center Management.
- For further details on Cost Centers in X Series follow this link.
Cross-PBX Dialing Enabled - Multiple PBX Accounts
- Accounts with more than one PBX that do not have cross-PBX dialing setup will have cross-PBX dialing enabled prior to the scheduled upgrade date.
- 8x8 will enable this feature for these customers within the two weeks prior to their scheduled upgrade date.
- There is no action to the admins or end-users before or after changes are made.
- Enabling cross-PBX dialing will not cause any changes to your current phone system functionality or dialing flow.
- When cross-PBX dialing is enabled the PBX dialing-code will immediately display in front of your users extension numbers in the contact directory of WorkD and WorkM (formerly 8x8 Work Desktop & Mobile), and will also be visible in the 8x8 Admin Console on the Users page after your upgrade (sample preview below¹). These changes will not be visible in Account Manager.
- Once this feature is enabled users will have the ability to dial-by-extension across other PBXs using the designated PBX dialing code.
IMPORTANT
Customers with multiple PBXs that have previously configured Branches but without a PBX access code will see a change in behavior for physical phone devices such as Poly, Cisco, and Yealink phones. The addition of a PBX access code during the upgrade process will require all users with these device types to enter in the new PBX access code generated by 8x8 to dial outside of the PBX. 8x8 Work for Desktop and Mobile applications will not see a change in dialing behavior, as the applications always use fully qualified extension numbers.
Below is a summary of cross-PBX dialing setups that will not have an impact on dialing behavior.
- No PBX access code or branches = No impact to previous dialing behavior. Upgrade will introduce the ability to cross-PBX dial, which was not present before.
- PBX access code only = After upgrade no impact or change in behavior for any device type.
- PBX code + branch code = After upgrade no impact or change in behavior for any device type.
See also: |
Emergency Service Address
- Existing Emergency Service Addresses will carry over as is after your upgrade.
- A users Emergency Service Address will be located in the user's profile, under the Emergency address section (screenshot below).
See also: |
Extensions
- All existing extensions are included in your system upgrade, and will be assigned to users.
- The voicemail extension, 555, cannot be assigned to users.
- The conference bridge extension, 556, cannot be assigned to users.
See also:
What is a User Profile and what can I do with it?
Fax Numbers
- All fax numbers, additional and the main fax line tied to a user's extension, are included in the upgrade.
- The fax number tied to a users primary extension will continue to be the main fax number for that user after the upgrade.
Integrations: ACT! Plug-In for Windows
The 8x8 ACT! plugin for Windows will not function for upgraded customers, as it requires Account Manager-based login credentials.
This plugin is in the process of being retired, so there will be no further development.
Integrations: Click2Pop
As of September 10, 2020 the Click2Pop application is retired and will no longer function for any user, including Account Manager users.
See also:
Meeting Dial-In Numbers - Dedicated Numbers
- Local and toll-free dial-in meeting numbers tied to a users extension are included in the upgrade, and will continue to work as dial-in numbers for meetings that were created before the upgrade.
- These dedicated meeting numbers will not be available to view in your system after the upgrade as they are not supported in Admin Console.
- Video Meetings offers a full list of domestic, toll-free, and international dial-in numbers for participants that would prefer to dial into the meeting as opposed to joining online.
Messaging & SMS
- Messaging can be disabled or enabled for all or some users in Admin Console via User Profile Policies.
- The option to allow the entire company to either save or delete message history is not supported.
- As long as messaging is enabled, any user with a US or Canada-based phone number will have SMS available to them.
See also:
Configure a User Policy Profile in 8x8 Admin Console
Metered & Pro (X Series) Services
- Customers moving from our Legacy offering may see the additional X Series Metered or Pro packages listed in their bill after their account is upgraded. The features of these services can be found in the below article:
See also: X Series Metered & Pro Services Table |
Password Policy Support
- Your current password policy settings will remain the same after your account upgrade.
- For a period, you will not have the ability to edit these password policy settings after your account is upgraded.
- At this time there is no option available in the 8x8 Admin Console or Virtual Configuration Manager for Contact Center to edit password policy settings.
- The ability to edit password policy settings will be available in the Admin Console in the coming months.
- If you need to modify your password policy settings after your account is upgraded, reach out to Support for assistance to make adjustments.
PBX & Company Name
- Only PBX Name and Company Name are available for review.
- Phone System Name is not supported.
See also:
Check Your PBX Name in 8x8 Admin Console
Physical Devices - Unsupported
- Physical devices and phones are included in the upgrade and will continue to function as normal after the upgrade, but not all makes/models are supported in Admin Console.
- Unsupported devices will continue to operate normally after the upgrade to Xseries. However below we will explain some of the limitations managing them in the future.
- A banner will display in the users profile where there is an unsupported device assigned.
- Devices included in the upgrade that are not supported in Admin Console
- It cannot be edited after the upgrade.
- It cannot be added back to your account if removed after the upgrade.
- Will be listed on the Devices page as an Unsupported Device.
- Any changes made to the user profile that has an unsupported device assigned to it will result in the device not working or changes not saving correctly, and the device will need to be replaced.
- You will not be able to swap the unsupported device with a supported device. A new user profile will have to be created to activate the new device, and the old user profile can be deleted.
- To replace the device, contact your Sales Representative to get more information for a new device and the Flex Program.
- Shared Lines (Aastra devices)
- Shared lines will continue to work after the upgrade, however you will not be able to edit these lines after the upgrade.
- Shared lines can only be used and configured on Astra devices, which are not supported in the 8x8 Admin Console.
- We would recommend replacing all Aastra devices on your account with a supported Poly device.
See also: A list of supported devices on Admin Console can be found here.A list of devices not supported on Admin Console can be in Unable to Activate Desk Phone After Upgrading to X Series.
Power Keys
- Existing power keys are included in the upgrade and will be brought over as is.
- While existing power keys will display correctly on the phone after the upgrade, they will not display correctly in the 8x8 Admin Console.
- Editing existing power keys after the upgrade will cause the keys to rearrange incorrectly on the phone, and will still not display correctly in the 8x8 Admin Console.
See also:
Configure Power Keys in Admin Console
Primary & Secondary Administrators
- The primary and secondary admins username and password will remain the same after the upgrade.
- Admins with partial permissions to billing will have full access to billing after the upgrade. The same applies for admins with partial permissions to ordering.
- Admins with full access to billing will continue to have full permissions to Billing after the upgrade. The same applies for admins with full permissions to ordering.
See also:
Receptionist Extension
- Existing custom receptionist extensions will still work after the upgrade, but editing these extensions is not supported in Admin Console in the front end.
- This includes receptionist extensions that are added to any Call Queues and Ring Groups, which is not supported in the 8x8 Admin Console in the front end.
- To remove a custom receptionist extension after the upgrade, create a case with 8x8 Support.
SIP Trunk
- There are no facilities in 8x8 Admin Console to edit SIP Trunk configurations in the new X Series environment. To make modifications in the future, submit a case to the 8x8 Technical Support team. More details can be found in the X Series SIP Trunk FAQ.
Users & User Setting Access
- Users have access to their own user profile options through Account Settings in 8x8 Work for Desktop.
See also:
8x8 Work for Desktop: Navigate Your Settings
Users Assigned Multiple Extensions
- Users assigned multiple extensions with one profile currently have the ability to log into their extensions on 8x8 Work for Desktop or 8x8 Work for Mobile with one username and can select the extension they wish to log in to from the list of assigned extensions that display after entering login credentials.
- Logging into an additional (non-primary) extension on the day of the upgrade will cause the voicemails for that extension to be unavailable until after the upgrade.
- Call recordings will be unavailable after the upgrade for additional (non-primary) extensions. To retrieve call recordings from additional extensions reach out to support.
- After the upgrade, all extensions will have their own individual usernames, and these users will have to log in to each extension individually.
- The user's 8x8 Work login will follow the extension that was last logged into before the upgrade and will include that extension's personal contacts and profile picture.
- The original username will be assigned to the extension that was last logged into the 8x8 Work application(s):
- If a user has 8x8 Work for Desktop only - the most recently logged into an extension on the Desktop app will be assigned the original username.
- If a user has 8x8 Work for Mobile only - the most recently logged into an extension on the Mobile app will be assigned the original username.
- If a user has 8x8 Work for Desktop & 8x8 Work for Mobile - the most recently logged into an extension on the Desktop app will be assigned the original username.
- The original username will be assigned to the extension that was last logged into the 8x8 Work application(s):
- The remaining extensions will still be assigned to the user but they will each have their own dummy user profile and 8x8 Work username. They will inherit the first name, last name, and voicemail to email notifications.
- The user will receive a Welcome Email for each dummy profile with the extension info, the new username, and a link to create a password.
Contact Center Users Assigned Multiple Extensions
- If a Contact Center agent's Account Manager profile has the "VCC Dedicated Extension" box checked, then that user's 8x8 Work login will follow that extension after the upgrade. (see screenshot below)
- If this box is not checked for any of the user's extensions, then the users 8x8 Work login will follow the last extension the user was logged into prior to the upgrade. (see screenshot below)
Example:
- User Joe is on account PBX1.
- Joe has the username joe8x8 assigned to four extensions in Account Manager: 1001, 1002, 1003, & 1004
- After the upgrade there will be three new users created for each additional extension and they will have their own individual usernames.
- The original username (joe8x8) will follow the extension that was last logged into 8x8 Work for Desktop or 8x8 Work for Mobile before the upgrade. In this example it is extension 1003.
- Joe will receive a Welcome Email for each of the other extensions and will include details such as the new username and a link to create a password.
VCC Users Assigned Multiple Extensions
Users With Only a Profile—No Extension or Phone Number Assigned
- Users in Account Manager that were only assigned a user profile and are not tied to any extension or phone number are included in your system upgrade.
- After upgrade, these users' time zone will default to US Pacific Time, and their language will default to English.
- These user settings can be adjusted as needed after the upgrade, when assigning an extension to the user.
- Users that have Analytics privileges and do not have an extension assigned will still have access after the upgrade. However, these users will fall into one of the two scenarios after the upgrade depending on whether they are assigned Essential or Supervisor access:
- Users without an extension that have access to Analytics Essentials will be able to access Analytics through their SSO Panel after the upgrade. To upgrade these users to have Supervisor Analytics access reach out to your sales representative to order the appropriate license.
- Users without an extension that have access to Analytics Supervisor will have a user profile created with an extension number and license assigned after the upgrade, and will have the same access they did before the upgrade.
See also:
Create a User Profile in 8x8 Admin Console
Virtual Extensions
- Virtual Extensions are not supported in Admin Console.
- Existing users assigned to Virtual Extensions are included in your upgrade, but will continue to NOT:
- Have access to the 8x8 Work for Desktop or 8x8 Work for Mobile.
- Be able to have physical devices (desk phones or adapters) activated on these extensions.
- To assign regular extensions to these users, the users will need to be deleted and recreated manually.
Virtual Numbers
- All your Virtual Numbers are included with the same routing in your upgrade.
- In Admin Console, Virtual Numbers are no different from regular phone numbers.
- All phone numbers on your account will be visible and managed in one location.
See also:
Claim Phone Numbers in 8x8 Admin Console
8x8 Work for Desktop & 8x8 Work for Mobile Applications
- Admins on X Series can continue to disable access to 8x8 Work for Desktop for users as needed.
- At this time, X series admins are unable to disable use of 8x8 Work for Mobile.
- Users may need to log out and log back into 8x8 Work for Desktop or 8x8 Work for Mobile after the upgrade.
8x8 Work for Web
- 8x8 Work for Web will not be available after the upgrade, but when the new version is available you will be automatically added to the beta list to test it out.
- More details will be provided when available.
Voicemail To Email Notifications
- Voicemail to email notification options are still configurable available per user -- however, the Link Only option is not available.
- Users previously configured for the Link & Attachment option will be set to Attachment Only.
- Users previously configured for the Link Only option will be set to Notification Only.
- The voicemail to email options available in Admin Console are:
- Notification Only
- Attachment Only
- Attachment only, delete original voicemail
- Disable
See also:
Change Voicemail Email Notification Settings for a User
Voicemail Transcription
- Voicemail transcription is an available option in Admin Console, and can be enabled or disabled as needed across your account.
See also:
Enabling Voicemail Transcription for Your Company in 8x8 Admin Console
More Helpful Links
Comprehensive information on Admin Console can be found in:
- Admin Console Web Guide - The complete administrative user guide.
- 8x8 University Admin Console Training - Get to know the basics of of using Admin Console in this free online course.