SMS Command workaround: No device-to-device MT SMS

Smashers09015 days ago

My IoT SIM provider does not allow device-to-device Mobile-Terminated SMS, i.e. there is no 'Phone' number to send SMS to. They (1NCE) only allow SMS to be sent from their own UI or via API.

This means that despite being able to send SMS notifications from my Traccar server, SMS commands to devices fail to deliver.

I'm curious to the following and appreciate any clarity:

  1. Is there any mechanism for sending SMS commands via a different API vs SMS notifications? (I think no)
  2. Is there any known workaround for my situation?
  3. Can I expect the same limitation from other IoT network providers?

Ultimately, I want to be able to set position period (interval) of a Topin protocol device from the web interface. I have also thoroughly explored sending non-SMS commands - I implemented Topin protocol's Command.TYPE_POSITION_PERIODIC command in the backend, and also tested sending the most basic verifiable hex command (787801480D0A - restart tracker) via the interface custom command, with no effect in either case. The hex command queued and then submitted when the device was connected (seen in logs), with no effect.

That leads to:
4 . Is there any common reason why hex commands would fail to affect the target device?

Thanks in advance for any answers.

Anton Tananaev15 days ago
  1. Not in Traccar itself.
  2. Have external service that can route to different APIs.
  3. It's not very common, as far as I know.
  4. Common if device lost connection, but server doesn't know about it.
Smashers09015 days ago

Super helpful.

For 2), setting up API router is a great idea, and useful for other services too. Now this will be my next step.
For 4), I do have the 'multiple connections per device issue' which may support this explanation.

Thank you!