Avaya™ Message Networking Help

Home | Search the Help
Print | Back | Fwd | Close

Admin

Maintenance

Reference

Home > Getting Started > Message Networking concepts and features > Feature support by protocol type

Feature support by protocol type

The following table outlines the Message Networking support of features by protocol type.

Tip: If you print this page, use the Landscape format.

Message Networking feature	INTUITY AUDIX	AMIS Analog	Octel Analog and Aria Digital	Serenade Digital	VPIM V2	SMTP/ MIME
Analog Encryption	Not supported	Not supported	Supported for Octel Analog	Not supported	N/A	N/A
Annotation	Supported Release 4.0.0 or later	Not supported	Not supported	Not supported	Supported as determined by the remote machine	Yes
Automatic Message Forwarding	Not supported	Supported as determined by the remote machine	Supported	Supported	Supported as determined by the remote machine	Supported as determined by the remote machine
Automatic Update of Remote Subscriber Records on remote machines	Supported	Not supported	For Octel Analog, add and change supported; delete not supported For UM: not supported For Aria Digital, add/change/ delete/message delivery supported	Add/change/ message delivery supported; delete not supported	Not supported	Supported for Avaya MM with LDAP
Automatic Update of Subscriber Records on the Message Networking system	Supported	Not supported	For Octel Analog, add and change supported; delete not supported UM: if "default" record exists on the Message Networking system. Subscribers are updated on Message Networking from the Unified Messenger directory only if a default record for the subscriber exists in the Message Networking directory. For Aria Digital, add/change/ delete/message delivery supported	Add and change supported; delete not supported (in general, oriented toward sender validation)	Not supported	Supported for Avaya MM with LDAP
Binary	Supported for Release 4.0.0 or later	Not supported	Not supported	Not supported	Not supported	Yes
Bulk Subscriber Additions/ Changes/ Deletions by File Ranges	Not supported; not required for digital	Supported	Supported; not required for digital	Not required	Supported	Supported (except for Avaya MM, which does not require this feature)
Call Detail Recording (CDR)	Supported	Supported	Supported	Supported	Supported	Supported
Component Delivery	Sends the components that Message Networking can deliver, along with a voice message to the recipient to indicate that one or more components were undeliverable	Sends the components that Message Networking can deliver, along with a voice message to the recipient to indicate that one or more components were undeliverable	Sends the components that Message Networking can deliver, along with a voice message to the recipient to indicate that one or more components were undeliverable	Sends the components that Message Networking can deliver, along with a voice message to the recipient to indicate that one or more components were undeliverable	Sends the components that Message Networking can deliver, along with a voice message to the recipient to indicate that one or more components were undeliverable	Sends all
Data/ Message Encryption	Not supported	Not supported	Supported for Aria Digital	Not supported	Not supported	Not supported
Demand Remote Updates	Supported	N/A	Supported by range; preferred method is with NameSend from Aria node	Performed by executing push from end node called NameSend	Not supported	Supported for Avaya MM with LDAP
Dial by ASCII Name	Supported	Supported as determined by the remote machine	Supported	Supported	Supported as determined by the remote machine	Supported as determined by the remote machine
Dial Plan Mapping	Supported	Supported	Supported	Supported	Supported	Supported
Directory Views (dynamic, with voiced name option)	Supported	N/A	Supported	Supported	Dynamic only	Dynamic for non-LDAP
Directory Views (static, with voiced name option)	Supported (with remote machine pull from INTUITY AUDIX at initialization)	N/A	Supported with Message Networking; remote machine push at initialization for Aria Digital	Supported with Message Networking; remote machine push at initialization	Not supported	Not supported
Failed Message Delivery from Message Networking	Supported with two incoming messages: Failed message notification Original copy of message	Supported with two incoming messages: Failed message notification Original copy of message	Supported with two incoming messages: Failed message notification Original copy of message	Supported with two incoming messages: Failed message notification Original copy of message	Supported with Nondelivery Notification (NDN) and single incoming message (DSN) containing: Failed message notification Original copy of message	Supported with Nondelivery Notification (NDN) and single incoming message (DSN) containing: Failed message notification Original copy of message
Failed Message Delivery to Message Networking	Supported	Supported	Supported	Supported	Supported	Supported
Fax	Supported for release 3.0 or later	Not supported	Supported for Release 2.03 or later for Aria Digital. Not supported for Unified Messenger and Octel 100.	Supported for Release 2.0 or later	Supported as determined by the remote machine	Supported as determined by the remote machine
Forwarding a Message	Supported	Supported as determined by the remote machine	Supported	Supported; Serenade to Serenade or Aria "forwarded" messages have this indicated in message header	Supported as determined by the remote machine	Supported as determined by the remote machine
Forward and Reply Indication to Recipient	Supported when subscriber replying or forwarding is a Serenade Octel Analog subscriber	Supported when subscriber replying or forwarding is a Serenade Octel Analog subscriber	Supported when subscriber replying or forwarding is a Serenade Octel Analog subscriber	Supported for Serenade Digital to Serenade Digital	Not supported	Not supported
Future Delivery	Supported	Supported as determined by the remote machine	Supported from Aria Digital to Aria Digital and Octel Analog only. Not supported for the following: Aria, UM, and Octel 100 to AUDIX, AMIS, Serenade Digital, and VPIM V2	Supported	Supported as determined by the remote machine	Supported as determined by the remote machine
Inbound Analog Fallback	Not supported	N/A	Not supported	Not supported	Not supported	Not supported
Maximum Number of Recipients per Single Message Transmission (inbound)	250	1	Octel 250/350 Analog: 100 X bad connection count in System Parameter Networking screen UM: unlimited Aria Digital: unlimited Octel 200/300 Analog: 10	10	1000	1000
Maximum Number of Recipients per Single Message Transmission (outbound)	250	1	Octel 250/350 Analog: 250 but tunable to fewer UM: 250 Octel 200/300 Analog: 250 but tunable to fewer (still stores in groups of 10) Aria Digital: 250 (not tunable)	10	250	250
Message Delivery Confirmation	Supported	Not supported	Supported	Supported	Supported as delivery to Message Networking	Supported as delivery to Message Networking
Multi- language Message Responses from Message Networking Network	American English	American English	American English	American English	American English	American English
Multiple Simultaneous Connections from the Same Remote Machine (Inbound)	Not supported	Supported as determined by remote machine	Supported for Octel Analog; not supported for Aria Digital	Not supported	Not supported	Not supported
Multiple Simultaneous Connections from the Same Remote Machine (Outbound)	Not supported	Supported for up to 9 sessions	Supported for Octel Analog Not supported for Aria Digital	Not supported	Not supported	Not supported
Name Confirmation (spoken)	Supported	Supported as determined by the remote machine	Supported	Supported	Supported as determined by the remote machine	Supported as determined by the remote machine
Network Turnaround	Supported	N/A	Not supported	Not supported	Not supported	Not supported
Outbound Analog Fallback	Not supported	N/A	Not supported	Not supported	Not supported	Not supported
Overlapping Prefixes/ Multiple Prefixes per Location	Supported	Supported as determined by the remote machine	Supported	Supported	Supported as determined by the remote machine	Supported as determined by the remote machine
Priority Message Indication	Supported	Supported, except for priority message originating from an AMIS sender	Supported	Supported	Supported	Supported
Private or Urgent Message Indication	Supported	Supported, except for private message originating from an AMIS sender	Supported (user hears "priority" notice vs. urgent)	Supported (user hears "priority" notice vs. urgent)	Supported as determined by the remote machine	Supported as determined by the remote machine
Receiving a Voice Message	Supported	Supported	Supported	Supported	Supported	Supported
Receiving Voiced Name of Sender	Sender's name in message header	Sender's name in message header	Sender's name in message header	Sender's name in message header	Sender's name in message header	Supported for Avaya MM
Recipient Name Confirmation when Addressing a Message	Supported	Supported as determined by the remote machine	Supported	Supported	Supported as determined by the remote machine	Supported as determined by the remote machine
Remote Machine Reports	Supported	Supported	Supported	Supported	Supported	Supported
Reply to a Network Message	Supported	Supported as determined by the remote machine	Supported	Supported; replied to messages have this indicated in message header	Supported as determined by the remote machine	Supported as determined by the remote machine
Accessed Return- Receipt/ Confirmation	See Message confirmation support	N/A	See Message confirmation support	See Message confirmation support	See Message confirmation support	See Message confirmation support
Self- Registration Agent	Not supported for digital	Supported	Not supported for digital	Not supported for digital	Supported	Supported for non-LDAP; not supported for Avaya MM (LDAP)
Sending a Message to an Aria Recipient with Extended Absence Greeting (EAG) block activated	Sender receives a failed message	Sender receives a failed message	Sender receives a failed message	Sender receives a failed message	Sender receives a failed message	Sender receives a failed message
Sending a Message to an Aria Recipient with Extended Absence Greeting (EAG) warning activated	Sender receives an EAG warning message	Sender receives an EAG warning message	Sender receives an EAG warning message	Sender receives an EAG warning message	Sender receives an EAG warning message	Sender receives an EAG warning message
Sending a Voice Message	Supported	Supported	Supported	Supported	Supported as determined by remote machine	Supported
Subscriber Community ID	Supported (default is 1)	Supported (default is 1)	Supported (default is 1)	Supported (default is 1)	Supported (default is 1)	Supported (default is 1)
Subscriber NetName Type	Supported (default is u)	Supported (default is u)	Supported	Supported (default is u)	Supported (default is u)	Supported (default is u)
Subscriber Reports	Supported	Supported	Supported	Supported	Supported	Supported
Text Message	Supported for Release 4.0.0 or later	Not supported	Not supported	Not supported	Supported	Supported
Time of Day Routing	Supported	Not supported	Not supported for outbound	Not supported for outbound	Not supported for outbound	Not supported for outbound
Traffic Reports
Network Load	Supported	Supported	Supported	Supported	Supported	Supported
Network Status	Supported	Supported	Supported	Supported	Supported	Supported
Port Utilization	Supported with selection by protocol resource type	Supported with selection by protocol resource type	Supported with selection by protocol resource type	Supported with selection by protocol resource type	Supported with selection by protocol resource type	Supported with selection by protocol resource type
Weekend/ Holiday/ Message Type Routing from Message Networking	Not supported	Not supported	Not supported	Not supported	Not supported	Not supported

