Which ports does the ClickShare Button and Base Unit use?

Article number: [4130] - Legacy code: [5085]

Applicable to

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!
  1. 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.
  2. The TCP/UDP ports referred here are bi-directional traffic.

    ClickShare CX and C-series

    SystemNetwork portsCX and C series
    ClickShare Button (wireless presentation)TCP2345, 6544
    UDPN/A
    ClickShare Desktop Apps and Mobile Apps (wireless presentation)TCP6541-6545
    UDP5353; 1900
    Additional ports for Wireless Conferencing (Button or Desktop App)TCP1235, 9999
    UDP1234
    AirPlayTCP4100-4200; 7000; 7100; 47000
    UDP4100-4200; 5353
    Google CastTCP8008; 8009; 9080
    UDP1900; 5353; 32768:61000[1]
    Miracast MS-MICETCP7236, 7250
    UDP7236
    ClickShare ConfiguratorTCP80; 443
    UDP N/A
    XMS CloudTCP443
    XMS EdgeTCP4003
    Auto-updateTCP80; 443
    UDPN/A
    Button ManagerTCP6546
    SNMPUDP161 and 162
    REST APITCP4003
    [1]  Google Cast will pick a random UDP port above 32768 to facilitate video streaming

    ClickShare CS and CSE-series

    SystemNetwork portsCS-seriesCSE-series
    ClickShare ButtonTCP6541-65456541-6545
    UDP514514
    ClickShare Desktop apps (Windows, and macOS) and Mobile apps (iOS and Android)TCP6541-65456541-6545
    UDP5353; 19005353; 1900
    AirPlayTCPN/A4100-4200; 7000; 7100; 47000
    UDPN/A4100-4200; 5353
    Google CastTCPN/A8008; 8009; 9080
    UDPN/A1900; 5353; 32768:61000[1]
    Miracast MICE[2]TCPN/A7236, 7250
    UDPN/A7236
    ClickShare ConfiguratorTCP80; 44380; 443
    UDPN/AN/A
    ClickShare REST API and XMS[3]TCP4000; 40014000; 4001
    UDPN/AN/A
    Auto-updateTCP80; 44380; 443
    UDPN/AN/A
    Button ManagerTCP65466546
    [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

    ClickShare CSC-1

    SystemNetwork portsCSC-1
    ClickShare ButtonTCP9870; 9876
    UDP514
    ClickShare Desktop apps (Windows, and macOS) and Mobile apps (iOS and Android)TCP389; 445; 515; 636; 1688; 1689; 3268; 8080
    UDP1047-1049; 9870
    AirPlayTCP4100-4200; 7000; 7100; 47000
    UDP4100-4200; 5353
    ClickShare ConfiguratorTCP80
    UDPN/A
    ClickShare REST API and XMS[1]TCP4000; 4001
    UDPN/A
    Auto-updateTCP80 (only via XMS)
    UDPN/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