Sendpage

Sendpage is a cool tool that lets you handle paging messages really easily. It works by taking in SNPP on one side and using TAP (or UCP) on the other side. When it gets pages from the network using SNPP, it sends those pages out through a modem or a direct serial connection to your Paging Central, which is like your paging terminal.

Key Features of Sendpage

Now, let’s talk about what makes Sendpage awesome:

• 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 and Client options available!


• A Direct-queue Client for ease!


• The DBI support for pager databases is super handy!

This list shows why Sendpage is a great choice for your paging needs!

Your Setup Needs for Sendpage

If you're going to use a modem with Sendpage, there are a couple of things you should know. First, you need your PC's access number, which usually isn't shared by your paging provider. Plus, you'll also need the PINs for the pagers you're sending messages to. Don't worry; if you're working with a paging provider, this info will be easy to get!

The Basics of Getting Started with Sendpage

If you want to install it, here’s how:

perl Makefile.PL

make

make install

You’ll Need These Requirements:

• Net::SNPP (part of the libnet Perl module bundle)
• Your device should have Device::SerialPort version 1.02+
• You will also need MailTools (provides Mail::Send)

The Latest Updates in Sendpage:

The newest release has some updated documentation that clears up non-free RFC copies.