mx-one v.4.1 migration oi 11

Ordering InformationAastra MX-ONETM Version 4.1 migration and upgrade from MD110/Telephony Switch and MX-ONETM V.2, V.3, V.3.1 and V.3.2

Aastra Telecom Sweden AB Box 42214, SE-126 17 Stockholm, SwedenTel +46 8 568 67000www.aastra.com

Date: 2011-07-04Doc no.: ASE/MXO/PLM/0093/EN/0/11Author: C. Brorsson

Revision Information2009-12-15 A First issue2010-01-13 B Updated for CoMo R1002010-04-15 C Updated for CoMo R1012010-04-29 D Updated for CoMo R1022010-05-31 E Updated for CoMo R1032010-06-24 F Updated for CoMo R1042010-08-26 G Updated for CoMo R1052010-11-03 H Updated for CoMo R1062011-02-16 J / 0/9 Updated for CoMo R107, new template2011-04-14 0/10 Updated for CoMo R107C2011-07-04 0/11 FABs removed.

2 (28)

Contents

1 General......................................................................................................................5

2 Migration...................................................................................................................5

2.1 Hardware Migration............................................................................................................................ 5

2.1.1 Hardware compatibility in MX-ONETM V.4.1.........................................................................................................5

2.1.2 Hardware delivered with a MD110/TSW system migration................................................................................6

2.1.3 Hardware to be ordered separately......................................................................................................................6

2.2 Software migration............................................................................................................................. 6

2.2.1 Licenses included in the migration of the basic system...................................................................................6

2.2.2 Software-licenses to be ordered separately........................................................................................................6

3 Migration ordering description:..............................................................................7

4 Basic system contents, standard system..............................................................7

5 General......................................................................................................................7

5.1 Upgrade or Migrate............................................................................................................................. 7

6 Upgrade.....................................................................................................................8

6.1 Software upgrade................................................................................................................................ 8

6.2 Upgrade to Multi Gateway.................................................................................................................. 8

6.2.1 Gateway SW key....................................................................................................................................................8

6.2.2 Multi gateway option – MGU board......................................................................................................................8

6.2.3 Server replacement................................................................................................................................................8

7 Migration...................................................................................................................9

7.1 Prerequisites for migration to MX-ONETM V.4.1 accepted................................................................9

7.2 Selection of BC release...................................................................................................................... 9

7.3 System licenses and SW.................................................................................................................... 9

7.3.1 System SW............................................................................................................................................................. 9

7.3.2 System SW key......................................................................................................................................................9

7.3.3 Gateway SW key....................................................................................................................................................9

7.3.4 Server SW key........................................................................................................................................................ 9

7.4 Software licenses and Ports............................................................................................................10

7.4.1 Ports...................................................................................................................................................................... 10

7.4.2 Ports and LIMs.....................................................................................................................................................11

7.4.3 ACD....................................................................................................................................................................... 11

7.4.4 Optional Features................................................................................................................................................11

7.5 System............................................................................................................................................... 13

7.5.1 Group Switch........................................................................................................................................................ 13

7.5.2 Basic hardware, migration to traditional system..............................................................................................13

7.5.3 Basic hardware, migration to Multi GW.............................................................................................................14

3 (28)

7.5.4 Server options......................................................................................................................................................14

7.5.5 Redundancy......................................................................................................................................................... 16

7.6 Management system......................................................................................................................... 16

7.6.1 Management system for operators....................................................................................................................17

7.7 Software Maintenance...................................................................................................................... 17

7.8 HW replacement for upgrading/migration......................................................................................18

7.8.1 FW, Set of PROMs for migration of the extension boards...............................................................................18

7.8.2 Boards................................................................................................................................................................... 18

7.8.3 FW, Set of PROMs for migrating the boards.....................................................................................................19

7.9 Additional upgraded HW and/or FW................................................................................................19

7.9.1 HW (Boards) and/or FW (PROMs) for extension boards..................................................................................19

7.9.2 HW (Boards) and/or FW (PROMs) trunk or tie line boards..............................................................................20

7.9.3 HW (Boards) and/or FW (PROMs) for the other boards...................................................................................23

7.9.4 HW upgrades (memory upgrades).....................................................................................................................24

7.9.5 Back-up package for HP server..........................................................................................................................24

7.9.6 Support fronts etc................................................................................................................................................24

8 Licenses..................................................................................................................26

8.1 Entering licenses.............................................................................................................................. 26

8.1.1 Migration from BC10, BC11, BC12 or TSW to MX-ONETM TSE.........................................................................26

8.1.2 Migration from a release earlier than BC10 to MX-ONETM TSE........................................................................26

8.2 License overview................................................................................................................................ 26

4 (28)

1 General This ordering information document describes how to order migration from various MD110 releases and TSW to MX-ONETM Telephony System, Telephony Server Version 4.1 (hereafter named MX-ONETM V.4.1 in this document).

Migration means to lift the MD110/TSW system from the present software release to the MX-ONETM V.4.1.

The document also describes upgrading from MX-ONETM Version 2, Version 3, Version 3.1 or Version 3.2.

The price for migration the MD110/TSW basic system depends on the number of ports in the system and the release the system is upgraded from.

Migration of hardware not included in the basic system may be charged separately.

Migration is ordered using Aastra Plan.

2 MigrationThe upgrade of a system consists of several parts:

Determine the release to migrate from (BC7 and earlier, BC8, BC9, BC10, BC11, BC12 or TSW)

Determine the type and number of ports to upgrade (By using PCREGEN)

Determine the hardware that is needed for the upgrade(By using Aastra Plan)

Determine the features to be converted to licenses.(Only when migration from BC9 or earlier)

To determine the migration price, it is in most cases sufficient to know the number of ports that are to be migrated. But before placing an order all of the above steps have to be performed.

