Paging providers typically provide several mechanisms
to send pages. Here's my take:
- SMTP This is the most widely supported,
but least well defined. The format of the message
is entirely up the provider and how they translate
email to a page. Also, unless you do a bit of work,
the message could sit in a local or remote mail queue.
( try a combination of Net::DNS::Resolver and
Net::SMTP if you want to connect directly
to the remote SMTP server).
- TAP (aka IXO ) This is probably the second
most widely supported method. Clunky because you
have to do it via a modem, but handy for the same reason.
( if your monitoring box notices that the network is
down, the modem could still be accessible for notification).
I've found it easiest to just have perl talk to kermit. Google around
for a script called "ckepage.ksc".
- SNPP (simple network paging protocol) Third most widely supported method. Check
out Net::SNPP. If your provider supports it,
this is probably the most straightforward way to send
pages.
- WCTP: (wireless communication transfer protocol ). This is probably the least widely supported
protocol, but is the "latest/greatest" thing. I'm not
aware of a perl implementation yet, but there general
info here.
Other links that might be helpful:
- sendpage - a pretty
comprehensive paging system that include SNPP and TAP
clients, as well as an SNPP server
- Part of the kermit faq explaining how to send a page from kermit
- Net::Pager this perl module uses Simplewire's quasi-free
paging service, which I don't like. Perhaps you will though.
I've done quite a bit of pager integration with perl,
so feel free to /msg me if you need more specific info.
Good luck !
Update:This link has fairly decent information on which paging
providers support SNPP, WCTP, etc. Also shows host
and port names for the services.
