|
|
The paging server is required for paging message notification or paging on Single Number Reach features. uOne interfaces with the Paging Server using the SNPP protocol. Paging administration must be closely coordinated between the Unified Messaging System Administration (UMSA) tool and the Paging Server for proper operation. For further information, see the uOneGateserver Installation and Configuration Manual.
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. 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:
MobileComm-Richmond should be before MobileComm-(.*). Otherwise, the search would select the wrong number.
<ProviderName>-<CityName>-<ST>-(.*)(\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
Step 3 The provider names on the left-hand side should appear 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 UMSA is
MobileComm-Richmond-VA
the entry in the pagermap file shall be
MobileComm-Richmond-VA-(.*)(\t)+18042702271/\1
It is strongly recommended that you go thru the Hylafax documentaion at the following URL:
http://www.hylafax.org/setup.html.
The man pages of all hylafax commands are available in /usr/local/man. If you set your MANPATH=/usr/local/man, you should be able to see the man pages of commands found in /usr/local/bin and /usr/local/sbin. Also read config, Hylafax related man pages.
The Hylafax software logs messages in the /var/adm/SYSLOG file. If you need to modify this, please consult Hylafax documentation. The faxqclean and faxcron commands need to be scheduled to run once a day for cleaning up and archiving (thru cron). For more information of server operation, please read http://www.vix.com/hylafax/operation.html.
The following table (Table 5-1) provides locations of associated server information.
| What | Description | Location* |
|---|---|---|
The fully qualified domain name of the server. |
| |
SNPP Paging server user. |
| |
SNPP Paging server user password. |
| |
SNPP server port number. Defaults to 444. |
|
*Assumes use of a UNIX-like OS.
The paging server services both paging for new message notification and paging for SNR. You must determine the peak load on the system for paging in order to engineer the Paging server properly. Certain SNPP servers use the IXO/TAP protocol 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 setup, connection to the paging provider, sending the page, and breakdown of 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.
Posted: Mon Sep 25 19:25:55 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.