Firewall configuration
Firewall configuration
In this section | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Version history | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
About this page
You must read this entire section to ensure that you configure your firewall correctly.
Inbound and outbound traffic terminology:
Inbound describes traffic from VCC.
Outbound describes traffic to VCC.
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 are processed in a timely and efficient manner (call steering buttons, call transfers, hold requests, and so on).
You should also review any IP packet inspection or local caching policies to optimize the user experience.
Ports
Outbound
All outbound traffic requires TCP port 443 (HTTPS). Responses are sent to a range of ephemeral ports. This requirement applies to:
VCC traffic, regardless of whether you use URL or IP allowlisting
VCC APIs
WebRTC traffic (see WebRTC sections later in this page for information about other ports required for WebRTC traffic)
All other third-party traffic (Amplitude, Cloudfront, and NewRelic)
SFTP access to call recordings requires TCP port 44044.
Inbound
All inbound traffic requires access to destination TCP port 443 (HTTPS) on our servers to establish a connection. Responses are sent to a range of ephemeral ports.
Virtual private network (VPN)
We recommend using a split tunnel configuration to ensure that traffic—especially voice traffic—to Vonage services is routed directly from the end user to our platform and not through a VPN. We do not recommend tunneling voice connectivity through a VPN tunnel due to the potential adverse effect on voice quality.
Using URL allowlisting (recommended)
Depending on whether you will use wildcard or fully qualified domain names, add the following URLs to your allowlist:
Using wildcard domains:
*.vonage.com
*.vonagenetworks.net
*.cc.vonage.com
*.api.cc.vonage.com
*.newvoicemedia.com
*.api.newvoicemedia.com
*.contact-world.net
api.amplitude.com
bam.nr-data.net
js-agent.newrelic.com
*.nexmo.com
*.adobedtm.com
Using fully qualified domain names (FQDN):
WalkMe traffic
Adobe Analytics
Add the URL addresses specified in the following page to any existing firewall permissions: https://experienceleague.adobe.com/docs/analytics/technotes/ip-addresses.html?lang=en
You must also add the IP addresses specified in the following sections to your allowlist:
Screen recording traffic
WebRTC traffic
Webhooks API traffic
Using IP allowlisting
If your firewall does not support URL or DNS allowlisting, add the following IP addresses for your region to any existing firewall permissions.
For general assistance, please contact Customer Support.
For help using this documentation, please send an email to docs_feedback@vonage.com. We're happy to hear from you. Your contribution helps everyone at Vonage! Please include the name of the page in your email.