|
|
The three types of standard message notification services available to uOne subscribers are notification by pager, by stutter dial tone, or by Message Waiting Light. In addition, Short Message Notification (SMS) is available (see "Administering SMS Notification Services").
System defaults for standard message notification are defined in the defaultData.ini file on the GateServer on which Unified Messaging System Administration (UMSA) resides. System Administrators can change these defaults whenever it is necessary.
Subscribers can customize their notification options through Personal Messaging Administration. For example, they might choose to set their mailbox up to page them on all urgent messages and normal fax messages, to light the light on their phone (Message Waiting Light) on normal voice, and have no notification on e-mail messages.
The four components of message notification are:
When a new SMTP message arrives on the Messaging Server, the SMTP process on the Messaging Server generates an SMTP_Accept. For every SMTP_Accept, MWI_PlugIn is called. MWI_PlugIn writes to a local FIFO queue. MWI_PassOff receives the request for notification via this FIFO and sends the notification records through a TCP connection to the Notification Access Server, where MWI_Notify and MWI_OnOff are located. (MWI_PassOff and MWI_Notify are "partner" applications that are responsible for network communications between the Messaging Server and the Notification Access Server.) MWI_Notify receives the notification records and passes them to MWI_OnOff via SSIO. MWI_OnOff handles the LDAP lookup and configuration logic to determine the type of notification defined for the subscriber. After MWI_OnOff has the subscriber's notification options from the LDAP database, it sends a request to the Telecom Object for SMSI signaling (MWI light or Stutter) and/or sends a request to the Paging Server for a page. The Telecom Object sends the SMSI notification to turn on or off the MWI light or stutter dial tone, and/or the Paging Server sends the page.
Before you start administering Notification Services, ensure that the following tasks have been completed.
You can perform the following tasks for Notification Services:
In smaller deployments, the Notification Access Server can be installed on a GateServer. If the Notification Access Server is installed separately, it should have an Application Object, and the MWI_OnOff and MWI_Notify applications. Each Messaging Server can only have one associated Notification Access Server.
The following steps provide the MWI_OnOff application with the information to communicate with the Directory and Paging Servers. This information is required for message notification and paging, and is set up during the initial configuration of your system.
Step 1 Go to the Notification Access Server 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 5-1).
ldapdn=
ldappw=
ldaphost=
ldapport=
ldapsearchbase=
ldaptimeout=
SNPPuser=
SNPPhost=
SNPPpw=
SNPPport=
| Attribute | Description | Valid Values |
|---|---|---|
The LDAP distinguishing name of the LDAP "superuser." This name can be found on the LDAP server; it is the rootdn entry in the slapd.conf file. | Default: cn=Directory Manager, o=Organization | |
This password resides on the LDAP server; it is the rootpw entry in the slapd.conf file. This can be encrypted. | ||
LDAP host name | A valid host name. | |
LDAP port number This number can be found on the LDAP server; it is the port entry in the slapd.conf file. | By convention, use 389 | |
The LDAP search base. This search base can be found on the LDAP server; it is the searchbase entry in the slapd.conf file. | Default: o=Organization | |
SNPP user name |
defaults to 'spmaster' | |
SNPP host name | ||
SNPP password | ||
SNPPport | SNPP port number | SNPP_PORT or blank defaults to '444' |
The MWI_Notify.ini file is configured during the initial installation of your system. The following procedure shows how this file is set up manually.
Step 1 Go to the Notification Access Server on which the MWI_Notify application resides
Step 2 Type: cd $PARMLIB/apps/MWI_Notify
Step 3 Edit the MWI_Notify.ini files and set the following attributes (Table 5-2).
Port=
Fifo=
| Attribute | Description | Valid Values |
|---|---|---|
The TCP/IP Port number is used for a socket connection between MWI_PassOff and MWI_Notify. This is how the two applications communicate. Specifying a value less than 1024 will require the application to have super-user privileges. | The Port value cannot be specified as zero. By convention, use 4077 as the port number. | |
The Fifo attribute should not be used. It is for advanced testing. | /tmp/sp_mwi |
The uOne product requires the same GateServer to turn MWI on and off. This is accomplished by administering the Application Routing table appropriately.
Step 1 If this is a new installation then the $PARMLIB/parms/APP/Route.<hostname> file needs to contain a SERVICE entry that specifies a Telecom Object with which to send SMSI (on/off), given a search token of the form "MWI <subscriber_mailbox.id>."
SERVICE TNT host MWI
The MWI_Notify and MWI_OnOff applications are added to Schedule.<hostname> file during the initial installation of your system. The following procedure shows how these applications are manually set up in the Schedule file.
Step 1 Go to the Notification Access Server on which the MWI_Notify and MWI_OnOff applications should reside.
$PARMLIB/parms/APP
Step 2 Add the following information to the Schedule.<hostname> file:
STATIC_NOWAIT 100 1 * * * MWI_Notify MWI_Notify/MWI_Notify
DATATOKEN 100 1 * * MWI_OnOff MWI_OnOff/MWI_OnOff
Step 3 Shutdown MWI_PassOff and MWI_Notify in an orderly fashion to ensure that notification events are not dropped:
Shutdown MWI_PassOff first:
kill <pid of MWI_PassOff>
Then shutdown MWI_Notify (if it exists)
kill <pid of MWI_Notify>
Step 4 Reload the schedule table. Type:
umcli
resched static MWI_Notify
Step 5 As superuser on the Messaging Server, start MWI_PassOff:
/tmp/MWI/MWI_PassOff -h <Notification Access Server>.cisco.com
where Notification Access Server is the host name of the machine where MWI_Notify is running.
Message notification is based on the message type (voice, fax - optional, and e-mail - optional) and the message urgency (normal or urgent). For example, the system can be set up to page on all urgent messages regardless of type, have SMSI (stutter or MWI) for all voice and fax messages, and have no message notification on normal e-mails.
The following steps will provide UMSA with the default (initial) notification values that will be set when a new subscriber and a pager (optional) are added through UMSA. Subscribers have the ability to tailor message notification to their own preferences by using the Personal Messaging Administration, the subscriber web administration tool.
Step 1 Go to the GateServer on which UMSA resides.
Step 2 Type:
cd /home2/spmaster/ADMIN/cgi-bin/MSGadmin/MSGdata
Step 3 Edit defaultData.ini files and set the following attributes (Table 5-3).
[addNotifyforNewSub]
numOfAttrs=<XX>
attr<YY>=<Value>
referenceAttr=<NotificationMethod>
| Attribute | Description | Valid Values |
|---|---|---|
This is a section label. | This field should not be edited. | |
numOfAttrs=XX | The number of attributes entry can be changed as long as it matches the number of attributes. | XX=Integer Value |
attrYY=Value | 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 = Integer Value Value = Notifyvoicenormal Notifyvoiceurgent Notifyfaxnormal Notifyfaxurgent Notifyemailnormal Notifyemailurgent |
ReferenceAttr= | 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 an SMSI signal on every message as defined by the attribute list. |
Posted: Mon Sep 25 19:44:38 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.