Release Notes

1 (20)

MX-ONE V.4.1 SP2

Contents

1Introduction

1.1Installation, MX-ONE V.4.1 SP2

1.2Verification

1.3Content

1.4Release Notes

2Prerequisites

2.1Hardware

2.2SUSE Linux software

3MX-ONE Telephony System V.4.1 SP2

3.1Installation

3.2Good to know

3.3New and changed functionality

4MX-ONE Manager Provisioning

4.1Environment

4.2Installation

4.3New and improved functionality

4.4Good to know

4.5Known Issues

5MX-ONE Manager Telephony System

5.1Environment

5.2Installation and Upgrade

5.3New and improved functionality

6MX-ONE New/Changed Hardware

6.1CMG or Solidus eCare used on ASU-E

7MX-ONE Solutions

7.1Aastra SIP DECT 2.1 OMM

7.2CMG 7.5

7.3SIP trunk interoperability with ACS

7.4One Box 5.0 SP1

7.5Solidus eCare 7.0 SP3

7.6Solidus eCare 7.0 SP3 HF318

7.7Enterprise Branch Node (EBN 7.0)

8MX-ONE Terminals

8.1Aastra 7444ip (Business model)

8.2Ethernet Gigabit Dongle for Aastra 7433, 7434 and 7444 ip terminals

8.3Improvements to the usability of the 67Xxi

8.4New functionality with Aastra743Xip and Aastra7446ip (5446ip) terminals

8.5Good to know

8.6Aastra Dect DT390 & 690 version 3.2.22

9Download

10MX-ONE 4.0 and 4.1 Software baseline

11Corrections

1Introduction

This document describes the release content and limitations of the MX-ONE release 4.1 SP2.

The MX-ONE 4.1 SP2 SW version is successor of the MX-ONE 4.1 SP1HF1& HF2.

1.1Installation, MX-ONE V.4.1 SP2

MX-ONE V.4.1 SP2 is intended for new customers, existing MX-ONE customers and TSW/MD110 migrating customers.

1.2Verification

The MX-ONE V.4.1 SP2 Field Trial has been performed in Sweden, UK, Germany, Austria, Netherlands, Belgium, Spain, Croatia, US, Canada, Serbia, South Africa, Brazil and Saudi Arabia.

1.3Content

MX-ONE V.4.1 SP2 contains the following:

  • Telephony Server 4.1 SP2
  • Manager Telephony Server 4.1 SP2
  • Manager Provisioning 4.1 SP2
  • Manager Availability 4.1 (same version as in MX-ONE SP1HF1)
  • PC-Regen 5.1 SP2 for MX-ONE
  • Aastra SIP DECT 2.1
  • One Box 5.0 SP1
  • CMG 7.5 with Speech Attendant 7.5
  • Updated FW list at ServiceSupportPlaza, Knowledge Base
  • Updated Application list at ServiceSupportPlaza, Knowledge Base
  • Updated CPI

For details about news and new functionality, please read the document Product News MX-ONE Version 4.1 SP2 (ASE/MXO/PLM/0199).

A CPI library is available on the Services Support Plaza Knowledge base.

Recovery DVDs will be delivered together with the MX-ONE V.4.1 SP2 release when ordered through the standard ordering process and after the CoMo 107 launch.

A Media Kit for SW only customers is delivered with the MX-ONE V.4.1 SP2 release when ordered through the standard ordering process, LZY 203187/1.

1.4Release Notes

For details about news and new functionality, please read Release Notes for each product included in MX-ONE V.4.1 SP2.

Release Notes are published on ServiceSupportPlaza, Knowledge Base for following products

  • MX-ONE 4.1 SP2
  • Solidus eCare 7.0 SP3
  • Aastra SIP-DECT OMM Software Version 2.1
  • One Box 5.0 SP1

2Prerequisites

Before the upgrade, please make sure that the system is stable and that you have read the instruction in the CPI library thoroughly.

2.1Hardware

The current MX-ONE Telephony Server HW is still supported, but system capacities can vary based on the hardware type and some field upgrades may be necessary to existing HW components (e.g. CPU memory, etc.).

For customers wishing to migrate from existing MD110 stackable and Telephony Switch installations, the existing HW is supported, although there are some configuration rules that must be applied based on the chassis type.

Migration is described in document Migrating MD110 to MX-ONE Version 4.1 16/1531-ASP 113 01.

The hardware must comply with the R-STATE SURVEY 1317-ASP 113 01in the CPI documentation.

You will find the list under General, Replacing Hardware and Product List MX-ONE.

2.2SUSE Linux software

SUSE Linux Enterprise Server 10 SP3 is required for this release.

Please be aware about procedure for SLES10 upgrades before the upgrade process is started. The SLES 10 SP3 package is available for download at ServiceSupportPlaza, Knowledge Base.

