You could set up a web server in the middle that would do something similar, using the API and PHP for instance. The SMS functionality would not be necessary in this case.
Skot thanks for answering, let me clarify the scope.
i’m integrating a sms gateway with my home automation box (veralite)
That box can easily interface using HTTP get requests (incoming and outgoing)
I’ve got Mikrotik 5.24 running on an Alix board 2D13 with a 3G usb stick hooked up.
My target schema is the following :
Devices<>Vera<(GET HTTP)>MK<->USB 3G<->SMS
I’m focused on the interface between Vera and MK :
1)incoming SMS into MK works actually with a scheduled script which catchs the SMS parses it and makes a HTTP get to the Vera
2)outcoming SMS (Vera ->MK->USB 3G) is what i’m trying to implement. I’d like to trigger this way like the other i.e.using HTTP get request
and therefore make use of a unique interface both directions.
Running a PHP script on the Vera works but does not comply with point 2
To add to skot’s point, if the veralite does allow you to run a PHP script on it* or something else, then you can also use the API no problem.
I mean, what’s more important - that you command RouterOS from Veralite somehow, or that you command RouterOS from Veralite using only HTTP? I’d argue the former is the more important bit.