Avaya

Message Networking Help

Home | Search  
Print | Back | Fwd | Close
  
Getting Started Admin Maintenance Reference
Home > Getting Started > Message Networking concepts and features > Remote machines overview > Remote machine considerations > Unified Messenger SMTP/MIME remote machine considerations

Unified Messenger SMTP/MIME remote machine considerations

The following are considerations related to Unified Messenger SMTP/MIME remote machines.

There are several known considerations when using SMTP/MIME as the message delivery mechanism to Unified Messenger with Microsoft Exchange or Lotus Notes:

  • Voiced name: For Unified Messenger subscribers, the remote subscribers on the Message Networking system have a text-to-speech name rather than the self-recorded voiced name.
  • No blind addressing: When numerically addressing a Message Networking recipient, that recipient must be preadministered as a remote subscriber on the UM/Exchange or UM/Lotus Notes system.
  • Manual directory initialization: On Unified Messenger systems (with either Microsoft Exchange or Lotus Notes), SMTP/MIME provides the message transport between the Message Networking system and the Unified Messenger. However, SMTP/MIME does not inherently provide automatic subscriber directory updates. Message Networking requires the directory entries to perform a mapping between the unique numeric Network Address (often the phone number) and the email address of the Unified Messenger subscriber (for example, 303-555-1234 is [email protected]). In addition, each subscriber residing on a system supported one of the other protocols supported by Message Networking also has a unique numeric Network Address and an email address (for example, 303-555-6789 is [email protected]). The Unified Messenger application requires the directory entries to map between the numeric Network Address and the email address of the Message Networking recipient.

    Because the subscriber directory updates are not automatically provided, the directory entries that map a Network Address and ASCII name to a Message Networking email address must be manually populated. There is a manual process that you can use to extract the directory from Message Networking and import it into the Exchange or Lotus directory. The UM subscriber records on the Message Networking side must also be built manually using one of the following methods:
    1. Bulk Adding the Subscribers by File: Use FTP to import a file into the Message Networking system that contains the numeric network address and email address.
    2. Self-Registration: Have each UM subscriber self-register on the Message Networking system by sending a voice name as a message and the network address in the Subject field to a predefined self-registration mailbox.
    3. Subscriber Administration: Have a Message Networking administrator administer each UM subscriber on the Message Networking system using the administration interface.
  • No Directory Updates: On the UM for Exchange or UM for Lotus Notes system, there are no ongoing directory updates (ASCII name or voiced name). On the Message Networking system, only the ASCII name is updated.
  • Voice message is email (MS Exchange only): When a voice message is sent to a UM/Exchange system, it is treated as an email message (that is, a .wav file binary attachment) rather than a voice message.
  • 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.
    Unified Messenger, with either Microsoft Exchange or Lotus Notes, uses the GSM voice encoding format. The actual SMTP/MIME communication is between the Message Networking system and the message storage server (Microsoft Exchange or Lotus Domino).
  • Message Networking currently does not recognize faxes that are part of message replies or forwards because of the way that Lotus Notes designates this type of faxes and treats the faxes as binary attachments. Binary attachments are stripped on remote machines that do not handle binary attachments.

Top of page

Home | Search | Print | Back | Fwd | Close
©2006 Avaya Inc. All rights reserved.
Last modified 11 January, 2006