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 > INTUITY AUDIX remote machine considerations

INTUITY AUDIX remote machine considerations

The following are considerations related to INTUITY AUDIX remote machines:

  • Scheduled message status for INTUITY AUDIX indicates that delivery has not been successfully completed, nor has it failed yet.
  • Failed messages can exist in both incoming and outgoing mailboxes for INTUITY AUDIX.
  • Accessed status is consistent on both the Message Networking and INTUITY AUDIX systems.
  • Large messages to INTUITY AUDIX from Aria and Serenade are failed with a message length failure code. INTUITY AUDIX LX systems support a larger message length size than do INTUITY AUDIX Release 4 or 5 systems.
  • When recipients of messages from INTUITY AUDIX, DEFINITY ONE, and IP600 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.
  • DEFINITY ONE and IP600 work in the same manner as does INTUITY AUDIX; therefore, DEFINITY ONE and IP600 systems do not support receipt of future delivery messages sent from Aria systems.
  • When you want to send a message to all subscribers in an Enterprise using a single Enterprise List, the following suggestions can help to reduce network traffic load and the effects of MWIs:
    • Reference a single mailbox per server in an Enterprise List that has broadcast permission. Using this method, only one message is sent to each server. After the message is deposited in the subscriber’s mailbox (with broadcast permission), the subscriber can then forward the message to the rest of the subscribers on the server with or without MWI.
    • Enterprise Lists can be created that reference local INTUITY AUDIX ELA lists containing all local subscribers. This methods also cuts down on network traffic load. When using Enterprise Lists and INTUITY AUDIX ELA, make sure that a range defined on an Enterprise List does not include an ELA list (unless that is the desired effect). Additionally, be careful not to create a cycle by referencing an ELA list in an Enterprise List that references the same Enterprise List.
  • There is an issue that can occur when you have a distribution list on an INTUITY AUDIX system (a personal list or an ELA list) that references remote Message Networking network addresses, and the Directory View for that INTUITY AUDIX system is quite large (usually greater than 10,000 remote subscribers). In this scenario, it is possible for the referenced network addresses to be deleted from the local INTUITY AUDIX list when a directory synchronization problem occurs during a Demand Remote Update between the two systems. When the Directory View is quite large and takes longer for a full update, the chance of the directory synchronization being interrupted and having to restart is greater (for example, because an audit has started). In some cases, this restart causes the remote subscribers on the INTUITY AUDIX system (the Message Networking network addresses) to be reassigned a new internal subscriber identifier (an internal number, not a new external network address). It is this internal subscriber identifier that is stored when the local INTUITY AUDIX list is built and, as a result, impacts the list. If this problem occurs, it is recommended that you create Enterprise Lists on the Message Networking system for these network addresses.

Top of page

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