As a general matter, you will not need to do anything with these IP addresses as our provisioning servers will take care of SIP device configuration.  Each client's dedicated domain name will resolve to the appropriate server automatically.


In certain situations, however, it may be necessary to open ports in the client site firewall.  We recommend utilizing the subnet ranges, as there may be more than one server on a given Geo-Node that can serve the same function.  The following are Subnet Ranges and IP Addresses that are in use by our system:


70.42.44.0/24 (Secaucus Geo-Node)

75.98.50.0/24 (Dallas Geo-Node)

216.24.144.0/24 (Las Vegas Geo-Node)

199.21.246.224/27 (Minneapolis Geo-Node)

207.254.80.0/22 (Overlay Cluster)
- 207.254.80.0/24 (Atlanta)
- 207.254.81.0/24 (Secaucus)
- 207.254.82.0/24 (Dallas)
- 207.254.83.0/24 (Las Vegas)

18.209.52.107/32 (Instant FAX ATA System)

54.219.249.208/32 (Instant FAX ATA System)


Our Modern UC Apps (ConnectUC and MeetingsUC) utilize Amazon's Elastic Load Balancer Service.  We recommend you allow traffic to the following domains:

- *.gazelletel.com
- ws.connectuc.io
- api.connectuc.io
- *.reachuc.com
- *.ws-messaging.chime.aws


The following protocols and ports are used by our systems:

ProtocolPort(s)Use
TCP80, 443HPBX Web UI's and Provisioning Server
TCP80, 442, 443Instant FAX System
UDP10000 - 65535ReachUC Media
TCP443, 4998, 5060ReachUC Signaling Functions
TCP7000, 7001Instant FAX ATA
TCP8089Management UI's
TCP24998ReachUC Messaging Functions
UDP4998ReachUC Presence
UDP5060HPBX SIP Signaling
TCP
5061HPBX SIP Signaling over TLS
UDP8889Web Meetings and Video Conferencing
UDP17000 - 35999HPBX RTP Traffic (Call Audio)
TCP443, 9002ConnectUC Encrypted Web Socket
UDP443, 30000 - 40000ConnectUC Media over DTLS