SMS Length using API, GSM-7

[mtamas]

RUTOS 7.14 drops support for SMS POST/GET.
When testing, I’ve found problems with processing long messages.
Seemingly regardless of content, max number of SMS per message is 3.
Even if message doesn’t contain any non-GSM-7 characters, trying to send message longer than 459 characters fails with “Max SMS count is 3 messages” error returned.
The same message is successfully sent using previous POST/GET mechanism.
Would it be possible to better implement detecting and limiting content length using API?

[anon46660955]

Good afternoon,

For the time being, the workaround is sending separate SMS messages, to bypass the Max SMS count is 3 messages" limitation in RutOS 7.14’s SMS API.

Send each message chunk as a separate API call
Use the /api/messages/actions/send endpoint with the Bearer token in the header. For each chunk, send a separate POST request with JSON body:

“number”: “0037060000001”,
“message”: “Your message chunk here”,
“modem”: “1-1”

Example curl command for one chunk:

curl -X POST “http://<router_ip>/api/messages/actions/send”
-H “Authorization: Bearer <your_token>”
-H “Content-Type: application/json”
-d '{“number”:“0037060000001”,“message”:“First part of your long message…”,“modem”:“1-1”}

Repeat the send request for each chunk sequentially
Send the second chunk, third chunk, etc., each as a separate SMS

Regards,
Arturas

[mtamas]

Thank You for suggestion.
Manually chunking messages may result in wrong arrival order or partial delivery due to service provider issues.
We are using modems to provide service to external users. We have no possibility to guarantee logically correct split of long messages.
For now we will enforce smaller limit and wait for further development in the topic.

[anon46660955]

Hi Mtamas,

I can confirm that this query is currently being investigated by our RnD departament. I will inform you as soon as i have a response. For now, the manual way is the only way.

Regards,
Arturas