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 > Aria Digital and Serenade Digital remote machine considerations

Aria Digital and Serenade Digital remote machine considerations

The following are considerations related to Aria Digital and Serenade Digital remote machines:

  • Announcements cannot be customized.
  • For fax-only messages to Aria remote machines, the following voice component is added by the Message Networking system: "Your fax message is attached."
  • Octel 200/300 message servers support multiple voice components or segments within the same message. When this type of message is sent through Message Networking, the Message Networking system concatenates all voice segments into a single component.
  • Message Networking supports connectivity to a Serenade gateway when the gateway is part of an Octel 200/300 domain. Message Networking does not support a Serenade gateway when it is in a remote configuration where it is the interface for non-domain message servers:
    • A Serenade gateway in a domain configuration is an Octel 200/300 server designated as the gateway for the entire cluster of digital Octel 200/300 servers (domain). It is the only system networked to the Message Networking system within the entire domain and must be connected to all of the Octel 200/300 servers in the cluster (domain) digitally.
    • A Serenade gateway in a remote configuration is an Octel 200/300 server being used as a networking gateway for other messaging systems (connected using Octel Analog, etc.)
  • In Octel 250/350 environments with alias mailboxes, it is important to consider when defining the dial plan that Message Networking delivers networked messages to the actual mailbox ID, not the alias mailbox ID. Alias mailboxes are used in Octel 250/350 systems when the call coverage number for a mailbox does not necessarily match the actual mailbox ID.
  • An Octel 250/350 server that has been previously upgraded from an Aspen system and will now be used for digital networking requires that the subscribers on the system rerecord their spoken (voiced) names for the spoken name to be transmitted to the Message Networking system. In some cases, although the Octel 250/350 server was installed new, the subscriber directory was loaded from an older Aspen system. These systems must also rerecord the subscriber names. This is a limitation of the Octel 250/350 server and is not specific to Message Networking. Message Networking does not support Aspen systems. Aspen servers must first be upgraded to Octel 250/350 servers before networking to Message Networking (preferably using Aria TCP/IP).
  • For an Octel 250/350 message server to use digital networking with Message Networking, it must be Release 2.05 or later. This version allows administrators to set a flag automatically requesting subscribers in the upgraded system to rerecord their spoken names. It is recommended that this flag be set several weeks before the digital connection is made to the Message Networking system to "clean out" nonconforming names.
  • Due to an issue with how Aria Digital systems send out subscriber ASCII names, Octel 250/350 Release 3.0 is not supported for Message Networking. Customers with Octel 250/350 must upgrade their systems to Release 3.01.
  • The Aria Message Locator feature applies to Message Networking delivery.
  • Aria Digital subscribers with no recorded spoken name are sent to Message Networking upon the demand execution of an Aria NameSend. However, a new subscriber added to an Aria Digital system for whom a spoken name has not been recorded is not sent to Message Networking as an add until a spoken name is recorded.
  • Large messages to AUDIX from Aria and Serenade are failed with a message length failure message.
    Note: AUDIX LX supports voice messages of up to 180 minutes.
  • When Aria senders send a mixed private and/or priority message to multiple Serenade or VPIM V2 digital recipients on the same remote machine, the message is marked Priority and/or Private for all recipients, even if one recipient is marked as such. The sender is not notified that this has happened.
  • Reply/Forward Indicator is supported:
    • From Serenade Octel Analog Networking to all machine types
    • From Serenade Digital to Serenade Digital
  • Serenade Digital call processing features (for example, Immediate Call, Check for Unlistened Messages) are not supported.
  • When recipients of messages from Aria Digital and Serenade Digital 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.
  • Note the use of "notice" versus "message" for Aria and Serenade systems. Historically, notices were used to indicate message delivery failure. However, when messaging using the Message Networking:
    • "Message" indicates a failure.
    • "Notices" indicate a positive message confirmation.
  • One message for multiple recipients is supported; each recipient receives header information (private, priority, AND confirmation request).
  • Subscriber updates are supported as follows:
    • Automatic on add, change, and delete (no delete for Serenade Digital).
    • Automatic on message delivery to a recipient (updates recipient).
  • The transmission of a subscriber spoken name with a length of eight seconds or greater is not supported when using Octel 250/350 with Octel Analog Networking. This is supported for all other remote machine and protocol types, including Aria Digital TCP/IP.
  • Self-registration is not supported for Aria/Serenade Digital; NameSend is used instead.
  • The Octel serial number for Message Networking defaults to 80000 (range of 80000 to 81000 reserved).
  • A maximum of 1 outbound port per remote machine, rounded up, is supported.
  • The following features are not supported:
    • Multiple inbound simultaneous sessions from a given remote machine.
    • Multiple outbound simultaneous sessions to a given remote machine.
    • Network turnaround.
  • Sender's Name:
    • Octel messages, Aria Digital messages, and Serenade Digital messages to Message Networking need to be configured to exclude the Sender's Name Prefix.
    • Octel Analog Networking, Aria Digital, Serenade Digital, and AMIS recipients receive the sender's name by using Message Networking prefixing.
    • AUDIX recipients receive the sender's name from the message header.
  • In some Dial Plans, the Message Networking system needs to build back the complete address of the sender (including prefix) before transmitting to a Serenade Digital machine. For example, if the Serenade Digital machine attaches a prefix of 1 before the 10-digit network address to a recipient, then the Message Networking system must be configured to attach the same prefix of 1 before that sender's 10-digit network address when the recipient replies to the Serenade Digital machine. In this case, Message Networking supports creation of a Serenade Digital Sender Dial Plan.
  • Serenade Digital remote machines do not support analog fallback on outbound or inbound messages.
  • The 3/4 Rule is supported for Serenade Digital remote machines for inbound and outbound ports:
    • No more than 3/4 of all Serenade Digital ports can be used for outbound.
    • No more than 3/4 of all Serenade Digital ports can be used for inbound.
    • Numbers are rounded up.
    • No ports are reserved for inbound or outbound if ports total 1, 2, or 3.
  • 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:
    • For Octel 250/350 servers, reference a single bulletin broadcast mailbox per server in an Enterprise List. Using this method, only one message is sent to each server. After the message is deposited in the bulletin broadcast mailbox, the message is sent to everyone on the server with the bulletin broadcast class of service (with no MWI). Use of this feature might require an Administrator to add the bulletin broadcast class of service to the subscriber on the Octel 250/350 server.
    • For Octel 200/300 servers, an Enterprise List can be created that references an Octel 200/300 System Distribution List (SDL) consisting of all local subscribers. SDLs have the option (through parameter 145) to invoke MWI or not. This scenario significantly decreases network traffic load and reduces the effects of MWI.

 

Top of page

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