Customers with firewall policies in place that are restricted to the node addresses used in Lifesize Cloud, must ensure their firewall rules whitelist all of the IP addresses outlined below. Failure to do so may result in loss of access to the service in the event of a fault or failure condition.
|Location||Front-End Server||SfB/Lync Gateway||Desktop Tunnel Gateway||Web App and New Desktop App |
|Dallas, TX, USA||188.8.131.52||184.108.40.206||220.127.116.11||18.104.22.168|
|Dallas, TX, USA||22.214.171.124||126.96.36.199||188.8.131.52|
|Mexico City, Mexico||184.108.40.206||220.127.116.11||18.104.22.168|
|San Jose, CA, USA||22.214.171.124||126.96.36.199||188.8.131.52|
|San Jose, CA, USA||184.108.40.206||220.127.116.11||18.104.22.168|
|Sau Paulo, Brazil||22.214.171.124||126.96.36.199||188.8.131.52|
|Washington DC, USA||184.108.40.206||220.127.116.11||18.104.22.168|
|Washington DC, USA||22.214.171.124||126.96.36.199||188.8.131.52|
The monitoring and calendaring micro services require communication over TCP port 443 with nucleusproxy.lifesizecloud.com. If you are unable to whitelist the domain, the current IP addresses are 184.108.40.206 and 220.127.116.11.
This complete list of Lifesize Cloud front-end server addresses is always current and available under Advanced Settings on the Lifesize Cloud Admin Console.
Lifesize also announces new server locations and node addresses via the Lifesize Cloud Status Page located at status.lifesizecloud.com. Please subscribe so you’re always in the know.
rev.06.14.2017 to update with information found here:How Calendaring / Icon Monitoring Services Communicate with Lifesize Cloud.