<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.28.3">
</HEAD>
<BODY>
Maybe I'm missing something. I do this all the time by having our servers email <myphonenumber>@vtext.com. Converts to an SMS message. <BR>
<BR>
Just make darn sure you throttle the number of messages. It's no fun to get 60 text messages a minute when it really goes off into the weeds. <BR>
<BR>
I'd rather get an SMS text message I can read whilst otherwise occupied, versus an audio I have to listen to. <BR>
<BR>
Neal <BR>
<BR>
On Mon, 2012-12-10 at 09:33 -0500, Dennis Ruzeski wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
I'd be very interested in this! I recently took a job with a place
that does alot of VOIP stuff and some quick and dirty one-liners that
might help troubleshooting would be a great.
On Mon, Dec 10, 2012 at 9:27 AM, Pete Hardie <<A HREF="mailto:pete.hardie@gmail.com">pete.hardie@gmail.com</A>> wrote:
> Sounds cool!
>
> Pete Hardie
> --------
> Better Living Through Bitmaps
>
>
>
> On Mon, Dec 10, 2012 at 9:15 AM, Richard Bronosky <<A HREF="mailto:richard@bronosky.com">richard@bronosky.com</A>>
> wrote:
>>
>> For the ATT mobile hackathon on the 30th I made a project that uses call
>> management web APIs. (Because it increased the prize pool from $300 to $500.
>> This was a good choice as I ended up winning first prize.)
>>
>> One of the gems was that I learned how to use a simple curl command to
>> call my phone. Now, doing something useful with that call (text to speech,
>> speech to text, or IVR menu tree) gets pretty complex, however making the
>> call can be pretty powerful alone. Let's say you put curl command in a
>> script named "callme". You can then go:
>> rsync /path server:/path || callme
>>
>> Then, if that rsync command that you expected to take 4 hours fails, you
>> get a call and don't lose half your day. Or, you can use a semicolon instead
>> of the double pipe and it calls you no matter what. There will be no one on
>> the other end of the call, but in this most basic form it is still pretty
>> useful.
>>
>> With a little bit more work I ought to be able to make it except an
>> argument that gets passed to the text to speech API. Then you could use it
>> for alerts of a less binary nature:
>> callme "I just met you and this is crazy"
>>
>> (If you get that joke, I hope you have young girls at home.)
>>
>> Would anyone be interested in seeing this? It'll take a little effort to
>> prepare.
>>
>>
>> _______________________________________________
>> Ale mailing list
>> <A HREF="mailto:Ale@ale.org">Ale@ale.org</A>
>> <A HREF="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</A>
>> See JOBS, ANNOUNCE and SCHOOLS lists at
>> <A HREF="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</A>
>>
>
>
> _______________________________________________
> Ale mailing list
> <A HREF="mailto:Ale@ale.org">Ale@ale.org</A>
> <A HREF="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</A>
> See JOBS, ANNOUNCE and SCHOOLS lists at
> <A HREF="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</A>
>
_______________________________________________
Ale mailing list
<A HREF="mailto:Ale@ale.org">Ale@ale.org</A>
<A HREF="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</A>
See JOBS, ANNOUNCE and SCHOOLS lists at
<A HREF="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</A>
</PRE>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>