Message Networking Help

Home | Search
Print | Back | Fwd | Close

Home > Administration > Administering subscribers > Overview of adding and updating subscribers

Overview of adding and updating subscribers

This topic describes in general terms how Message Networking and its administered remote machines populate subscriber information on the Message Networking system and how the Message Networking system delivers this information to other remote machines.

Populating directories means adding, updating, or deleting subscribers in a messaging system database (directory). How each system performs these actions with the Message Networking system depends on the type of messaging system. How much and what kind of subscriber information is exchanged between remote machine and Message Networking also depends on the type of subscriber updates selected for that remote machine (full, directory view, or dynamic).

Important! There are considerations for configuring directory updates for Avaya Modular Messaging systems that you should be aware of before administering the MM systems on your network.

The following information is provided:

Notes:

When adding subscribers to the Message Networking system, do not attempt to add subscriber extensions beyond the range defined in the system's dial plan.
In addition to the methods listed in the following tables, you can also administer Message Networking subscribers via the system's secure LDAP interface.

Adding subscribers

When a new remote machine is added to the Message Networking network, Message Networking either pulls the new subscriber information from the remote machine or the new subscriber information is pushed to the Message Networking system from the remote machine (for AUDIX TCP/IP, Aria TCP/IP, Serenade TCP/IP, and Modular Messaging with an MSS through LDAP). Once the subscriber information is retrieved from a remote machine, that subscriber information can then be propagated to the other remote machines administered on the Message Networking system.

For those systems that cannot automatically send their subscriber directories, Message Networking supports the following methods of adding subscribers to the Message Networking directory, in the recommended order of priority. Whether information is pulled or pushed depends on the remote machine involved in the messaging exchange:

