Sendpage

Sendpage is a handy tool that helps you send pages using SNPP on one side and TAP (or UCP) on the other. It grabs pages from your network via SNPP and then sends them out to a Paging Central or "paging terminal" using either a modem or a direct serial connection. Pretty cool, right?

How Does Sendpage Work?

So, when you're using Sendpage with a modem, you'll need to know your PC's access number. This number isn't usually out there for everyone to see, so you'll want to check with your paging provider. Plus, don’t forget that you’ll also need the PINs for the pagers you want to send messages to. Your paging provider will have all this info handy!

For Paging Providers

If you're actually working as a paging provider, you're in luck! You’ve got it much easier when it comes to setting up Sendpage.

Key Features of Sendpage

Here are some standout features:

• 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 & Client features!


• A direct-queue Client option!


• A DBI support for pager database!

Getting Started with Sendpage

If you’re ready to dive in, here’s how you can install it:

perl Makefile.PL

make

make install

Requirements for Using Sendpage

You’ll need the following:

• The Net::SNPP module (part of the libnet Perl module bundle)


• The Device::SerialPort version 1.02+


• The MailTools module (which includes Mail::Send)

What's New in This Release?

This latest version has updated documentation—specifically, it removes non-free RFC copies.