URLs and ports used by ClickShare

상품 번호: [3220] - 레거시 코드: [12420]

적용 가능

This article describes the urls and ports the ClickShare system requires to be opened in your corporate firewall per functionality.

1	For devices to communicate to XMS Cloud	"sil-xms-prd01-iothub.azure-devices.net" Port "443" ** ".cloudapp.azure.com" Port "443" * "silxmsprd01sa.blob.core.windows.net" Port "443" ".azure-devices.net" Port "443" (IOT XMS for device control) "barcoprdwebsitefs.azureedge.net" Port "443" "xms.cloud.barco.com" Port "443" ".core.windows.net" Port "443" (for device logs) "azure.microsoft.com" Port "443" (for connection test) "*barco.com" Port "80' (for firmware download) "xms-reg.cloud.barco.com"
2	For Registration/FW update	www.barco.com" Port "80" (location of the JSON file containing the firmware file list) xms-reg.cloud.barco.com
3	Dedicated for XMS Edge devices its own firmware	"update-xms.cloud.barco.com" TCP Port "443" ".cloudfront.net" TCP Port "443"
4	Dedicated Base Unit Firmware download to XMS Edge	"update.barco.com" Port "80" ** "barcoprdwebsitefs.azureedge.net" TCP Port "443" "sil-xms-prd01-iothub.azure-devices.net" TCP Port "443"
5	Dedicated CX/C series firmware; (Cloud update)	"update.cmp.barco.com" TCP Port "443" (related to warranty status)* "assets.cloud.barco.com" TCP Port "443" * "global.azure-devices-provisioning.net" TCP Port "443" (one time for registration @ startup) "eeprom.cmp.barco.com" TCP Port "443"
6	Dedicated CS/CSE series firmware	“d3ougq224v1a9r.cloudfront.net” TCP Port “443” * "cs-update.barco.com" Port "80"
7	To use the XMS Cloud portal on a PC	"xms.cloud.barco.com" TCP Port "443"
8	Dedicated for Barco ClickShare Desktop App	“assets.cloud.barco.com" TCP Port "443" * "api.amplitude.com TCP port 443"
9	Google Cast certificate status checking	IP address "52.38.51.93" TCP Port "443"

*	These are redirects generated by Amazon Web Services that can change and are managed by Amazon.
**	These are redirects generated by Azure Cloud Services that can change in the future and are managed by Azure.

In strictly secured environments above mentioned wildcards for XMS Cloud connectivity might not be the preferred solution. We strongly advise to configure as mentioned above but here are the more Specific URL incase required, be aware these are more sensitive to sudden and unannounced changes what can lead to unexpected disconnects as result.