LDAP-based: LDAP is used to exchange subscriber information with Modular Messaging systems. Message Networking also supports a secure LDAP interface that allows third-party application access for administering subscribers.
Bulk subscriber administration by file: Subscribers can be added using FTP.
Self-registration: Subscribers can self-register by sending a voice message (consisting of the subscriber's voiced name) to the administrator-defined self registration ID network address.
Sending a message through Message Networking: Subscribers who send messages through Message Networking are automatically added to the Message Networking directory.
Subscriber Parameters Administration: Subscribers can be manually added through the Message Networking Subscriber Parameters Administration page (not supported for Modular Messaging remote machines).
Bulk subscriber administration by range: Subscribers can be added using the Message Networking Add Subscribers from Range page.

The following table describes how new remote machine subscribers are added to the Message Networking system.

New node	What to do
AUDIX (DEFINITY ONE Release 2.0, INTUITY AUDIX Release 4.0 or later, IP600 9.2.1, INTUITY AUDIX LX, and Interchange Release 5.4)	Message Networking administrator uses Demand Remote Update.
AMIS	Use one of the following methods: Initiate bulk add from the Message Networking system. Use self-registration to add subscribers' voiced names. Send a message from the new subscriber. Add via the administration page on the Message Networking system.
Octel Analog Networking	Use one of the following methods: Use self-registration. Prompt new Octel Analog Networking, Aria Analog, and Serenade Analog subscriber to send a message. Add via the administration page on the Message Networking system. LDAP (customer must write LDAP Client application). Initiate name pull from Message Networking.
Octel Analog Networking with Unified Messenger	Use the same methods as those of Octel Analog Networking nodes.
Aria Digital	Initiate NameSend from the Aria Digital.
Serenade Digital	Initiate NameSend from the Serenade Digital.
VPIM v2	Use one of the following methods: Use FTP to add subscribers. Initiate bulk add from the Message Networking system. Use self-registration to add subscribers' voiced names. Send a message from the new subscriber. Add via the administration page on the Message Networking system. LDAP (customer must write LDAP Client application).
SMTP/MIME (LDAP-based)	Use LDAP either dynamically or through a Demand Remote Update (Avaya Modular Messaging with an Avaya Message Store and Message Networking only).
SMTP/MIME (non-LDAP)	Use one of the following methods: Use self-registration to add subscribers' voiced names. Initiate bulk administration by file from the Message Networking system. Administer via the administration page. Initiate bulk administration by range (with email defaulting to Network Address @ Domain). LDAP (customer must write LDAP Client application).

Notes:

On UM for Lotus Notes Release 5.0 or later systems, remote subscribers must be administered as users on the Lotus Notes/Domino system. This allows subscribers on the local UM for Lotus Notes system to send TUI messages to remote subscribers via Message Networking.
On UM for Exchange systems, remote subscribers must be administered as users on the Exchange system. This allows subscribers on the local UM for Exchange system to send TUI messages to remote subscribers via Message Networking.

Updating subscribers

The following table describes how Message Networking updates remote machine and remote machines update Message Networking.

Protocol	When the remote machine updates MN	When MN updates the remote machine
AMIS	Adds and changes are not supported. When Message Networking attempts to deliver to a nonexistent subscriber on an AMIS remote machine, it fails the messages and deletes that subscriber from the Message Networking subscriber directory.	Updates are not supported.
AUDIX	When a subscriber is added, changed, or deleted through administration, Message Networking is automatically notified.	When Message Networking detects a subscriber add, change, or delete, it pushes an update to the AUDIX remote machine.
Octel Analog Networking	When Message Networking delivers a message to the remote machine, it performs an ASCII match on the recipient (if ASCII name check is set to yes). If the recipient mismatches, Message Networking fails the message and immediately requests a pull from the remote machine (when Updates In is set to yes on Message Networking and Updates Out is activated on the remote machine). If the ASCII name is a default on the Message Networking system, a comparison is not performed by Message Networking, the message is delivered, and the pull is immediately requested (when Updates In is set to yes on Message Networking and Updates Out is activated on the remote machine). If the subscriber does not exist on the remote machine but does exist on the Message Networking system, then the message is failed and Message Networking defaults the ASCII name and nulls the voice name of the subscriber. For any name pull to succeed, the remote machine must be set to Protocol Level 2 or 3.	When the remote machine delivers a message to Message Networking, it performs an ASCII name match on the recipient. If the recipient mismatches, the remote machine fails the message and deletes the subscriber entry. The next time a message is sent to that subscriber, the remote machine requests a pull from Message Networking. If the ASCII name is a default on Message Networking, Message Networking always accepts the message (it does not perform a name comparison), and the Message Networking system schedules the pull. If a subscriber does not exist on Message Networking and that subscriber sends a message through Message Networking, the Message Networking system adds the subscriber as a default and then a name pull is scheduled. Also, when Message Networking detects a subscriber add or a change (not a delete), Message Networking pushes out an update.
Aria Digital	When Message Networking delivers a message to the remote machine, it requests that the remote machine perform an ASCII match on the recipient. If the recipient mismatches, the remote machine fails the message and then Message Networking requests a pull from the remote machine. If the ASCII name is a default on the Message Networking system, a comparison is not requested, the message is delivered, and the pull is requested. If the subscriber does not exist on the remote machine but does exist on the Message Networking system, then the message is failed by the remote machine and the Message Networking system defaults the ASCII name and nulls the voice name of the subscriber. Also, Aria Digital can automatically push an add, change, or delete of a subscriber when the update occurs.	When the remote machine delivers a message to Message Networking, Message Networking performs an ASCII match on the recipient. If the recipient mismatches, Message Networking fails the message and the remote machine deletes the entry. The next time that a message is sent to the subscriber, the remote machine requests a pull from Message Networking. Also, when Message Networking detects an add, change, or delete of a subscriber, it pushes out an update.
Serenade Digital	When the Serenade Digital system delivers a message to Message Networking, it automatically pushes the sender's ASCII and spoken name (only when the spoken name exists). The Serenade Digital can automatically push an add or change (but not a delete) of a subscriber when the update occurs. When Message Networking delivers a message to the remote machine, it does an ASCII name match on the recipient (if ASCII name match is set to yes). If the recipient mismatches, Message Networking fails the message and defaults the ASCII name and nulls the spoken name. If the ASCII name is a default on Message Networking, a comparison is not performed and the message is delivered. If the subscriber does not exist on the remote machine but does on Message Networking, the message is failed and Message Networking defaults the ASCII name and nulls the spoken name of the subscriber.	When Message Networking delivers a message to the Serenade Digital system, it automatically pushes the sender's ASCII and spoken name (only done when a spoken name exists). When Message Networking detects a subscriber add or change (but not a delete), it pushes out the update. When the remote machine delivers a message to Message Networking, it performs an ASCII match on the recipient if addressed alphabetically. If the recipient mismatches, the Serenade system fails the message and deletes the entry.
VPIM v2	When a VPIM sender sends a message through Message Networking, that subscriber's record information is updated on Message Networking if the ASCII name/voice name has changed and the sending system supports this information.	When a Message Networking sender sends a message to a VPIM system, that subscriber's record information is updated on the receiving VPIM system is the ASCII name/voice name has changed and the receiving system supports this information.
SMTP/MIME (LDAP-based)	When a subscriber is added, changed, or deleted through administration, Message Networking is automatically notified.	When Message Networking detects a subscriber add, change, or delete, it pushes out an update.
SMTP/MIME (non-LDAP)	When an SMTP/MIME sender sends a message through Message Networking, that subscriber's record information is updated on Message Networking if the ASCII name (not voice name) has changed and the sending system supports this information.	When Message Networking sends a message to an SMTP/MIME system, that subscriber's record information is updated on the receiving SMTP/MIME system, if the ASCII name (not voice name) has changed and the receiving system supports this information.

Populating subscriber information

If callers do not receive the recipient's voiced name or if they cannot use Dial-by-name, then the recipient subscriber may or may not be available on the Message Networking system. The following tables explain what actions can be taken to populate subscriber information on the Message Networking system and to transfer subscriber information from the Message Networking system to the remote machine requesting the update.

The outcomes of these actions depend on proper configuration of both the Message Networking system and the remote machines.

The following table describes the actions that can be taken to populate subscriber information on the Message Networking system.

Remote machine type	Action
AUDIX	Initiate Demand Remote Update from the Message Networking system to the AUDIX end node.
AMIS	Recipient needs to self-register for Dial-by-name; system administrator must manually add the ASCII name on the Message Networking system.
Octel Analog Networking	Initiate demand remote update from the Message Networking system to the Octel Analog Networking end node. Use bulk add utility where appropriate.
Octel Analog Networking with Unified Messenger	Same as Octel Analog Networking.
Aria Digital	From the Aria Digital node, use NameSend to push the subscriber name to the Message Networking system.
Serenade Digital	From the Serenade Digital node, use NameSend to push the subscriber name to the Message Networking system.
VPIM v2	Use one of the following methods: Use bulk add utility where appropriate. Enter subscriber information using the administration screens. Recipient can self-register. Have VPIM subscriber send a message.
SMTP/MIME	Use one of the following methods: Use bulk add utility where appropriate. Enter subscriber information using the administration screens. Recipient can self-register. Initiate Demand Remote Update from the Message Networking system to the SMTP/MIME end node (LDAP-based only).

The following table describes how subscriber information is populated from the Message Networking system to a remote machine.

Remote Machine	Action
AUDIX	Initiate delta update to the Message Networking system.
AMIS	System administrator must administer subscriber information locally.
Octel Analog Networking	From any mailbox on the Octel Analog Networking node (where the subscriber information is not available), send a message to that address using digit addressing.
Octel Analog Networking with Unified Messenger	Same as Octel Analog Networking.
Aria Digital	From any mailbox on the Aria Digital node (where the subscriber information is not available), send a message to that address using digit addressing.
Serenade Digital	The new subscriber (whose information is missing) must address a message to any mailbox on the system missing that subscriber information.
VPIM v2	Send a message through the Message Networking system to the VPIM machine; sender information on the VPIM machine is updated, if the VPIM machine stores and automatically updates subscriber information.
SMTP/MIME (LDAP-based)	Initiate delta update to the Message Networking system.
SMTP/MIME (non-LDAP)	Send a message through the Message Networking system to the SMTP/MIME machine; sender information on the SMTP/MIME machine is updated, if the SMTP/MIME machine stores and automatically updates subscriber information.

Top of page