Introduction
HootBoard platform based kiosks require un-interrupted broadband internet access to work. We recommend that all HootBoard based screens (interactive or otherwise) are connected to hardwired internet with at the minimum 10 MBPS connection speed. The speed requirements will increase if you are using data-hungry applications like 3D walkthroughs, mapping tools, videos, etc. While a lot of HootBoard kiosks might support WiFi, we highly recommend using hardwired connectivity for mission-critical applications.
Connectivity basics and requirements
HootBoard kiosks use a variety of services them to work properly. Please see the list below for ports and services that are required to be available for basic HootBoard functions to work. Additionally, each application installed could add additional internet-based sources to be white-labeled.
Ports required
The Kiosk needs outgoing traffic to be enabled on the following ports
- TCP traffic on Port 80
- TCP traffic on Port 443
- TCP traffic on Port 8443
- UDP traffic on ports 5959 through 5970 should be enabled ( For remote access utility - optional )
Services required
- https://*.mxpnl.com/
- https://*.hootboard.com
- https://*.googleapis.com
- https://*.cloudflare.com
- https://*.cloudfront.com
- https://*.ravenjs.com
- https://*.gstatic.com
- *.yoics.net
- *.weaved.com
- *.remot3.it.
Frequently Asked Questions
What happens if the internet connectivity drops?
The kiosks will show the current idle state modes and might even respond to specific touch requests from users. However, as they try to navigate to specific applications OR content (hoots) the data might not be pre-downloaded locally and hence might showcase network unavailable messages to the user. When the user session ends, HootBoard wipes out all locally stored data (for security purposes) and hence will show "Network connectivity" messages as required.
Comments
0 comments
Article is closed for comments.