| Section | |||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Tip | ||||||
|---|---|---|---|---|---|---|
| ||||||
Web browsersFor all browsers you must enable the following:
We support the following browsers:
We do NOT support Apple® Safari® on an Apple Mac when using the Mid-Call Payment Transfer solution or Conversation Analyzer Analytics. We do NOT support privacy mode in any browsers when using ContactPad. |
...
Your processor speed and RAM must meet the recommended specification for your operating system.
Screen resolution
1024 x 768 pixels
Firewall
Vonage Contact Center, including screen pops, requires port 443 (HTTPS)
SFTP access to call recordings requires port 22
Bandwidth
ContactPad uses 8 kilobytes per second (KBps)
...
*Ephemeral Range: The application will select any available port from a range depending on the operating system. On most machines, the port range is 1,024 to 65,535.
Firewall configuration
For the browsers that will be using ContactPad with WebRTC, your firewalls should allow the outgoing traffic as specified and return traffic in response.
All service endpoints are IPv4, IPv6 is not currently supported.
Vonage Contact Center's WebRTC servers use fixed IP addresses from a public range. The WebRTC client uses Global Low Latency (GLL) architecture. GLL reduces the latency of calls by selecting the closest IP address for WebRTC, but includes failover to another IP address if the closest one is not available.
We recommend that you configure your firewall to allow all of the following IP addresses to prevent loss of service in case of failover:
| Iframe | ||||||||
|---|---|---|---|---|---|---|---|---|
|
In addition you should allow the IP addresses listed in the following pages:
...
.
...
To ensure the quality of service for time-critical communications during occasional traffic peaks, we recommend that you prioritize UDP and TCP traffic to and from these IP addresses. Vonage Contact Center WebRTC servers use dynamic port numbers. We therefore strongly recommend that your firewall does not limit access to a specific range of port numbers for those IP addresses.
Additional requirements for using WebRTC
| Item | Requirement/recommendation | ||
|---|---|---|---|
| Supported browsers | Google Chrome™, latest version, using the WebRTC for Vonage Contact Center extension.
| ||
| Salesforce integration | WebRTC is only supported in Salesforce Lightning Experience and in the console view in Salesforce Classic. For information about Salesforce console, see Salesforce help. | ||
| Backup phone | All agents should have access to an alternative phone as a backup for WebRTC. | ||
| Alternative phone | We recommend that agents have access to an alternative phone for non-Vonage Contact Center related calls. |
| Include Page | ||
|---|---|---|
|
...
| Note |
|---|
You must read this entire section—including Application acceleration later in this section—to ensure that you configure your firewall correctly. |
The following table contains the URLs of our data centers with their corresponding IP addresses. You must add the appropriate IP addresses for your region to any existing firewall permissions.
We recommend adding the appropriate URLs and IP addresses to any firewall rules that restrict employee access, and we request that you treat Vonage Contact Center as a business critical application. By this, we mean optimizing and prioritizing IP traffic to Vonage Contact Center over other non-critical traffic. This is to ensure real-time responses to agent requests (call steering buttons, call transfers, hold requests, and so on).
We recommend that you also review any IP packet inspection or local caching policies to optimize the user experience.
...
194.140.251.7
194.140.251.14
194.140.252.7
194.140.252.14
89.187.126.117
194.140.251.71
194.140.251.84
194.140.252.71
194.140.252.84
35.178.30.136
3.11.193.198
3.126.22.243
3.121.175.40
...
107.23.216.122
18.208.11.69
54.176.97.247
54.176.165.234
...
13.236.101.83
13.55.214.98
52.74.111.52
52.77.102.86
...
| Info |
|---|
Outbound IP addressesOutbound IP addresses are used for standard web access, for example, agents and supervisors accessing Vonage Contact Center applications. All customers will need to allow this. Inbound IP addressesInbound IP addresses are used when Vonage Contact Center interacts with an external system where IP allowlisting is in place. Such systems include Salesforce; a customer-owned, or managed, server or service; and other cloud provider services. |
Application acceleration
To improve performance and response time, we use a content delivery network (CDN) for some of our static Vonage Contact Center website resources.
Your firewall must allow requests to cdn.newvoicemedia.com for supervisors and agents to access Vonage Contact Center applications.
If your firewall does not support URL/DNS allowlisting, you must allow the IP addresses listed at http://d7uri8nf7uskq.cloudfront.net/tools/list-cloudfront-ips.
| Note |
|---|
You must allow these addresses regardless of your region and in addition to the region-specific URLs in the table. The list of addresses at http://d7uri8nf7uskq.cloudfront.net/tools/list-cloudfront-ips is subject to change. |
...
|