linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris DiTrani <chris@livedata.com>
To: linux-admin@vger.kernel.org
Subject: Re: SMS as server infos
Date: 24 Jun 2004 09:30:00 -0400	[thread overview]
Message-ID: <1088083800.2841.26.camel@chris.livedata.com> (raw)
In-Reply-To: <17daa8560406240556640b1806@mail.gmail.com>

On Thu, 2004-06-24 at 08:56, Ahsan Ali wrote:
> Most cell phone carriers have websites where you can go and SMS one of
> their subscribers for free. Often called "Internet Chat" or
> "Web-2-SMS" or something similar.
> 
> Using a HTTP POST means you put together something that will go to
> that particular site and do a HTTP POST (same as you typing something
> into some fields on a web page and clicking "send" or "submit" on the
> page) to send a line of text or a message to your particular number.
> 

Yes. If you find your cell provider's web portal to sms (my provers:
http://www.mymmode.com/messagecenter/), either by looking at the source
html or worst case sniffing the packet when submitting the form you can
figure out what the data posted to the server looks like and emulate
that from a script (probably 1/2 dozen lines of Python code). This
approach is a hack since it's depending on a private interface (the
format of the posted data and url itself) that can be changed at any
time (i.e. you wouldn't want to build a critical notification system
around it), so substituting  a real sms api or toolset for the post to
your cell provider would probably be better. Using a already available
package that wraps all this up would be better still, but I don't have
any experience with that.

CD


  reply	other threads:[~2004-06-24 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-23 16:41 SMS as server infos Luca Ferrari
2004-06-23 17:12 ` Chris DiTrani
2004-06-24 11:15   ` joy
2004-06-24 12:56     ` Ahsan Ali
2004-06-24 13:30       ` Chris DiTrani [this message]
2004-06-25 12:35         ` joy
2004-06-24  4:58 ` Andreas Unterkircher
2004-07-27  8:24 ` Ag. System Administrator

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1088083800.2841.26.camel@chris.livedata.com \
    --to=chris@livedata.com \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).