Release Notes MX-ONE Messaging V4.2 Service Pack...

Commercial in Confidence

Release Notes

MX-ONE Messaging V4.2 Service Pack 1

Aastra Telecom Sweden ABSE-126 37 Hägersten, Sweden

www.aastra.com

http://www.aastra.se/cps/rde/xchg/SID-3D8CCB6A-7B3F26BD/11/hs.xsl/index.htm%00%E5%A1%B9%EF%92%81%E1%B4%BB%E4%A1%BF%E2%B2%AF%E5%B6%82%E8%97%84%E6%8C%A7%00%00%EA%AE%A5

Product Introduction ASE/MXO/PLM/0088

2009-12-202/24


Release Notes for MX-ONE Messaging V4.2 Service Pack 1

Contents

1.............................................................................................................................................Introduction.............................................................................................................................................................3

1.1 Purpose................................................................................................................................3

1.2 Scope...................................................................................................................................3

1.3 Prerequisites........................................................................................................................3

1.4 Update procedures..............................................................................................................3

1.4.1 Updating from previous releases..................................................................................3

2 Good to Know.............................................................................................................................3

2.1 Native SIP Support..............................................................................................................3

2.2 Parameter MWI Subscription period in sec..........................................................................3

2.3 Recognising the correct version information........................................................................3

3 Software......................................................................................................................................3

3.1 O & M Documentation..........................................................................................................3

4 Hardware.....................................................................................................................................3

4.1 Required Hardware..............................................................................................................3

4.2 New Hardware or Products..................................................................................................3

5 New Features & Enhancement...................................................................................................3

5.1 New Features at a Glance...................................................................................................3

5.2 Native SIP Support with MX-ONE V4.0...............................................................................3

5.3 New Dialogic Drivers............................................................................................................3

5.4 New Mitel MiTAI SDK..........................................................................................................3

5.5 Meridian Mail TUI.................................................................................................................3

5.5.1 Meridian Mail TUI Localization......................................................................................3

5.6 Redesigned NetConnect Digital Networking Configurator...................................................3

5.6.1 Digital Networking Configurator Capabilities................................................................3

5.7 Improvements to Web PhoneManager................................................................................3

5.7.1 Live Reply.....................................................................................................................3

5.7.2 Customizable User Resources Page............................................................................3

5.7.3 Purge On Exit...............................................................................................................3

5.8 Improvement to Unified Messaging for IMAP......................................................................3

5.9 Support for Exchange 2007.................................................................................................3

2009-12-203/24


5.10 Support for Lotus Notes/Domino R8 and R8.5.................................................................3

5.11 Updates to Distribution Lists.............................................................................................3

5.11.1 Notification Suppression...............................................................................................3

5.11.2 Self Copy of Messages.................................................................................................3

5.12 Updates to Reports..........................................................................................................3

5.12.1 Crystal Reports Update................................................................................................3

5.12.2 Subscriber CSV Additions............................................................................................3

5.13 System Prompts...............................................................................................................3

5.13.1 Updated German Prompt Set.......................................................................................3

5.13.2 Updated Swedish Prompt Set.......................................................................................3

5.13.3 Updated UK English Prompt Set..................................................................................3

5.13.4 New Russian Prompt Set..............................................................................................3

5.13.5 New European Portuguese Prompt Set........................................................................3

5.14 VIM Prompts.....................................................................................................................3

5.14.1 Updated time/weekday Prompts...................................................................................3

5.14.2 Change in the order of the VIM language option..........................................................3

5.15 New and Updated Telephone System Integrations..........................................................3

6 MX-ONE Messaging Platform Minimum Requirements..............................................................3

7 Corrections..................................................................................................................................3

1 Introduction

1.1 Purpose

The purpose of the Release Notes document is to communicate the enhancements and corrections provided with MX-ONE Messaging V4.2 Service Pack 1 VM and UM suite.

1.2 Scope

This document provides a short description of new features and enhancements and information on trouble reports that are corrected in this release.

