There are two ways to set up directory updates between multiple
Avaya Modular Messaging (MM) systems:
- Each MM system provides updates directly to the other MM systems
in the network (that is, without using Message Networking).
- Message Networking provides the updates to the MM systems in
the network (that is, in a hub-and-spoke topology).
There are considerations for each directory update option.
Option 1: MM systems provide the directory updates directly to
other MM systems
This is the most common option for setting up directory updates
between MM systems. In this scenario, each Modular Messaging system
provides directory updates directly to every other Modular Messaging
system in the network. Updates occur more quickly using this option,
but it requires more administration.
To configure the MM systems and the Message Networking system to
use this option, you must perform the following administration on
the MM systems and the Message Networking system:
- Administer each MM system as an LDAP Machine Type on the other
MM systems in the network.
- Administer each MM system as a remote machine on the Message
Networking system.
- On the Message Networking system, set the Subscriber
Update Type on the Remote Machine Parameters page to Full
for each MM system.
- Modify the Directory View for each MM remote machine on the
Message Networking system to delete
the other MM systems from the view. This will prevent both
the MM system and the Message Networking system from providing
the same directory updates.
- If there are two Message Networking systems in the network,
each Message Networking system is defined as a remote machine
on the other Message Networking system. In this case, you must
modify the Directory View of
the Message Networking remote machine on both Message Networking
systems to remove the range of addresses that represent the MM
subscribers.
Example
In the following example, there are two Modular Messaging systems,
named MM1 and MM2, and there is a single Message Networking system
in the network. To set up the Modular Messaging systems to provide
updates directly to each other, the following administration is
performed on each Modular Messaging system and on the Message Networking
system:
- MM1:
- Administer the MM2 system as an LDAP Machine Type on the
MM1 system.
- MM2:
- Administer the MM1 system as an LDAP Machine Type on the
MM2 system.
- Message Networking:
- Administer the MM1 and MM2 systems as Avaya Modular Messaging
remote machines on the Message Networking system.
- Verify that the Subscriber Update Type on the Remote Machine
Parameters page is set to Full for each of the Avaya Modular
Messaging remote machines.
- Modify the Directory View of the MM1 remote machine to delete
the MM2 remote machine.
- Modify the Directory View of the MM2 remote machine to delete
the MM1 remote machine.
Option 2: Message Networking provides the directory updates between
the MM systems
In this scenario, the Message Networking system provides the directory
updates between the Modular Messaging system. The advantage of this
option is that if you have many MM systems in your network, the
Message Networking system can simplify the update process and administration.
To configure the MM systems and the Message Networking system to
use this option, you must perform the following administration on
the MM systems and the Message Networking system:
- Administer each MM system as a remote machine on the Message
Networking system. Do not administer each MM system on the other
MM systems in the network. The MM systems would then only know
about the Message Networking system and not about each other.
- On the Message Networking system, set the Subscriber
Update Type on the Remote Machine Parameters page for each
MM system to Full.
Note: The Subscriber Name field, when sent from an MM system
to another MM system through a Message Networking system, will contain
a numeric Node ID value as assigned by the Message Networking system.
Example
In the following example, there are three sites. Each has multiple
Modular Messaging systems and each has a Message Networking system
(hub and spoke topology):
Site |
Modular Messaging systems |
Message Networking systems |
New York |
NY1 |
MN A |
|
NY2 |
|
|
NY3 |
|
Denver |
DV1 |
MN B |
|
DV2 |
|
|
DV3 |
|
|
DV4 |
|
Orlando |
OL1 |
MN C |
|
OL2 |
|
|
OL3 |
|
|
OL4 |
|
|
OL5 |
|
To set up Message Networking to provide the directory updates,
the following administration is performed for each site:
- New York:
- On the MN A system, administer NY1 through NY3 and and MN
B and MN C as remote machines.
- Verify that the Subscriber Update Type on the Remote Machine
Parameters page is set to Full for each of the Avaya Modular
Messaging remote machines.
- Denver:
- On the MN B system, administer DV1 through DV4 and MN A
and MN C as remote machines.
- Verify that the Subscriber Update Type on the Remote Machine
Parameters page is set to Full for each of the Avaya Modular
Messaging remote machines.
- Orlando:
- On the MN C system, administer OL1 through OL5 and MN A
and MN B as remote machines.
- Verify that the Subscriber Update Type on the Remote Machine
Parameters page is set to Full for each of the Avaya Modular
Messaging remote machines.
|