We recommend upgrade with latest SLES 10 SP3 patches available for download at ServiceSupportPlaza, Knowledge Base.

An upgrading customer must secure that Java 1.5 is installed before using the ICT tool. Java 1.5 can be extracted from the recovery DVD.

It is strongly recommended to make a safety back-up before upgrade or migration as no automatic roll-back is supported. This is also valid for Manager Telephony Server and Manager Provision (MTS/MP)

3MX-ONE Telephony System V.4.1 SP2

3.1Installation

3.1.1How to install

Use PC-Regen 5.1 SP2 build02 for MX-ONE to regenerate the data. Exchange data must be re-initiated when upgrading from 3.x systems.

Existing MX-ONE V.3.2 and V.4.0/4.1 customers can upgrade without uninstall to minimize downtime.

New and MX-ONE V.3.1 and prior customers shall use the recovery DVD.

Migrating MD110 and TSW customers should be considered as a new installation with new HW.

Any reconfiguration of an upgrading or migrating system should be treated as a new installation. PC-

Regen only supports data generation to an identical system as the original.

Detailed description for each scenario is available in the CPI library.

3.1.2Re-initiations GH, ACD and CTI members and groups

Due to enhancements (capacity increases) in GH, ACD/CTI the following actions must be done when upgrading to MX-ONE V.4.1 SP2.
GH, ACD and CTI groups initiated in the exchange have to be ended before upgrade and re-initiated after upgrade.

As members cannot be ended from the groups if they "logged in" you have to auth lock each ACD phone before you can remove the members. In a large installation this could take long time.

A simple solution is to restart program unit DER in all servers before ending - this resets the Agents to auth locked, and you can then end the members and groups. This shouldn't be a problem since you are about to upgrade the system & downtime is expected anyway.

[Regen the exchange data to make reinitiating groups easier.]

1) Restart DER in all servers

2) End all GH, ACD and CTI group members

3) End all GH, ACD and CTI Groups

4) Dump system

5) Upgrade to SP2 as usual

6) Reinitiate all GH, ACD and CTI Groups

7) Reinitiate all Members in GH groups, ACD groups and CTI groups

3.1.3Re-initiations Parallel ringing

If user experience problem with parallel ringing after upgrading to MX-ONE 4.1 SP2, the suggested workaround is to remove and re-insert it by using the command parallel_ringing.

3.1.4Re-initiations T1/E1 trunks

When upgrading from MX-ONE V.4.0 versions (SP0 and SP1) following actions must be performed:
Interface changes have made it necessary to remove and reinitiate all T1 trunks. This applies for TLU77, MGU, and EMG. Also, for the MGU board, as the E1 board identity will change, from 57 (TLU76) to 125 (PRI), when adding the Service Pack 1 software, all virtual trunk boards must be removed. Then the MGU firmware should be updated. When the MGU FW is updated, the Telephony System should be updated to MX-ONE 4.1 SP2. After this, a board scan shall be performed, and a re-initiation of the trunk boards be made.

Actions

  1. Run board_list. Locate the board positions for all assigned trunks with Boardid 57 (E1) and 71 (T1). For example, Boardpos 1A-1-00 is found with Boardid 57.
  2. Run syedp:bpos=...; for the found board positions to find the Route and Trunk identities.
    For example, syedp:bpos=1A-1-00; could show ROU/TRU from 11/001-0001 to 11/001-0015.
  3. End the trunk function for all individuals. Use the data from step 2.
    Run roeqe:rou=, tru= ; Ex. roeqe:rou=11,tru=1-1&1-15;
  4. Remove all trunk boards on the MGU boards by removing the boards.
    Run board_config -remove –bpos
  5. Remove all T1trunk boards on the EMG.
    Run board_config -remove -bpos
  6. Remove all TLU77 boards in the Media Gateway Classic.
    Run board_config -remove –bpos
  7. For each MGU board, upgrade the firmware.
    Run board_sw -gateway -netload -path –host
  8. For each MGU board, activate the firmware.
    Run board_sw -gateway –activate
  9. Make a board scan to detect the hardware.
    Run board_config –scan
  10. Reinitiate all the trunks. Use the data from step 2
    Run roeqi:rou=, tru= ;

3.1.5SLES 10 SP3 upgrade

Read the readme file on SLES10 SP3 DVD on how to set up an NFS server.

IMPORTANT:

The MX-ONE Telephony system will be out of order during the SLES SP3 upgrade; no telephony traffic will be possible.
The system will be shutdown before the upgrade when the prepare_upgrade.sh script is executed.

Update_instruction and prepare_upgrade.sh script is found in below folder in server node folder:/home/eri_sn_admin/install_sw/prepare_sles_upgrade/

3.1.6EPN must be removed before upgrade