In the upgrading module of Aastra Plan, there are a number of questions that will configure the order with the correct hardware and software for the particular configuration.It is also possible to order special updates (new boards or new firmware) for existing hardware. These updates are not required for the system to operate flawless in MX-ONETM V.4.1.

The migration ordering must be done using the Aastra Plan.

2.1 Hardware Migration

All equipment necessary for the migration of the basic system hardware is delivered in a so-called Basic System Migration. The Basic System Migration contains firmware (PROMs) and/or hardware (boards) needed for the basic system to run flawless after the software migration.Some phased out hardware, like old basic system boards, IOU, SSU and BSU, as well as LPU5 and LSU, cannot be used in MX-ONETM V.4.1 and will be replaced as part of the migration.Some phased out hardware, like extension boards ELU5 and ELU25, can be used in MX-ONETM V.4.1 but we recommend that they are replaced with latest available boards, while the phased out boards are no longer supported from a service point of view, and we therefore can not guarantee their full functionality.

2.1.1 Hardware compatibility in MX-ONETM V.4.1

All boards are supported in the same building practice as they first were delivered in new sales.To place boards in other building practices may result in malfunctioning, or even worse, damaging the system.

5 (28)

The compatibility of hardware depends on the software level as well as other connected hardware.Supported hardware for each Software release is listed in Hardware status ASP 113 01, 1317-ASP 113 01The document lists Backplanes, Boards and other Hardware supported by the system.

The document states the boards that are allowed to be put in the new building practice Media Gateway Classic. Media Gateway Classic building practice consists of the backplane LBP22.These boards are also backward compatible with older building practices, as described in the document Installing MX-ONETM, 6/1531-ASP 113 01.

2.1.2 Hardware delivered with a MD110/TSW system migration

The Basic System Migration handles the hardware included in the basic system as defined above.Hardware not included in the basic system (non-basic hardware), is not normally handled by the Basic System Migration.

The hardware migration is divided into 4 groups: LPU5 and LSU are replaced by other servers and LSU-E The Group Switch is optional and the GJUL4 can be replaced by IPLU. NIU/NIU2, AAU and HDU are removed and no longer used Other Basic System HW is updated

2.1.3 Hardware to be ordered separately

The equipment needed for migration of all other non-basic hardware must be specified and ordered separately in Aastra Plan.

Upgrade of hardware specified as “Additional “, is not needed for the migration.This is an option for the customer to refresh the hardware to the latest available status.

2.2 Software migration

2.2.1 Licenses included in the migration of the basic system

Basic system migration includes existing MD110/TSW software licenses.

When migrating BC releases earlier than BC10, the necessary licenses for the existing software, the number and type of existing extensions, trunks, tie lines and optional features must be specified in Aastra Plan. Based on this input, a new license file for MX-ONETM V.4.1 will be generated.For more details see the section Licenses.When migrating from BC10, BC11, BC12 or TSW, the license file is already defined and will be automatically upgraded and replaced by a new license file for MX-ONETM V.4.1. While not all licenses in an existing system may be used, it is now possible to decrease the number of port licenses while migrating.The License file will be updated according to the number of extensions and external ports specified.It is not possible to increase the number of licenses, this is done as add-on sales.

2.2.2 Software-licenses to be ordered separately

Migration of software licenses for ACD-agents must be specified separately in Aastra Plan.

Migration of all external applications must be ordered and will be charged separately.

6 (28)

3 Migration ordering description:Migration is always done using Aastra Plan. This paragraph describes how to perform migration ordering using Aastra Plan.

The migration of an MD110/TSW system is ordered primarily by stating the existing system release and the number of system ports, with a minimum of 48 ports (MD110). The number of system ports is defined as the sum of extension ports (analogue + digital + cordless + mobile extensions + IP extensions), trunk ports (analogue + digital) and tie line ports (analogue + digital + IP).

These ports are calculated by using the PCREGEN functionality in SAM-Toolbox.

Secondly questions around existing functionality (in releases earlier than BC10) and hardware must be answered. The questions vary depending on original SW release, building practice and requested functionality. If the existing SW release is BC10, BC11, BC12 or TSW, the number of questions is substantially reduced, since the needed information is already available in the existing license file.

4 Basic system contents, standard systemMX-ONETM version 4.1, as supplied in basic format, has the following contents:The functions listed below, may in different MD110 releases have had license numbers, but are now unlicensed.

Name and number log Original A-number Dial by name Authorization code Choice of language MX TS Personal number RTU 1 user MX TS Free seating service Compressed 16 kbit/s switching & multiplexing Centralized Operator Centralized voice mail MX TS Enhanced networking facility RTU 1 system MX TS Enhanced networking facility RTU 1 system MX-ONETM Networked ACD RTU 1 system Least Cost Routing (LCR) Multi PBX / Multi customer PBX Traffic recording Message diversion Account code MX TS repeated individual diversion RTU 1 user MX TS Application link RTU 1 Ethernet session MX TS SMDR/CIL RTU 1 Ethernet session MX TS Electronic mail RTU 1 Ethernet session MX TS Interception RTU 1 Ethernet session MX TS Voice mail RTU 1 Ethernet session Dialed Number Information Service (DNIS)

5 General

5.1 Upgrade or Migrate

By selecting Migrate and Migration to Release = V.4.1, MD110 and TSW can be migrated to MX-ONETM V.4.1.By selecting Upgrade and Upgrade to release = V.4.1, earlier versions of MX-ONETM can be upgraded.

7 (28)

6 Upgrade

6.1 Software upgrade

Upgrade from MX-ONETM Version 2 or higher is done within the Software maintenance agreement.

Remark Product No Designation Q

SWM/FAB1060950/140 SW Maintenance package MX-ONETM V.4.0 1 / systema For upgrade to V.4.1

6.2 Upgrade to Multi Gateway

It is possible to upgrade to Multi Gateway, meaning that the system can be collapsed and one server can handle up to 15 gateways.

6.2.1 Gateway SW key

