First post here, not sure if this is the correct category for this question.
I have an RUT950 which I have had for several years and essentially I am happy with it.
However, I had a problem with forwarding SMS to Email which would always fail, but SMS to HTTP (GET) and SMS to SMS have always worked OK.
The Email failing to send was always shown in the Events Log after the HTTP GET and SMS to SMS success were logged.
Carefully checking that the SMTP settings were correct failed to fix it.
The router had a fairly old version of firmware which used the Legacy Web UI, so I decided to update the firmware to the latest version (via the Web UI) in the hope it might fix the SMS to Email problem.
The (new style) Web UI says that the firmware is now the latest version.
The firmware is Version: RUT9_R_00.07.06.19
Modem firmware Version: EC25ECGAR06A09M1G_01.001.01.001
Kernel Version: 5.4.291
Unfortunately this has seemingly added another problem as now the SMS to HTTP GET doesn’t work (it did before) and the SMS to Email still doesn’t work!
Also, now both SMS to HTTP GET, and SMS to email, don’t put anything in the Event Log at all, but the SMS to SMS still works fine.
To troubleshoot the issue further, we will need some sensitive information from your device, such as a troubleshoot file. For this, I have sent a form to the email address you registered with on the community forum. Once you complete the form, I will contact you privately. Please use ticket ID “15334” when filling it out.
After investigation by the Teltonika technical team the solutions to the issues raised were as follows.
In the SMS to HTTP GET failure that occurred after a firmware update, I was told that it was now no longer required to include a “?” after the domain name in the URL that called the relevant webpage. The reason was the “?” is now added automatically by the new firmware version, unlike the version I had upgraded from.
I should also note that Base 64 encoding of the passed text appeared to be selected by default in the settings of the new firmware update, meaning that the text passed was not readable without Base 64 decoding at the receiving website, I had to disable that feature in the router settings to send the message in plain text to the called webpage.
The SMS to email issue (which had not worked in the previous version either) was fixed by changing the SMTP Server Port details entered into the router settings from Port 465 to Port 587 as, despite Port 465 (still) working from a website on the network of the SMTP provider, sending mail from an external internet connection appears it needs to be set to Port 587. The SMS to email now works.
I should however note that the failures I had previously experienced were not shown in the Log in the latest firmware version, unlike the earlier one.