Caller ID and dialling troubleshooting
On the affected terminal, open Back Office → Diagnostics and read the Telephony card. Listening means the callback listener is running. Connected means the USB bridge reports a device. Check Last Refused Callback and make a test call to confirm that calls reach the till. Off means no source is chosen. Then open Back Office → Local Settings → Caller ID & Clover in the desktop app. Both pages need an administrator.
No incoming call appears
Section titled “No incoming call appears”- In the Caller ID Source section, check Device on This Terminal.
- Check that the selected source matches the device connected: Yealink Action URL, AD102 USB Caller ID or Phonic USB Caller ID.
- Select Save Caller ID & Clover and read Device Status.
- Follow only the section below for that source.
Caller ID & Dialling
Illustration, not a screenshot. The real screen can differ with the theme or version.
Only one source is active at a time. When a USB source is chosen, FMX EPOS ignores Yealink callbacks, so two devices cannot record the same call. Each till records the calls of its own device, so several tills can each have their own phone.
AD102 or Phonic USB
Section titled “AD102 or Phonic USB”- Check that the device is plugged into this PC and has power if it needs it.
- Check that the exact USB type is selected.
- Read Device Status. “AD102 connected · 1 device” means the device is found. “Starting AD102…” means FMX EPOS is still looking for it. “No AD102 detected. Check USB and driver.” or “AD102 unavailable. Check the USB connection and driver. Retrying…” means it is not found.
- Reconnect the device, then check the Telephony card in Diagnostics again.
- Make one test call to the shop.
USB devices only receive caller ID; they cannot make calls. If the device is still not found, check its Windows driver and the hardware before you switch the software to a different device type.
With a USB caller ID box, a call that arrives without a number is not shown on the till or kept in Customers → Calls. Whether a withheld number arrives without one depends on the device. With a Yealink phone, FMX EPOS can keep a call even when no number is sent.
“… call pending: waiting for database.” means a call was received while the database was unavailable. The call is saved as soon as the database answers again.
Yealink incoming callbacks
Section titled “Yealink incoming callbacks”- Check that Yealink Action URL is the selected source.
- Check that a valid Yealink Dial URL is saved. FMX EPOS saves the Yealink settings only with a valid dial URL, and listens for the phone only once they are saved, even if you never dial out. Until then Device Status says “Configure the Yealink dial URL to enable callbacks.”
- Check the Callback Port (880 unless you changed it) and the Action URLs saved on the phone. Action URL Help shows the exact addresses to enter on the phone. They use plain HTTP on the callback port, not port 5139, and contain this till PC’s network address.
- Check that Windows Firewall allows the callback port through to this terminal.
- Check Allowed Callback IPs. It must contain the phone’s current IP address; separate several addresses with commas. The settings cannot be saved while this box is empty (“Enter the phone’s IP address. Callbacks from other addresses are rejected.”).
- Give the phone and this till PC fixed IP addresses or DHCP reservations.
- Select Save Caller ID & Clover. Device Status should then say “Listening on port …”, and the Telephony card in Diagnostics should show Listening.
- Test one incoming call.
Caller ID & Dialling
Illustration, not a screenshot. The real screen can differ with the theme or version.
If Device Status says “Callback port … could not open. Check whether another application is using it.”, another program on this PC is using that port. The rest of the settings were still saved. Close it, or choose a different Callback Port and update the Action URLs on the phone to match. The port cannot be 5139 or 8990, which FMX EPOS and Clover use.
The callback listener has its own Allowed Callback IPs list, which the Allowed IP Addresses list in Local Settings → Security does not replace. A callback from any address that is not on the list is rejected and its call is not recorded. The listener keeps showing Listening, but Last Refused Callback in Caller ID & Clover and on the Diagnostics Telephony card shows the refused address and time. If it is the phone’s new address, add it to Allowed Callback IPs.
Yealink dialling does not work
Section titled “Yealink dialling does not work”If the call buttons on the till are greyed out, Device on This Terminal is not Yealink Action URL. USB devices cannot dial.
- Check that a Yealink Dial URL is saved. Once one is saved, the box stays empty and the note under it shows “Saved securely ·” followed by the phone’s address without the sign-in details.
- A new URL must start with
https://and must end with=or contain{number}, so that FMX EPOS can insert the telephone number. Otherwise saving says “Enter a valid HTTPS Yealink dial URL.” or “The Yealink dial URL must end with = or contain {number}.” - If the phone uses a self-signed HTTPS certificate, tick Allow the Phone’s Self-Signed HTTPS Certificate. Do this only for that known phone.
- Show Keys shows only a new value you have just typed, so you can check it before saving. The saved URL is never shown again.
- Save, then try dialling one number.
Caller ID & Dialling
Illustration, not a screenshot. The real screen can differ with the theme or version.
The message on the till tells you where to look:
- “Calling …”: the phone accepted the request.
- “The phone could not be reached.” or “The phone did not respond.”: check the phone’s address in the dial URL, the network and that the phone is switched on. For a phone with a self-signed certificate, also check that Allow the Phone’s Self-Signed HTTPS Certificate is ticked.
- “The phone rejected the dial request.”: check the user name and password in the dial URL and the phone’s own settings.
- “Enter a valid UK telephone number.”: the number on the order or customer record cannot be dialled.
When you save other fields, leave the dial URL box empty to keep the saved URL. Never send a dial URL that contains the phone’s sign-in details to support.
The status keeps switching between connected and failed
Section titled “The status keeps switching between connected and failed”Check for a changed address, a firewall rule or the phone restarting. Compare the time of the problem with Recent Errors in Diagnostics. If the phone has a new address, update Allowed Callback IPs before you test again. If this till PC has a new address, update the Action URLs on the phone.