While each LIM license is automatically replaced by a server license, each gateway will get its own license.


FAL 104 9028/1 MX TS GW SW key 1/gateway

6.2.2 Multi gateway option – MGU board

For subracks in BYB 501 (Media Gateway Classic) the LSU-E boards can be replaced by the new MGU board.


ROF 137 6304/1 MGU 1/gatewaySXK 106 1040/05 MGU front 1/gateway

a TSR 482 0211/2400 RJ45-RJ45 straight 2/gatewayTSR 899 135/1 Adapter USB -> 1xSeriell RS232 DB9HA 1/system

a Can be replaced by TSR 482 0211/20M, by choice

6.2.3 Server replacement

As an option, old ESU servers can be replaced by an HP server or an ASU server.

HP ServerRemark Product No Designation Q

KDU 137 460/8 MX TS Telephony Server 4.x DL360 Gx 1

ASU-E board


ROF 137 6307/1 ASU-E board incl ComExpress 1EN/LZT 103 100/21 Customization Telephony Server, ASU-E board 1

a TSR 482 0211/2400 RJ45>RJ45 straight 1a Can be replaced by TSR 482 0211/20M, by choice

8 (28)

Hard disc drive (HDD) for ASU-E serverRemark Product No Designation Q

NTM/KDR 509 103/1 HDD 2,5 inch incl sledge for ASU-E / ASU server 1 / server

Solid state disc (SSD) for ASU-E server


NTM/KDR 509 104/1 SSD 2,5 inch incl sledge for ASU-E / ASU server 1 / server

7 Migration

7.1 Prerequisites for migration to MX-ONETM V.4.1 accepted

While not all MD110/TSW configurations can be migrated to MX-ONETM Version 4.1, it is very important that the configuration of the existing system and the future need is reviewed before the migration.Supported features, functions and hardware products, and the comparison with different MD110/TSW/ MX-ONETM releases can be found in document ASE/MXO/PLM/0089/EN.

7.2 Selection of BC release

The configuration alternatives vary depending on the migration starting point (BC Release).For migration of licensed systems (BC10, BC11, BC12 and TSW), some questions are not shown, while the licenses are generated automatically.

7.3 System licenses and SW

7.3.1 System SWRemark Product No Designation Q

LZY 203 186/1 MX-ONETM 4.x RecDVD 1/systemLZY 203 187/1 MX-ONETM 4.x Media kit 1/system

7.3.2 System SW key


FAL 104 9026 MX TS Telephony System 4.x 1 / system

7.3.3 Gateway SW key


FAL 104 9028/1 MX TS GW SW key 1 / gateway

7.3.4 Server SW key


FAL 104 5849 MX TS Telephony Server 1 / gateway

7.4 Software licenses and Ports

7.4.1 Ports

Extension ports

The existing number of extensions are entered. Remark Product No Designation Q

FAL 104 5303/1 MX TS Analog extension RTU 1 port 1 / extension

9 (28)

FAL 104 6523/1 MX TS Analogue Extension CLIP RTU 1 User 1 / FAL1045303FAL 104 6515/1 MX TS CAS extension RTU 1 port 1 / extensionFAL 104 5502/1 MX TS Digital extension RTU 1 port 1 / extensionFAL 104 6625/1 MX TS Cordless extension RTU 1 user 1 / extensionFAL 104 5302/1 MX TS IP extension RTU 1 port 1 / extensionFAL 104 5477/1 MX TS Mobile extension RTU 1 port 1 / extensionFAL 104 6627/1 MX TS ISDN S0 extension RTU 1 port 1 / extensionFAL 104 6729/1 MX TS Virtual extension SW key 1 user 1 / extensionFAL 104 5504/1 MX TS Operator extension RTU 1 port 1 / extension

Trunk ports

The existing number of different trunk lines are entered in the system.Remark Product No Designation Q

FAL 104 6508/1 MX TS Analogue trunk line RTU 1 port 1 / trunk lineFAL 104 6510/1 MX TS CAS trunk line RTU 1 port 1 / trunk lineFAL 104 6512/1 MX TS DASS2 trunk line RTU 1 port 1 / trunk lineFAL 104 5309/1 MX TS Public ISDN user side RTU 1 port 1 / trunk line

Tie line ports

The existing number of different tie lines are entered in the system.Remark Product No Designation Q

FAL 104 6514/1 MX TS DPNSS trunk line RTU 1 port 1 / tie lineFAL 104 5310/1 MX TS ISDN tie line RTU 1 port 1 / tie lineFAL 104 5307/1 MX TS IP trunk RTU 1 port 1 / tie lineFAL 104 5308/1 MX TS IP Networking Enhanced Services RTU 1 port 1 / IP TrunkFAL 104 6513/1 MX TS CCSS7 trunk line RTU 1 port 1 / tie line

10 (28)

Basic port SW keys needed for the migrationRemark Product No Designation Q

FAL 104 6857P7V4 MX TS Port Migr =< BC7 - TSE V.4 1FAL 104 6857P8V4 MX TS Port Migr BC8 - TSE V.4 1FAL 104 6857P9V4 MX TS Port Migr BC9 - TSE V.4 1FAL 104 6857P10V4 MX TS Port Migr BC10 - TSE V.4 1FAL 104 6857P11V4 MX TS Port Migr BC11 - TSE V.4 1FAL 104 6857/P12V4 MX TS Port Migr BC12 - TSE V.4 1FAL 104 6857TSWV4 MX TS Port Migr TSW - TSE V.4 1

7.4.2 Ports and LIMs

DTMF receiver for Mobile Extension (For BC11 migration only)

The TMU with 4 DTMF receivers used in BC11 for Mobile Extension has in TSE V.4.1 been replaced with SPU4 with 32 DTMF receivers per board. This replacement is mandatory while TMU, as DTMF receiver for Mobile Extension, is not supported in MX-ONETM V.4.1.

