| Section | |||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Your processor speed and RAM must meet the recommended specification for your operating system.
Screen resolution
1024 x 768 pixels
...
| Note |
|---|
| Vonage will provide additional IP and port information where relevant for your location. |
WebRTC
...
Server-side ports—outbound traffic (packets leaving the customer's network)
...
Signaling: 443
Presence: 443
Real-time Transport Protocol (RTP): 10,000-20,000
...
Client-side ports—
return traffic (packets entering the customer's network)
...
Connectivity requirements
| Purpose | Protocol | Source IP | Source port | Destination IP | Destination port |
|---|---|---|---|---|---|
| Signalling/presence | TCP | Your local network addresses | *Ephemeral range | See Firewall configuration. | 443 |
| Media | UDP | Your local network addresses | *Ephemeral range | See Firewall configuration. | 10,000–50,000 |
*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.
...
Signaling: TCP
Presence: TCP
RTP: User Datagram Protocol (UDP)
...
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.
...
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. |
...
| Note |
|---|
You must whitelist 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. |
| Iframe | ||||||||
|---|---|---|---|---|---|---|---|---|
|