|
|
uOne interfaces with the messaging server using IMAP and SMTP protocols. The primary use of the messaging server is to store subscriber messages. It is also used for some administrative functions including: storing subscriber personal greetings and distribution list recorded names, temporarily storing faxes to be printed, temporarily storing messages which cause SMS notifications, and temporarily storing outbound AMIS-A messages. Administration of the messaging server is accomplished through vendor-supplied tools and Cisco Web-based tools. Cisco tools include:
uOne provides two plug-ins for Netscape Messaging Server.
 |
Note To allow notification with other vendors' messaging servers, some customization or extension may be necessary. |
The following information will be required when administering uOne. You should document this for every messaging server.
| What | Description | Where to find it1 |
|---|---|---|
Host name of Messaging Server | The fully qualified domain name of the server. |
|
| 1Assumes use of a UNIX-like operating system. |
uOne supports optional outbound Simplified Message Station Interface (SMSI) for MWI message arrival notification. Throughout these manuals, the terms SMDI, Simplified Message Desk Interface, and SMSI will be used interchangeably.
uOne supports the Bellcore (Telcordia) specification TR-NWT-000283 SMDI, Generic Performance Requirements and Generic Requirements. Instead of using inbound SMSI, uOne obtains inbound call data (e.g., ANI, DNIS, RDNIS, and CallType) via the H.225.0 SETUP.
|
Note This is required only if you implement MWI or pager notification services. |
There are four components to notification services:
| Cisco Software | Where is it located? |
|---|---|
Notification Server | |
Notification Server | |
Messaging Server | |
Messaging Server |
For MWI/pager notification services to work, you must administer all four components. This section will cover installing MWI_Plugin.so and MWI_Passoff. For more information on administering these, see the uOne Administration Manual.
Before you begin installation of the MWI/pager notification services software, the Netscape Messaging Server should be installed and configured properly.
To install the software from the CD-ROM:
Step 2 Insert the CD into the CD-ROM drive on your machine.
Step 3 Open a terminal window.
Step 4 Become superuser.
Step 5 cd /cdrom/uone_42xs
Step 6 Type ls at the command line to list the files in the current directory. The following should be available—
Step 7 Run the installation script according to the instructions in the "Installation Script" section in Chapter 5 of the uOne Gateserver Installation and Configuration Manual.
Step 2 After these have been downloaded, issue the following command on the appropriate uone-421s-<product>-solaris26.pkg.Z file(s) to get them into a usable format.
Step 3 Run the installation script according to the instructions in the "Installation Script" section in Chapter 5 of the uOne Gateserver Installation and Configuration Manual.
Step 2 Restart Netscape Messaging Server.
|
Note The installation script installs the MWI plug-in (/opt/local/lib/MWI_PlugIn.so)into the proper location. |
Select the Edit button, and fill out the plug-in information.
Make the following entries:
Entry: PostSmtpAccept
Path: /opt/local/lib/MWI_PlugIn.so
Functions: mwi_notify
Init: mwi_init
Options:
|
Note Available options are provided in Table 4-3. |
Options | Description | Valid Values |
|---|---|---|
|
| |
|
| |
|
|
Step 2 Start MWI_PassOff, providing it with the MWI_Notify server name (Table 4-2):
Option | Description | Valid Values |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
To install the software from the CD-ROM:
Step 2 Insert the CD into the CD-ROM drive on your machine.
Step 3 Open a terminal window.
Step 4 Become superuser.
Step 5 cd /cdrom/uone_42xs
Step 6 Type ls at the command line to list the files in the current directory. The following should be available—
Step 7 Run the installation script according to the instructions in the "Installation Script" section in Chapter 5 of the uOne Gateserver Installation and Configuration Manual.
Step 2 After these have been downloaded, issue the following command on the appropriate uone-421s-<product>-solaris26.pkg.Z file(s) to get them into a usable format.
Step 3 Run the installation script according to the instructions in the "Installation Script" section in Chapter 5 of the uOne Gateserver Installation and Configuration Manual.
Step 2 Restart Netscape Messaging Server.
Expand the Services tree until you get to the SMTP plug-ins and select the plug-ins node.
|
Note The installation script installs the SMS plug-in (/opt/local/lib/notify.so)into the proper location. |
Select the Edit button, and fill out the plug-in information.
Make the following entries:
Entry: PostSmtpAccept
Path: /opt/local/lib/notify.so
Functions: notify
Init: notify_init
Options: NotifyAddress=<notifier@yourdomain>
|
Note Ensure that the < > brackets are included in the Options field entry. In this special case, they are not used as a non-literal notation. |
The following table (Table 4-5) introduces various configuration requirements for the messaging server
.
The "Search for custom domain" feature of Netscape Messaging Server should be enabled if using AMIS-A Out. It is located in the Netscape Messaging Server console on the "Configuration" tab within the SMTP category in the "Address" tab. | |||
To optimize disk storage utilization for broadcast messages, the single copy message store feature of Netscape Messaging Server should be used. According to Netscape Messaging Server documentation, server performance is degraded somewhat in exchange for optimized disk storage utilization. The single copy message store feature deletes the single copy of the message automatically when all references to it are deleted.
| |||
Directory Enabled | If possible, the messaging server should be "directory enabled"; i.e., it should use your directory server(s) to track profile information on subscribers. | ||
Distribution List | See Example 4-5 for the proper SMTP configuration. This will ensure that when a subscriber has been deleted from a distribution list, the message is still accepted by the messaging server.
|
To support a large number of simultaneous IMAP or SMTP protocol sessions, it may be necessary to increase messaging server or operating system configurable parameters that govern the maximum number of:
|
Note On some operating systems (e.g., IRIX), disk block buffer cache and semaphores may need modifications for optimum performance. |
The following table (Table 4-6) provides a formula for calculating IMAP sessions:
IMAP sessions per messaging server | The maximum simultaneous IMAP sessions per messaging server equals: (2 x maximum possible number of uOne processes that can be running at a time) + (expected number of simultaneous e-mail client sessions) + (number of FaxPrint and amisaout processes)
|
Posted: Mon Sep 25 20:44:34 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.