SMSGTE was a great service that allowed SMS text messages to be sent to an APRS station, and vice-versa. Unfortunately, it was shut down due to new FCC regulations designed to stop spam and robocalls, even though it was unsuitable for that kind of abuse.
Now, however, a new service has arisen that does the same thing with only minor differences designed to work with the updated regulations.
The service is called SMS, and it uses the messaging capability of APRS, as SMSGTE did. It was created by NA7Q, and works for phone numbers in the U.S, UK, and Canada. It is a free service, but donations are accepted.
I haven't tried it yet, but I know SMSGTE was a popular service among the local amateur community and I wanted to inform people of this replacement service ASAP.
Here are the links to learn more:
- https://www.youtube.com/watch?v=pYsMJ41u7h8&t=2s YouTube video of someone actually using the service.
- http://aprs.wiki/SMS/ Opt-in page for the phone number(s) you will sending to and from.
- http://aprs.wiki/SMS/howto.html A nice page with info on how to use the SMS service from either end (APRS or phone).
Even if you aren't an APRS operator, you may wish to opt-in your cell number so that you can receive messages from APRS stations on your phone. Even relatively primitive cell phones can handle SMS text messages, so a smart-phone isn't a requirement.
As with any APRS messaging service, one end must be a messaging-capable APRS station. If that messaging-capable station operates only on RF (no internet service), then it will need to be able to reach a TX (bidirectional) gateway to receive a reply over RF. If your messaging-capable station has -IS capability -- meaning it can connect to the APRS servers over the internet -- then you don't need a gateway at all. An RX-only gateway can receive a message you send over RF, and have it sent to a cellphone, but it can't transmit a reply sent by a cellphone over RF.One of the bigger disappointments operators run into using DireWolf is that it isn't messaging-capable when used as a standalone solution. If it's used as a client in conjunction with a TNC, then it is messaging-capable. However, if you use DireWolf as both the TNC and client (i.e. standalone), you are not able to send messages. You can gate/digipeat messages sent by others, but you can't generate a message of your own. Likewise, solutions such as the Byonics trackers have no messaging capability and no interface to view messages received.
Clients such as APRSDroid, UI-View, YAAC, and APRSICE32 are all messaging-capable. If the client is connected to a radio, then RF-based messaging is possible. In any case, you should use the "ack" option for messages sent to the SMS service. The only times you should not use "ack" -- which requests an acknowledgement from the intended recipient -- is if you are sending a bulletin, announcement, or general-target message (QST or ALL).
In the "how to" information, it's stated that cellphone users should use the callsign+SSID of the station they are replying to. This is a potential issue if you are sending a message to a non-ham's cellphone and expecting a reply. They may not understand what a callsign is, much less what an SSID is.
There's no need to install anything on a gateway or digipeater in order to handle these messages. It's all handled by the NA7Q gateway through APRS messaging and the national phone network. It's not clear to me if an operator can send messages from one country to another (e.g. U.S. to UK), or just within a country.
While most local users seem to view this kind of service as a novelty, it has real uses in remote areas without cell coverage. I wish that we could get clubs and operators in the Iron Range (for example) to see the value of such a service, and establish TX gateways that would enable hams to reach loved ones (or emergency services) with a simple VHF station.
No comments:
Post a Comment