[GreenKeys] baudotrss ability to use Google Voice to receive SMS messages ends May 15, 2014.
Javier Albinarrate
javier at albinarrate.com
Mon Dec 9 11:44:33 EST 2013
Hi Gil,
In principle yes, that's the idea, whatever the script is it must be
prepared to receive all parameters by GET (not by POST)
You can setup a rule to forward a message to a URL, and build the URL
like this:
http://mydomain.com/myscript.php?from=%from%&body=%body% etc etc etc
So, whenever you get an SMS, it gets sent to the script. Then that
script can do anything with that info.
I have a pretty busy week and weekend, but I could put up something the
following weekend perhaps.
Let me elaborate what I could do.
1- The user has to install the android app, SMS Gateway Ultimate Free
2- You configure no outbound (unless you want to), and configure an
inbound rule.
3- The rule could/should have some flag to allow the message to go
through, like simply the string TTY in the body
4- The SMS gets forwarded to
http://albinarrate.com/heavymetal/?action=receiveSMS&name=MyStationId&password=MyPass&from=%from%&body=%body%&time=%time%&fallback=MyEmail
5- The forwarder then contacts the ip and port of the HM3 station (HMNet
feature of HM3, which is just a simple directory)
6- The forwarder delivers the SMS to HM3 using a guest level command
7- If it cannot connect, it optionally delivers it by email with [SMS]
preffix
The infrastructure is already there, I would just need to add the
receiveSMS action.
For it to work you would only need to have the inbound telnet open, and
be registered at the HMNet
technically you don't even need HM, as you could have your own station
software running, which just needs a listening telnet connection, and be
registered at HMNet.
The same could be done with pretty much anything.
Regards!
Javier
On 09/12/2013 12:38, gil at baudot.net wrote:
> Hi Javier:
>
> That is interesting. I grabbed the free version to play with (the Pro
> version is only a couple of bucks).
>
> I don't quite understand how it works though; do you have a simple
> example? Can I add a form or other page to a wordpress site and send
> the messages there? Or send it to a specific ip address of a box on
> the local net?
>
> thx, gil
>
>
> gil smith, AF7EZ
> greenkeys moderator
> gil at baudot.net <mailto:gil at baudot.net>
>
>
> -------- Original Message --------
> Subject: Re: [GreenKeys] baudotrss ability to use Google Voice to
> receive SMS messages ends May 15, 2014.
> From: Javier Albinarrate <javier at albinarrate.com
> <mailto:javier at albinarrate.com>>
> Date: Mon, December 09, 2013 7:49 am
> To: greenkeys at mailman.qth.net <mailto:greenkeys at mailman.qth.net>
>
> Hi all
>
> The solution should be ready made, generic.
> Like this for example:
> https://play.google.com/store/apps/details?id=com.icecoldapps.smsgatewayultimatepro&hl=en
>
> With it you receive the SMS in your phone, and forward it to a
> URL, the URL would be a router script into whatever program (like
> Heavymetal for example)
> You have many options from there:
> 1- The script connects to the loop program over telnet (HM3),
> authenticates and dispatches the message directly to the TTY, all
> on the fly.
> 2- The script saves the message as a txt file with incrementing
> numbers, and the loop program simply pools the message. If the
> file does not exist (HTTP error 404) simply tries again later. If
> the file exists, retrieves the content, increments a counter and
> tries again.
> 3- You can route to email, and retrieve periodically emails from
> the TTY, in fact you could use a "[SMS]" flag at the subject and
> only retrieve those emails.
> 4- Lots of fancy things can be done on the backend with a DB and
> an API
>
> I am pretty sure the Android Play Store has other options as well.
>
> Regards!
>
> Javier
> LU8AJA
>
> On 09/12/2013 11:09, Paul Heller wrote:
>> Hi Gil,
>>
>> Well, not so great...
>>
>> I did some investigation last night. iOS apps run in a sandbox
>> intended to prevent them from accessing other apps. Apple pushes
>> pretty hard to enforce this. Unfortunately the public API in iOS
>> does not allow access to SMS messages because that breaks the
>> sandbox design. There is probably a private API somewhere that
>> gives access to SMS, but if it were found and used then the app
>> could be distributed in the app store (Apple checks for these
>> kinds of things). Plus the user would be required to "jailbreak"
>> their phone. That is a real hack for the phone and every iOS
>> update requires you to figure out how to jailbreak it again. I
>> doubt this is something people would really want to do (of course
>> some hams might enjoy the challenge...).
>>
>> So the iOS SMS message approach is probably out. We could explore
>> the email or RSS route.
>>
>> Android typically does not have these types of restrictions, so
>> the SMS approach might be possible there - I don't really know. I
>> have built a number of iOS apps but have not done any android
>> work yet. I am interested to learn android, but I have too many
>> other projects (ITTY included!) on my plate ahead of doing that,
>> so we best find someone else for any android work.
>>
>> Looking forward to hear from others...
>>
>> Paul
>> W2TTY
>>
>> On Dec 9, 2013, at 6:59 AM, Paul Heller <paulsheller at comcast.net
>> <mailto:paulsheller at comcast.net>> wrote:
>>
>>> Hi Gil,
>>>
>>> Well, not so great...
>>>
>>> I did some investigation last night. iOS apps run in a sandbox
>>> intended to prevent them from accessing other apps. Apple pushes
>>> pretty hard to enforce this. Unfortunately the public API in iOS
>>> does not allow access to SMS messages because that breaks the
>>> sandbox design. There is probably a private API somewhere that
>>> gives access to SMS, but if it were found and used then the app
>>> could be distributed in the app store (Apple checks for these
>>> kinds of things). Plus the user would be required to "jailbreak"
>>> their phone. That is a real hack for the phone and every iOS
>>> update requires you to figure out how to jailbreak it again. I
>>> doubt this is something people would really want to do (of
>>> course some hams might enjoy the challenge...).
>>>
>>> So the iOS SMS message approach is probably out. We could
>>> explore the email or RSS route.
>>>
>>> Android typically does not have these types of restrictions, so
>>> the SMS approach might be possible there - I don't really know.
>>> I have built a number of iOS apps but have not done any android
>>> work yet. I am interested to learn android, but I have too many
>>> other projects (ITTY included!) on my plate ahead of doing that,
>>> so we best find someone else for any android work.
>>>
>>> Looking forward to hear from others...
>>>
>>> Paul
>>> W2TTY
>>>
>>>
>>> On Dec 8, 2013, at 6:57 PM, gil at baudot.net
>>> <mailto:gil at baudot.net> wrote:
>>>
>>>> Hey Paul:
>>>>
>>>> That would be great!
>>>>
>>>> I think the first part of the puzzle would be to intercept an
>>>> sms text that is coming from one or more known phone numbers
>>>> (that could be configured in settings), and an option to allow
>>>> all or no numbers through. Another possibility would be to poll
>>>> an email account for received messages as well, but I don't
>>>> know how much work that would be.
>>>>
>>>> The second part of the project would be to identify an external
>>>> wifi gizmo (or possibly bluetooth, but wifi would have better
>>>> range and probably be cheaper hardware), to which to send the
>>>> message. Either a simple discovery to find find the
>>>> ip-addr/port number, or a simple programmable static-ip, could
>>>> be used. Then a tcp/ip socket could be opened, the message
>>>> sent, and the socket closed. A udp datagram could be used as
>>>> well, but would not have the error checking and delivery guarantee.
>>>>
>>>> There could be multiple wifi gizmos available, which could
>>>> identify themselves during discovery. Actually, you would only
>>>> need wifi to the house router, and hard-wired ethernet units on
>>>> the local net could all be found.
>>>>
>>>> To keep it as simple as possible, you could broadcast the
>>>> messages to all found ethenet devices, and let them sort it out
>>>> -- a simple message could be printed by all, or an optional bit
>>>> of addressing could be added to the first-line of the message.
>>>>
>>>> Just some first ramblings -- I'm sure John has some ideas.
>>>>
>>>> thx, gil
>>>>
>>>> gil smith, AF7EZ
>>>> greenkeys moderator
>>>> gil at baudot.net <mailto:gil at baudot.net>
>>>>
>>>>
>>>> -------- Original Message --------
>>>> Subject: Re: [GreenKeys] baudotrss ability to use Google
>>>> Voice to
>>>> receive SMS messages ends May 15, 2014.
>>>> From: Paul Heller <paulsheller at comcast.net
>>>> <mailto:paulsheller at comcast.net>>
>>>> Date: Sun, December 08, 2013 1:11 pm
>>>> To: gil at baudot.net <mailto:gil at baudot.net>
>>>> Cc: nagle at animats.com <mailto:nagle at animats.com>,
>>>> greenkeys at mailman.qth.net <mailto:greenkeys at mailman.qth.net>
>>>>
>>>> I could try it for iOS...
>>>>
>>>> Paul
>>>> W2TTY
>>>>
>>>> On Dec 8, 2013, at 9:39 AM, gil at baudot.net
>>>> <mailto:gil at baudot.net> wrote:
>>>>
>>>>> Hey John:
>>>>>
>>>>> How would the phone connect to the outside? Wifi? I
>>>>> might be interested in making just such a bit of hardware
>>>>> (wifi to loop) if some app programmer wants to write an
>>>>> app. It would only need to provide ASCII, as I could
>>>>> convert to baudot easily for a loop and also provide ASCII
>>>>> serial out, to make the box more useful. I could see how
>>>>> there could be lots of applications for both baudot and
>>>>> ASCII out.
>>>>>
>>>>> So yeah, great idea. Any programmers for android and/or
>>>>> iOS who could intercept SMS from a (programmable) phone
>>>>> number or two, discover the tcpip address/port of a gizmo
>>>>> (or three), and send messages? I'd love to do a bit of
>>>>> hardware for that.
>>>>>
>>>>> Gil
>>>>>
>>>>>
>>>>> gil smith, AF7EZ
>>>>> greenkeys moderator
>>>>> gil at baudot.net <mailto:gil at baudot.net>
>>>>>
>>>>>
>>>>> -------- Original Message --------
>>>>> Subject: [GreenKeys] baudotrss ability to use Google
>>>>> Voice to receive
>>>>> SMS messages ends May 15, 2014.
>>>>> From: John Nagle <nagle at animats.com
>>>>> <mailto:nagle at animats.com>>
>>>>> Date: Sat, December 07, 2013 8:50 pm
>>>>> To: greenkeys at mailman.qth.net
>>>>> <mailto:greenkeys at mailman.qth.net>
>>>>>
>>>>> Due to a redesign and change in policy regarding
>>>>> Google Voice, the
>>>>> capability in my "baudotrss" package to receive SMS
>>>>> messages via
>>>>> Google Voice will stop working on May 15, 2014.
>>>>>
>>>>> We still have support for SMS via Twilio, but that
>>>>> requires a
>>>>> paid Twilio account, and a separate web site to
>>>>> receive SMS
>>>>> messages.
>>>>>
>>>>> The right solution for this would be to implement SMS to
>>>>> Teletype as a smartphone app. Anybody interested in
>>>>> doing that?
>>>>>
>>>>> John Nagle
>>>>> ______________________________________________________________
>>>>> GreenKeys mailing list
>>>>> Home: http://mailman.qth.net/mailman/listinfo/greenkeys
>>>>> Help: http://mailman.qth.net/mmfaq.htm
>>>>> Post: mailto:GreenKeys at mailman.qth.net
>>>>>
>>>>> 2002-to-present greenkeys archive:
>>>>> http://mailman.qth.net/pipermail/greenkeys/
>>>>> 1998-to-2001 greenkeys archive:
>>>>> http://mailman.qth.net/archive/greenkeys/greenkeys.html
>>>>> Randy Guttery's 2001-to-2009 GreenKeys Search Tool:
>>>>> http://comcents.com/tty/greenkeyssearch.html
>>>>>
>>>>> This list hosted by: http://www.qsl.net
>>>>> <http://www.qsl.net/>
>>>>> Please help support this email list:
>>>>> http://www.qsl.net/donate.html
>>>>>
>>>>> ______________________________________________________________
>>>>> GreenKeys mailing list
>>>>> Home: http://mailman.qth.net/mailman/listinfo/greenkeys
>>>>> Help: http://mailman.qth.net/mmfaq.htm
>>>>> Post: mailto:GreenKeys at mailman.qth.net
>>>>>
>>>>> 2002-to-present greenkeys archive:
>>>>> http://mailman.qth.net/pipermail/greenkeys/
>>>>> 1998-to-2001 greenkeys archive:
>>>>> http://mailman.qth.net/archive/greenkeys/greenkeys.html
>>>>> Randy Guttery's 2001-to-2009 GreenKeys Search Tool:
>>>>> http://comcents.com/tty/greenkeyssearch.html
>>>>>
>>>>> This list hosted by: http://www.qsl.net <http://www.qsl.net/>
>>>>> Please help support this email list:
>>>>> http://www.qsl.net/donate.html
>>>>
>>>
>>
>>
>>
>> ______________________________________________________________
>> GreenKeys mailing list
>> Home:http://mailman.qth.net/mailman/listinfo/greenkeys
>> Help:http://mailman.qth.net/mmfaq.htm
>> Post:mailto:GreenKeys at mailman.qth.net
>>
>> 2002-to-present greenkeys archive:http://mailman.qth.net/pipermail/greenkeys/
>> 1998-to-2001 greenkeys archive:http://mailman.qth.net/archive/greenkeys/greenkeys.html
>> Randy Guttery's 2001-to-2009 GreenKeys Search Tool:http://comcents.com/tty/greenkeyssearch.html
>>
>> This list hosted by:http://www.qsl.net
>> Please help support this email list:http://www.qsl.net/donate.html
>
> ------------------------------------------------------------------------
> ______________________________________________________________
> GreenKeys mailing list
> Home: http://mailman.qth.net/mailman/listinfo/greenkeys
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:GreenKeys at mailman.qth.net
>
> 2002-to-present greenkeys archive:
> http://mailman.qth.net/pipermail/greenkeys/
> 1998-to-2001 greenkeys archive:
> http://mailman.qth.net/archive/greenkeys/greenkeys.html
> Randy Guttery's 2001-to-2009 GreenKeys Search Tool:
> http://comcents.com/tty/greenkeyssearch.html
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qth.net/pipermail/greenkeys/attachments/20131209/b240d8b7/attachment-0001.html>
More information about the GreenKeys
mailing list