|
The following are notes and considerations related to Unified Messenger
remote machines:
- On Message Networking, networking is provided through:
- Octel Analog or SMTP/MIME for Unified Messenger for Exchange
Release 4.0 and 5.0.
- SMTP/MIME for Unified Messenger for Lotus Notes Release
5.0.
- The Microsoft Exchange Directory is used for data storage of
directory updates for Unified Messenger analog remote machines.
As a result of using the Microsoft Exchange Directory, there are
limitations on the updates of the remote subscriber directory
stored on the UM system:
- UM does not execute a pull/update for nonexistent remote
subscribers. Each remote subscriber must be preadministered
as a Custom Recipient Record on the UM system for the UM system
to execute a pull/update. Only the spoken name from the Message
Networking system is added to the Custom Recipient Record
when a UM originator sends a message to the recipient and
the recipient has a recorded name for Octel Analog on the
Message Networking system.
- The Unified Messenger directory will not accept a push from
the Message Networking system.
- All remote subscriber entries are permanent (versus usage-based)
on the UM.
- UM does not support the concept of ASCII name mismatch for
updating its directory. No updates, other than the first population
of the spoken name in the Custom Recipient Record, are performed.
- For Unified Messenger remote machines using SMTP/MIME, there
are limitations related to the remote subscriber directory updates
stored on the UM system:
- UM does not execute a pull/update for nonexistent remote
subscribers. Each remote subscriber must be preadministered
as a Custom Recipient Record on the UM system for the UM system
to execute a pull/update.
- When a UM sender sends a message through Message Networking,
the Message Networking system updates 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 UM.
- When a voice message is sent to a UM using Microsoft Exchange,
the voice message is treated as an email message (a .wav file
binary attachment) rather than a voice message.
- Only voice components are sent to a Unified Messenger user's
mailbox. Faxes are dropped, and receivers hear a voice message
asking them to contact the sender (Octel Analog Networking only).
- To use spoken name confirmation for messages sent from Unified
Messenger through the Message Networking gateway, a custom recipient with an
Octel Analog Networking address type is required for each Message Networking
user in the Exchange directory.
- When recipients of messages from Unified Messenger systems are
notified that one or more components of a multimedia message cannot
be delivered, the sender is not notified. The recipient is notified
to contact the sender for missing components.
- UM does not support private message marking using Octel Analog.
This is important to note as the recipient can forward private
messages sent from Message Networking to a UM recipient.
Top of page
|
