|
|
Paging is available for two separate features in uOne.
 |
Note The tasks presented in this section are required only if you implement paging services for either of the above features. |
Two types of pagers are supported:
For numeric paging, two components of paging administration must be closely coordinated. The first is administration of the paging server file that holds information about paging providers and their access numbers. Access numbers are the telephone numbers the paging server modem dials to connect to a particular paging provider modem pool. This is how uOne reaches to paging providers when it sends out a page.
The second component of numeric paging that requires close coordination is the subscriber's profile, which is stored in the LDAP directory. The profile contains information about the subscriber specific paging information. The information required to communicate with the subscriber's paging provider includes the Paging Provider and Pager ID. There is other subscriber preference information for single number reach and message notification that determines when the subscriber will be paged.
|
Note The paging server is required for numeric paging. However, text paging does not require the paging server. |
For text (alphanumeric) paging, the only coordination required is that a proper pager e-mail address is used and an SMTP server host is used that can reach that address.
When the system pages a subscriber, the following events occur:
Before you start administering Paging Services, ensure that the following tasks have been completed:
You perform the following tasks to manage Paging Services:
Perform the following steps to provide the UM application agent with the information to find the SNPP paging server. This information is required for only for numeric Single Number Reach paging.
Step 2 Type: cd $PARMLIB/apps/UM
Step 3 Edit the UM.ini files and set the following parameters (Table 7-1).
[UMConfig]
SNPPHost=
SNPPPort=
SNPPPassword=
SNPPuser=
|
Note You must configure these parameters for numeric Single Number Reach paging to work. SNPP is the protocol the UM application agent uses to send numeric page requests to the SNPP paging server. |
|
Note Note that there is no place in the UM.ini file to configure the SMTP servers used for Single Number Reach text paging. When Single Number Reach text paging occurs, the subscriber's configured SMTP server is used. You must ensure that this SMTP server can reach your SMTP paging service. |
| Parameter | Description | Valid Values | ||
The UM.ini configuration section label. | Should not be edited. | |||
SNPPHost=<hostname> | The SNPP paging server host name used for numeric SNR paging. | Valid machine name. | ||
SNPPPort=<port number> | The SNPP paging server port number used for numeric SNR paging. | 444 Default = N/A | ||
SNPPPassword=<password> | The SNPP paging server user password used for numeric SNR paging. | Valid password for the SNPPuser in the /var/spool/fax/etc/hosts file.
Default = N/A | ||
SNPPuser=<pager server user> | The SNPP paging server user used for numeric SNR paging. | Valid user name in the /var/spool/fax/etc/hosts file for SNPP paging server. Default = spmaster
|
Perform the following steps to provide the MWI_OnOff application with the information to find the SNPP paging server used for numeric paging and the SMTP server used for text paging. This information is required for Message Notification Paging.
Step 2 Type: cd $PARMLIB/apps/MWI_OnOff
Step 3 Edit the MWI_OnOff.ini file as desired (Table 7-2).
|
Note You must configure the SNPP parameters for message notification for numeric paging to work. The ReturnPath and SMTPHosts parameters are required for text paging to work. |
|
Note Multiple language support is provided for text paging. See"Multiple Language Support" in this chapter for parameter set up. |
| Parameter | Description | Valid Values |
The SNPP pager server user used for numeric paging. | SNPP_USERNAME from /var/spool/fax/etc/hosts or blank defaults to spmaster. | |
The SNPP pager server host name used for numeric paging. | ||
SNPPpw | The SNPP pager server user password used for numeric paging. | |
The SNPP pager server user used for numeric paging. | The SNPPport parameter. By convention, use 444. | |
ReturnPath | Specifies the e-mail account to which paging failure notification mail should be sent. Used for text paging. | Valid e-mail address. By convention, use the Postmaster e-mail address. |
SMTPHosts | SMTP hosts used for text paging. | One or valid host name(s). If multiple host names are specified, a comma, space, or TAB must separate each host name. |
To support multiple languages for text paging, the MWI_OnOff.ini file must contain a language section for each supported language similar to the default [eng] section provided in the MWI_OnOff sample file (see Figure 7-1). The language name must be ISO639 standard. Each language section must have an entry for each notification type that will contain text for the page e-mail subject.
| |
The SNPP paging provider information in the subscriber profile must match the provider names configured in the SNPP paging server. In order to facilitate this, the pagerData.ini file is available for you to enter the appropriate data once and make it available through a pull down menu in uOne Administration.
Step 2 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata
Step 3 Edit the pagerData.ini file as desired (Table 7-3). Ensure that it is consistent with the information on the SNPP paging server.
|
Note You must configure these parameters for numeric paging to work. |
| Parameter | Description | Valid Values |
|---|---|---|
[pagingprovider] | The options list label. | Should not be edited. |
NumOfOptions=XX | The number of providers that will be displayed in the options list. Ensure that this value matches the number of options you specify. | XX— a number |
Option<XX>=<value>, <text string> | <XX> indicates the order in which the options will appear in the drop-down list box for the Paging Provider field on the uOne Administration screen. <value> is the data that will be stored in the LDAP database. Place a comma after that value. <text string> is the on-screen name of the provider. This name will appear in the drop-down list box for the Paging Provider field. | XX—A number. There must be no gaps in the numbering of options. value—An existing provider name value configured in the SNPP paging server. text string—A name that identifies the provider. |
DefaultValue=<X> | The <Value> of the option to be used for the default. This field can be edited, but should not be removed. | A <Value> listed in this file. |
| [pagingprovider] numOfOptions=14 option1=MobileComm, MobileComm option2=MobileComm-Richmond-VA, MobileComm Richmond VA option3=MobileComm-TX, MobileComm TX option4=MobileComm-TX2, MobileComm TX 2 option5=MobileComm-DC, MobileComm DC option6=MobileComm-WA, MobileComm WA option7=MobileComm-MA, MobileComm MA option8=MobileComm-AL, MobileComm AL option9=MobileComm-LongIsland_NY, MobileComm LongIsland NY option10=MobileComm-MICH, MobileComm MICH option11=MobileComm-CA, MobileComm CA option12=PageNet, PageNet option13=PageNet-Richmond-VA, PageNet Richmond VA option14=SkyTel, SkyTel toll free defaultValue=MobileComm
|
If you are adding paging to your system, you may want to update the defaultData.ini file to set up the system level defaults for MWI/pager message notification preferences.
Step 2 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata
Step 3 Edit the defaultData.ini file as desired (Table 7-4).
|
Note You must configure these parameters for message notification to work. |
| [addNotifyforNewPager] numOfAttrs=2 attr1=notifyvoicenormal attr2=notifyvoiceurgent referenceAttr=pager [addNotifyforNewSub] numOfAttrs=2 attr1=notifyvoicenormal attr2=notifyvoiceurgent referenceAttr=cn
|
| Parameter | Description | Valid Values |
[addNotifyforNewPager] | The section label. | Should not be edited. |
numOfAttrs=<XX> | The number of attributes entry can be changed as long as it matches the number of attributes. | XX—A number |
attr<YY>=<Value> | Where YY is a numeric value corresponding to its position within the attribute list. There must be no gaps in the numbering of options. Value describes what message type and urgency will apply to this type of Message Notification (e.g. pager or MWI). | YY—A number Value: notifyvoicenormal notifyvoiceurgent notifyfaxnormal notifyfaxurgent notifyemailnormal notifyemailurgent |
referenceAttr= | Notification Method describes the notification method to be used as defined by the attribute list. This field can be edited, but should not be removed. | Notification Method: pager—sends a page on every message defined by the attribute list. cn—sends a MWI signal on every message defined by the attribute list. |
Posted: Mon Sep 25 20:06:33 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.