|
This topic provides an overview of subscriber directory updates
to Message Networking remote machines.
The directory update type determines the Message Networking subscribers
that are populated to a new remote machine and included in updates
to a remote machine. You specify the type of directory updates in
the Subscriber Updates Type field on the Remote Machine Parameters
page for a specific remote machine.
Note: How subscribers are populated to new remote
machines and how updates are initiated to remote machines depends
on the remote machine type. See the Adding
and updating subscribers overview for additional information
about how subscribers are added and updated on Message Networking
remote machines.
Message Networking supports the following types of directory updates:
Full updates. Full updates include every subscriber on every
system in the Message Networking network. This option ensures that
subscribers on the new system can address by name every subscriber
in the network. However, this option can require a large amount
of disk space on the new system. Also, remote subscribers who do
not send or receive messages will be stored unnecessarily. To specify
full updates for a remote machine, select full
as the Subscriber Updates Type on the Remote Machine Parameters
page.
If you select full updates, Message Networking performs a full
update when you first administer the new system and run a Demand
Remote Push to the new system. Subsequent updates occur in either
of the following circumstances:
- When you perform a Demand Remote Push for the remote machine.
- When Message Networking receives a subscriber change from a
remote machine.
Caution! If you begin with full updates or later change
to dynamic updates, Message Networking removes all subscribers from
the remote subscriber directory and begins to repopulate the directory
with dynamic updates.
Dynamic updates. With this update option, each time a subscriber
on the new system sends a message to a remote subscriber, that remote
subscriber is added to the Dynamic Directory List for the new system.
Likewise, each time a remote subscriber sends a message to a subscriber
on the new system, that remote subscriber is added to the list.
To specify dynamic updates for a remote machine, select dynamic
as the Subscriber Updates Type on the Remote Machine Parameters
page.
If, typically within the next 90 days (as set on the Dynamic Sub
Expiration Days on the General Parameters page), no other messages
are sent from the new system to that remote subscriber or vice versa,
that remote subscriber is removed from the list. This removal helps
save storage space on the new system.
Directory View updates only. With this option, the new system's
remote subscriber list includes subscribers within ranges of extensions
on the systems you specify. A Directory View list for a system is
static and, as with full updates, this option can use a lot of disk
space. Additionally, with this option, subscribers who fall outside
of the ranges and systems you specify are not addressable by name
from the new system. To specify directory view updates for a remote
machine, select directory-view as the Subscriber
Updates Type on the Remote Machine Parameters page.
If you select directory view updates, Message Networking performs
a Directory View update when you first administer the new system
and run a Demand Remote Push to the new system. Subsequent updates
include changes to subscriber lists of remote systems, where subscribers
are added or removed. Subsequent updates occur in either of the
following ways:
- When you perform a Demand Remote Push for this system
- When Message Networking receives a subscriber change from a
remote system.
Combination of dynamic and Directory View updates. You can
use dynamic and Directory View updates in combination. In this case,
dynamic updates occur as described above, but the Directory Views
option also identifies specific ranges of extensions on specific
remote machines to ensure that remote subscribers on those systems
can be addressed by name on the new system. To specify this combination
for a remote machine, select directory-view as
the Subscriber Updates Type on the Remote Machine Parameters page
and then add a directory a view for
the remote machine.
This type of setup is useful when you are converting a high-traffic
point-to-point system to the Message Networking network or when
it is important that all or a subset of remote subscribers on a
specific system are addressable by name for subscribers on the new
system.
The following table provides a comparison of the network directory
update types supported for each type of remote machine. The directory
update types listed are the Subscriber Update
|
Protocol Type |
Full |
Directory View |
Dynamic |
None |
|
AMIS |
No |
No |
No |
No |
|
AUDIX Digital (including DEFINITY ONE and IP600) |
Yes |
Yes |
Yes |
Yes |
|
Octel Analog Networking |
Yes |
Yes |
Yes |
Yes |
|
Aria Digital |
Yes |
Yes |
Yes |
Yes |
|
Serenade Digital |
Yes |
Yes |
Yes |
Yes |
|
VPIM |
No |
No |
Yes |
No |
| SMTP/MIME |
Recommended
for MM systems with an Avaya message Store and remote MN systems |
Yes (for MM/Avaya
Message Store)
|
SMTP/MIME
systems other than MM/Avaya Message Store and MN systems |
Yes (for MM/Avaya
Message Store) |
Note: Modular Messaging
systems will not accept more than 250,000 subscribers (with or without
voice names) during an update. Therefore, if the Message Networking
system has more than 250,000 subscribers, you must administer
the Modular Messaging remote machine to use directory view updates,
and the directory view you administer
for the Modular Messaging system must include no more than 250,000
subscribers.
Top of page
|