The Service Pack contains the following:

Updated version of the Messaging V4.2 SP1 VM/UM Software

New Media Kits for download on the service plaza or delivered with new orders

New Recovery DVD for turnkey HP servers and ESU based servers delivered with new orders

2009-12-204/24


1.3 Prerequisites

Before the update, make sure that the system is stable. A system update must be performed during a period with low traffic (during the update the system will be reloaded).

It is assumed the installation is running MX-ONE Messaging V4.1 or V4.2 where the USB dongle is present. When upgrading from earlier versions of OneBox, you must change from the Parallel port dongle to a USB based dongle. Please refer to the Ordering information for MX-ONE Messaging V4.2 to get the procedure to exchange the existing dongle for the new one. Otherwise, this can be solved by ordering a Media Kit with the USB dongle directly when you place your order for the upgrade.

Prior to upgrading from V4.1 or earlier releases, please ensure that you have obtained the updated license file with your upgrade order. There is no need to change the license file if you are already running MX-ONE Messaging V4.2.

Update to MX-ONE Messaging V4.2 SP1 is verified to function with following MX-ONE releases:

MX-ONE TSE V4.0 base release

MX-ONE TSE 3.2 SP4 or later releases

MX-ONE TSW SP6 or later releases

Note: with MX-ONE TSE V3.2 SP4, the SIP converter is needed unless the first Hot Fix package is loaded. Please refer to MX-ONE 3.2 SP4 HF1 release notes for details.

Note: For use with MX-ONE Telephony Switch (TSW), the SIP converter is needed.

For integration with 3rd party PBXs, the corresponding Integration Technical Note (ITN) applies. The ITN for the different integrations can be found in the documentation provided with the Media Kit.

1.4 Update procedures

1.4.1 Updating from previous releases

Update from previous versions of MX-ONE Messaging can be executed in one step by simply executing the Setup Wizard from the Media kit root directly.

For versions prior to V4.1, you must insert the USB dongle into the target server prior to starting the upgrade.

It is strongly recommended to a back-up of the system and user data prior to doing the upgrade. Refer to the Administrator’s On-line guide or to the admin guide in the Media kit for the proper procedure to do the back-up and perform the upgrade. But in general all

2009-12-205/24


configuration, user data and even specific customer developed auto-attendant scripts will remain untouched during the upgrade.

2 Good to Know

2.1 Native SIP SupportWith MX-ONE TSE V3.2 SP4 (with the first HotFix package) and later releases, the native SIP integration is fully supported. This means there is no longer a need for the SIP converter to ensure IP integration.

However, with earlier releases of V3.2 and V3.1 and well as with MX-ONE Telephony Switch, the SIP converter delivered with the media kit shall be used.

As the IP extension implementation in MX-ONE V3.2 SP4 and later releases is generic, the choice of SIP or EETS integration has little or no impact on the IP extension or VM group setup. The choice of H.323 or SIP is decided when the Messaging ports register with MX-ONE. If the SIP converter is present, they shall register as H.323 extensions, otherwise, they shall register as SIP extensions. Please refer to the Aastra MX-ONE EETS or SIP integration ITN for programming guidelines.

Some issues that will be resolved in coming releases of MX-ONE Messaging as well as MX-ONE 3.2 have to be taken in to consideration when setting up Native SIP integration.

The MX-ONE Messaging server can’t make outgoing calls unless the following configurations been made.

For MX-ONE V3.2 SP4 and V4.0:

Add an external sip domain entry containing the MX-ONE messaging server IP-address.

Example: sip_external_domain –add –domain 10.10.10.100

For MX-ONE V3.2 SP4:

Add an entry in the ip_telephony.conf file disabling early replaces.

On the MX-ONE server edit the /etc/opt/eri_sn/ip_telephony.conf file adding an entry in the “User Agent Overrides” section. (This file is located on every MX-ONE TSE server but it is only nessesary to make the changes on the server that MX-ONE Messaging registers its ports in.)

