When Buttons are network integrated and the company network is set to load balancing, the Button may disconnect intermittently.
For example: Cisco Meraki Client Balancing
If Meraki AP (Access Point) is configured to use "Client Steering" it is proprietary to Meraki. The industry frequently calls this Layer 3 Load Sharing.
When the AP gets under load and stressed it sends clients that want to connect a message that indicates that they are congested and to connect to an alternative AP.
This form of steering is not supported by the Button, it will keep attempting to connect to the congested AP (the one with the strongest RSSI).
Solution:
Please contact your network team to disable the Client Steering in the Access Point for ClickShare devices.
Useful links:
- Info of Client Steering: https://documentation.meraki.com/MR/Other_Topics/Client_Balancing.
- Specific info on ClickShare Buttons using Meraki: https://community.meraki.com/t5/Wireless-LAN/Clients-cannot-connect-sometimes/td-p/20476.
LAST ENTRY: If you would like Barco to pursue this further we can raise a product improvement request. We do not have Meraki AP's. Barco at the very least, needs to see a Wi-Fi Wireshark trace of the messages between the AP and the Button when the client redirect message is being sent. There is no guarantee this will be implemented, we can add it to the Queue for consideration.
