• Protects investments in existing Messaging systems.
• Simplifies network administration, management and expansion.
• Can reduce long-distance costs.
• Can reduce management/administration costs.

 

Seamless Networked Messaging
The Message Networking solution enables enterprise-wide messaging that helps streamline costs and makes employees more productive.

Sending voice mail messages can replace many costly and time-consuming long-distance calls between locations as employees can easily communicate with others regardless of location or time zone. With a single command, users can also inexpensively send voice, fax, text, and attachments to multiple offices or individuals worldwide by allowing messages to be sent over existing corporate-wide TCP/IP Wide Area Network (WAN) facilities.

 

---

 

Centralized Network Management
Enterprises can perform most administrative, networking, and reporting tasks through an easy-to-use PC-based system that provides access to their entire messaging network.

Centrally managing and administering the entire Messaging system network can reduce costs and allow for faster updates to the network. Improves communications across the entire enterprise, regardless of location or messaging system type.

 

---

 

Enterprise Lists
Enables users to create lists to all subscribers within the network through a variety of methods (including dynamic creation of lists such as location, organization, etc.) to broadcast messages enterprise-wide.

Enhances communications across the enterprise, improving information sharing, including timely dissemination of information. The use of Enterprise Lists can also provide significant costs savings when sending messages over the corporate wide area network, as opposed to using the PSTN.

 

---

 

Web Browser-Based Administration
Supports web browser-based administration similar to that of Avaya INTUITY™ AUDIX® LX and supports access to equivalent Avaya Interchange Release 5.4 menus, screens, and reports, including: Networking Administration, System Administration, Customer Services/Administration.

Simplifies the Messaging system network administration, reducing the time it takes to make adds, moves, changes to the end-point messaging systems.

 

---

 

Enterprise Directory Management
The directory-view types include the entire directory, only those subscribers that have messaged to each other, portions of the directory (i.e. communities of interest), or none. This still allows messaging, but does not support any ASCII name addressing or voice name confirmation.

Can reduce the amount of administration time required to maintain and manage enterprise directories, ensuring that messages can be quickly addressed and sent.

 

---

 

Dial Plan Mapping
Supports message delivery between locations with different addressing schemes, simplifying how users send messages to each other.

Users dial a previously-defined, fixed number of digits to address their message, regardless of the destination server, and Message Networking automatically converts the address to the proper number of digits for the destination server and delivers the message. This feature helps make it easier for enterprise associates to use message networking, improving communications and businesses processes.

 

---

 

Lightweight Directory Access Protocol (LDAP) Interface
Release 2.0 supports an LDAP interface (secured by password) that will allow external, third-party vendors to add, change, delete, and query Enterprise Lists and the entries in those lists. It will also allow the query of Enterprise List System Parameters (including system-wide subscriber permissions).

Allows customers or third-party vendors to write applications to streamline administration, which might include subscriber administration of lists, synchronization between an enterprise's personnel direction and the E-List application.

 

---

 

Enterprise Addressing
Employees can address messages to anyone else in the enterprise simply by using the subscriber's voice message network address, even if the subscriber name is not downloaded in the remote end-point server's Directory View. The numbering scheme (or dial plan) should be uniform throughout the company, of a fixed length, and can be between 3 and 10 digits in length. Ten digits are recommended to allow for future growth and eliminate overlapping address ranges.

Allows associates to easily address messages to key colleagues, helping to ensure better communication throughout the enterprise.

 

---

 

Multiple Speech Compression Technique Support
Translates different message transmission protocols and transcodes the various speech compression techniques, so businesses can network almost any messaging system they have in their enterprises. Because all transmission protocol translations are performed within the Message Networking solution, there's no need to reconfigure each individual end-point server or equip them with translation software.

Helps to improve communications across the entire enterprise, as well as any of the millions of email users reachable via the Internet.

 

---

 

Multiple Protocol Support
Supports: TCP/IP digital protocols (for INTUITY™ AUDIX® server, Octel® 200SX/200/300 messaging servers, Octel 250SX/250/350 message servers, and non-Avaya messaging servers that are VPIM compatible), Octel® analog networking, AMIS-analog networking and SMTP/MIME (for Modular Messaging, Unified Messenger and non-Avaya Messaging Systems).

