The Edge WAN IPs are not required to be public IP addresses and private IP addresses will allow the Edges to connect to the cloud, talk to internal resources, and even support public WebRTC clients. Using private IPs on your Edge may limit some other functionality, for example if you have a telco carrier that requires it. Additionally, when the Edge uses a private IP address and you have public WebRTC clients connecting, you are traversing a NAT boundary. NATs are supported, but you should validate your configuration to ensure the optimal media path is used. Symmetric NATs are known to introduce less desirable media paths.
WebRTC calls will use TURN servers when network access is restricted or NAT configurations, such as symmetric NATs, restrict direct media. It is always recommended to trace your call paths to ensure traffic is flowing in the intended direction for the highest quality call experience.
------------------------------
Phil Whitener
Genesys - Employees
------------------------------
Original Message:
Sent: 09-03-2020 19:03
From: Vaun McCarthy
Subject: Edge WAN IPs?
Do the Edge WAN ports require their own public facing IPs? Or is it sufficient that they have their own private IP behind NAT? If they share a public IP as with the rest of an org, then any communication iniitated externally wouldn't know which Edge device to go to, or would that be handled internally by the Cloud platform with the Edge being in service?
#Implementation
#SIP/VolP
#Telephony
------------------------------
Vaun McCarthy
NTT New Zealand Limited
------------------------------