Problem / Question
-
How do I change the time on the signage devices?
-
The time on the tablets is a few minutes out how do I correct this?
-
The time is incorrect on my tablet or kiosk. What do I do?
-
My device is in the wrong time zone. How do I change this?
Solution / Answer
To resolve the incorrect time on your devices depends on your hardware options:
-
Hardware as a Service (HaaS) or you got your hardware through Matrix Booking and have Mobile Device Management (MDM).
-
HaaS or you got your hardware through Matrix Booking and don’t have MDM.
Regardless of what the hardware option you picked, you should make sure that your organisation has our servers as approved endpoints where applicable.
With MDM
If your room signage or kiosk devices are showing the incorrect time, this is normally because the devices are blocked from looking for the current time using a firewall.
Matrix Booking can push time zone changes via MDM if you have our Hardware as a Service subscription. For this to work, your organisation needs to make sure that all of Matrix Booking’s endpoints including the NTP server (the time server described above) are approved endpoints. Otherwise, it could affect the time displayed on your devices.
When the devices are sent out to your organisation, they are set up to reach out to one of the international time servers constantly. These Android devices normally use: *.pool.ntp.org. Sometimes they will be set with 2.android.pool.ntp.org or something similar, but it will normally always be a variant of *.pool.ntp.org unless you’ve requested a specific server.
If your devices are locked to a Matrix Booking app using our Hexnode MDM kiosk software, you need to:
-
Go to the Android settings screen.
-
Change the time zone settings.
-
To re-enter kiosk mode, open the Hexnode MDM application
-
Select Activate.
If you’re unable make the time server an approved endpoint or you’re having issues exiting kiosk mode, raise a support ticket and our Hardware Team will help you.
Without MDM
If you’ve opted to not use our MDM software, raise a support ticket and our Hardware Team will help you.
Your own hardware
If you’ve opted to purchase your own hardware, raise a support ticket and our Hardware Team will help you.
Servers you should have as approved endpoints
The table below shows the full list of application endpoints that you need to include in the allowed or trusted list to fully utilise the Matrix Booking applications on a closed network. If any endpoints aren’t in your allowed or trusted list, you may have issues with the service related to the endpoint.
|
Server name |
Protocol |
Port |
Application |
Notes |
|
HTTPS (TCP) |
443 |
Signage Floor plan Welcome |
Matrix Booking data |
|
|
HTTPS (TCP) |
443 |
Signage Floor plan Welcome |
Organisation logo |
|
|
HTTPS (TCP) |
443 |
Signage |
Event-based communication |
|
|
UDP |
123 |
Signage Floor plan Welcome |
Time and date server ProDVX Android devices only
|
|
|
Outbound (TCP) |
443 |
Hexnode MDM |
Hexnode app updates and remote view |
|
|
Outbound HTTPS (TCP) |
443 |
Hexnode MDM |
Hexnode remote view |
|
|
Outbound HTTPS (TCP) |
443 |
Hexnode MDM |
Hexnode remote view |
|
|
Outbound HTTPS (TCP) |
443 |
Hexnode MDM |
Hexnode client portal |
|
|
Outbound TCP and UDP |
3478 |
Hexnode MDM |
Hexnode remote view |
|
|
Outbound TCP |
5349 |
Hexnode MDM |
Hexnode remote view |
|
|
Outbound TCP and UDP |
3478 |
Hexnode MDM |
Hexnode remote view |
|
|
Outbound TCP |
5349 |
Hexnode MDM |
Hexnode remote view |
|
|
Outbound TCP |
1883, 8883 |
Hexnode MDM |
Hexnode remote view: Receive push notifications via MQTT. |
|
|
Outbound TCP |
1883, 8883 |
Hexnode MDM |
Hexnode remote view: Receive push notifications via MQTT. |
|
|
Outbound TCP |
1883, 8883 |
Hexnode MDM |
Hexnode remote view: Receive push notifications via MQTT. |
|
|
HTTPS (TCP) |
443 |
Hexnode MDM |
Remote view push notifications |
|
|
TCP |
5228–5230 |
Hexnode MDM |
Remote view persistent connection |