RUTC50 SMS issues

NETWORKING SOLUTIONS
1

I have the new RUTC50 5G Cellular/mobile WiFi router. I can receive SMS messages but it wont let me send SMS. The SIM card used in the router works just fine in a phone sending and receiving SMS messages and also worked fine when it was used in an earlier Chinese manufactured GLiNet 5G router. I have read a number of posts related to this issue and tried all the suggestions like clearing the cache, using different locations for storing SMS messages, changing the VoLTE settings and so on. Nothing seems to change our ability to send a message from the router to a local phone, both incidentally using the same Carrier network. I just get a “Failed to send message” every time we try to send a message out from the router. I can only guess that this is why non of the ‘SMS Utilities’ work when I send the appropriate text message to the router. We were going to buy a number of these routers for our narrow boat fleet, however, I think we will be looking for something that functions a little better. The phone has no problem receiving messages from other phones and devices, so it’s not the phone that is at issue and the RUTC50 router is using the latest firmware and modem drivers. I have done some investigating and I may of found the problem? The setting of the SMSC number, might be the issue. The RUTC50 is struggling to set the correct SMSC number, even though other devices seem to have no problem. The is no manual way to check or change the SMSC via the Web interface. The SMSC number that my Sim carrier (SMARTY) provides is +447782000800. How can I check that this is the number being used by my RUTC50?

3

Hello,

Could you please confirm whether the same issue occurs with the latest 7.13.4 firmware version? You can download it from our wiki page here.

Best regards,

4

I gave up and sent the crap back.

5

I’m having exactly the same problems sending SMS messages.
I want to send SMS messages via the API interface.
Has anything changed in the API?
Receiving SMS messages works, but unfortunately sending them doesn’t.
cgi-bin/sms_send?
api/sms_gateway/sms/send?
Is there a detailed description of the API interface?

greetings Harry

6

API documentation can be found https://developers.teltonika-networks.com/reference/RUTX50/7.14/v1.6/messages#messages-send-messages

7

Hello @harry73,

Could you please let me know if the API documentation helped resolve your issue, or if you still need any assistance?

Best regards,

8

Unfortunately, the problem could not be resolved. Here is a detailed description:

Subject

RUTX50 API v1.0 – SMS sending fails with “Missing bearer token” on FW 7.14

1. Device and Firmware Information

2. Steps and Observed Behavior

Step API Call Expected Actual
1. Login (v1.0) POST /api/v1.0/session/login with JSON {username, password} JSON response with payload.data.token success=false, error: Missing bearer token
2. Send SMS POST /api/v1.0/messages/actions/send with Bearer token in headers and JSON body Response with success: true Not reached – login fails
3. Login (legacy sms_gateway) POST /api/sms_gateway/session/login JSON response with token in payload.data.token success=false, error: Missing bearer token

3. What I Tried

  1. Tried multiple endpoints: /cgi-bin/sms_send, /api/v1.0/session/login, /api/sms_gateway/session/login – all fail with the same issue.
  2. Used correct headers: Tried Authorization: Bearer <token> where applicable.
  3. Payload format: Used proper JSON body (not form-data or query string).
  4. Modem ID: Tried with "modem": "1-1" as described in the docs.
  5. Browser UI works: I can send SMS from the web interface, but the API login always fails.

4. Debug Output (Node-RED / HTTP Request)

Login Response payload = {
  "success": false,
  "errors": [
    {
      "source": "Authorization",
      "code": 121,
      "error": "Missing bearer token"
    }
  ]
}

This appears every time I try the login route. No token is ever returned in the response body (data.token is undefined or missing).

5. Expected Behavior

  • The login request (/api/v1.0/session/login) should return a valid bearer token.
  • With the token, I should be able to POST to /api/v1.0/messages/actions/send to send SMS.

6. Request for Assistance

  • Is this a known issue in FW 7.14?
  • Is there any configuration needed to enable API access for SMS?
  • Is the /api/v1.0/session/login endpoint fully functional and implemented?
  • Are there any required roles or permissions to generate tokens?

Thanks in advance for your support!

9

Hello,

You should not use v1.0 when sending requests.
To log in, please use the endpoint: api/login (not /api/v1.0/session/login).
To send a message, use: api/messages/actions/send.

Regarding /api/sms_gateway/session/login — we do not have such an endpoint.

Could you please try using the endpoints I provided and let me know if you still encounter any issues or have further questions?

Best regards,