Firewall configuration
In this section | ||||||
|---|---|---|---|---|---|---|
| ||||||
| Version history | ||||||
|
| Note | ||
|---|---|---|
| ||
|
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).
...
- Using wildcard domains:
- *.vonage.com
- *.cc.vonage.com
- *.newvoicemedia.com
- *.api.newvoicemedia.com
- *.contact-world.net
- api.amplitude.com
- bam.nr-data.net
- js-agent.newrelic.com
- *.nexmo.com
Using fully qualified domain names (FQDN):
WalkMe traffic
Insert excerpt _ExcerptWalkMeFirewallConfiguration _ExcerptWalkMeFirewallConfiguration nopanel true
You must also add the IP addresses specified in the following sections to your allowlist:
...
WebRTC traffic
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
| Insert excerpt | ||||||
|
WalkMe traffic
|
...
Using IP allowlisting
...
If your firewall does not support URL/DNS allowlisting, add the following IP addresses for your region to any existing firewall permissions:
--Amazon Web Services (AWS)
Most of VCC uses Amazon Web Services (AWS).
...