Note: Reload of program unit SIPLP needed after changing ip_telephony.conf.

Add the following:

#OneBox-Aastra_MX-ONE Messaging Voice Mail [A server will not handle B-party display info]UserAgent:Aastra-OneBox:Name: "Aastra_MX-ONE Messaging Voice Mail"UserAgent:Aastra-OneBox:EarlyReplaces: no

2009-12-206/24


2.2 Parameter MWI Subscription period in sec

1. A configuration parameter “MWI Subscription period in sec” has now been exposed for Aastra EETS and Aastra SIP integration. The default value for this item has been changed to 240 for EETS integration. This value MUST be less than or equal to the subscription duration the convertor / switch requests.

2. Steps required after installing the update build containing the fix:

a. For new installations and upgrades from previous Messaging versions: No change required, MWI should work with the new build.

b. For installations that upgrade from an messaging 4.2 where MWI does not work: Follow one of the two steps in the Messaging administration tool.

1. Delete and recreate the integration.

2. Open the Integrations Options dialog. You should see “MWI Subscription period in secs” field whose value is set to 240. Change that value, save it. Open the dialog box again, change it back to 240 and save it again. This step will ensure that the configured value is now saved into the integration data. Restart MX-ONE Messaging

2.3 Recognising the correct version information

There can be some confusion as to which version of MX-ONE Messaging your system is running when displaying version information in the administration tool. To be clear:

MX-ONE Messaging V4.2 SP1 corresponds to version 7.92 Build 235

If version 7.90 Build 256 Service Pack 1 is displayed, then your system is running MX-ONE Messaging V4.2

2009-12-207/24


3 SoftwareThe Following package is available for download in this release:

MX-ONE Messaging V4.2 SP1 Media Kit.

For new sales, an updated Media kit with a new revision state will be delivered and contains the Messaging V4.2 SP1 software and documentation.

For turnkey HP server installations, the image installed on the server contains the latest Messaging V4.2 SP1 Media kit installed on the E: drive. Please refer to the Getting Started Guide delivered with the system for the installation procedure.

3.1 O & M Documentation

For MX-ONE Messaging CPI documentation, you can either use the on-line documentation with the MX-ONE Messaging administrator function or the Administrator Guide delivered in PDF format with the media kit or use the relevant Messaging documentation provided with the MX-ONE CPI documentation.

For MX-ONE TSW, please refer to the relevant ALEX library for MX-ONE Telephony Switch SP6 or later.

For MX-ONE TSE version V3.2 the ALEX libraries should be used up to SP1. Revised and new documents for MX-ONE 3.2 SP4 will be available for download from MX-ONE Knowledge Base at Service Support Plaza in PDF format.

O&M documentation for Telephony Server version 3.2 SP4

For MX-ONE Version 4.0 please refer to the new MX-ONE V4.0 CPI documentation.

2009-12-208/24


4 Hardware

4.1 Required Hardware

When updating from OneBox releases 4.01 or earlier, you must change the licence dongle from the parallel port model to the current supported USB dongle (KDU 137 318/1). This may be purchased as a spare part or is included with the delivery of the Media Kit LZY 601 308/42. Alternatively, if the customer purchases an upgrade from a previous version of OneBox, this parallel dongle may be exchanged for a new one under certain conditions. Refer to the Ordering Information for MX-ONE Messaging V4.2 for details.

For specific platform HW related questions, see list of supported PC HW and boards in the Minimum Requirements section below.

4.2 New Hardware or Products

There is no new hardware for this release.

5 New Features & Enhancement

5.1 New Features at a GlanceThis new MX-ONE Messaging release includes the following additions and improvements:

Full Support for Native SIP integration with MX-ONE V4.0 New Dialogic Drivers New Mitel MiTAI SDK Lotus Notes R8 and R8.5 Support Meridian Mail TUI Redesigned NetConnect Digital Networking Configurator Improvements to Web PhoneManager Improvement to Unified Messaging for IMAP Support for Exchange 2007 Updates to Distribution Lists Updates to Reports New and updated integrations