The following table shows the dimensioning of TMU vs. SPU4. 1-7 TMU replaced with 1 SPU48-14 TMU replaced with 2 SPU415-21 TMU replaced with 3 SPU422-24 TMU replaced with 4 SPU4

Note: Only TMU boards used for Mobile Extension shall be replaced. The maximum number of TMU’s for replacement is related to the number of ports. This sales object contains the license and the board for the DTMF Receiver, SPU4. The SPU4 is used only with Mobile and Fixed Remote Extension.


ROF 137 5430/11 SPU4 1CAA 158 0023 FW, DTMF Receiver 1

7.4.3 ACD

The sales objects to be used when ordering migration of ACD agents are listed below.


FAL 104 6622 MX TS ACD RTU 1 Agent 1 / agent

7.4.4 Optional Features

MFC equipment Remark Product No Designation Q

FAL 104 6511/1 MX TS MFC RTU 1 device 1 / device

Failure through transfer – Trunk through connection


FAL 104 6774/1 MX TS Failure trunk through connection RTU 1 port 1 / trunk line

Call metering on analog trunk lines


FAL 104 6509/1MX TS Call metering on analogue trunk line RTU 1 port

1 / trunk line

11 (28)

Networking functionality DPNSS


FAL 104 5312 MX TS Enhanced networking facility RTU 1 system1 / QSIG tie line1 / VPN trunk line1 / DPNSS tie line

Networking functionality Q-sig


FAL 104 5312 MX TS Enhanced networking facility RTU 1 system1 / QSIG tie line1 / VPN trunk line1 / DPNSS tie line

Virtual private network


FAL 104 6733/1 MX TS Virtual private network RTU 1 / trunk line

Voice compression for FAX III recognition


FAL 104 6631/1 MX TS VC FAX III recognition RTU 1 port 1 / user

Music on hold


FAL 104 6730/1 MX TS Music on hold RTU 1 MOH port 1 / MOH port

DISA


FAL 104 6731/1 MX TS DISA number RTU 1 system 1 / system

Internal RVA


FAL 104 5505 MX TS Integrated RVA RTU 1 port1 / internal RVA port

External RVA


FAL 104 6732/1 MX TS external RVA RTU 1 port1 / external RVA port

12 (28)

PagingRemark Product No Designation Q

FAL 104 6628/1 MX TS paging loop RTU 1 port 1 / portFAL 104 6758/1 MX TS paging parallel RTU 1 port 1 / portFAL 104 6629/1 MX TS paging serial RTU 1 port 1 / port

7.5 System

LIMs: This is the total number of LIMs in the system.

7.5.1 Group Switch

In case of keeping the Group Switch: Enter the total quantity of Group Switch Links that in the system.

In case of replacing the Group Switch: Enter the number of GS Links that shall be replaced. (each LIM in the system must have at least one IPLU).


ROF 137 5067/1 IPLU 1 / GS LinkTSR 482 0211/2400 RJ45>RJ45 straight 1 / IPLU

7.5.2 Basic hardware, migration to traditional system

Migration to LSU-E

Sales objectsRemark Product No Designation Q

a ROF 137 6302/1 LSU-E 1 / LIMb ROF 137 6302/11 LSU-E 1 / LIMa TSR 491 411/1850 LSU(E) – DSU(n) 1 / Magazinea TSR 491 409/100 LSU-E -> DSU 1 / LIMb, c TSR 491 409/100 LSU-E -> DSU 2 / Subrack Ab, c TSR 491 411/1050 Connection cable 2/ Subrack B b, d TSR 491 406/1850 Connection cable 2/ Subrack B1

TSR 432 95/1200 100Base-TX, Cross-Over cable 1 / LIMa For mounting in Stackable or olderb For mounting in Media Gateway Classicc For connection to DSU/4d For connection to DSU/14

Migration to MGU


ROF 137 6304/1 MGU 1/gatewaySXK 106 1040/05 MGU front 1/gateway

a TSR 482 0211/2400 RJ45-RJ45 straight 2/gatewayTSR 899 135/1 Adapter USB -> 1xSeriell RS232 DB9HA 1/system


13 (28)

7.5.3 Basic hardware, migration to Multi GW

Migration to LSU-E


a ROF 137 6302/1 LSU-E 1 / gatewayb ROF 137 6302/11 LSU-E 1 / gateway

ROF 137 5067/1 IPLU 2 / gatewayTSR 491 409/100 LSU-E – DSU (old to new), shortTSR 491 411/1850 LSU-E – DSU (old to new), longTSR 491 406/120 LSU-E - DSU (new to new), 120 cmTSR 491 406/1850 LSU-E – DSU (new to new), 1850 cmTSR 432 95/1200 100Base-TX, Cross-Over cable 1 / gatewayTSR 482 0211/400 RJ45>RJ45 straight 1 / IPLU

a For mounting in Stackable or olderb For mounting in Media Gateway Classic

Migration to MGU, 1st gateway


ROF 137 6304/1 MGU 1 SXK 106 1040/05 MGU Front 1

a TSR 899 135/1 V24 -> USB Cable 1 / Systemb TSR 482 0211/2400 RJ45>RJ45 straight 2

a One per systemb Can be replaced by TSR 482 0211/20M, by choice

Multi GW migration Package 2nd to 15th GW


ROF 137 6304/1 MGU 1 SXK 106 1040/05 MGU Front 1

a TSR 482 0211/2400 RJ45>RJ45 straight 2 a Can be replaced by TSR 482 0211/20M, by choice

7.5.4 Server options

ASU-E boardRemark Product No Designation Q

ROF 137 6307/1 ASU-E board incl ComExpress 1EN/LZT 103 100/21 Customization Telephony Server, ASU-E board 1


14 (28)

ASU serverRemark Product No Designation Q

BFD 761 45/2 LBP25 1U chassis 1ROF 137 6307/21 ASU-E board incl ComExpress 1EN/LZT 103 100/21 Customization Telephony Server, ASU-E board 1

