To make our WebRTC solution more resilient, we use two WebRTC providers. You must configure your firewall for both providers. | Note |
|---|
| Adding an IP address to your outbound firewall enables both inbound and outbound WebRTC traffic so you do not need to add the IP address to your inbound firewall too. |
- Vonage WebRTC provider
When using WebRTC, you must use IPv4 over IPv6 in prefix policies. | Purpose | Protocol | Source IP | Source port | Destination port | Destination IP |
|---|
| Signalling/presence | TCP | Your local network addresses | *Ephemeral range | 443 | See Destination IP addresses. | | Media | UDP | *Ephemeral range |
*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, with source ports generally up to 20,000 and destination ports generally over 50,000.
Destination IP addresses
Your firewall settings should allow outbound traffic as specified in the following list:
| Iframe |
|---|
| src | https://dailcp68gmmru.cloudfront.net/ip-whitelist.html |
|---|
| width | 75% |
|---|
| height | 150 |
|---|
|
- Backup WebRTC provider
Add all the IP addresses listed in the following pages to your allowlist:
If your agents use VPN clients, you must also add *.nexmo.com to your allowlist; failure to do so may result in agents not being able to use WebRTC. Where relevant, you must also add *.nexmo.com to the VPN's proxy bypass list and then restart your agents' clients. |