|
This topic describes in general terms how Message Networking and
its administered remote machines (nodes) 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, or node. How much and what kind of subscriber
information is exchanged between nodes and Message Networking also
depends on how each messaging system's Directory View is configured
(full, static, or dynamic).
The following information is provided:
Note: 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.
Adding subscribers
When a new node is added to the messaging network, Message Networking
either pulls the new subscriber information or the new subscriber
information is pushed to the Message Networking system. Once the
subscriber information is retrieved from a node, it is available
to the other remote machines administered on the Message Networking
system.
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
particular nodes involved in the messaging exchange:
- LDAP-based: Subscribers may be added through an open
LDAP session. This may occur automatically as subscribers are
added on the remote system or by executing a manual pull command
requesting the new subscribers.
- Bulk subscriber administration by file: Subscribers can
be added by importing an FTP file that includes the subscribers
to be added.
- 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 Avaya MM 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 node subscribers add their
information 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.
- Register through the administration page on the Message
Networking system.
|
| Octel Analog Networking |
Use one of the following methods:
- Initiate name pull from Message Networking.
- Use self-registration.
- Prompt new Octel Analog Networking, Aria Analog, and Serenade
Analog subscribers to send a message.
- Register through the administration screen.
|
| 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.
- Register through the administration page.
|
| SMTP/MIME (LDAP-based) |
- Use LDAP either dynamically in an open LDAP session or
manually through a Demand Remote Update (Avaya MM and Message
Networking only).
|
| SMTP/MIME (non-LDAP) |
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.
- Register through the administration page.
|
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.
Populating new subscribers to preexisting
nodes
New subscribers are populated to preexisting nodes after the subscribers
are added to the Message Networking system. The following table
describes how the new subscribers are added to each remote machine
type.
| Remote machine type |
Population method |
| AUDIX |
Message Networking automatically sends information to remote
machines. |
| AMIS |
N/A |
| Octel Analog Networking |
Message Networking automatically sends information to remote
machines. |
| Octel Analog Networking with Unified Messenger |
N/A |
| Octel 100 |
Message Networking automatically sends information to remote
machines. |
| Aria Digital |
Message Networking automatically sends information to remote
machines. |
| Serenade Digital |
Message Networking automatically sends information to remote
machines. |
| VPIM v2 |
When a message is sent to the VPIM system. |
| SMTP/MIME (LDAP-based) |
Message Networking automatically sends information to remote
machines. |
| SMTP/MIME (non-LDAP) |
Message Networking sends the ASCII name and email address
of the sender on an outbound message. |
If dynamic views are set up, sending messages to and from the end
node updates the remote subscribers on the end node.
Updating subscribers
The following table describes how subscriber updates are propagated
to Message Networking depending on the remote machine type.
| Remote machine type |
Actions propagated (A=add, M=modify, D=delete) |
Update method |
| AUDIX |
A, M, D |
New information is provided to the Message Networking system.
|
| AMIS |
None |
N/A |
| Octel Analog Networking |
A, M |
New information is provided to the Message Networking system;
deletes are not propagated. |
| Octel Analog Networking with Unified Messenger |
A |
Default subscriber records are updated only the first time.
|
| Aria Digital |
A, M, D |
New information is provided to the Message Networking system.
|
| Serenade Digital |
A, M |
New information is provided to the Message Networking system;
deletes are not propagated. |
| VPIM v2 |
A, M |
Subscriber information (ASCII name and voice name, if the
sending VPIM remote machine sends the voice name) is provided
to the Message Networking system when an inbound message is
received. |
| SMTP/MIME (LDAP-based) |
A, M, D |
New information is provided to the Message Networking system.
|
| SMTP/MIME (non-LDAP) |
A, M |
Subscriber information (ASCII name and email address) is provided
to the Message Networking system when an inbound message is
received. |
Once subscriber information is updated on a remote machine and
on the Message Networking system, Message Networking transmits that
information to other end nodes as described in the following table.
| Remote machine type |
Transmittal method of updated information |
| AUDIX |
Updated subscriber information is automatically sent from
the Message Networking system. |
| AMIS |
N/A |
| Octel Analog Networking |
Updated subscriber information is automatically sent from
the Message Networking system. See note. |
| Aria Digital |
Updated subscriber information is automatically sent from
the Message Networking system. |
| Serenade Digital |
Updated subscriber information is automatically sent from
the Message Networking system. |
| VPIM v2 |
When a message is sent to the VPIM system. |
| SMTP/MIME (LDAP-based) |
Updated subscriber information is automatically sent from
the Message Networking system. |
| SMTP/MIME (non-LDAP) |
Message Networking sends the ASCII name and email address
of the sender on an outbound message. |
Note: Except for Unified Messenger and Octel 100.
Updating the Message Networking system
and other remote machines
The following tables describe what happens as a message is sent
from an updated subscriber on an originating node and how Message
Networking propagates that information to other nodes.
| Originating remote machine |
Flow |
| AUDIX |
- The originator can use Dial-by-name if the recipient
subscriber information exists on the originator's node;
otherwise, originator must dial by number.
- If the recipient subscriber's information is not available,
the originating node pulls the information from the Message
Networking system. The originator is then allowed to send
a message.
(In AUDIX, directories and messages are independent.) |
| AMIS |
- No ASCII names verification.
- Message is accepted by the Message Networking system.
|
| Octel Analog Networking |
- The originator can use Dial-by-name if the recipient
subscriber information exists on the originator's node.
The originator is also provided with Name Confirmation in
that case.
- If the recipient subscriber's information is not available,
the originating node pulls the information from the Message
Networking system. Now a message can be sent by name.
- The recipient's ASCII name is checked:
- If the name matches, Message Networking accepts the
message.
- If the Message Networking system has a default name
for the recipient, it accepts the message. In that case,
it then pulls the recipient name information if the
recipient is on an Octel Analog Networking or an Aria
Digital node.
- If the ASCII name does not match, the node removes
the recipient's information from its remote subscriber
database. Subsequent addressing to this recipient initiates
a name pull from the Message Networking system.
|
| Octel Analog Networking with Unified Messenger
|
Same as Octel Analog Networking, except:
- If the extension is found, but the ASCII name does not
match, the message is still delivered, regardless of whether
the recipient name is correct. This can happen when an extension
is reused after the previous subscriber leaves the company
and the extension ASCII name is changed.
|
| Aria Digital |
Same as Octel Analog Networking. |
| Serenade Digital |
- The originator can use Dial-by-name if the recipient
subscriber information exists on the originator's node.
The originator is also provided with Name Confirmation in
that case.
- If the recipient subscriber information is not available,
it is added to the originating end node when:
- The recipient sends a message to a subscriber on
this system.
- Depending on the Directory View mode (full, static,
or dynamic), if the Message Networking system propagates
an update it received for the recipient subscriber,
the originator is allowed to send a message.
- The Message Networking system is given the originating
subscriber's name information. If either the voiced or ASCII
name differs on the Message Networking system, the originating
subscriber information on the Message Networking system
is updated. All nodes on the Message Networking system are
provided with this updated subscriber information.
- The recipient's ASCII name is checked:
- If the name matches, the Message Networking system
accepts the message.
- If the Message Networking system has a default name
for the recipient, it accepts the message. In that case,
it pulls the recipient name information if the recipient
is on an Octel Analog Networking or an Aria Digital
node.
- If the ASCII name does not match, the node removes
the recipient's information from its remote subscriber
database. Subsequent addressing to this recipient initiates
a name pull from the Avaya Message Networking system.
|
| VPIM v2 |
- The VPIM sender's ASCII name is updated on the Message
Networking system.
- The VPIM sender's voiced name (if populated in the inbound
VPIM envelope) is updated on the Message Networking system.
|
| SMTP/MIME (LDAP-based) |
- The originator can use Dial-by-name if the recipient
subscriber information exists on the originator's node;
otherwise, originator must dial by number.
- If the recipient subscriber's information is not available,
the originating node pulls the information from the Message
Networking system. The originator is then allowed to send
a message.
|
| SMTP/MIME (non-LDAP) |
The SMTP/MIME sender's ASCII name and email address are
updated on the Message Networking system.
|
The following table describes what happens as the message is delivered
from the Message Networking system to a destination node.
| Remote machine type |
Flow |
| AUDIX |
- If dynamic, sender is pushed on to receiving system.
- Message is delivered if recipient exists on the destination
node.
|
| AMIS |
- No ASCII name verification.
- Message is delivered if recipient exists on the destination
node.
|
| Octel Analog Networking |
- If the Message Networking system has a default name for
the recipient, it does not perform an ASCII name check.
It does, however, deliver the message.
- If the Message Networking system has an ASCII name for
the recipient, it performs name verification:
- If the name matches, the message is delivered.
- If the name does not match or the recipient subscriber
does not exist, message delivery fails, and the message
is returned. The Message Networking system removes the
voiced name, and the ASCII name becomes the default.
Other end nodes are provided with this update. New information
about this subscriber is updated as described previously
in the message flow.
|
| Octel Analog Networking with Unified
Messenger |
Same as Octel Analog Networking,
except:
- If the extension is found, but the ASCII name does not
match, the message is still delivered, regardless of whether
the recipient name is correct. This can happen when an extension
is reused after the previous subscriber leaves the company
and the extension ASCII name is changed.
|
| Aria Digital |
Same as Octel Analog Networking.
|
| Serenade Digital |
- If the Message Networking system has a default name for
the recipient, it does not perform an ASCII name check.
It does, however, deliver the message.
- If the Message Networking system has an ASCII name for
the recipient, it does perform name verification:
- If the name matches, the message is delivered.
- If the name does not match or the recipient subscriber
does not exist, message delivery fails, and the message
is returned. The Message Networking system removes the
voiced name and the ASCII name becomes the default.
Other end nodes are provided with this update. New information
about this subscriber is updated as described in the
message flow.
- The Message Networking system gives the originating subscriber
information to the destination node. The destination node
updates its remote subscriber database accordingly.
|
| VPIM v2 |
The Message Networking system sends the sender's ASCII and
voiced names in the envelope to be updated on the VPIM v2
machine.
What each remote VPIM system does with the voiced name depends
upon the individual VPIM vendor.
|
| SMTP/MIME (LDAP-based) |
- Message is delivered if recipient exists on the destination
node.
|
| SMTP/MIME (non-LDAP) |
The Message Networking system sends the ASCII name and email
address to be updated.
|
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
|
