|
The following are considerations related to Modular Messaging remote
machines.
General Modular Messaging/MSS considerations
The following are general Modular Messaging/Avaya Message Store (MSS) system considerations:
-
LDAP updates (between Modular Messaging and
Message Networking systems and between multiple Message Networking systems)
can impact system performance, including delay of administration
page displays and report results. Note that while the LDAP update
is in progress between the two systems, messages are not transmitted
between them. The length of time to complete an LDAP update
depends on:
- The type of Modular Messaging system (Standard or High Availability)
- The number of MASs in the system
- The size of the system's database
- The number of subscribers to be updated and the voice name
message lengths
- The number of updates occurring at the same time (multiple
updates running slow the update rate)
It is recommended that remote updates of more than approximately
4,000 subscribers with voiced names be scheduled during non-prime-time
hours, and that remote updates of 50,000 subscribers or more
be scheduled over a weekend.
For Modular Messaging system updates, Standard Availability
systems and systems with multiple MASs will take longer to update.
The following numbers are provided to help estimate the total
time required for a remote update. The update rate on a Standard
Availability system with one MAS is approximately 4,000 subscribers
updated per hour. The update rate on a High Availability system
with one MAS is approximately 9,000 subscribers updated per
hour.
For Message Networking to Message Networking updates, the update
rate for the S3210 server is from 5,000 to 7,000 subscribers
updated per hour. For Message Networking to Message Networking
updates, the update rate for the S3400-H server is from 14,000
to 15,000 subscribers updated per hour.
- When administering multiple Modular Messaging systems in a network,
there are two scenarios for directory updates:
- Each Modular Messaging system provides updates directly to
the other Modular Messaging systems in the network.
- Message Networking provides the updates to the Modular Messaging
systems in the network.
There are considerations for
each scenario that you must be aware of before administering the
Modular Messaging systems.
- Modular Messaging systems do 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.
- When setting up an email client such as Outlook Express for
use with Avaya Modular Networking, you must provide an email address
for each subscriber. There are two ways that you can specify email
addresses on the Avaya Modular Networking system:
- Mailbox number (which is also used in the Account Name field
in the Outlook Express administration setup) combined with the
domain of the Avaya Modular Networking (for example, [email protected]).
- ASCII name email address (for example, [email protected]).
However, to send messages from an Avaya Modular Networking mailbox
through Message Networking, the subscriber's email address in
Outlook Express must match the subscriber's ASCII name email address.
- Replies to messages originating from an Avaya Modular Messaging
system Enhanced List Application are not supported when the message
is passed through a Message Networking system. The only way for
the recipient to reply to the sender is to forward the message
back to the originator.
Note: This consideration is not related to the reply-all
feature of Message Networking's Enterprise List application,
supported on the S3400-H server, which does support reply-all
regardless of the sender or originator type.
- Avaya Modular Messaging supports a reply-all capability when
are exchanged between Modular Messaging subscribers. However,
the reply-all capability is not supported for messages originating
from non-Modular-Messaging senders that are passed through Message
Networking.
Note: This consideration is not related to the reply-all
feature of Message Networking's Enterprise List application,
supported on the S3400-H server, which does support reply-all
regardless of the sender or originator type.
- Avaya Modular Messaging Release 1 and 2 systems do not support private message marking
when sending or receiving a networked message. This is important
to note as a recipient can forward private messages sent from
Message Networking to a another recipient. Priority message markings
are supported.
- The length of the Numeric Address for a Modular Messaging subscriber
cannot be the same length as the Mailbox ID value for a subscriber
when those subscribers are in the same Voice Mail Domain. The
numeric Network Address value can, however, be the same length.
This is important to note when the customer is planning the numeric
dial plan for the network.
- Modular Messaging allows a recipient of a message to call the
sender of a networked message. The dial plan to call the sender
must match the sender value used when the message is delivered.
It is important to plan for the Mailbox ID length, Numeric Address
length, and Network Address length when designing a network that
involves Modular Messaging and Message Networking.
-
With the Reply to Call Answer Message feature in Modular Messaging,
a recipient of a call answer message can reply back to the caller
using Message Networking only when both the caller and recipient
are in the same Voice Mail Domain.
Modular Messaging/MSS using SMTP/MIME
There are several considerations when using SMTP/MIME as the message
delivery mechanism to Modular Messaging with an Avaya Message Storage
Server (MSS):
Considerations using Octel Analog Networking with Modular Messaging/Exchange
The following considerations are specific to Modular Messaging
with Exchange systems using Octel Analog Networking.
Modular Messaging with Exchange Directory Updates using Octel
Analog Networking
Modular Messaging/Exchange uses Microsoft Exchange's directory.
As a result, there are certain limitations relative to the updates
of the remote subscriber directory stored on the Modular Messaging
system. These limitations include:
- Message Networking can pull updates from Modular Messaging/Exchange systems for administered local subscribers. See the Avaya Modular Messaging for Microsoft Exchange Installation for information on administering local subscribers on Modular Messaging/Exchange systems.
- Modular Messaging/Exchange does not execute a pull/update for
non-existent remote subscribers. All remote subscribers must be
preadministered as a Custom Recipient Record on the Modular Messaging/Exchange
system for Modular Messaging/Exchange software to execute a pull/update.
Only the spoken name from the Message Networking solution is added
to this record when a Modular Messaging/Exchange originator sends
a message to the Custom Recipient and the recipient has a recorded
name on the Message Networking solution.
- Modular Messaging/Exchange does not support the concept of ASCII
name mismatch for updating its directory (this feature is used
by other Octel� Analog Networking systems). No updates, other
than the first population of the spoken name in the Custom Recipient
Record, are performed.
- No subscriber pushes/updates are accepted from Message Networking.
- All remote subscriber entries are permanent (versus usage-based)
on the Modular Messaging/Exchange solution.
These are directory limitations of Modular Messaging/Exchange and
not the Message Networking implementation of Octel Analog Networking.
Component types such as text and binary are not supported
in Modular Messaging/Exchange using Octel Analog Networking as a
transport. Modular Messaging/Exchange systems require a separate fax server to support fax components
Modular Messaging with Exchange Directory Updates using Octel
Analog Networking for Message Delivery
Modular Messaging/Exchange uses Microsoft Exchange's directory,
and, as a result, has certain limitations relative to the updates
of the remote subscriber directory stored on the Modular Messaging/Exchange
system. These limitations include:
- The Modular Messaging/Exchange solution does not execute a pull/update
for remote subscribers. All remote subscribers must be preadministered
as a Custom Recipient Record on the Modular Messaging/Exchange
system.
- When a Modular Messaging/Exchange sender sends a message through
the Message Networking solution, the Message Networking solution
will update the sender's ASCII name in its directory if it has
changed from the current ASCII name for that subscriber.
- All remote subscriber entries are permanent (versus usage-based)
on the Modular Messaging/Exchange solution.
Private messages
Modular Messaging/Exchange does not support private message marking
using Octel Analog Networking. This is important to note as the
recipient can forward private messages sent from Message Networking
to a Modular Messaging with Exchange Directory Updates using Octel
Analog Networking for Message Delivery/Exchange recipient. Priority
message markings are supported.
Top of page
|