The remainder of this section provides more information about each of these new features.

2009-12-209/24


5.2 Native SIP Support with MX-ONE V4.0With MX-ONE TSE V4.0 native SIP integration is fully supported. This means there is no longer a need for the SIP converter to ensure IP integration.

Please refer to the Aastra MX-ONE SIP integration ITN for programming guidelines.

5.3 New Dialogic DriversFor improved performance and stability on systems with quad-core processors, MX-ONE Messaging version V4.2 SP1 includes a new version of Dialogic drivers. During the upgrade process, you must uninstall the previous version of Dialogic prior to installing this new version.

5.4 New Mitel MiTAI SDKFor improved performance and stability in some customer environments, MX-ONE Messaging version V4.2 SP1 includes a new Mitel MiTAI software development kit.

5.5 Meridian Mail TUINew Emulation for the Nortel Meridian Mail Telephone User Interface (TUI)

MX-ONE Messaging version V4.2 SP1 includes a new Meridian Mail option in the TUI Type list on the Presentation tab in the Subscriber and Class of Service mailboxes. When this option is selected, subscribers hear an emulation of the

Nortel Meridian Mail telephone user interface (TUI) when they perform the following tasks:

Using the main subscriber menu Reviewing incoming messages Sending new voice and fax messages Forwarding existing voice and fax messages Using the caller interface

With their most commonly used commands still available to them, existing Meridian Mail users can migrate to MX-ONE Messaging comfortably, with very little effort. For reference information about this new TUI, refer to the online user reference and navigation map located on the MX-ONE Messaging DVD.

5.5.1 Meridian Mail TUI LocalizationThe Meridian Mail TUI supports the following localizations:

English – U.S. & U.K. French – North American Spanish – North American

2009-12-2010/24


5.6 Redesigned NetConnect Digital Networking ConfiguratorIn MX-ONE Messaging V4.2 SP1, the Digital Networking Configurator has been rebuilt from the bottom up. Not only does it provide a more intuitive interface, but the entire architecture has been redesigned. Rather than the legacy peer-to-peer (P2P) topology used in previous versions, the Configurator now routes all propagation data through a master server that controls changes to each node. This new ‘star architecture’ provides a more robust and reliable digital network, including:

Increased digital networking capacity to support 75 nodes and 50,000 subscribers Eliminated need for dedicated digital networking server at each site Controlled timing of network administration updates by the recipient rather than the sender

5.6.1 Digital Networking Configurator CapabilitiesAfter setting up a master server, the digital networking administrator can perform numerous tasks from the console.

Setup new nodes and mailboxes Migrate the legacy P2P network to Star Maintain a ‘mixed’ network of P2P and Star combined Automatically detect missing elements from the network View the status of all propagation data across the network Perform backup and restore procedures

2009-12-2011/24


Handle maintenance of the master server

New Digital Networking Configurator

2009-12-2012/24


5.7 Improvements to Web PhoneManagerIn version V4.2 SP1, Web PhoneManager contains a few important enhancements.

5.7.1 Live ReplyWeb PhoneManager now offers the Live Reply option to allow subscribers to make direct ‘live’ calls to senders, regardless of how the subsriber receives messages. For example, a subscriber listening to a message on a handset can click the Live Reply link in Web PhoneManager, and the sender is called through the handset. Alternatively, a subscriber listening to an audio stream message can also click the Live Reply link to have the handset first ring and, once the subscriber answers, dial the sender.

5.7.2 Customizable User Resources PageIn the previous version of Web PhoneManager, administrators had no method for including or excluding the materials displayed on the User Resource Page. For example, users would see the Audix TUI Quick Reference Card and not understand the purpose of the file since they were not using that particular TUI.

With the current release, administrators are able to modify the links in the resources.xml file to hide or add resources displayed for their users.

5.7.3 Purge On ExitIn the previous version of Web PhoneManager, messages were set to purge based on a setting in the subscriber mailbox. When set to thirty days, for example, old messages accumulate, consuming unnecessary disk space.