Future delivery considerations

Remote machines in a Message Networking network handle future delivery messages in one of two ways:

The sending machine stores the future-dated message and then sends the message to its receiving machine at the stipulated time. The receiving machine then immediately distributes the message to the recipient. Unified Messenger using Octel Analog Networking, Serenade, and INTUITY AUDIX Digital (DEFINITY ONE Release 2.0, INTUITY AUDIX Release 4.0 or later, IP600 Release 9.2.1, Avaya IA770, INTUITY AUDIX LX Release 1.0, and Interchange Release 5.4) remote machines store messages marked for future delivery until the stipulated time.
The sending machine does not store the future-dated message, but instead sends it immediately to the receiving machine. The receiving machine then stores the message and distributes it to the recipient at the stipulated time. Aria, and Octel 100 remote machines do not hold future delivery messages and instead send them immediately. These types of remote machines expect the receiving system to display the message at the appropriate time.

Note: All messages received from VPIM V2 and SMTP/MIME systems are assumed to be delivered as soon as normal delivery schedules permit. VPIM and SMTP/MIME machines can receive future delivery messages if they are sent by a machine that holds future delivery messages and then sends them at the time specified.

In either case, Message Networking does not control the sending and receiving of future delivery messages. Message Networking rejects future delivery messages that are scheduled to be delivered before the expected date. Most sending end nodes hold a future delivery message until it is time to send it. In these cases, Message Networking ignores the future delivery flag and sends the message.

In cases where the sending machine does not hold the message, Message Networking verifies that the receiving machine will hold the message. If the receiving machine will not hold the message, Message Networking rejects the message.

In a configuration where there are multiple Message Networking or Interchange 5.4 systems and the sender is on one hub and the recipient on another, the sent message is delivered immediately.

Failed delivery notification considerations

Note the following considerations related to failed message notification:

The failure notification message is generated in US English by Message Networking. This is slightly different than messages that fail to be delivered from one message server to another remote machine.
When the same message fails to be sent to multiple recipients, Message Networking groups all of the failed recipients into one failure notification message.
Extended Absence Greeting blocks are treated as a failed message delivery by Message Networking.

Top of page