a TSR 482 0211/2400 RJ45>RJ45 straight 1RPM 945 3xx Power supply cord 1TSR 902 0279/2000 Power cable 48V, 4-pol 1NTM 144 264 Mounting set 4+4 screw+nut 1


Hard disc drive (HDD) for ASU-E serverRemark Product No Designation Q

NTM/KDR 509 103/1 HDD 2,5 inch incl sledge for ASU-E / ASU server 1 / server

Solid state disc (SSD) for ASU-E server


NTM/KDR 509 104/1 SSD 2,5 inch incl sledge for ASU-E / ASU server 1 / server

Mounting set for ASU server in Stackable


NTM 144 271 MX HW Mounting plate Server

Server farm


BFD 509 08/4 MX Fan 1BFD 761 40/1 MX Magazine LBP22 Classic 1TSR 903 021/5000 Power cable 48V 5m 2TSR 903 021/12M Power cable 48V 12m 1NTM 144 264 MX HW set of 4 screws & 4 nuts 1NTM 144 262 MX Air plate upper and lowerNTM 144 263 MX Air plate front and rearSXK 106 1020/01 MX Magazine Front 20mmSXK 106 2097/1 MX Plug for alarm in Fan2 1TSR 902 0274/2200 MX Cable Fan2 – Alarm 2.2m 1TSR 902 0277/2000 MX Cable DC/DC-AC/DC free end 1

HP server


KDU 137 460/8 MX TS Telephony Server (HPDL360Gx) 1

15 (28)

7.5.5 Redundancy

Network and Server RedundancyMX-ONETM provides network redundancy for inter-LIM signaling. A back-up server can also be installed (N+1).Redundancy is available for MX-ONETM Telephony System. One redundant server can handle a maximum of 10 Telephony Servers. For server choices, see section .

Network RedundancyRemark Product No Designation Q

FAL 104 6858 MX TS Network Redundancy (system) 1TSR 432 97/1000 Cable for LSU-E 1

a, b TSR 482 0211/2400 RJ45>RJ45 straight 1/servera One per Telephony Serverb Can be replaced by TSR 482 0211/20M, by choice

Server RedundancyRemark Product No Designation Q

FAL 104 6787 MX TS Redundancy 1/systemFAL 104 6788 MX TS Redundancy, Call processing (N+1) 1


IP HW calculation

Whenever the migrated system contains IP extensions, IP networking or Inter LIM IP connectivity, the total number of IPLU boards has to be calculated. The number of IPLUs to replace existing ELU32s is entered.(ELU32 is no longer supported)- There is also a possibility to order extra IPLU boards.


ROF 137 5067/1 IPLU 1 / GS LinkTSR 482 0211/2400 RJ45>RJ45 straight 1 / IPLU

Here it is to be considered that IP telephony as well as IP inter LIM connectivity requires at least one IPLU in each LIM.Example.:4 IPLUs for IP extensions in LIM 1 and LIM 5 out of 10 is using IP inter LIM connectivity (with 3 links), but the remaining 9 LIMs still use the GS.This will result in a total of 4+8+3=15 IPLU, or if the IP extensions are spread out 9+3=12 IPLU.

7.6 Management systemRemark Product No Designation Q

FAL 104 8158/1 MX MP SW Mgr Provisioning System 1/systemFAL 104 8759/1 MX MP SW Mgr Provisioning Managed user 1/userLZY 203 184/2 MX MP SW Mgr Provisioning Media Kit 1/system

16 (28)

7.6.1 Management system for operators

For operators, when not using management system DNA or CMG.


LZY 601 177 DNA server media kit 1/systemFAL 104 8079 DNA Open OPI user pack 1/operator

7.7 Software Maintenance

As the market and technology changes and more and more of our products become software based, we are also entering the software business with new requirements on how to sell and get paid.With the launch of MX-ONETM V.3, a revised Software Maintenance Program was introduced with two separate alternatives; Software Assurance and Software Basic. Both are sold on an individual customer and system basis.Both Assurance and Basic will absorb and replace the current service fee based on annual net sales value.

Telephony GatewayRemark Product No Designation

FAF 901 517/B1 MX TS Telephony Gateway, Software Basic for 1 yearFAF 901 517/A1 MX TS Telephony Gateway, SW Assurance 1 yearFAF 901 517/A2 MX TS Telephony Gateway, SW Assurance 2 yearsFAF 901 517/A3 MX TS Telephony Gateway, SW Assurance 3 years

Telephony systemRemark Product No Designation

FAF 901 498/B1 MX TS Telephony System, Software Basic for 1 yearFAF 901 498/A1 MX TS Telephony System, SW Assurance 1 yearFAF 901 498/A2 MX TS Telephony System, SW Assurance 2 yearsFAF 901 498/A3 MX TS Telephony System, SW Assurance 3 years

Telephony userRemark Product No Designation

FAF 901 519/B1 MX TS Telephony User, Software Basic for 1 yearFAF 901 519/A1 MX TS Telephony User, SW Assurance 1 yearFAF 901 519/A2 MX TS Telephony User, SW Assurance 2 yearsFAF 901 519/A3 MX TS Telephony User, SW Assurance 3 years

Manager Provisioning systemRemark Product No Designation

FAF 901 639/B1 MX MP SW Mgr Provisioning System, SW Basic 1 yearFAF 901 639/A1 MX MP SW Mgr Provisioning System, SW Assurance 1 yearFAF 901 639/A2 MX MP SW Mgr Provisioning System, SW Assurance 2 yearsFAF 901 639/A3 MX MP SW Mgr Provisioning System, SW Assurance 3 years

17 (28)

Manager Provisioning managed userRemark Product No Designation