With the current release, administrators have the option to edit the config.xml file to force a deleted message purge on logout. When set, this purge occurs automatically.

5.8 Improvement to Unified Messaging for IMAPIn response to customer requests, the IMAP interface has been modified to allow an SMTP path that is different from the IMAP server. This change offers the ability to have Unified Messaging in environments where the SMTP and IMAP servers are separate and distinct.

New IMAP Configuration

2009-12-2013/24


5.9 Support for Exchange 2007In the Server-based Unified Messaging category, version V4.2 SP1 offers a full integration to Microsoft Exchange 2007, including a new 64 bit MWI application.

With MX-ONE Messaging Unified Messaging for Microsoft Exchange 2007, subscribers can manage voice, fax, and email messages using Microsoft Outlook. MX-ONE Messaging Unified Messaging accomplishes this by enhancing the Microsoft Outlook email client so that it can support voice and fax messages in addition to email messages.

5.10 Support for Lotus Notes/Domino R8 and R8.5Also in the Server-based Unified Messaging category, version V4.2 SP1 provides support for Lotus Notes/Domino R8 and R8.5 32 bit versions.

Subscribers can manage voice and fax messages along with email messages in their Lotus Notes Inbox folder. MX-ONE Messaging Unified Messaging accomplishes this by enhancing the Lotus Notes email template so the new features are seamless in an environment already familiar to subscribers.

In addition, no longer are there separate templates for iNotes and regular Notes; both of these are now combined in a single template.

5.11 Updates to Distribution Lists

5.11.1 Notification SuppressionIn previous versions of MX-ONE Messaging, when a message was sent to a distribution list all subscribers to the list would be notified of the new message. In version V4.2 SP1, we allow system administrators to suppress such notifications on any of the following notification methods:

Message Waiting Indication (MWI) Short Message Service (SMS) / Email (SMTP) Immediate Message Notification Automatic Message Forwarding

Even though the notification of the message is suppressed, the message still appears as a new message in the subscriber's mailbox.

When notification suppression settings differ between the distribution list and the member distribution lists, then member lists inherit the notification suppression configuration of the parent distribution list. To understand the inheritance more clearly, remember these two rules:

Suppression overrides non-suppression Non-suppression does not override suppression

Notification suppression does not function across a network. Network recipients of a propagated distribution list with notification suppression enabled still receive notification.

2009-12-2014/24


5.11.2 Self Copy of MessagesSubscribers, who send messages to a distribution list that they themselves are a member of, will receive a copy of the message in their inbox. This change better aligns the way MX-ONE Messaging distribution lists work with the way that e-mail system distribution lists work.

5.12 Updates to Reports

5.12.1 Crystal Reports UpdateThe latest version of Crystal Reports is now incorporated into MX-ONE Messaging Reports. This upgrade allows a more sophisticated split-pane view as well as the ability to perform more robust reporting using Crystal Reports.

5.12.2 Subscriber CSV AdditionsThe subscriber CSV file now includes two fields from the SMS Tab in Subscriber mailboxes:

SMTP Address Send Message Attachment

Users can include this information in any custom reports they generate.

5.13 System Prompts

5.13.1 Updated German Prompt SetThe German prompt set has been re-recorded to fix contextual grammar inconsistencies (e.g. usage of Um/Von, etc…)

5.13.2 Updated Swedish Prompt SetThe Swedish prompt set has been re-recorded to update some terms/nouns to more common Swedish terminology (Sjärna, Fyrkant, Knappa, Telefonist, etc…) and correct some contextual grammar inconsistencies for some prompts.

5.13.3 Updated UK English Prompt SetThe UK English prompt set has been re-recorded in a new voice and now includes prompts for all TUI types.

5.13.4 New Russian Prompt SetMX-ONE Messaging now includes a complete Russian prompts set including all TUI types.

5.13.5 New European Portuguese Prompt SetMX-ONE Messaging now includes a complete EU Portuguese prompts set including all TUI types.

