Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Make sure you understand what pairing before continuing troubleshooting by reading this article.

This article contains list of recommended steps to pair a terminal.
Recommended steps differ based on different state the terminal is in and a different version it has installed on it.

This guide assumes you have sever version at least 20230801.

Jump here to right section that applies to your case:

My terminal has version 20230801 and higher

Pairing steps

Deployment Scenario

Terminal state

Actions to take

Notes

Terminal operates in Deployment Scenario A

Terminal was paired in past to this server and has VPN configuration already generated.

  1. Set on terminal server’s host/ip via advanced administration. Terminal should show error screen with pairing code displayed.

  2. On server in CAS new pairing request will appear on terminal list page.

  3. Approve the pairing request.

  4. Terminal will pair and connect to master service via VPN channel.

If terminal displays “VPN connection error” it means that you probably didn’t generate VPN configuration.

Terminal operates in Deployment Scenario A

Terminal has never been paired to this server and doesn’t have VPN configuration generated yet.

This case applies for example to new terminals that has been purchased.

  1. Create terminal on server.

  2. Generate VPN configuration for terminal.

  3. Set on terminal server’s host/ip via advanced administration. Terminal should show error screen with pairing code displayed.

  4. On server in CAS new pairing request will appear on terminal list page.

  5. Approve the pairing request.

  6. Terminal will pair and connect to master service via VPN channel.

If terminal displays “VPN connection error” it means that you probably didn’t generate VPN configuration.

Terminal operates in Deployment Scenario B

Terminal has never been paired to this server.

This case applies for example to new terminals that has been purchased.

  1. Create terminal on server.

  2. Set on terminal server’s host/ip via advanced administration. Terminal should show error screen with pairing code displayed.

  3. On server in CAS new pairing request will appear on terminal list page.

  4. Approve the pairing request.

  5. Terminal will pair and connect to master service.

Terminal operates in Deployment Scenario B

Terminal was paired in past to this server.

  1. Set on terminal server’s host/ip via advanced administration. Terminal should show error screen with pairing code displayed.

  2. On server in CAS new pairing request will appear on terminal list page.

  3. Approve the pairing request.

  4. Terminal will pair and connect to master service.

Unpairing steps

Deployment Scenario

Terminal state

Actions to take

Notes

Terminal operates in Deployment Scenario A

Terminal is paired and connected to VPN and master service

  1. Unpair terminal via action menu in list of terminals.

  2. Terminal will unpair and show error screen with pairing code displayed.

!!! This action should not be necessary. Only reason for unpair is when terminal is stolen or when server is changed !!!

Terminal operates in Deployment Scenario B

Terminal is paired and connected to master service

  1. Unpair terminal via action menu in list of terminals.

  2. Terminal will unpair and show error screen with pairing code displayed.

!!! This action should not be necessary. Only reason for unpair is when terminal is stolen or when server is changed !!!

My terminal has newer version than 20190130 but has older version then 20230801

My terminal is version 20190130 and older

  • No labels

Copyright © 2020-2024 General Bytes USA LLC