FAF 901 640/B1 MX MP SW Mgr Provisioning managed user, SW Basic 1 yearFAF 901 640/A1 MX MP SW Mgr Provisioning managed user, SW Assurance 1 yearFAF 901 640/A2 MX MP SW Mgr Provisioning managed user, SW Assurance 2 yearsFAF 901 640/A3 MX MP SW Mgr Provisioning managed user, SW Assurance 3 years

7.8 HW replacement for upgrading/migration

The following upgrade of hardware is included in the upgrade price. The migration is either done by changing firmware (PROM) or the entire hardware. The different alternatives are determined by the original software release and hardware building practice.

The assumption is that previous hardware updates are performed, i.e. that the appropriate hardware level is used for a certain software release. The upgrade alternatives state the original revision level of the board, the revision level of the new board (in case of replacement) and the final revision level of the board (in case of firmware upgrade).

(Rev replaced board - Rev new board) (From Rev ----> to Rev)

The firmware upgrade is always to the latest approved revision of that particular board. In some cases the revision can vary depending on original hardware level. In some cases the revision is stepped back, due to cancelled firmware releases.

7.8.1 FW, Set of PROMs for migration of the extension boards

Enter the number of existing ELU28/2 or ELU28/3 boards for digital telephones (ROF 137 5334/3) with a revision state lower than R3A that is to be upgraded to revision R3A.


RYS 102 669/1 ELF28 1 / ELU28SVB 131 65 Label for new R-state 1 / ELU28

7.8.2 Boards

Replacement for DSU/1 or /3Remark Product No Designation Q

1/ROF 131 4414/14 DSU 1 / SSU or DSU

Cables for LSU-E to DSU/14


TSR 491 406/120 Connection cable LSU-DSUTSR 491 406/1850 Connection cable LSU-DSU

Replacement for GPU R1A


ROF 137 5393/1 GJUL4ROF 137 5393/2 GJUL4ROF 137 5394/1 GPU

7.8.3 FW, Set of PROMs for migrating the boards

Upgrade of DSU/4 < R10ARemark Product No Designation Q

RYS 102 328 DSF 1 / DSUSVB 131 65 Label for new R-state *

Upgrade of GJUG5 < R6A


18 (28)

RYS 102 703/1 Memory set GJUG5 1 / GJUG5SVB 131 65 Label for new R-state *

Upgrade of GJUL4 < R8A


RYS 102 716/1 Memory set GJUL4 1 / GJUL4SVB 131 65 Label for new R-state *

*) The largest number of new revision states for the boards determines the number of label sets. E.g. If the order ends up with 3 pieces of boards in revision R3A, 2 pieces of R8B and 5 pieces of R5A, 5 sets of labels are delivered.

7.9 Additional upgraded HW and/or FW

The following upgrade of hardware is NOT included in the upgrade price.These questions are not mandatory for the upgrade, and can therefore be omitted, if not wanted.The migration is done by changing the entire board, or by changing the firmware (PROM)

Board: the upgrade alternatives state the original revision level of the board, the revision level of the new board.

(Rev replaced board - Rev new board)

Firmware: the upgrade alternatives state the original revision level of the board and the final revision level of the board.

(From Rev ----> to Rev)

The firmware upgrade is always to the latest approved revision of that particular board. In some cases the revision can vary depending on original hardware level. In some cases the revision is stepped back, due to cancelled firmware releases.

7.9.1 HW (Boards) and/or FW (PROMs) for extension boards

Replacement for ELU26/2 up to R3A (boards)Remark Product No Designation Q

ROF 137 5321/12 ELU26 1TSR 491 415/2000 Adapter cable ELU26/12, TLU79/11 1NTM 144 269/3 Conv. TMU/MFU DSU TLU79 ELU26 1

19 (28)

Upgrade of ELU26/2, R4A, R5A or R6A (PROMs)Remark Product No Designation Q

RYS 102 452/1 PROM ELF26 R7A 1 / ELU26SVB 131 65 Label for new R-state *

Upgrade of ELU26/2 R4B, R5B or R6B (PROMs)


FAB 106 0367/16 PROM ELF26 R6A 1 / ELU26SVB 131 65 Label for new R-state *

Upgrade of ELU29, except /11 R7G, R9G, /12 R8F, /13 R8G, /14 R9F, /15 R8F (PROMs)


FAB 106 0367/8 PROM ELF29 R5B1 / ELU29 (all except below)

SVB 131 65 Label for new R-state *

Upgrade of ELU29 (PROMs)


FAB 106 0367/9 PROM ELF29 R7A

1 / ELU29/11 (R7G, R9G),ELU29/12 (R8F), ELU29/13 (R8G), ELU29/14 (R9F), ELU29/15 (R8F).


Upgrade of ELU30 (PROMs)


RYS 102 664/1 PROM ELF30 R3A 1 / ELU30SVB 131 65 Label for new R-state *

*) The largest number of new revision states for the boards determines the number of label sets. E.g. If the order ends up with 3 pieces of boards in revision R3A, 2 pieces of R8B and 5 pieces of R5A, 5 sets of labels are delivered

7.9.2 HW (Boards) and/or FW (PROMs) trunk or tie line boards

Upgrade of TLU75/1 up to R4A and TLU75/6 up to R1B (PROMs)Remark Product No Designation Q

FAB 106 0367/2 PROM TLF75 R5A1 / TLU75/1 and / 6 (R1A or R1B)


Upgrade of TLU75/1 > R4A (PROMs)


FAB 106 0367/12 PROM TLF75 R14A 1/TLU75/1SVB 131 65 Label for new R-state *

Upgrade of TLU75/2 (PROMs)


RYS 102 661/1 TLF75/2 R4A 1 / TLU75/2SVB 131 65 Label for new R-state *

Upgrade of TLU75/6 R3A or R4A (PROMs)


FAB 106 0367/3 PROM TLF75 R10A1 / TLU75/6 (R3A or R4A)

20 (28)


Replacement of TLU76/1 up to R2A (boards)


FAB 106 0662/11 TLU76 ISDN 1

Products includedRemark Product No Designation Q