2009-12-2015/24


5.14 VIM Prompts

5.14.1 Updated time/weekday PromptsThe VIM prompt set logic has been changed to fix language specific grammar inconsistencies when playing greeting with weekday versus day of the month. Explanation: In many languages, there is no “the” when referring to a weekday, whereas there is one when referring to a date. In the previous VIM logic, “the” was inserted regardless of weekday (used if the return date is less than one week) or day of the month.

This has now been corrected with this release and affects several languages.

5.14.2 Change in the order of the VIM language optionThe VIM prompt set logic has been changed to put the “language change” option before listening to the Absence message and options menu. This way a caller doesn’t have to wait until the absence greeting is played in the default language before getting the option to change the language.

2009-12-2016/24


5.15 New and Updated Telephone System IntegrationsMX-ONE Messaging V4.2 SP1 provides to the following new integrations for this release:

The NEC Sphere Sphericall IP-PBX SIP integration for up to 48 ports. The Dialogic 1008LS Media Gateway SIP Trunk integration supports 8 analog lines of the telephone system and provides a network connection to MX-ONE Messaging.

In addition, this release encompasses updates to the following integrations:

MX-ONE Messaging SIP stack has been updated to use RADVISION version 4, which is the basis for all IP integrations. A new ITN has been written describing the Native SIP integration with MX-ONE TSE. The Alcatel-Lucent OmniPCX Enterprise (4400) SIP Trunk integration now includes failover capabilities and supports 96 ports on the IP integration The Cisco Unified Communications Manager SCCP integration has been updated for version 6.0 of the Unified Communications Manager (formerly CallManager) software. The Nortel Meridian CS 1000 integrations have been verified against version 5.0 of the Succession software. The Mitel MiAUDIO based IP integration has been updated to use the 3.0 Software Development Kit (SDK) from Mitel which adds support for multi-CPU servers, Multi-core CPUs, and CPUs that use hyperthreading. Full qualification of the Avaya S8500/S8700 Communication Manager (CM) SIP based IP integration was done using version 4.0 of the Avaya CM software.

6 MX-ONE Messaging Platform Minimum Requirements You must dedicate a platform to the operation of MX-ONE Messaging, its client utilities, and its maintenance programs. This computer platform must satisfy the following minimum requirements:

The following list represents the basic minimum hardware and software required for version 4.2 SP1 of MX-ONE Messaging. The hardware requirements for your implementation of MX-ONE Messaging may be greater, depending on the features purchased for it, the type of integration installed with it, the amount of use it is expected to receive,

2009-12-2017/24


and the hardware or software upgrades it is expected to need in the future. Contact Aastra for specific hardware requirements based on your implementation.

Aastra highly recommends placing RightFax 9.3/9.4 on a separate server if you are going to use a SQL database other than the embedded SQL that comes with RightFax 9.3 or 9.4. See the RightFax Getting Started Guide for more information.

20 gigabyte (GB) hard disk drive with an 8-GB drive C partition (this configuration supports 1,500 subscribers) 1.0 GHz Intel® Pentium IIITM or better microprocessor Sufficient full-length PCIe, PCI, or PCI-X expansion slots to support all required linecards, DSP cards, and digital interface cards. 5-volt cards require 5-volt PCI slots, while “universal” cards may be installed in 5-volt PCI, 3.3-volt PCI, or PCI-X slots. See Table 1 : Recommended Voltage for the properties of the recommended cards. Appropriate RAM needed is based on Table 3 found later in this section Windows Server 2003 with Service Pack 2. For systems with 16 voice ports or fewer and no Unified Messaging support, Windows XP Professional with Service Pack 2 may also be used. Color VGA-compliant graphics adapter and monitor DVD drive compatible with DVD-R media Network interface card Remote connectivity through TCP/IP (preferred), or a Windows-compliant external modem and dedicated RS-232 serial (COM) port, to support remote administration Appropriately configured feature and license certificate files At least one USB port If integrating using an outband RS-232 integration, at least one dedicated COM port and serial cable to communicate with the telephone system If Short Message Service (SMS) support is installed, a dedicated modem to contact the SMS provider or the subscribers’ GSM-based mobile telephones (in addition to the modem used for remote administration); contact your SMS