Extra Paging Numbers must be ended before upgrade from MX-ONE V.4.0 versions (SP0 and SP1). Re-Initiate EPN after upgrade.

3.2Good to know

3.2.1IPLU in MGU gateways

IPLU cannot co-exist with the MGU in same server/chassis. But, as the MGU contains all IPLU functionality, there is no need for IPLU-boards in an MGU Gateway configuration.

3.2.2Rollback is not supported to V3.2

Although it is possible to execute the upgrading script when upgrading a site from MX-ONE V3.2 to MX-ONE V4.1 SP2, roll back is not supported.

3.2.3Parameter VARC D8 for TLP60

Parameter D8 in VARC for TLP60 has been changed in MX-ONE 4.1. For correct values for D8 read the CPI documentation.

3.2.4Change behavior of Call_list command

In previous MX-ONE 4.0 and MX-ONE 4.1 versions it was possible to program a non-generic extension (analog, digital, etc) with a call_list command that included the customer parameter (a customer number greater than zero).

In MX-ONE 4.1 SP1 this has been changed. The customer number parameter in the call_list command shall only be used when programming personal-number lists for generic extensions (virtual, DECT, IP, Mobile Extension)

Existing personal-number lists for non-generic extensions that has been programmed with a customer-number needs to be removed (it is still possible to use the customer parameter during the removal procedure) and re-initiated again without specifying a customer number. This can be done before or after upgrading to MX-ONE 4.1 SP2

3.3New and changed functionality

3.3.1Boss/Secretary PEN key enhancement

The PEN key is used for activating or deactivating the Boss/Secretary feature by pressing the predefined PEN key on the IP terminal. The active list is shown in the terminal display. When activating or deactivating the PEN function (for Boss-Secretary scenarios) it is possible to select which list to use, for example to define the default distribution behavior when the PEN key is not active. The call list numbers are given in extension_key command

3.3.2CSTA V3 Improvements

These are improvements and corrections to the CSTA V.3call offer functionality.

3.3.3HLR + Server Redundancy in the same system

The co-existence of HLR and N+1 type redundancy in the same logical system including support for local and remote gateways. A new system license for HLR Redundancy is implemented. Customer who wants to use this function or use it in their existing system must order new license before upgrade to get function working after upgrade to MX-ONE 4.1 SP2.

3.3.4TLS security for H.323 trunks

It is possible to do TLS signaling encryption on H.323 networking lines.

3.3.5SOM corrections

There are improvements and fixes to the SOM functionality – a.k.a. lawful intercept, mainly used in Russia and certain European countries such asCroatia, etc.

3.3.6Name on T1 trunk based on ANSI T1.641-1995

Name on T1 is a general requirement for North America, based on ANSI T1.641-1995. However, in this case we are referring to the specific DMS-100 type implementation of Name on ISDN T1.

New unix style commands “name” for initiating, printing and ending name.

3.3.7Free on busy option for multiple terminal services

When a user has several terminals (and thus has the multiple terminal services) it is possible to seize/ring idle terminals, even if the user is already occupied on one terminal.

A new parameter controlling the user busy behavior has been created in the generic extension service profile (ext-serv parameter of the extension_profile command). No support for ATS, DTS, CAS

3.3.8Blocking of Common Authorization Code for certain extensions

When the ‘common authorization code’ (non directory associated authorization codes) feature is available in the system, it is now possible to block certain individual extensions from using the codes.

A new parameter which controls if the extension shall be allowed to use common authorization codes, has been created in the generic extension service profile (extension_profile command). No support for ATS, DTS, CAS

3.3.9Support for Service codes (SC) without using * and #

Possible to use numeric digits (without A and B) in comand number_initiate -numbertype sc-xxx.

3.3.10Forward Switching in Additional Category for Route Data (ADC) parameter

Forward switching D28 in parameter ADC defines if forward switching shall be done for all redirection services requested from trunks.

3.3.11Increase of members per server in hunt group

Number of Group hunt members per server is increased to 1000

4MX-ONE Manager Provisioning

4.1Environment

Manager Provisioning Server:

  • SUSE Linux Enterprise Server 10 Service Pack 3
  • JBoss 4.2 (included with the Manager Provisioning media kit)

Manager Provisioning Clients:

  • Microsoft Internet Explorer 7.0
  • Microsoft Internet Explorer 8.0
  • Mozilla Firefox 3.0

SQL Server:

  • Postgre SQL 8.1 (included with the Manager Provisioning media kit)

MX-ONE Messaging:

  • MX-ONE Messaging 4.2
  • MX-ONE Messaging 4.2 SP1
  • One Box 5.0
  • One Box 5.0 SP1

MX-ONE Telephony Server:

  • MX-ONE Telephony Server 3.2
  • MX-ONE Telephony Server 3.2 SP1-SP5
  • MX-ONE Telephony Server 4.0 SP1
  • MX-ONE Telephony Server 4.1
  • MX-ONE Telephony Server 4.1 SP1
  • MX-ONE Telephony Server 4.1 SP1 Hotfix 1
  • MX-ONE Telephony Server 4.1 SP2

