SNPP Paging Server Configuration

The paging server is required for numeric paging message notification or paging on Single Number Reach features. For numeric pages, uOne interfaces with a paging server using SNPP. Paging administration must be closely coordinated between the uOne Administration tool and the paging server for proper operation, specifically with respect to paging provider names. For further information, see the uOne Administration Manual.

For alphanumeric pages, uOne interfaces with an SMTP paging server. Only the SNPP paging server requirements are covered in this section.

Note The following information is required when administering uOne. You should document this for every paging server.

Prerequisites

Step 1 Add an spmaster entry to the /var/spool/fax/etc/hosts file on the paging server. This is the SnppUser configured in UM.ini and MWI_OnOff.ini on the AMM setup. In this example, since no password is used, you must configure SnppPassword to the empty string in the UM.ini and MWI_OnOff.ini files. A sample host file (that uses no passwords) follows:

: @localhost$
@127.0.0.1$
^spmaster@

Step 2 Edit the /var/spool/fax/etc/pagermap file to introduce the provider name/numbers in the following format:

Example

<ProviderName>(.*)(\t)+<countrycode><area_code><phonenumber>/\1

Sample pagermap file:

MobileComm-Richmond-VA-(.*)(\t)+18042702271/\1
MobileComm-TX2-(.*)\t+18003442270/\1
MobileComm-TX-(.*)\t+18004353582/\1
MobileComm-CA-(.*)\t+18006556555/\1 #Northern CA
MobileComm-(.*)\t+18009464644/\1 #central number
PageNet-Richmond-VA-(.*)\t+18042787844/\1
PageNet-(.*)\t+18007669619/\1
SkyTel-(.*)\t+18007596366/\1

Note The "\t" in the samples signifies use of the Tab key.
Also, longer names must appear in the file before shorter names. For example:
MobileComm-Richmond-VA-(.*) must be before MobileComm-(.*). Otherwise, the search would always select the more general MobileComm-(.*), ignoring MobileComm-Richmond-VA-(.*).

Step 3 Ensure that the provider names on the left-hand side are written as they appear in the pagerData.ini file located in /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata.

For example, if the provider name in the pagerData.ini is

: MobileComm-Richmond-VA

and this provider's IXO/TAP terminal has phone number + 18042702271, then the entry in the pagermap file would be

: MobileComm-Richmond-VA-(.*)\t+18042702271/\1

Recommendations for setup and maintenance

The following table (Table 5-1) provides the locations of associated server information.

Table 5-1: Server Information Location

What Description Location¹

SNPP Host Name

The fully qualified domain name of the paging server.

/etc/hosts

uname -n command (appended with the domain suffix. See the resolv.conf file.)

SNPPport

SNPP server port number. Defaults to 444.

/etc/init.d/<paging server provider directory>

SNPPpw

SNPP paging server user password.

/var/spool/fax/etc/hosts

SNPPuser

SNPP paging server user.

/var/spool/fax/etc/hosts

¹Assumes use of a UNIX-like OS.

What	Description	Location¹
SNPP Host Name	The fully qualified domain name of the paging server.	/etc/hosts uname -n command (appended with the domain suffix. See the resolv.conf file.)
SNPPport	SNPP server port number. Defaults to 444.	/etc/init.d/<paging server provider directory>
SNPPpw	SNPP paging server user password.	/var/spool/fax/etc/hosts
SNPPuser	SNPP paging server user.	/var/spool/fax/etc/hosts

Engineering

The paging server services numeric paging for new message notification. You must determine the peak load on the system for paging in order to engineer the paging server properly. Certain SNPP servers use IXO/TAP to access the paging providers. Our experience with IXO/TAP has shown that our fastest throughput rate based on a modem pool connected to the paging server is one minute per page, per modem. This includes the modem setup, connection to the paging provider, sending the page request, and tearing down the call.

You should be able to determine the number of modems you require by understanding the peak load and the throughput rate. You should also check the paging providers you will be using to ensure they support a sufficient number of access lines when IXO/TAP is used on their end.

Table of Contents