Which ports does the ClickShare Button and Base Unit use?
Article number: [4130]
- Legacy code: [5085]
To ensure that you can successfully share content via the ClickShare Button or from mobile devices to the Base Unit, you need to ensure the correct ports are open on your network.
Below you find the list of the ports required for the different ClickShare Base Unit models (see KB 2865 for tips to identify your ClickShare model).
More information on the deployment of ClickShare within your corporate network is available in our network deployment guides:
Good to know!
- AirPlay and Google cast, as well as the ClickShare App, require multicast to make the ClickShare Base Unit discoverable within your network. Therefore, allowing multicast within the network is required to use AirPlay and Google Cast. The Base Unit should be connected in the same subnet as the mobile device or a network connection should be available from the mobile device to the Base Unit.
- The TCP/UDP ports referred here are bi-directional traffic.
System | Network ports | CX and C series |
---|
ClickShare Button (wireless presentation) | TCP | 2345, 6544 |
UDP | N/A |
ClickShare Desktop Apps and Mobile Apps (wireless presentation) | TCP | 6541-6545 |
UDP | 5353; 1900 |
Additional ports for Wireless Conferencing (Button or Desktop App) | TCP | 1235, 9999 |
UDP | 1234 |
AirPlay | TCP | 4100-4200; 7000; 7100; 47000 |
UDP | 4100-4200; 5353 |
Google Cast | TCP | 8008; 8009; 9080 |
UDP | 1900; 5353; 32768:61000[1] |
Miracast MS-MICE | TCP | 7236, 7250 |
UDP | 7236 |
ClickShare Configurator | TCP | 80; 443 |
UDP | N/A |
XMS Cloud | TCP | 443 |
XMS Edge | TCP | 4003 |
Auto-update | TCP | 80; 443 |
UDP | N/A |
Button Manager | TCP | 6546 |
SNMP | UDP | 161 and 162 |
REST API | TCP | 4003 |
[1] Google Cast will pick a random UDP port above 32768 to facilitate video streaming
System | Network ports | CS-series | CSE-series |
---|
ClickShare Button | TCP | 6541-6545 | 6541-6545 |
UDP | 514 | 514 |
ClickShare Desktop apps (Windows, and macOS) and Mobile apps (iOS and Android) | TCP | 6541-6545 | 6541-6545 |
UDP | 5353; 1900 | 5353; 1900 |
AirPlay | TCP | N/A | 4100-4200; 7000; 7100; 47000 |
UDP | N/A | 4100-4200; 5353 |
Google Cast | TCP | N/A | 8008; 8009; 9080 |
UDP | N/A | 1900; 5353; 32768:61000[1] |
Miracast MICE[2] | TCP | N/A | 7236, 7250 |
UDP | N/A | 7236 |
ClickShare Configurator | TCP | 80; 443 | 80; 443 |
UDP | N/A | N/A |
ClickShare REST API and XMS[3] | TCP | 4000; 4001 | 4000; 4001 |
UDP | N/A | N/A |
Auto-update | TCP | 80; 443 | 80; 443 |
UDP | N/A | N/A |
Button Manager | TCP | 6546 | 6546 |
[1] Google Cast will pick a random UDP port above 32768 to facilitate video streaming
[2] Supported with CSE-220+ only
[3] When a Base Unit firmware update is performed using XMS, the XMS (Virtual) Edge will use a dynamic port within the range 1024 – 65000 to send the firmware to the Base Unit. Hence make sure that connections already established between the ports mentioned in the table are allowed within the network
System | Network ports | CSC-1 |
---|
ClickShare Button | TCP | 9870; 9876 |
UDP | 514 |
ClickShare Desktop apps (Windows, and macOS) and Mobile apps (iOS and Android) | TCP | 389; 445; 515; 636; 1688; 1689; 3268; 8080 |
UDP | 1047-1049; 9870 |
AirPlay | TCP | 4100-4200; 7000; 7100; 47000 |
UDP | 4100-4200; 5353 |
ClickShare Configurator | TCP | 80 |
UDP | N/A |
ClickShare REST API and XMS[1] | TCP | 4000; 4001 |
UDP | N/A |
Auto-update | TCP | 80 (only via XMS) |
UDP | N/A |
[1] When a Base Unit firmware update is performed using XMS, the XMS (Virtual) Edge will use a dynamic port within the range 1024 – 65000 to send the firmware to the Base Unit. Hence make sure that connections already established between the ports mentioned in the table are allowed within the network
Properties
Last updated Aug 10, 2023