ROF 137 5338/11 TLU76 ISDN 1



RYS 102 643/1 TLF76 R8A 1 / TLU76/1SVB 131 65 Label for new R-state *

Replacement of TLU76/2 up to R1A/1 (boards)


ROF 137 5338/12 TLU76 DPNSS 1

Upgrade of TLU76/2 > R1A/1 (PROMs)



Replacement of TLU76/3 up to R1A/1 (boards)


ROF 137 5338/13 TLU76 CAS 1

Upgrade of TLU76/3 > R1A/1 (PROMs)



21 (28)

Upgrade of TLU76/4 (PROMs)Remark Product No Designation Q

RYS 102 653/1 TLF76/4 1 / TLU76/4SVB 131 65 Label for new R-state *



FAB 106 0367/13 PROM TLU76/1 R10A 1 / TLU76/11SVB 131 65 Label for new R-state *







Replacement of TLU77/1 (boards)


ROF 137 5387/11 TLU77/11 1



ROF 137 5387/12 TLU77/12 1



ROF 137 5387/13 TLU77/13 1

Upgrade of TLU79/1 and TLU79/2 < R4A (PROMs)


RYS 102 644/1 PROM TLF79 R9A 1 / TLU79SVB 131 65 Label for new R-state *

Replacement of TLU79/2 up to R4A (boards)


ROF 137 5349/11 TLU79 1

Products includedRemark Product No Designation Q

NTM 144 269/3 Conv. TMU/MFU DSU TLU79 ELU26 1

Upgrade of TLU80/1 up to R3A (PROMs)Remark Product No Designation Q

RYS 102 650/2 TLF80/2 R3A1 / TLU80/1 (R2A or R3A)




22 (28)

RYS 102 650/1 PROM TLF80/1 R9A1 / TLU80/1 (R2A or R3A) ,R4A


Upgrade of TLU81 (PROMs)


RYS 102 683/1 TLF81 R2A 1 / TLU81SVB 131 65 Label for new R-state *


7.9.3 HW (Boards) and/or FW (PROMs) for the other boards

Replacement of MFU/1 (boards)Remark Product No Designation Q

ROF 137 5348/11 MFU/11 1

Upgrade of MFU/11 <R1C (PROMs)


RYS 102 630/1 PROM MFU/11 1 / MFU/11

Upgrade of SPU2 (PROMs)


RON 104 117 Prom for SPU2 1 / SPU2SVB 131 65 Label for new R-state *

Replacement of TMU/2, TRU (boards)


ROF 137 5335/12 TMU/12 1NTM 144 269/3 Conv. TMU/MFU DSU TLU79 ELU26 1

23 (28)

Replacement of VCU, VSU1 and VSU2 (boards)Remark Product No Designation Q

ROF 137 5430/11 SPU4/11 1


7.9.4 HW upgrades (memory upgrades)Remark Product No Designation Q

NTM 144 275 ESU memory upgrade to 2GB 1

7.9.5 Back-up package for HP server


KDY 307 08/8 HP HDD & PSU for TelSys Server 1

7.9.6 Support fronts etc.

Support fronts for TMU, MFU, DSU, TLU79, ELU26Remark Product No Designation Q

NTM 144 269/3 Conv. TMU/MFU DSU TLU79 ELU26 1

Support fronts for IPLU, SPU


NTM 144 269/5 Conversion to IPLU and SPU 1

Support fronts for TLU76, GJUL4


NTM 144 269/7 Conversion to TLU76 and GJUL4 1

Support fronts for ELU33/34, TLU80, FTU2


NTM 144 269 Conv. to ELU33/34 TLU80 FTU2 1

Support fronts for ELU31/3


NTM 144 269/2 Conversion to ELU31/3 1

Support fronts for LSU-E, ALU2


NTM 144 269/4 Conversion to LSU-E and ALU2 1

Support fronts for TLU77


NTM 144 269/6 Conversion to TLU77 1

Front 20mm for empty board positions


SXK 106 1020/01 Front 20mm 1

Adapter cables for replaced ELU28 and ELU29 boards (32 individuals)


24 (28)

TSR 910 1058/2000 Cable adapter ELU28-33, ELU29-34 1

Adapter cables for replaced ELU28 and ELU29 boards (16 individuals)


TSR 910 1056/2000Cable adapter ELU33/11 ELU34/11 TLU80/11 FTU2/11

1

Adapter cables for replaced ELU31/2


TSR 910 1056/20001Cable adapter ELU33/11 ELU34/11 TLU80/11 FTU2/11

1

Earth clip set


NTM 144 270 Earth Clip kit 1

25 (28)

8 Licenses

8.1 Entering licenses

There are two migration cases:

From BC10, BC11, BC12 or TSW to MX-ONETM TSE From a release earlier than BC10 to MX-ONETM TSE

If additional functionality in the upgraded system is required compared to the functionality in the existing system, such functionality must be ordered separately, and an add-on order must be created.

8.1.1 Migration from BC10, BC11, BC12 or TSW to MX-ONETM TSE

The distributor must define the number of LIMs and the number of ports in Aastra Plan. The number of licenses in the new MX-ONETM V.4.1 license file is created by the database License Control System, LCS, based on the existing BC10, BC11, BC12 or TSW license file. The license file is retrieved from the license application.

Each type of extension end external line must be specified.By doing this, it is possible to decrease the number of different extensions and trunks/tie-lines.This will result in decreased number of ports, and decreased migration and software maintenance fee.It is not possible to increase the number of the different extensions and external lines.For this purpose, add-on sales must be selected.

8.1.2 Migration from a release earlier than BC10 to MX-ONETM TSE

When migrating from a release earlier than BC10 to MX-ONETM TSE, the number of licenses in the system to upgrade has to be calculated. This must be done with a tool in SAM toolbox called PCREGEN, using an option for calculating licenses. The PCREGEN uses printout data from the existing system as a base for the calculation. Licenses shall never be calculated manually.The data is used for manual input into Aastra Plan.

