27 Dec
2008
27 Dec
'08
4:09 p.m.
I want to start sending text messages from a cron job - does anyone already
do this and do you have any hints or recommendations for technologies or
providers? I'd only want to send a dozen or so a month, so I'm hardly a
bulk user
Cheers
James
27 Dec
27 Dec
4:39 p.m.
On Saturday 27 December 2008 16:09:17 James Ogden wrote:
I want to start sending text messages from a cron job
- does anyone already
do this and do you have any hints or recommendations for technologies or
providers? I'd only want to send a dozen or so a month, so I'm hardly a
bulk user
There are loads of gateways for this. I've used http://sms2email.com (AQL) in
the past without problems, just setting up an e-mail forward on their site
(something(a)sms2email.com) then sending messages to that. The subject line
and message body are included in the SMS, so it's easy to work with. Like
most providers, they have APIs if you want something more.
--
Dominic Cleal
dominic(a)computerkb.co.uk
4:53 p.m.
I want to
start sending text messages from a cron job - does anyone already
do this and do you have any hints or recommendations for technologies or
providers? I'd only want to send a dozen or so a month, so I'm hardly a
bulk user
There are loads of gateways for this. I've used http://sms2email.com (AQL) in
the past without problems, just setting up an e-mail forward on their site
(something(a)sms2email.com) then sending messages to that. The subject line
and message body are included in the SMS, so it's easy to work with. Like
most providers, they have APIs if you want something more.
11:12 p.m.
On Saturday 27 December 2008 16:53:34 Mat Johns wrote:
I agree that it adds another layer of complexity, but I don't agree that
there's no easy way to provide "debug info". I think you're in exactly
the
same boat whether you use HTTP or SMTP for an interface if your network or
SMS provider fails. Most MTAs have extensive logging if there is a need to
debug -- they're pretty tried and tested.
Running an MTA (rather than ssmtp etc) means you will have queueing and
message retries provided in case your SMS provider falls over. It's also
easy to test and switch providers if necessary with little change.
--
Dominic Cleal
dominic(a)computerkb.co.uk
Like most
providers, they have APIs if you want something more.
Heh yes, however I in fact work for one such a company [1]. We are
probably a little out of your target volume bracket (however I'm not
the sales side, hence the bad pitch). One of our more popular
interfaces is quite simply a HTTP based one [2]. I would suggest if
you are using this for server monitoring, adding in the extra layer of
SMTP will just add complexity to the issue as there is no easy way of
providing debug info if your network / mta / sms provider; falls over. 
11:19 p.m.
Dominic Cleal wrote:
I agree that it adds another layer of complexity, but
I don't agree that
there's no easy way to provide "debug info". I think you're in exactly
the
same boat whether you use HTTP or SMTP for an interface if your network or
SMS provider fails. Most MTAs have extensive logging if there is a need to
debug -- they're pretty tried and tested.
Actually SMTP would be more complex, most smtp apps would dump the
message into the local MTA and you'd have to hope it was running, where
as doing HTTP, and this is where the perceived level of complexity
increases, you do the connection directly from your app or what not.
Running an MTA (rather than ssmtp etc) means you will
have queueing and
message retries provided in case your SMS provider falls over. It's also
easy to test and switch providers if necessary with little change.
Exactly! :) It also means the level of complexity goes up with it.
--
Best regards,
Duane
http://www.freeauth.org - Enterprise Two Factor Authentication
http://www.nodedb.com - Think globally, network locally
http://www.sydneywireless.com - Telecommunications Freedom
http://e164.org - Global Communication for the 21st Century
"In the long run the pessimist may be proved right,
but the optimist has a better time on the trip."
11:32 p.m.
On Saturday 27 December 2008 23:19:41 Duane at e164 dot org wrote:
Dominic Cleal wrote:
You must have missed my first line. I agree it adds complexity, though I
believe it's worthwhile for a lot of uses, especially casual, infrequent use
(see OP).
I agree that it adds another layer of complexity,
but I don't agree that
there's no easy way to provide "debug info". I think you're in
exactly
the same boat whether you use HTTP or SMTP for an interface if your
network or SMS provider fails. Most MTAs have extensive logging if there
is a need to debug -- they're pretty tried and tested.
Actually SMTP would be more complex [..], most smtp apps would dump the
message into the local MTA and you'd have to hope it was running, where
as doing HTTP, and this is where the perceived level of complexity
increases, you do the connection directly from your app or what not.
You "hope"? If you rely on this, check it's running, run a test! Most
server
distros have an MTA set up to go out of the box, it shouldn't require much
effort.
--
Dominic Cleal
dominic(a)computerkb.co.uk
4:58 p.m.
On Sat, Dec 27, 2008 at 16:09, James Ogden <james(a)jeo.org.uk> wrote:
I want to start sending text messages from a cron job
- does anyone already
do this and do you have any hints or recommendations for technologies or
providers? I'd only want to send a dozen or so a month, so I'm hardly a
bulk user
I've not used AQL for a very long time, but they were great back then.
5599
days inactive
5599
days old
6 comments
5 participants
participants (5)
-
Alexander Mann -
Dominic Cleal -
Duane at e164 dot org -
James Ogden -
Mat Johns