Provides investment protection benefits by allowing existing Avaya and multi-vendor messaging systems to be networked together. That means virtually any voice or multimedia messaging systems can be easily networked via the Message Networking solution. There is no need to remove or replace existing systems that are compatible with the Avaya proprietary protocols or industry-standard protocols (including SMTP-MIME or VPIM).

 

Hardware Requirements

Avaya S3210 or Avaya S3400 Message Server

Message Networking R2.0 provides the option for purchasing the solution on either the Avaya S3210 Message Server or the Avaya S3400 Message Server, depending upon capabilities and functions that are required.

 

15" CRT Monitor

Requires a monitor that is sold seperately.

 

---

 

Network Requirements
Avaya Message Networking supports the following message transmission protocol standards:

• AMIS
• VPIMvs
• SMTP/MIME (email) using both GSM and G.711 voice encoding.

 

Additional information regarding G.711 can be found at: http://www.itu.int/rec/recommendation.asp?type=folders&lang=e&parent=T-REC-G.711

 

---

 

Security Requirements
Please see technical documents to refer to the requirement table for logical ports used by the protocols. See documentation for security information in the Security and TCIP/IP Data Usage documents for Message Networking 1.1.
Message Networking Release 2.0 will have no facility to scan attachments in incoming messages for viruses. Furthermore, no facility is planned at this time to allow an enterprise to globally scan for and remove viruses from existing messages. Enterprises should be concerned about email viruses and should be advised to deploy a third party email virus scanner. Such scanners are available in a number of forms including both standalone email relay hosts and firewall/router based scanning systems.

 

• Message Networking receives incoming email for end users via SMTP on TCP/IP port 25.
• The Release 1.1 system will support the administrative ability to allow/block SMTP usage by individual or ranges of subscribers (by Network Address) as well as domain definitions.
• Message Networking Release 1.1 provides a secure WEB connection that requires the administrator's browser to have a "security certificate."
• System Access - An addition level of security is obtained through the server design.
• Message Networking does not allow any subscriber (TUI, WUI, etc.) into the server. That is, there are no mailboxes to access.

 

---

 

Software Requirements
Message Networking R1.1 Application Software or R.2.0
This is required to install the Message Networking application.

 

Interoperability with Non-Avaya Products
Message Networking will provide robust interoperability with other ESMTP/MIME compliant Message Transfer Agents (MTAs).
As such, the Message Networking ESMTP/MIME networking functionality will conform to those sections of the RFC 821, RFC 822, RFC 974, RFC 1123, and RFC 1521 specifications that "MUST" be supported, and many of those specifications that "SHOULD" be implemented. (The "MUST" and "SHOULD" terms used here refer to the features in the respective RFC columns.)

The following URL template may be used to reference these RFCs (where NNNN is the RFC number prefixed with zeroes as necessary to make a four digit number.)

 

SMTP/MIME support by an alternate reference, RFC 2821, summarizes the relevant RFCs addressing ESMTP and includes clarifications and cautions on common non-compliant implementations.
Specifically, Message Networking Release 2.0 supports the GSM 6.10, G711-mu law, and G711-a law voice encoding for SMTP/MIME. The application can transcode from any of these formats to any of the others it supports on the system.

Additional information regarding GSM 6.10 (13Kbits/sec) voice encoding can be found at the this site.

 

Message Networking supports multiple manufacturer's switches.

• NEC NEAX 2400
• Rolm 8000, 9000, 9751
• Northern Telecom SL-1
• Northern Telecom Meridian -1
• Northern Telecom Meridian SL-1
• Mitel SX200D
• 5 ESS
• DMS100

 

VPIMv2 Interoperability
The following other vendor's products have been tested with Message Networking Release 2.0:

• Nortel CallPilot
• Nortel Meridian Mail (though the Meridian Mail Net Gateway 1.1)
• Nortel BCM
• Nortel Norstar Mail
• Alcatel 4635
• Microsoft Exchange 2000
• AccessLine
• 3COM NBX100
• Cisco Unity

 