2009-12-2018/24


provider for their modem requirements and refer to the SMS Online Book for additional information. (Note that SMTP-based message notification and delivery, which is configured as an SMS provider, does not require such a modem; instead, it uses the network interface card and TCP/IP connectivity specified earlier in this list) If Voice Intercept Messaging (VIM) is installed on the platform, a dedicated COM port or a TCP/IP network interface should be used to communicate with the Contact ManaGement attendant Suite (CMG) or Dynamic Network Administration (D.N.A.) Server Attendant Suite via the GICI protocol. If integrating with a circuit-switched PBX, at least one voice line board is needed in the server. Refer to the list in Table 1 below for supported boards. No physical voice line cards are required with SIP/IP telephony integration. If installing a Captaris/Opentext RightFax server on the MX-ONE Messaging platform, one or 2 Brooktrout analog fax cards may be used, as listed in Table 2 : Approved Brooktrout/Dailogic fax cards below. To support fax features, Captaris RightFax 9.4, 9.3 FP1b HF3, 9.0 SP2, or 8.7 with appropriate service packs (and hot fixes) must be installed to support telephony gateway interworking with MX-ONE Messaging Voice. The processor and RAM requirements for MX-ONE Messaging vary with the options and ports it must support. See Tables 3 to display the capacity of version 4.2 SP1 to support various combinations of features, users, and ports.

Additional hardware or software may be required to use advanced applications of MX-ONE Messaging. Refer to the appropriate online book for any additional requirements to use these applications.

If you are considering upgrading from a MX-ONE Messaging version prior to 4.2, examine Table 3 closely to ensure that your server meets the platform requirements for the upgrade.

2009-12-2019/24


Table 1 : Recommended1 Voice linecards for MX-ONE Messaging 4.2 SP1

Linecard or Digital Interface Card PCI Slot Requirements

Aculab E1/T1 Network Interface Card2

UniPCIeversal (compatible with 5-volt PCI, 3.3-volt PCI, and PCI-X slots)

Dialogic D/4PCI-U Universal (compatible with PCIe, 5-volt PCI, 3.3-volt PCI, and PCI-X slots)

Dialogic D/41JCT-LS Universal (compatible with PCIe, 5-volt PCI, 3.3-volt PCI, and PCI-X slots)

Dialogic D/41JCT-LS Euro Universal (compatible with 5-volt PCI, 3.3-volt PCI and PCI-X slots)

Dialogic D/42JCT-U Universal (compatible with PCIe, 5-volt PCI, 3.3-volt PCI and PCI-X slots)

Dialogic D/82JCT-U PCIe and 5-volt PCI

Dialogic D/82JCT-U-PCI-UNIV Universal (compatible with 5-volt PCI, 3.3-volt PCI, and PCI-X slots)

Dialogic D/120JCT-LS PCIe and 5-volt PCI

Dialogic D/120JCT-LS-U Universal (compatible with 5-volt PCI, 3.3-volt PCI, and PCI-X slots)

Dialogic D/120JCT-LS Euro Universal (compatible with 5-volt PCI, 3.3-volt PCI, and PCI-X slots)

Dialogic D/320JCT-U Universal (compatible with 5-volt PCI, 3.3-volt PCI, and PCI-X slots)

1These cards all support the GSM 6.10 audio format and are therefore usable in IBM Lotus Domino Unified Communications Services environments.

2The D/160JCT-U and D/320JCT-U linecards must be installed in conjunction with an Aculab Digital Network Access Card.

2009-12-2020/24


Table 2 : Approved Brooktrout/Dailogic fax cards

TruFax PCI Cards TR1034 PCI Fax CardsTR114 PCI Analog Fax Cards