When the order is received the license information in License Control System is updated and a license file is created. The license file is retrieved from the license application.

8.2 License overview

The table below shows all licenses in MX-ONETM Version 4.1 and their counterpart in MD110/TSW.The table shows:

The license number used in MX-ONETM V.4.1 License file The license number generated in Aastra Plan for migration The old license number used in MD110/TSW

DesignationLicense numberMX-ONETM

License numberAastra Plan

License numberMD110/TSW

MX TS IP extension RTU 1 port FAL 104 5302 FAL 104 5302/1 FAL 104 706MX TS Analog extension RTU 1 port FAL 104 5303 FAL 104 5303/1 FAL 104 451MX TS LIM RTU 1 LIM FAL 104 5304 FAL 104 5304/1 FAL 104 0049MX TS Free seating service FAL 104 5305 FAL 104 0050MX TS IP trunk RTU 1 port FAL 104 5307 FAL 104 5307/1 FAL 104 2179MX TS IP Networking Enhanced Services RTU 1 port

FAL 104 5308 FAL 104 5308/1 FAL 104 3611

MX TS Public ISDN user side RTU 1 port FAL 104 5309 FAL 104 5309/1 FAL 104 464MX TS ISDN tie line RTU 1 port FAL 104 5310 FAL 104 5310/1 FAL 104 466MX TS Personal number RTU 1 user FAL 104 5311 FAL 104 472

MX TS Enhanced networking facility RTU 1 system FAL 104 5312FAL 104 505 or FAL 104 506

MX TS DSS1 Network side RTU 1 port FAL 104 5313 FAL 104 5313/1 FAL 104 507

26 (28)

MX TS Interception RTU 1 Ethernet session FAL 104 5314 FAL 104 533MX TS Voice mail RTU 1 Ethernet session FAL 104 5315 FAL 104 535MX TS Application link RTU 1 Ethernet session FAL 104 5316 FAL 104 536MX TS Electronic mail RTU 1 Ethernet session FAL 104 5317 FAL 104 538MX TS IP teleph interf RTU 1 interf FAL 104 5319 FAL 104 707

MX TS Mobile extension RTU 1 port FAL 104 5477 FAL 104 5477/1FAL 104 0524 + FAL 104 0525

MX TS repeated individual diversion RTU 1 user FAL 104 5498 FAL 104 471MX TS Digital extension RTU 1 port FAL 104 5502 FAL 104 5502/1 FAL 104 452MX TS Operator extension RTU 1 port FAL 104 5504 FAL 104 5504/1 FAL 104 456MX TS Integrated RVA RTU 1 port FAL 104 5505 FAL 104 5505/1 FAL 104 486MX TS Analogue trunk line RTU 1 port FAL 104 6508 FAL 104 6508/1 FAL 104 461MX TS Call metering on analogue trunk line RTU 1 port

FAL 104 6509 FAL 104 6509/1 FAL 104 503

MX TS CAS trunk line RTU 1 port FAL 104 6510 FAL 104 6510/1 FAL 104 462MX TS MFC RTU 1 device FAL 104 6511 FAL 104 6511/1 FAL 104 502MX TS DASS2 trunk line RTU 1 port FAL 104 6512 FAL 104 6512/1 FAL 104 463

MX TS CCSS7 trunk line RTU 1 port FAL 104 6513 FAL 104 6513/1FAL 104 468 or FAL 104 705

MX TS DPNSS tie line RTU 1 port FAL 104 6514 FAL 104 6514/1 FAL 104 465MX TS CAS extension RTU 1 port FAL 104 6515 FAL 104 6515/1 FAL 104 455MX TS ACD RTU 1 Agent FAL 104 6622 FAL 104 6622/1 FAL 104 525MX TS Analogue Extension CLIP RTU 1 User FAL 104 6623 FAL 104 6623/1 FAL 104 6191MX TS Base station DECT RTU 1 interface FAL 104 6624 FAL 104 520MX TS Cordless extension RTU 1 user FAL 104 6625 FAL 104 6625/1 FAL 104 454MX TS CCM RTU 1 Ethernet sessio FAL 104 6626 FAL 104 531MX TS ISDN S0 extension RTU 1 port FAL 104 6627 FAL 104 6627/1 FAL 104 453MX TS paging loop RTU 1 port FAL 104 6628 FAL 104 6628/1 FAL 104 518MX TS paging serial RTU 1 port FAL 104 6629 FAL 104 6629/1 FAL 104 517MX TS SMDR/CIL RTU 1 Ethernet session FAL 104 6630 FAL 104 489MX TS VC FAX III recognition RTU 1 port FAL 104 6631 FAL 104 6631/1 FAL 104 512MX TS Music on hold RTU 1 MOH port FAL 104 6730 FAL 104 6730/1 FAL 104 480MX TS DISA number RTU 1 system FAL 104 6731 FAL 104 6731/1 FAL 104 484MX TS external RVA RTU 1 port FAL 104 6732 FAL 104 6732/1 FAL 104 487MX TS Virtual private network RTU FAL 104 6733 FAL 104 6733/1 FAL 104 508MX TS Routing-server-server FAL 104 6734 FAL 104 6734/1 FAL 104 6192MX TS Routing-server-client FAL 104 6735 FAL 104 6735/1 FAL 104 6193MX TS paging parallel RTU 1 port FAL 104 6758 FAL 104 6758/1 FAL 104 519MX TS Encryption FAL 104 6986 newMX TS VoIP Security SW key 1 system FAL 104 6975 new

27 (28)

-----------------------------------------------------------------------------------------------------------------------© 2011 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 the 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, neither for incidental nor for consequential damages in connection with the furnishing, performance, or use of these materials. Aastra Technologies Limited Concord, Ontario, Canada

28 (28)

mx-one v.4.1 migration oi 11

Documents