Please post a screenshot of your REF/XRF connector settings, and also a screenshot of the call log, which shows your call from the transceiver. Please make sure advanced mode is turned on before taking the screenshot.

Tyrbiter is right. Slow charging does not supply enough power for the openSPOT3 to operate, so it will drain the battery while the openSPOT3 is turned on. Make sure the charge speed is normal or fast: use the supplied wall charge adapter, or connect the openSPOT3 to a standard USB port of a computer...

You can try setting a static IP address for the openSPOT (Network page, IP settings).

Note that this is the openSPOT2 support forum. If you use the openSPOT1 to bridge a repeater to an FCS room, then all users of that repeater has access to all the openSPOT1 functions, as they are coming to the openSPOT1 from the radio side.

As you can see in the log, the openSPOT3 is working correctly - it correctly starts a new call if the TG changes (you can see this also in the call log on the Status page), however, it seems that sometimes the server sends 2 calls simultaneously, which it should not, as the openSPOT3 is a DMO client...

Please see my answer at viewtopic.php?f=13&t=3922

We chose this as it is a very reliable, Google-hosted connectivity check and it's also used by all Android devices and several other services. We don't plan to make this an editable setting.

Please note that the openSPOT3 is not an MMDVM device and it does not use any DMRid.dat files.

The OS3 plays back the exact audio data it received when using the local echo. It does not modify it.

Please make sure the OS3's TX power is set to 100% to avoid any TX power issues. If it still does not work, then this is a transceiver configuration issue, as the OS3's local echo sends back a private call to your transceiver, which should be always heard, regardless of RX group list and other setti...