FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
+1 vote
473 views 5 comments
by
Hi,

I would like to use the function "SMS Forwarding To Email". But I would like to add the phone number from the incoming sms as a subject in the email going out. Preferably if you could specify the subject and use the phone number as a parameter in the subject. Like this:

Subject: SMS from {SendersPhoneNumber}

Subject: SMS from 0043847293023

Is this possible to accomplish in some way in the Teltonika RUT routers? Or does anyone have some other solution for this problem?

Cheers!

Henrik

2 Answers

–1 vote
by anonymous
Hi,

For now, there is no such possibility, but I can report this to RnD as a suggestion.

EB.
by
That would be great! And, I imagine, not that difficult to accomplish.

I'd be happy to be a BETA tester of this function :)

Thank you!

/H
by
BTW. I'm using a Teltonika RUT950 for the moment.

/H
by
Here is another nice use case for this feature. Maybe you can bounce that over to the RnD team also @ErnestasB :)

We setup a mailbox named textmessages@ourdomain.com. In the RUT950 router we setup "SMS Forwarding To Email" to that address.  As subject we specify only the senders phone number:

Subject: {SendersPhoneNumber}

Using the "Email to SMS" function we specify the same mailbox (textmessages@ourdomain.com) for the router to fetch mails from.

Now, when we receive a SMS forwarded as a mail to textmessages@ourdomain.com we can simply hit "Reply" in our mail program and actually do a reply on the SMS we received.

That's a use case we would love! :)

Cheers!

/Henrik
0 votes
by anonymous
Huge +1 on this.

Looks like accomplishing this requires enhancements to sms_utils.c from mobutils. Unfortunately I wasn't able to find the source code for this package - it isn't in the SDK either. Could you please share the source code so I can take a look at implementing this feature myself?
by anonymous
Just a friendly reminder to share the source code for the mobutils package in your sdk. In case you think that package can remain closed-source, I think you may have misunderstood how the GPL license works. Here's a refresher. If you sell a product that contains ANY GPLv2 code (even as a tiny library), then you MUST release to your customers ALL the source code FOR THE ENTIRE PRODUCT. This is why big software companies like Microsoft are SUPER careful to never use GPL-licensed code in their closed-source products, like Windows. I'll wait a few more days, but if I don't see action, I may need to refer this matter to ... I dunno. Jesus. Anyway, thanks for a great product. Please just give me the source code so I can build this much-needed feature for myself. Thanks.
by anonymous

Hello,

I would like to point a couple of things.

  • mobutils package is developed by Teltonika and uses third party libraries which do not have source code disclosure requirement listed in their licenses.

"If you sell a product that contains ANY GPLv2 code (even as a tiny library), then you MUST release to your customers ALL the source code FOR THE ENTIRE PRODUCT."

  • The above statement is not correct as our firmware is not a single program, but consists of different software packages bundled together. This means that Teltonika is not "combining two modules into one program" but is using what can be phased as "mere aggregation". Please refer here (https://www.gnu.org/licenses/old-licenses/gpl-2.0-faq.html#MereAggregation) for more information. To expand on this, you can take any Linux distribution as an example and consider this: there are only ~10 distributions which are 100% open-source. All the others use a bunch of closed-source, proprietary drivers, codecs and other software. Linux kernel being licensed under GPLv2 and having requirement to disclose source code or necessity to use the same GPLv2 license for any derivative work brings no such licensing restrictions on user-space programs.

Best regards,