Other messages might be displayed (depending on version):
“Terminal Not Registered”, see also: Error: Terminal is not registered
“Client Certificate Mismatch”
Your BATM connects to the server (CAS) over the Internet using an encrypted and secure channel. To identify itself to the server, the BATM presents a pre-authorized fingerprint to the server. If this fingerprint changes for any reason, the server will refuse to converse with the BATM, and the error message above will be displayed. You should also note the error in the affected Terminal’s Event Log.
This is a security measure.
The authorization process is called "pairing", and is a discrete step performed when the BATM is put into service. Typically, this process is only done once, and is automatic that first time only.
Something changed, and now you see this message. Don't fret. This is easily resolved in one of two ways:
From CAS:
1. Navigate to your Terminal.
2. Click “Unpair Terminal”:
From the CLI:
1. Note the BATM serial number (e.g. BT101308) for step 3 (serialno).
2. Tell CAS to forget the old fingerprint:
sudo /batm/batm-manage terminal-unpair serialno
3. Turn the BATM back on.
After booting, the BATM will again attempt to connect to CAS.
CAS will now reauthorize the BATM’s fingerprint.
The problem should not normally recur.
The error should disappear within 15 minutes.
Troubleshooting
Is your Server IP set correctly? Instructions found here.
Try powering off your BATM while unpairing.
Is the IP Whitelist disabled? The “pairing” can never occur if the BATM’s IP is rejected.
On older CAS versions: is your Shared Secret Hash properly set in the Terminal settings?
Try resetting it to the default, even if you haven’t changed it recently.
This hash is emailed to you after you've confirmed receipt of your BATM.
Contact the Support department if you've lost your Shared Secret Hash.The Shared Secret Hash was eliminated in 2020 (20201015).