As more data is received on customer field trials with other VPIM vendors, this list will be updated.

 

---

 

Platform Interoperability
Networking Protocol Interoperability Support
The Avaya Message Networking solution utilizes all the Avaya proprietary protocols, with the exception of DCP and RS232 transports for AUDIX Digital.

 

The supported Avaya propriatary protocols include:

• AUDIX TCP/IP
• Aria TCP/IP
• Serenade TCP/IP
• Octel Analog Networking

 

The Message Networking solution has been tested with Unified Messenger-Exchange, Unified Messenger-Lotus Domino, and Avaya Modular Messaging for SMTP/MIME integration.

Message Networking also supports VPIMv2, and can network with any voice mail system that supports VPIMv2. Avaya IP Office Voice Pro has been successfully tested to network to Message Networking Release 2.0 using VPIMv2.

Message Networking Release 2.0 also supports AMIS, an analog networking standard.

 

LDAP Interoperability Support
Message Networking Release 2.0 also provides LDAP access to its directory for administration and data queries. Please refer to the "Message Networking Release 2.0: LDAP Interface" document for additional information.

 

---

 

Compatibility Issues
The Message Networking solution will support the following switch integrations with R2.0:

• System 75/DEFINITY®
• System 85/Dimenstion
• System 25
• NEC NEAX 2400
• Rolm 8000, 9000, 9751
• Northern Telecom SL-1
• Northern Telecom Meridian -1
• Northern Telecom Meridian SL-1
• Mitel SX200D
• 5 ESS
• DMS100

 

Both the S3210 and S3400H platforms used by the Message Networking Release 2.0 application are highly reliable. The S3400H has some additional redundancies and hot-swappable components that make it an even more reliable platform. These include RAID Level 5 disks, power supplies, and fans. A UPS is required for the S3400H platform, increasing its reliability.

 

Both the S3210 and S3400H platforms of the Message Networking Release 2.0 application have available an "Attended High Availability" offer, which includes the use of a spare system as a backup for the primary. This offer is described in the "Message Networking Release 2.0: Attended High Availability" document, located in the Sales Resources section of this web site.

Busy Hour Message Minutes
On average, the Message Networking Release 2.0 application on the S3210 platform can support 3,768 message minutes (1,884 one minute messages in and 1,884 one minute messages out) during the network busy hour. Note that this figure is a combined one of all protocols and ports supported on the system.

On average, the Message Networking Release 2.0 application on the S3400H platform can support 11,334 message minutes (5,672 one minute messages in and 5,672 one minute messages out) during the network busy hour. Note that this figure is a combined one for all or the protocols and ports supported on the system.

The Message Networking Release 2.0 application does include a number of Security features. These include:

• FTP Deactivation
• Access Security Gateway (ASG) (S3400H Only)
• SMTP/MIME Blocking (by Sender and Recipient)
• User Permissions for Enterprise Lists
• Complete Documentation of all IP Services and Ports Used by the System (this can be found in the "Message Networking Release 2.0: TCP/IP Port Usage" document)
• Networking Protocol Passwords
• A comprehensive description of all of the Security features and considerations of the system are defined in the "Message Networking Release 2.0 Printable Concepts and Features Guide."

 

Security Issues
The Avaya Message Networking solution requires modem access for proactive support and it is based on the Linux operating system, Linux network facilities (Telnet and FTP) are potentially accessible to Avaya support personnel. Note that the system by default is shipped with FTP deactivated.

Avaya has a strict policy regarding conduct when supporting servers connected to an enterprise's network. However, many enterprises require absolute technical assurance. One of the ways for the customer to technically assure that Avaya personnel will not use common networking facilities is to use a firewall to filter the traffic from Avaya Message Networking.

Other considerations:

• All servers should be kept behind a firewall to shield them from hackers and denial of service attacks.
• Access Security Gateway (ASG) provides security.
• File Transfer Protocol (FTP) is turned off by default.
• Telnet is turned off by default.
• Avaya recommends proper client and email service virus protection as well as firewall designs.