|
|
Paging is available in uOne.
Two components of Paging administration must be closely coordinated. The first is administration of the Hylafax Paging Server file, pagermap. This file holds information about Paging Providers and their access numbers. Access numbers are the 800 numbers the Paging Server modem dials to connect to a particular Paging Provider. This is how uOne talks to Paging Providers when it wants to send out a page.
The second component is the subscriber's profile, which is stored on 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, Pager ID, and Pager PIN. There is other subscriber preference information for single number reach and message notification that determines when the subscriber will be paged.
When the system wants to page a subscriber, the following events occur:
Before you start administering Paging Services, ensure that the following tasks have been completed:
Refer to the HylaFAX Paging Server documentation for information about adding, modifying and deleting entries in the HylaFAX pagermap file (See Figure 7-1). This documentation can be found at: http://www.vix.com/hylafax/toc.html.
You perform the following tasks to manage Paging Services:
Perform the following steps to provide the MWI_OnOff application with the information to find the Paging Server. This information is required for Message Notification Paging.
Step 1 Go to the GateServer where the MWI_OnOff application resides
Step 2 Type: cd $PARMLIB/apps/MWI_OnOff
Step 3 Edit the MWI_OnOff.ini files and set the following attributes (Table 7-1).
SNPPuser=
SNPPhost=
SNPPpw=
SNPPport=
| Attribute | Description | Valid Values |
The Pager Server user. | ||
The Pager Server host name. | ||
SNPPpw | The Pager Server user password. | |
The Pager Server user. | The SNPPport attribute must be set to 444. |
The paging provider information in the subscriber profile must match the syntax required by the 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 Unified Messaging System Administration (UMSA).
Step 1 Go to the GateServer where the pagerData.ini file resides for UMSA and log in as spmaster.
Step 2 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata
Step 3 Edit the pagerData.ini files and set the following attributes (Table 7-2).
[pagingprovider]
numOfOptions=
optionXX=Value, Text string
defaultValue=
| Attribute | 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 UMSA screen. <value> is the data that will be stored in the LDAP database. Place a comma after that value. The pagermap configuration file on the Paging Server contains information needed to actually make the call for the pager. Note that the <Value> used in the pagerData.ini must match the first part of an entry in the pagermap file. Otherwise, the Paging Server will not know what number to dial for a subscriber's paging service. <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 Value from the pagermap file on the 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. |
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 message notification preferences.
Step 1 Go to the GateServer where the defaultData.ini file resides for UMSA and log in as spmaster.
Step 2 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata
Step 3 Edit defaultData.ini files and set the following attributes (Table 7-3).
[addNotifyforNewSub]
numOfAttrs=<XX>
attr<YY>=<Value>
referenceAttr=<NotificationMethod>
| Attribute | 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 SMSI) | 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. | NotificationMethod: pager—sends a page on every message as defined by the attribute list. cn—sends a SMSI signal on every message as defined by the attribute list. |
Posted: Mon Sep 25 19:44:37 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.