CMG Server:

  • CMG Server 2007 SP3-SP5
  • CMG Server 7.5

4.2Installation

4.2.1Prerequisites for Manager Provision Installation

The telephony server software must be installed.

Manager Provisioning must have the same software version (for example, 4.1 SP2) as Manager Telephony System and the Telephony Server, if installed on the same server. For more information, see INSTALLING AND CONFIGURING MX-ONE TELEPHONY SYSTEM.

4.2.2How to install

Copy the bin file to the Manager Provisioning server and execute it. The script will automatically stop and upgrade an earlier Manager Provisioning version if one is installed.

If the Telephony Server and Manager Telephony System are upgraded in association with the Manager Provisioning upgrade, it will be needed to execute the mp_config linux command and to select the Manager Provisioning Repair option to get the Manager Provisioning data back into the database. Make sure that you make a backup in Manager Provisioning first. The reason is that the Manager Telephony Server upgrade will clean the database that Manager Provisioning also uses. This applies only when Manager Provisioning and Manager Telephony System are installed on the same server.

For further instructions, please see the installation and upgrade documentation in the O&M documentation.

You use the mp_uninstall command to uninstall MP, but if the installation fails before it is completed and mp_uninstall cannot be executed, this is how you revert to restart the installation:

1) list RPMs: rpm -qa | grep eri_mp

2) remove theMP RPM: rpm -e <rpm-name>

Note 1:
Make sure, in the Subsystem task, to adjust the version fields for the Telephony Server, CMG and Messaging Server after upgrading the different parts of the system. Otherwise you will not get the new functions in the extension task pages and the interface to the subsystems may fail.

Note 2:
1. The installation/upgrade shall be executed with the “eri_sn_admin” linux user account.

2. If you need to make a reinstallation of the Telephony Server / Manager Telephony Server, unlike previous instructions, you DO NOT need to uninstall Manager Provisioning first if it runs on the same server.

Note 3:

The backup and restore function in the script mp_config has been updated. It is separated from the GUI backup and restores function. The GUI backup and restore is a safety backup that is only valid as long as you are running the same version of Manager Provisioning. In mp_config you can make a backup that will work also on an upgraded version of MP. That means that mp_config can restore an earlier version of the backup file, however not earlier than 4.0 SP1. Also, when uninstalling Manager Provisioning, it will automatically create a backup of the same type as the mp_config script.

4.2.3Install with ICT and authentication MP

When you install with ICT and choose authentication method MP you have to use http.

You can later change to https as described in ALEX document Manager provisioning =>Installation instructions 9/1531-ANF 90115 chapter 15.2

4.3New and improved functionality

4.3.1Available Extensions Task

A new task has been added to MP where you can list available extensions. There are two kinds of available extensions: “Free extensions” that are defined in the number series but not yet initiated as an extension, and there are “Unassigned extension numbers” that are existing extensions that are not associated with a User in MP. Description text can be added to each listed number, as well as the free time is shown since the extension was deleted or unassociated.

4.3.2Shortcuts from MP to MTS

In the extension task, the add and change pages, there is a shortcut field at the top of the page where you quickly can navigate to a selection of MTS tasks. By selecting a shortcut, a window will open with MTS and you will get automatically logged in and navigated to the selected task, providing you have the correct privileges (“MTS: Manage extension data” in your MP security profile if you are using the MP Login Method).

4.3.3Wildcards in Extension and Mailbox tasks

You can use wildcard in searches in the Extension and Mailbox task. An asterisk can be used at the end of the searched number, e.g. 10*

4.3.4Bulk Add of Extensions

The Import from CSV task has been extended to also manage additions of extensions and mailboxes to the imported users. A couple of CSV templates with instructions are available on the import page, which you can download and open in e.g. Excel or CSVed. When you are done editing the CSV file, you upload it, double check that all columns are correctly defined and execute it. All types of extensions can be created, as long as there are templates predefined for it. The dynamic data you need to fill in on the CSV file is presented on the import page.

4.3.5MP Backup Number Limitation

The backup task now limits the number of MP backups to 10. This became needed after introducing scheduling in the last release to limit the number of backups and saving disk space. This has no impact on the MTS and TS backups, it is only for MP’s own database.

4.3.6Terminal Image on the Function Key Page

Terminal Image on the Function Key Page
On the function key page you can see an image of the selected terminal. That way it is easier to verify that the correct terminal is selected.

4.3.7IP Terminal Link in the Self Service Page

IP Terminal Link in the Self Service Page
As an end user you can log on to MP and when listing your extensions get links to the terminals own web pages where additional phone configuration can be done.