Sendpage 1.0.2 review
DownloadSendpage is designed to speak SNPP on one end and TAP (or UCP) on the other
|
|
Sendpage is designed to speak SNPP on one end and TAP (or UCP) on the other. Sendpage gets pages from the network via SNPP, and then uses a modem or a direct serial connection to deliver the pages to a Paging Central (or "paging terminal").
Sendpage requires, for modem use, that you know your PC's access number (which is not usually advertised by your paging provider), and you need to know the PINs of the pagers you want to deliver pages to.
All of this information is known by your paging provider. If you ARE a paging provider, your job is much easier.
Here are some key features of "Sendpage":
UCP communication
TAP communication
Daemonized queue manager
Multiple modem support
Modem sharing
Multiple Paging Centrals
Parallel Paging Central delivery
Dynamic reconfiguration
Modem-level debugging
Paging Central-level debugging
Pager alias support
Pager alias-level debugging
Syslog notification
Progress logging
Email notification on success/failure
SNPP Server
SNPP Client
Direct-queue Client
DBI support for pager database
Installation:
perl Makefile.PL
make
make install
Requirements:
Net::SNPP (part of the libnet Perl module bundle)
Device::SerialPort version 1.02+
MailTools (provides Mail::Send)
What's New in This Release:
The time-out code was fixed to handle endless failure situations.
Recipient bleed-through across SEND/RESE in SNPP was fixed.
Queue filename collision was fixed.
Minimal "use" testing was added.
Version number reporting on banner was corrected.
Sendpage 1.0.2 search tags