On Thu, Sep 28, 2000 at 04:40:02PM +1100, Matt Allen wrote:
> >
> > > I've got a setup here that bounces email messages to Qpage, which
> > > sends them SMS to my mobile. Works nicely.
> > >
> > > If Qpage doesn't take your fancy, there are other programs that
> > > do the same thing. Look for the TAP (or IXO) protocol, and SNPP
> > > (Simple Network Paging Protocol)
> > >
> > > A word of caution. This is working with the Telstra SMS system.
> > > I don't know of the other telcos. It should work, but I haven't
> > > tried it.
>
> Is there ever a delay? does the SMS come though straight away if your mobile is
> turned on ?
$qpage -d -i paul testing
23 seconds: modem connection
29 seconds: TAP exchange completed. Message sent
35 seconds: Mobile phone rings.
Note, these times are accurate to within a couple of seconds.
The time is affected by:
- Busy TAP phone # (shouldn't happen, but it's a possibility)
- Large SMS queue
- Lack of bandwidth to the Mobile
I've been told by a friend working in GSM that the SMS is essentially
unused out-of-voice-channel capacity, so if there are a lot of SMS's
being sent in the cell you're in, then your message can be delayed.
Bottom line: it's more than fast enough for most purposes.
Keep in mind that you need redundant alert paths if you *really*
want to be sure you get notified. The requirements for a system that'll
tell you "the server's on fire!" are somewhat different to one that
sends traffic on the level of "meet me 4 lunch?".
Didn't I have this conversation a while back? Or was that another
mailing list ;)
Cheers
Paul Haddon
Technical Services Manager
Hartingdale Internet
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
