Octel Analog Networking remote machine considerations

General considerations

The following general considerations are related to Octel Analog Networking remote machines:

Reply to sender of analog messages is supported.

Playback of name during message addressing and directory searches for registered subscribers (for those sending from AUDIX, Aria, or Serenade, not AMIS) are supported.

Automatic directory updates are supported.
Note: Subscribers are updated on the Message Networking system from the Unified Messenger directory only if a default record for the subscriber exists in the Message Networking directory. For more information about creating default records, contact the Professional Services Organization (PSO).

Voice name in messages sent from INTUITY AUDIX, Aria Digital, and Serenade Digital subscribers to Octel Analog Networking subscribers are supported.

Message designations sent from INTUITY AUDIX, Aria Digital, and Serenade Digital subscribers to Octel Analog Networking subscribers are changed from Priority and Private to Urgent and Private.

Undeliverable messages are automatically returned to sender on other remote machines.

The Message Networking system allows a network address of 3 to 10 digits. A 10-digit dial plan is recommended.

A subscriber on a remote system must be registered on a Message Networking system for that Message Networking system to accept messages for delivery.

A scheduled message status indicates that delivery has not been successfully completed, nor has it failed yet.

Senders receive notification of failed messages in two ways, including:

An error message indicating each mailbox that failed to receive the sent message. This can be an optional Priority message.
A copy of the failed original message from the Failed Message Delivery Manager.

When sending a fax message to a recipient on an Octel Analog Networking node or an Aria Digital node, the sender must include a voice message. If the fax is sent without a voice message, the Message Networking system adds a default voice component to the message.

Unified Messenger and Octel 100 can exchange voice, but not fax, messages. If a Unified Messenger or Octel 100 user receives a voice message with a fax attached, the fax is discarded, and the user is asked to contact the sender.

Large messages (approximately 20 minutes in length) sent to an INTUITY AUDIX remote machine from an Octel Analog Networking remote machine through the Message Networking system are failed with a message length failure code.

When an Octel Analog Networking Aria sender sends a mixed Private and Priority message to multiple INTUITY AUDIX recipients and has marked any of the recipients as Priority or Private on the same remote machine, the message is marked as Priority or Private to all recipients.

The forward and reply indicators for recipients are supported when the sender of a message through the Message Networking system is an Octel Analog Networking Serenade subscriber.

For Demand Remote Push:

When executing the Demand Remote Push, be aware that it takes 25 seconds per subscriber to update the remote Octel Analog Networking machine. Thus, if you have 1,000 subscribers to be updated on the remote machine, this function takes approximately eight hours to run.
Demand Remote Push updates are not supported for Octel 100 remote machines.

If three messages are already in the queue for a port and the maximum number of simultaneous ports for an Octel Analog Networking remote machine has not been exceeded, then the system starts a new port.

Network turnaround is not supported for Octel Analog Networking remote machines.

Multiple simultaneous sessions (inbound and outbound) to an Octel Analog Networking remote machine are supported.

Encryption of DTMF is supported.

Different term definitions used by the Message Networking and Octel Analog Networking machines:

Notice indicates a positive message confirmation for an Octel Analog Networking remote subscriber.
Message indicates a message failure from the Message Networking system.

If the remote machine is Unified Messenger, an Octel gateway must be administered on the Unified Messenger system for messages to be transmitted properly. For more information about the steps required to administer the Octel gateway, see the Unified Messenger documentation.

Octel 100 Octel Analog considerations

The following considerations are related to Octel 100 Octel Analog remote machines:

Octel 100 remote machines do not support an update by Demand Remote Push from the Message Networking system.

Octel 100 remote machines do not send a positive message confirmation to 10-digit dial plans.

If a message is received by an Octel 100 subscriber that was flagged as a negative confirmation, it is turned into a positive confirmation by the Octel 100 and the sender receives a positive confirmation message.

Based on the way that the Octel 100 machine sends a future delivery message (the Octel 100 machine sends the message immediately and expects the remote machine to hold the message until time to be delivered), future delivery messages are supported only through the Message Networking system when sent to Octel 100 Octel Analog, UM Octel Analog Networking, and Aria/Serenade Octel Analog Networking remote machines.

When recipients of messages from Octel 100 Octel Analog 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.

Aria and Serenade Octel Analog considerations

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

When sending a message using a distribution list from an Aria Octel Analog remote machine to another Aria Octel Analog remote machine, the maximum number of subscribers to which the message can be sent is based on the Aria networking parameter that defines the number of attempts the Aria machine will make to deliver a message before giving up on the connection.

Future delivery messages are supported only through the Message Networking system when sent to Octel 100, Unified Messenger, and Aria/Serenade Octel Analog Networking remote machines. When sending future delivery messages from an Aria Octel Analog machine to any other type of end node, the message is failed by the Message Networking system and returned to the sender with a future delivery error type. The Message Networking system uses the time stamp it receives to determine if a message is for future delivery.

For fax-only messages to Aria systems, "Your fax message is attached" is added as a voice component.

The Aria Message Locator feature applies to Message Networking delivery.

When Aria subscribers send a mixed Private or Priority message to multiple Avaya recipients on the same remote machine, the message is marked Priority or Private for all recipients, even if only one recipient is marked as such.

When recipients of messages from Aria and Serenade Octel Analog 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.

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 are NOT supported (for example, Immediate Call).

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 system:

"Message" indicates a failure.
"Notices" indicate a positive message confirmation.

The transmission of a subscriber voiced name with a length of 8 seconds or greater is not supported when using Octel 250/350 with Octel Analog. This is a limitation of the Octel 250/350 when using Octel Analog Networking and is not specific to Message Networking.

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.