TruFax 100-R PCI Half Size 1 - Port Analog

TR1034+P2-2L-R analog fax card

TR114+P2C analog fax card*

TruFax 200-R PCI Half Size – 2 - Port Analog

TR1034+P4-4L-R analog fax card

TR114+P2L analog fax card*

TruFax 250-R PCI Half Size – 1 x BRI

TR1034+P8-H-E1-R Digital E1 card

TR114+P4C analog fax card*

TruFax 450-R PCI Half Size – 2 x BRI

TR1034+P16-H-E1-R Digital E1 fax card

TR114+P4D analog fax card*

TR114+P4L analog fax card*

TR114+uP1L analog fax card^

TR114+uP2D analog fax card

*Supported in both the 5-volt and universal PCI versions.

^For use only in the European nations that support the CTR-21 standard.

2009-12-2021/24


Table 3: MX-ONE Messaging V4.2 SP1 feature and integration capacityby number of voice ports installed.

16 or FewerVoice Ports

17–24Voice Ports

25–48Voice Ports

49–64VoicePorts

65–96Voice Ports

97–144Voice Ports

145-192 Voice Ports

Onboard fax ports (see Notes in minimum configuration requirements above)

up to 4 0 0 0 0 0 0

Text-to-speech channels up to 4 up to 8 up to 8 up to 16

up to 16

up to 24

up to 24

TUI-based Email Access Yes Yes Yes* Yes* Yes* Yes* Yes*†

Unified Messaging/Unified Communications

Yes Yes Yes* Yes* Yes* Yes* Yes*†

Integrations:

Inband (single) Yes Yes Yes Yes Yes* Yes* No

Serial outband (including NTDIU-based integrations—see Note 4; single)

Yes Yes Yes Yes Yes* Yes* No

Dialogic D/82–based (single)

Yes Yes Yes Yes Yes No No

T1-based (single) Yes* Yes* Yes* Yes* Yes* Yes* Yes***

E1-based (single) Yes* Yes* Yes* Yes* Yes* Yes* Yes*‡

Aastra SIP or IP based integration

Yes Yes Yes Yes** No No No

Other IP-based (single; see Note 6)

Yes Yes Yes Yes No No No

Multiple-switch Yes* Yes* Yes* Yes* Yes* No No

Processor group (defined below)

A A B C C D D

RAM in MB 512 512 512 512 1024 2048 2048

Notes:*Before you order this configuration, contact Aastra Sales Engineering to discuss the specific requirements of your system. **For Aastra SIP/IP based integration, ESU board only supports up to 24 channels. *** T-1 based QSIG integrations are supported only on systems of up to 184 ports.† These features are supported only on systems of up to 168 ports.‡ E-1 based integrations are supported only on systems of up to 180 ports.

2009-12-2022/24


7 Corrections

This release includes all the hot fixes since the release of MX-ONE Messaging V4.2 in April 2008. It therefore consolidates all prior fix packages and corrections delivered during this period. MX-ONE Messaging V4.2 SP1 corresponds to the AVST CX 7.92 build 235, which is being released at the same time.

2009-12-2023/24


© 2009 Aastra Technologies Limited. All rights reserved.

This document contains proprietary information, which is protected by copyright.

No part of this document may be reproduced or transmitted in any form or by any

means, electronic or mechanical, including photocopying, recording, or by any

information storage and retrieval system, or translated into another language,

without prior written consent of Aastra Technologies Limited, Concord, Ontario, Canada.

NOTICE

The information in this document is subject to change without notice.

AASTRA MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL,

INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY

AND FITNESS FOR A PARTICULAR PURPOSE. AASTRA shall not be liable for errors

contained herein nor for incidental or consequential damages in connection with the

furnishing, performance or use of this material.

Aastra Technologies Limited

Concord, Ontario, Canada.

2009-12-2024/24

Release Notes MX-ONE Messaging V4.2 Service Pack...

Documents

Transcript of Release Notes MX-ONE Messaging V4.2 Service Pack...