ORDERING GUIDE System - Aastra 5000 - R5.4

1 

ORDERING GUIDE 

System - Aastra 5000 - R5.4 

June 2012 edition

2 

TABLE OF CONTENT 

ORDERING GUIDE SYSTEM - AASTRA 5000 - R5.4 .................................................................................. 1 

RELEASE NOTES ................................................................................................................................................... 3 

SYSTEMES ........................................................................................................................................................... 4 

INTRODUCTION .................................................................................................................................................... 4 

A – AASTRA 5000 SERVER (A5000) .................................................................................................................... 4 

1. Product presentation ................................................................................................................................... 4 

2. Server pre-requisites ................................................................................................................................... 6 

2. Product structure ........................................................................................................................................ 7 

3. How to order the Aastra 5000 Server ......................................................................................................... 8 

4. Virtualization of the Aastra 5000 Server ..................................................................................................... 9 

B –AASTRA X SERIES: AXS/AXL/AXD ........................................................................................................... 10 

1. Product presentation ................................................................................................................................. 10 

6. Aastra X Series gateways common components ........................................................................................ 11 

7. How to order the Aastra X Series gateways .............................................................................................. 16 

C – DRG22I ....................................................................................................................................................... 20 

1. Product presentation ................................................................................................................................. 20 

2. How to order the DRG22i ......................................................................................................................... 20 

E – SOFTWARE LICENSES ................................................................................................................................... 21 

1. Locking principles ..................................................................................................................................... 21 

2. Demonstration license ............................................................................................................................... 21 

3. New R5.4 systems and R5.4 software extensions ...................................................................................... 22 

4. How to order software licenses ................................................................................................................. 31 

5. Credits ....................................................................................................................................................... 31 

6. UCV board standard replacement ............................................................................................................ 31 

7. License move ............................................................................................................................................. 31 

8. Virtual TDM to IP terminal migration ...................................................................................................... 32 

F – HARDWARE MAINTENANCE: SPARE PARTS ................................................................................................... 33 

6. Standard replacement of UCV motherboard with its key .......................................................................... 34 

G – DEMO PACKS ............................................................................................................................................... 34 

R5.1 TO R5.4 UPGRADE .................................................................................................................................. 37 



NEXSPAN TO R5.4 MIGRATION ................................................................................................................... 40 

A - MIGRATION FROM NCS TO A5000 R5.4 ...................................................................................................... 40 

B - MIGRATION OF NEXSPAN S12/S/L/D TO AASTRA X SERIES AXS12AXS/AXL/AXD ................................. 42 

1. Prerequisites ............................................................................................................................................. 42 

2. Hardware migration ................................................................................................................................. 42 

3. NeXspan C ................................................................................................................................................ 43 

4. NeXspan S12/S-E/S to Aastra XS12/S-E/S ................................................................................................ 43 

5. NeXspan L to Aastra XL ............................................................................................................................ 43 

6. NeXspan D to Aastra XD .......................................................................................................................... 44 

7. What should be sent back to the Repair Center (CDR) ............................................................................. 45 

8. Migration of the extension boards ............................................................................................................ 45 

9. Color change through standard replacement ........................................................................................... 47 

C – SOFTWARE MIGRATION ................................................................................................................................ 49 

1. Applications and Aastra 5000 R5.4 ........................................................................................................... 49 

2. Migration of the software and licenses, to R5.4 ........................................................................................ 49 

D- HOW TO ORDER A MIGRATION NEXSPAN TO R5.4 ......................................................................................... 50

Release notes 

R5.2 

Edition 1: First edition – May 2010 

Edition 2: July 2010 

• Dell Servers compatible with Linux RedHat 5.4 and A5000 R5.2 

• IP license for Call pit 

• ACP 1.2 not compatible with A5000 R5.2 

Edition 3: October 2010 

• Chapter A – §3 : Content of A5000 Server duplex for VMWare 

• Chapter E – §3.5 : IP license and call pit: i2070 dimensioning 

• Chapter E – §3.13 : Round-robin SDA (Hostel / Hospital) 

Edition 4: November 2010 

• NeXspan Migration – Chapter B §8 : Stocko boards 

Edition 5: February 2011 

• Chapter E – §3.14 : i2070 attendant : licenses required 

• NeXspan Migration – Chapter C - §1 : UCP release R2.0 minimum 

• InTouch Softphone 

Edition 6: June 2011 

• NeXspan Migration – Chapter B.6: to avoid any problem, 

replacement of R-UCT-D becomes mandatory 

R5.3 

Edition 1: June 2011 

• R5.3 

• A5000 Server: Media Server 

• Licenses: Codecs and Media Server 

• Migration: R5.3 

Edition 2: September 2011 

• HP Networking => HP Networking 

Edition 3: November 2011 

• Chapter E – §3.6 : new : BluStar 8000i 

• Chapter E – §3.7 : new : BluStar Client 

• Chapter E –: new : Aastra Dialer 

• Chapter E – §3.10 : CSTA maximum sessions per Gateway and per A5000 Server 

• Chapter E – §3.18 : e-voicemail: precision for the installed base (

4 

SYSTEMES 

Introduction 

Aastra 5000 is the Aastra Enterprise Communication solution. 

Universal, this solution addresses both the large systems from 500 to 150 000 extensions, spread on 

numerous sites, and the SME market, with all in one product from 8 to 1000 subscribers 

Result of several years of R&D, the A5000 call processing software is the heart of this solution, on of 

the most complete on the market, with more than 500 features 

This document is the Ordering Guide of the Aastra 5000 solution, release R5.3, regarding: 

- The call server: Aastra 5000 Server 

- The gateways: Aastra X Series 

- The resources for translation of voice between the TDM and the IP world (codec): VoIP and EIP 

- The DRG22i media gateways 

- The software licenses of these products 

- The demo packs dedicated for resellers 

� The last part of this document is about migration toward the R5.4 release 

- of Aastra 5000 R5.1, R5.2 or R5.3 

- and of the NCS and NeXspan S/L/D 

Some other Ordering guides are available, regarding 

- The A5000 C²I 

- Phones and soft-phones 

- Applications (UCP, ACP, TWP, i2070) 

- Servers (hardware) 

- Migration of M6550/NeXspan 500 systems to R5.3/R5.4 

The Ordering guide may help to prepare an order using the price list. 

For any order of a new system or new application, Aastra recommends to use the Aastra Plan 

quotation tool, in order to be more efficient and reduce the risk of mistake. 

A – Aastra 5000 Server (A5000) 

1. Product presentation 

The Aastra 5000 Server is the software form of the Aastra 5000 solution. It is designed to run on a 

standard server. 

Full IP, the Aastra 5000 Server supports IP phones, SIP, DECT over IP, Wi-Fi SIP phones, IP softphones. 

For external calls, it may access to VoIP provider services. 

It connects to IP applications: unified messaging, CTI, web server, contact center, greeting services, 

attendant, conference bridge, etc. 

It includes an IP management portal (Aastra Management Portal), accessed through a web browser. 

An Aastra 5000 server may manage up to 15 000 IP extensions.

The Aastra 5000 provides telephony and video services, control services such as address translation, 

call admission and bandwidth control, call authorization between phones and gateway, all based on 

the Aastra 5000 software (calling, call receipt services, out of band services). 

Since R5.3, the Aastra 5000 Server includes a Media Server which provides the following voice 

services 

- Music, announcements, vocal guides 

- The integrated voice messaging with the unified messaging option 

- The Interactive Voice Responder 

- The 3 party conferences (since R5.3 SP1). 

Moreover, the Aastra 5000 software provides advanced services such as the Automatic Call 

Distribution (ACD) and an LDAP Directory (Caller/called Name ID, Call by name). 

It may be linked with Aastra X Series (see chapter B) to connect TDM equipment (analog or digital): 

TDM extensions, DECT TDM, TDM applications, TDM provider services. 

Since R5.3, in a Full IP configuration, the Media Server allows a standalone A5000 Server, without 

the need for a gateway. So, the Aastra 5000 Server may be deployed as a full IP monosite. 

The Aastra 5000 Server includes the two following software: 

• The telephony and call processing software : the Call Manager 

• The SIP proxy to connect SIP phones and SIP network links (SIP trunks). 

The Aastra5000 Server is available as: 

• A software for standard or virtualized server: DVD-ROM including software, documentation, 

identification key, licenses. See server pre-requisites below. 

• Or a software for HP Networking Advanced zl module: USB key including software, 

documentation, identification key, Aastra and HP Networking licenses. 

• Or integrated with an hardware server: this includes an hardware server + the CentOS R6.2 64 

bits Linux OS + the Aastra 5000 application, all that installed on the hardware server. For more 

details, see the ordering guide relative to the servers. 

A5000 Server – AM7450 co-residency 

On a standard hardware server, co-residency of the A5000 Server with the AM7450 on the same 

server is possible over VMWare ESXi. 

For more details please read the A5000-AM7450 co-residency ordering guide. 

A5000 Server Capacity and pre-requisite 

5 

IP extensions 15 000 

Simultaneous calls 1 900 

Calls per hour (CCPH) 57 000 

Directory size (number of entries) 80 000 

IP extensions with CTI supervision 15 000 

Number of companies/services (for multi-tenant services) 256 

Number of sites (A5000 servers or Aastra X series gateways) 99

2. Server pre-requisites 

The standard server should be homologated on CentOS 6.2 or RedHat 6.2 64 bits. 

The compatibility of standard servers with RedHat Enterprise R5.4 may be checked on 

https://hardware.redhat.com/index.cgi 

The 1U or 2U Dell servers previously proposed by Aastra PE2950-III, R200, R210, R300 and R410 

are compatible (PE860 is no more compatible). However, their capacity may be reduced after upgrade 

to R5.4 (see R5.4 pre-requisites below). Possibly, their memory may be extended, when required. 

Requested standard server configuration for R5.4 

for 1 000 subscribers 

Components Minimum requirements for 1 000 IP subscribers 

Processor Dual Core Intel 2 GHz or equivalent 

Hard disk 80 Go 

RAM memory 2 Go 

Operating system Linux CentOS or RedHat ES 6.2 64 bits 

IP Ports 1 IP 10BaseT/100BaseTx port 

Extended to 2 IP ports in case of 

- double attachment 

- separated management flood 

USB ports 2 ports USB 


or for CO-residency : 2000 IP users on A5000 Server and 4000 users on AM7450 


Processor Quad Core Intel 2,5GHz or equivalent 








USB ports 2 ports USB 

6 



Processor 2 * Quad Core Intel 2.4 GHz or equivalent 








USB ports 2 ports USB

2. Product structure 

Aastra 5000 Server for standard server or for virtualized solution 

As a new system, the Aastra 5000 Server is composed of 

- 1 DVD-ROM including 

- The application to be installed on a Linux CentOS or RedHat ES 6.2 64 bits server 

- The technical documentation 

- 2 SIP Aastra licenses 

- 5 x100 LDAP directory entries license 

- 1 software ID to identify uniquely the instance of the Aastra 5000 and to obtain the software key of 

release R5.4, when installing. 

� Depending on the number of IP extensions, the capacity of some interfaces or to be able to use 

some features, it may be necessary to acquire some software licenses. 

For more details, please see the Software licenses chapter. 

Aastra 5000 duplicated physical or virtualized Server 

You may duplicate the Aastra 5000 server, this means to install another hardware server (back-up 

server), on another place, in order to secure the system. 

This second server will replace the first one in case of serious problem, e.g. network access broken or 

server out of order. 

To do so, you should order through Aastra Plan (in addition to the first Aastra 5000 server) 

a) The A5000 duplication pack, which contains: 

- 1 DVD-ROM with the A5000 software and documentation 

- 1 software ID to identify uniquely the instance of the Aastra 5000 duplex and to obtain 

the software key of release R5.4, when installing. 

- 2 duplex IP licenses 

- 5 x100 LDAP directory entries duplex licenses 

7 

b) The duplex software licenses for the back-up server (corresponding to the back-up server 

dongle ID). These licenses must correspond to the licenses on the main (the 1st) server, 

except the Dual-homing licenses which are not required on the duplex server. 

Please note that these parts are in addition to the parts of the main server. 

Aastra 5000 Server for HP Networking zl module 

Same as for Standard server + the HP Networking license to run the A5000 Server on the Advanced 

Zl module. 

As a new system, the Aastra 5000 Server for HP Networking zl module is composed of 

- 1 USB key including 

- The image of the A5000 Server + OS CentOS 6.2 to be installed on the Advanced zl module 

- And the technical documentation, notably the installation guide on Advanced Zl module. 





- The HP Networking software key to allow the A5000 application to run on the module zl.


some features, it may be necessary to acquire some software licenses (identical to these of the 

A5000 on standard server). 


The HP Networking zl module should be ordered in addition. 

Aastra 5000 Server duplex for HP Networking zl module 

As a new system, the Aastra 5000 Server duplex for HP Networking Advanced zl module is composed 

of 

- 1 USB key including 

- The image of the A5000 Server + OS CentOS 6.2 to be installed on the Advanced zl module 

- And the technical documentation, notably the installation guide on Advanced zl module. 





- The HP Networking software key to allow the A5000 application to run on the zl module. 


some features, it may be necessary to acquire some software licenses (identical to these of the 

A5000 duplex on standard server). 


The HP Networking Advanced zl module should be ordered in addition. 

3. How to order the Aastra 5000 Server 

You may order the Aastra 5000 Server: 

• Either using the Aastra Plan tool (recommended) 

The Aastra Plan tool proposes: 

- the Aastra 5000 software 

- for standard or virtualized server 

- or for HP Networking Advanced zl module 

- as an option the Aastra 5000 duplex 

- as an option, the standard hardware server (with Linux CentOS) and the installation service (OS+ 

A5000 software installation on the server). For more details, please see the Servers Ordering 

Guide. 

- The various software licenses you may require (IP subscribers, directory entries, etc.) 

- The phones and applications 

Please, join with the purchase order the document provided by Aastra Plan. 

• Or as spare parts 

In the price list, you will find: 

- The Aastra 5000 software 

- for standard or virtualized server 

- or for HP Networking Advanced zl module 

- including 2 SIP Aastra licenses + 5x100 directory entries licenses 

- The A5000 spatial duplication kit (see before) for standard hardware server 

- The software licenses 

8

And if you want to order the hardware standard server to Aastra: 

- The rack server with Linux CentOS 6.2 

- BASIC server: supports up to 4 000 IP subscribers 

- RESILIENT server: same capacity with, in addition, an hot plug redundant power supply and 

an hot plug Raid 1 redundant disk. 

- POWER server: same as Resilient, but extended capacity to 15 000 IP users. 

- The A5000 integration service : 

- OS installed on the Dell server 

- Aastra 5000 application installed and tested, 

� For more details on the hardware standard server and the integration service, please see the 

Servers Ordering Guide. 

4. Virtualization of the Aastra 5000 Server 

It is possible to port an existing Aastra 5000 Server R5.4 with USB Dongle (A5000 R5.4 upgrade from 

R5.1, R5.1 or R5.3) in a virtualized architecture (VMWare ESX/I 4.1 or 5.0). 

To do so, 

- For the main server, this requires a virtualization kit 

- For the back-up server, virtualization pack of the duplex A5000 Server is required. 

An A5000 Server R5.4 for virtualization license will be then provided in the same release as the 

existing one, and the initial USB dongle will be returned back to Aastra, after installation on VMWare. 

For virtualization of R5.2 or R5.3 server, please see the R5.2 or R5.3 ordering guide. 

9

B –Aastra X Series: AXS/AXL/AXD 

Aastra X Series, the new generation of ToIP solution, is a gateways range providing many integrated 

services. 


The Aastra X Series answers to types of requirements: 

• For autonomous and independent architectures, AXS, AXL and AXD are used as IPBX. 

10 

• For networking with a centralized architecture, AXS, AXL and AXD play a media gateway 

role. 

These products are available in R5.4 release. 

XS12/XS/XL/XD systems of the installed base in release R3.1, R3.2, R4.1 or R4.2 may be upgraded 

in release R5.4 (see Migration chapter). 

Name Abbreviation Software 

release 

Numer IP/SIP 

extensions 

Number of TDM 

extensions 

Aastra XS6 AXS6 R5.4 50 4-44 

Aastra XS12 AXS12 R5.4 500 4-44 

Aastra XS AXS R5.4 500 4-48 

Aastra X2S AX2S R5.4 500 4-96 

Aastra XL AXL R5.4 500 16-192 

Aastra X2L AX2L R5.4 500 16-416 

Aastra X3L AX3L R5.4 500 16-640 

Aastra XD AXD R5.4 500 16-192 

Aastra X2D AX2D R5.4 500 16-448 

Aastra X3D AX3D R5.4 500 16-704 

See dimensioning details in the A5000 product guide, chapter 10. 

Each gateway includes a mother-board with the telephony software and many services embedded. 

Moreover the AXS6, AXS12 and AXS include by default some analog and digital extension line ports 

and ISDN network ports (to connect to provider’s access) 

The AXS6, AXS12, AXS, AXL and AXD capacity and services can be expanded thanks to the addition 

of daughter boards to the motherboard and expansion cards in available card slots. 

The AXS, AXL and AXD capacity and services can be further expanded thanks to the addition of 

expansion boxes. No expansion box can be added to the AXS6. 

All these products have front panels with RJ45 connectors. 

Details on integrated services and greeting services are presented in the Product Guide of the release 

R5.4. 

For more details on these products see the Aastra 5000 R5.4 Product guide.

6. Aastra X Series gateways common components 

Services included 

Aastra X Series gateways include the following services 


- 5 Dialer/i2052 licenses 

- 5 oral languages per country 

- Multisite feature 

- Voice messaging up to 1000 voice mail boxes 

- A 500 entries LDAP directories (internal users or external contacts) 

- The web management portal (Aastra Management Portal) including (see A5000 product guide for 

more details): 

• Installation and provisioning features: LDAP directory, Voice messaging, IVR, DHCP and FTP 

servers for IP phones, TMA Terminal Management Application for inventory and provisioning 

of the 67xxi, 53xxip et 53xx phones, etc. 

• Configuration management: software and hardware inventory, updates, backup/restore of 

software and configuration, etc. 

• Security managements: user’s rights, administrator’s accounts and rights, keys management, 

etc. 

• Defects management: alarms filtering and routing, logbooks, SNMP traps, etc. 

• Performance management: state of the services, state of software and hardware resources, 

etc. 

Embedded IP Interface 

The IP interface on the motherboard of an Aastra X Series supports the interface with various 

applications on external servers. 

Thus it is possible to deploy the following application, linked to this interface: 

- Billing and traffic analysis based on CDR tickets 

11 

- CTI interfaces : CSTA, TAPI, SAE, Web Services 

- i2070 Attendant Console : Attendant console application 

- Integrated LDAP Directory interface: read/write 

- Web administration of the Aastra X Series through the embedded portal (Aastra 

Management Portal) or with the AM7450 management software. 

- M7900 alarm server for DECT mobiles 

- Aastra Dialer (CTI client) 

- i2052 CTI or i2052 soft-phone 

- Blustar Client softphone (Blustar for PC) 

- ACP 

- UCP 2.0 

- DHCP, FTP, NTP servers for IP extensions 

- TFTP server for Dect IP

Common expansion boards to AXS12, AXS, AXL and AXD 

The Aastra X Series gateways are modular platforms. Configuration can be customized. The following 

boards can be used: 

� Subscribers boards : 

LA8 board: to connect 8 analog extensions. 

LA16 board: to connect 16 analog extensions. 

LN8 board: to connect 8 digital extensions. 

DL8 board : to connect 8 digital extensions with energy saving feature 

LN16 board: to connect 16 digital extensions. 

DL16 board : to connect 16 digital extensions with energy saving feature 

LH8 board: to connect 8 analog hotel sets. It offers the same functions as the LA8 

card with an additional function for lighting a Depaepe or Teledex message lamp on 

sets, to indicate that a message has been left (Hotel function). 

LH16 board: to connect 16 analog hotel sets. It offers the same functions as the 

LA16 card with an additional function for lighting a Depaepe or Teledex message 

lamp on sets, to indicate that a message has been left (Hotel function) 

LM8 board: to connect 8 analog sets (4) and digital sets (4). 

� Analog trunk lines: 

LR4 board: to connect 4 analogue trunk lines. It can also be fitted with busy tone 

detection (DTOC) or billing (FTXA or FTXC) daughter cards. 

LI1 board to interconnect 2 private iPBXs through an analogue tie line 

� ISDN and digital interfaces 

LD4NX board: 4 S0/T0 ISDN interface card used to connect to 2- or 4-channel 

DECT base stations, or ISDN terminals (S0), or ISDN BRI interfaces (T0). The LD4X 

working mode is obtained by a removing a specific jumper, and allows the use of 

additional functions. 

LT2 board: Access port card S2/T2 ISDN primary rate or PCM digital port. 

Digital network access card for connecting either to 1 primary access of a European 

ISDN network (E1, 32IT) or an American ISDN network (T1, 24IT), or to PCM digital 

links (S2/T2) channel by channel or an S2 bus. 

� Data interface 

PT2X board: TCP/IP and voice over IP gateway card used for connection to a 

10/100 Mb Ethernet LAN. This card provides both a "TCP/IP – internal buses" 

gateway function for signaling and a "voice over IP" gateway function. It is used for 

connection to an Ethernet 10/100Mbits Base TX LAN socket, in compliance with 

IEEE 802.3 specifications. It is able to manage 8, 16 or 32 VoIP gateway channels, 

with the addition of an optional VoIP daughter card performing speech signal 

processing tasks (see details after). 

IPS board: On Aastra X Series, the SIP interface (signaling proxy) is integrated in 

the mother board. The IPS board cannot be used for this feature on Aastra X 

Series. However, the IPS board may be used as an SBC (Session Border Controller) 

for NAT traversal (used when traversal of some equipment with Network Address 

Translation activated is required). See Product guide A5000, chapter security, for 

more details. 

CA1 board: This card is used to connect V24 computer terminals (DTE or DCE) in 

V10 or V28 mode (RS232C). It is fitted with 4 RS232 ports used to connect 4 

asynchronous terminals for data transmission (max speed 19200 bit/s). 

CS1 board: This card enables two X.25 synchronous interfaces to be connected in 

V28 or V10 mode. 

12

Every expansion board is available in one format: RJ45. 

Compact Flash board 

The Compact Flash board of the Aastra X Series gateways contains the operating system, the 

software (including the Aastra Management Portal), the data configuration and the software licenses. 

On new AXSeries gateways, it is 2GB Compact Flash for AXS with less than 100 users and a new 

4GB Compact Flash for all other configurations. 

Note, only the Compact Flash provided by Aastra are warranted and certified by par Aastra. 

Languages 

The Aastra X Series gateways allow provisioning of telephony services with several simultaneous 

spoken languages. Announcements, guides, are thus available in several languages. By default, the 

gateways are provided with 5 languages, depending on the country. 

To change the default languages, please order the part number of the required additional languages. 

These languages are loaded on the system in factory and cannot be changed after. It is hardly 

recommended to use Aastra Plan to specify languages different from the default ones. 

13 

Spoken languages (voice mail, announcements) 

Daughter boards 

German BHX0198AADE Italian BHX0198AAIT 

English BHX0198AAEN Mandarin BHX0198AAMD 

Catalan BHX0198AACT Mexican BHX0198AAMX 

Danish BHX0198AADK Norwegian BHX0198AANO 

Spanish BHX0198AAES Polish BHX0198AAPL 

Finnish BHX0198AAFI Portuguese BHX0198AAPT 

Flemish BHX0198AAFL Swedish BHX0198AASW 

French BHX0198AAFR Czech BHX0198AACZ 

Nederland BHX0198AANL Slovak BHX0198AASL 

ADPCM16 daughter board: This optional daughter board allow to increasing from 2 to 4 

simultaneous channels the capacity of TDM DECT base stations connected to the AXS6/AXS12/AXS 

mother board. TDM DECT base stations connected to LD4 board have already a capacity of 4 

channels. 

Voice over IP 

The AXS6, AXS12, AXS, AXL and AXD may include VoIP resources to provide voice translation 

between the TDM world and the IP world.

These resources are daughter boards with G.711, G729A and G.723.1 codec, and T.38 (on EIP only). 

On the AXS6, AXS12, AXS, AXL and AXD motherboard (called UCVS, UCVL, UCVD) may be placed 

1 or 2 EIP-4, EIP-8, EIP-32 or EIP-64 daughter boards 

On duplex AXD (duplicated motherboard), the EIP configuration must be identical on each 

motherboard. 

On the PT2 extension board, may be placed 1 VOIP4E-8, VOIP4E-16 or VOIP4E-32 daughter board. 

EIP daughter boards for UCV motherboard 

EIP4, EIP-8, EIP-32 and EIP64 are to be placed on UCV motherboard. 

EIP4 requires R5.3 SP1 minimum. 

EIP64 requires UCV2 and R5.3 SP1 minimum. 

An UCV may have 0, 1 or 2 EIP daughter boards. 

So: 0, 4, 8, 12, 16, 32, 36, 40, 64, 68, 72, 96 and 128 VoIP resources. 

EIP-4 capacity 

C oding law G723 .1 G723.1 G729A G729A G711 G711 G711 G711 fax Fax T.38 

Voice sampling interval 30ms 60ms 20ms 30ms 10ms 20ms 30ms 

Ethernet real bandwidth per 

channel (kb/s) 

Maximum number of 

22 15 24 31 79 87 107 87 14,4 

simultaneous VoIP 

4 4 4 4 4 4 4 4 4 

communications 


ciphered simultaneous 

VoIP communications 


14 

4 4 4 4 4 4 4 






22 15 24 31 79 87 107 87 14,4 




8 8 8 8 8 8 8 8 8 



8 8 8 8 8 8 8 




Ethernet real bandwidth 

per channel (kb/s) 


22 15 24 31 79 87 107 87 14,4 




20 20 32 32 32 32 32 32 32 



20 20 32 32 32 32 32


Coding law G723 .1 G723.1 G729A G729A G711 G711 G711 G711 fax Fax T.38 


Ethernet real bandwidth 

per channel (kb/s) 


22 15 24 31 79 87 107 87 14,4 


64 64 64 64 64 64 64 64 64 





VoIP daughter boards for PT2 extension board 

15 

64 64 64 64 64 64 64 

VoIP4E-8, VoIP4E-16 and VoIP4E-32 are to be placed on PT2 extension board. 

A PT2 may have 0 or 1 VoIP4E daughter board. 

So: 0, 8, 16 or 32 VoIP resources. 

Note: Fax T.38 is not available on PT2. 

PT2 boards of the installed based are compatible with the Aastra X Series gateways in term of 

hardware. A new boot file software may be loaded on these boards. 

The software update can be performed by qualified technician, by use of a BOF3 board. 

Standard exchange by advance provided by the repair center (CDR) will be referenced in the repair 

price list. 

VOIP-8 capacity 






22 15 24 31 79 87 107 87 14,4 




8 8 8 8 8 8 8 8 0 



8 8 8 8 8 8 8 

VOIP-16 capacity 






22 15 24 31 79 87 107 87 14,4 




16 16 16 16 16 16 16 16 0 



16 16 16 16 16 16 16 

VOIP-32 capacity






22 15 24 31 79 87 107 87 14,4 


32 32 32 32 32 32 32 32 0 





16 

32 32 32 32 16 16 16 

• These values are provided for a simple multisite configuration, without codec mixing. 

• Switch to fax mode on 2100 Hz signal detection 

7. How to order the Aastra X Series gateways 

To ensure an easy and mistake free order, we recommend the use of Aastra Plan (provisioning tool). 

The main steps to prepare an order are: 

• Dimensioning need definition (number and type of extension lines, number of DECT base stations, 

network interfaces, others interfaces), 

• Definition of security level 

• Identification of the platform (AXS12/AXS/AXL/AXD), and number of possible extension cabinets: 

Aastra Plan proposes the most adapted configuration but this may be modified. 

Each cabinet (main or extension) is provided with its power supply. 

Extension cabinets are provided with the cable to connect to the main cabinet. 

• Identification of necessary extension boards for link of subscribers, networks and others 

interfaces: Aastra Plan proposes the most adapted configuration but this may be modified 

• Check of boards location in the cabinets and number of cap for unused slots 

• Identification of necessary daughter boards. 

• Identification of necessary software options 

• Identification of necessary spare parts 

• Remote maintenance mode: IP, ISDN/PPP, or analogue with an external modem 

• Identification of necessary services (factory configuration, …) 

Included services 

The Aastra X Series include by default the following services: 


- 5 Dialer licenses 

- Voice messaging up to 1 000 boxes 

- The ordered software release license (R5.4 license) 

- 500 internal or external entries in the LDAP directory 

- 5 spoken languages per country 

- Least Cost Routing (LCR) feature 

- Multisite feature 

- The embedded Aastra Management Portal with the following features (for more details see the 

R5.4 Product Guide) : 

o Installation and provisioning features: LDAP directory, voice messaging, IVR, DHCP and FTP 

servers for IP extensions, etc. 

o The configuration management: software and hardware inventories, updates/upgrades, 

backup/restore of the software and of the configuration, etc. 

o Security management: user’s rights, administrator’s accounts and profile, keys management, 

etc. 

o Alarms and errors management: filtering and routing of alarms, logs, SNMP traps, etc. 

o Performances management: state of services, state ad load of software and hardware 

resources, etc.

Licenses are provided in a key code linked with the identity number for the gateway. The identity 

number uniquely identifies the gateway. It is in the i-button included on the motherboard. 

Optional services to be ordered 

17 

• If needed, several software options can be ordered. Please take care of corresponding licenses 

(see chapter “Software licenses”). 

• IP licenses: up to 500 on AXD, AXL, AXS or AXS12, up to 50 on AXS6. An extension box 

does not increase the number of IP licenses. To increase number of IP licenses beyond these 

figures, an additional gateway or an A5000 server is necessary. 

• Languages when different than the default ones (total of up to 5 languages): please order the 

part numbers of the required languages. 

• Fixation kit (in cabinet or on a wall) should be ordered separately. 

• Battery cabinets are optional for AXS6, AXS12, AXS, AXL and AXD. Autonomy depends on 

the configuration. It is advised to order one battery cabinet per Aastra X Series box. 

There is a part number for battery cabinet for AXS6/AXS12/AXS cabinet, this cabinet is 

delivered with its 4 batteries 12V/2.1 A.h. 

There is a part number for battery cabinet for AXL/AXD cabinet, this cabinet is delivered with its 

4 batteries 12V/17 A.h. 

The battery cabinets can be integrated in 19 inches cabinets, be fixed on the wall, or be put on 

a table. 

It is necessary to also order also the battery cord to connect it. 

• Technical documentation CD-ROM is proposed as an option. 

Extension boards to be ordered 

Depending on the configuration and customer requirements, extension boards should be ordered (see 

previous chapters): 

Boards to connect phones: 

Analog network boards 

ISDN and digital network boards 

Data interfaces 

If the number of extension boards is beyond the capacity of the main box, one or two extension 

box may be ordered, depending on the type of gateway (max 1 on AXS12/AXS, max 2 on 

AXL/AXD). 

Concept of equipment cabled-equipped 

In the eQuation configuration tool, with each line, two columns are proposed: "equipped", and 

"cabled". 

An "equipped" board is taken into account in the configuration, and provided in the order (for 

example, 8 analog lines equipped cause the ordering of a LA8, for which a slot in the hardware 

configuration will be reserved). 

A "cabled" board is taken into account in the configuration, but will not be provided in the order (for 

example, 8 digital lines "cable lengths" cause the reservation of a slot for a LN8 in the hardware 

configuration, but does not cause the ordering of a LN8). This concept of "cabled" equipment makes it 

possible to envisage the case of an evolution and to anticipate it. 

Daughter boards to be ordered 

EIP daughter board on Aastra X Series motherboard (AXS6, AXS12, AXS, AXL and AXD) 

On the AXS, AXL and AXD motherboard (called UCVS, UCVL and UCVD) may be placed 1 or 2 EIP4, 

EIP-8, EIP-32 or EIP64 daughter boards. 

EIP-4 requires R5.3 SP1 minimum. 

EIP-64 requires UCV2 and R5.3 SP1 minimum 

This allows up to 128 channels without use of PT2 board.

VoIP daughter board on PT2 extension board 

On each PT2 extension board, may be placed 1 VOIP4E-8, VOIP4E-16 or VOIP4E-32 daughter 

board. This allows increasing moreover the VoIP capacity of the gateway. 

ADPCM16 daughter board for AXS6, AXS12 and AXS motherboard 

• An ADPCM16 board can be directly added on AXS6, AXS12 and AXS motherboard in order to 

increase the number of channels (from 2 to 4) on TDM DECT base stations S0 connected on 

the motherboard. It is also possible to deploy a GSM base station on the S0 port of this 

motherboard. 

• On its motherboard, AXS6 or AXS12 can support 2 TDM DECT base stations with 4 channels 

on its motherboard. On its motherboard, AXS can support up to 4 TDM DECT base stations 

with 4 voices. Number of TDM DECT base stations can be increased by addition of LD4 

boards. 

Duplication of an AXD simplex 

To duplicate an AXD simplex, here are the spare parts to be ordered: 

In the main box: 

- One UCV-D additional board 

- If the 1 st UCV-D has a 4GB Compact Flash, then the 2 nd UCV-D must have also the same 

4GB CF 

- 0, 1 or 2 EIP daughter boards: type and number of EIP on the 2 nd UCV-D must be the same 

as on the 1st UCV-D. 

- A power supply 

Be careful : both power supplies should be the same type : 

o either 2 ADS300XD, 

o or 2 ADS350XD, 

but no mix of the two types in the same box 

In each expansion box (if any): 

- One RUCV-D additional board 

- A power supply 

Be careful: both power supplies should be the same type 

o either 2 ADS300XD, 

o or 2 ADS350XD, 

but no mix of the two types in the same box. 

However, it is possible to have 

o 2 ADS350XD in one box (e.g. the main box), and 

o 2 ADS300XD in an other box (e.g. the expansion box) 

No additional license required for AXD duplication 

18

Multi-site DECT synchronization and Modect 

The DECT synchronization between TDM DECT base stations is required when hand-over 

(communication sustain when moving) is required between these base stations. 

DECT synchronization between base stations connected to one common PBX is provided by the PBX 

itself (mono-site handover) 

The DECT synchronization between base stations connected to different PBX in a multi-site 

requires addition links. 

It may be 

- CASE 1: DECT synchronization links between the base stations themselves (solution known 

as « Third pair distribution »). 

- CASE 2: or, for an easier cabling, DECT synchronization links between the sites (the PBX) of 

the multi-site. Each site then broadcasts the synchronization signal to its connected base 

stations. 

In the latter case (CASE 2: synchronization between sites), the solution depends on the cabling 

conditions. 

If (CASE 2A) 

- Links between sites are under 800 m long 

- And sites are connected to the same electrical power installation (typically inside a common 

building) with a common connection to the ground 

- And these sites are not in strong stormy zone (high keraunic activity) 

then the synchronization may be provided through an ISDN cabling between the DECT Synchro ports 

(see the installation technical documentation) : 

• on A5000 AXSeries or NeXspan, these ports are on the motherboard 

• on M6550, an BCSI + RHMIC kit – PN HT8113A – is required on the FPHBG2 backplane 

• on X500, an BCSI + RHMIC2 kit – PN AHT0714A – is required on the FPS backplane 

In the contrary (CASE 2B), a solution based on the Modect is required. 

This allows synchronization 

- between sites with a distance up to 1200m 

- including with galvanic isolation (separated ground connection), typically between two 

buildings on a campus 

- and to reduced impact of flashes of lightning (storms) 

The Modect is a hardware equipment to be installed on each site. 

The Modect kit that has to be ordered (equipment + specific cables to connect to the PBX) depends 

on the type of PBX. 

On NeXspan or A5000 Gateway (AXSeries), one BHR0151A Modect kit per gateway is required. 

On X500: 

o If an BCSI+RHMIC2 kit is already installed on the FPS, one BHR0152A Modect kit 

o If no BCSI+ RHMIC2 kit on FPS, 

o one BHR0153A Modect kit if the X500 is Master of synchronization 

o one BHR0154A Modect kit if the X500 is Slave of synchronization 

On M6550, 

o If an BCSI+RHMIC kit is already installed on the FPHBG/FPHBG2, one BHR0152A Modect kit 

o If no BCSI+RHMIC kit on FPHBG/FPHBG2, 

o If the system cluster is an FPHBG 

� one BHR0156A Modect kit if the M6550 is Master of synchronization 

� one BHR0158A Modect kit if the M6550 is Slave of synchronization 

o If the system cluster is an FPHBG2 

� one BHR0157A Modect kit if the M6550 is Master of synchronization 

� one BHR0159A Modect kit if the M6550 is Slave of synchronization 

19

C – DRG22i 


The DRG22i is a media-gateway providing a remote access to some analogue equipment through 

an IP link. 

20 

So, it allows connecting these analogue terminals remotely 

This solution is use full to deploy small offices and connect them to a central site through a 

WAN/IP router. 

The DRG22i has two (2) RJ11 analogue ports for terminals, one (1) WAN RJ45 port and one (1) 

LAN 10/100Mb/s RJ45 port. 

The DRG22i provides level 2 and 3 QoS features (VLAN tagging, DiffServ). 

The DRG22i may be interfaced through IP to the Aastra 5000, to connect 

• Analogue phones 

• Group 3 or Super Group 3 faxes 

The interface with the Aastra 5000 is in SIP line mode meaning the terminal is seen as a generic 

SIP terminal (requires a Generic IP license on the A5000 Server or AXSeries). 

The DRG22i is compatible with G.711 and G.729A for voice over IP. 

The DRG22i is compatible with G.711 and Fax T.38 for fax over IP. 

2. How to order the DRG22i 

The DRG22i for Aastra 5000 is available on the price list. 

Each analogue port used is seen by the Aastra 5000 (Server or Gateway), as a generic SIP terminal. 

A generic IP license is required in the A5000 Server or AXSeries, for each terminal connected on the 

DRG22i.

E – Software licenses 

1. Locking principles 

The Astra 5000 server and the Aastra X Series gateways (AXS6/AXS12/AXS/AXL/AXD) are delivered 

with the R5.4 software. This software provides more than 500 functions. Most of them are included. 

Some functions are locked and their use requires a license. 

This principle exists also on the applications. All the hardware associated with these software is 

uniquely identified by an ID, provided by Aastra services. 

This #ID is clearly recalled on the sticker on the mother board or on a sticker on the server provided by 

Aastra. In all cases, the #ID is accessible through the MMI of each server or gateway. 

We invite you, as soon as you receipt a system, to note this #ID and store it in your Customers 

database, as it will allow you to order and unlock new features that your customer would 

require. 

You software license order should include 4 essential data that our ADV services (or the online AKOP 

tool) require to be able to deliver a new license: 

� The part number of the software license 

� The #ID of the system (server or gateway) where this license will be used (#ID of the 

A5000 software or i-button) 

� The mail address where this license should be sent 

� The part number of the licensed customer (name or code created by the reseller) 

21 

Prior to any software license order, please check the compatibility of the platform with the 

license required. 

A5000 Server 

The software requires the configuration of the Identification key on the server. 

For software extensions, the #ID key should be noted, before to make an order of additional 

licenses. 

Gateway X Series 

The software requires the presence of an i-button on the hardware (UCV-S, UCV-L or iUCV-D). 

For software extensions, the #ID of the i-button should be noted, before to make an order of 

additional licenses. 

The i-Button simplifies the identification process, during migration or repair procedures. Indeed, 

the i-Button is unplugged from the board to be repaired or upgraded and plugged on the new 

board UCV-S, UCV-L or iUCV-D. 

Note: the i-button cannot be moved from one type of mother-board (e.g. UCV-S) to another 

type of motherboard (e.g. UCV-L), the software key would not function anymore in that case. 

2. Demonstration license 

To allow the demonstration of software features to a customer, a demonstration license is proposed to 

resellers, on each type of system.

The demonstration license opens all features for limited duration of 30 days (1 month). This license 

may be renewed once. 

Note: Before the end of the demonstration period, the old software key should be entered on the 

system, to retrieve the initial situation. 

3. New R5.4 systems and R5.4 software extensions 

3.1 ID and key 

In R5.4, a unique key unlocks all acquired licenses on a site (server or gateway). 

This key is mandatory to run the R5.4 software. 

This key is specific to the #ID of the site: 

- The A5000 USB dongle in case of the Aastra 5000 Server upgrade from R5.1, R5.2 or R5.3 

release 

- The ID key for new A5000 server or for virtualization on Aastra 5000 Server on VMware 

- The i-button in the case of the AXS/AXL/AXD gateways 

On a new system, the ID or i-button with its #ID is provided, and the R5.4 software key also, that 

unlocks all free and ordered licenses. 

For software extension, you must provide the #ID (of the dongle or ID or i-button) in the order, to 

obtain a new key for this site, with all previously acquired licenses + the new ordered licenses. 

� Please, one order per site (server or gateway), to reduce the risk of mistake. 

3.2 Free licenses 

To allow you to discover the AASTRA SIP phones offer, in R5.4 the new A5000 servers or Aastra X 

Series Gateways are provided with 

- 2 SIP Aastra licenses for free 

- + 5x100 LDAP directory entries for free 

- 5 Dialer licenses on AX Series Gateways 

The other licenses are to be ordered in addition, if required. 

3.3 Licenses « one by one » 

On Aastra 5000, all licenses with quantities are sold one by one (except the Directory license: per 

hundred entries). This allows you to order exactly the quantity required. 

Moreover, a licenses order does not depend on the quantity already acquired in the past. 

Example: to order 3 more CSTA licenses, you order the part « CSTA license up to 5 » indicating the 

quantity « 3 », whatever is the number of CSTA licenses already unlocked on this site. Note: the price 

applied does not depend on the quantity already acquired in the past, it is the price for CSTA 

unitary license between 1 and 5. 

3.4 R5.4 software licenses 

The following table summarizes the existing software licenses on R5.4. 

22

23 

Options 

R5.3 

IP licenses 

(audio, generic 

or mobile) 

Video licenses 

SIP Aastra 

Quantity to 

be ordered 

Monosite 

Multisite 

1 i 

1 I 

Remarks 

- A set of licenses where some IP subscribers are declared 

- License one by one, depending on the number and type of IP extension (see 

below) 

- A set of licenses where some IP subscribers are declared 

- License one by one, depending on the number of Video Blustar 8000i or Blustar 

for PC (see below) 

Trunk SIP 1 I 

- A set of licenses where the IP trunks are declared P 

- License one by one, depending on the number simultaneous communications on 

the SIP trunk 

Virtual TDM 1 i - A set of licenses on each site where some users are declared with a remote 

digital phone. 

- License one by one, one per digital phone connected on a remote gateway 

(remote from the site where the user is declared). 

G.722 codec 1 I - One per site where G.722 codec should be authorized 

G.729 codec 1 I - One per site where G.729 codec should be authorized 

Other codec 1 I - One per site where other voice codec than G.711, G.729 or G.722 should be 

authorized 

Video codec 1 I - One per site where Video over IP should be authorized 

VoIP Ciphering 1 i - One per site where VoIP ciphering is required 

Directory 1 i - on each site interfaced with the LDAP Directory 

- License depends on the number of entries (hundreds of), out of abbreviated 

numbers 

Media Server 

channels 

Simple (regular) 

voice mail box 

Unified voice 

mail box 

- 500 entries for free on each AXS6/AXS12/AXS/AXL/AXD 

1 I - A set of licenses on each A5000 Server where the Media Server is required 

- Unitary license per number of simultaneous communications on the Media 

Server, whatever are the voice services used : (music, announcement, IVR, voice 

messaging, 3 party conference) 

1 I - A set of licenses on each A5000 Server where the simple (regular) Integrated 

voice messaging is required for users declared on the A5000 Server 

- Unitary license per number of simple voicemail box (= per user) 

1 I - A set of licenses on each A5000 Server where the unified Integrated voice 

messaging is required for users declared on the A5000 Server 

- Unitary license per number of unified voicemail box (= per user) 

BVI Interactivity 1 i One per site where interactivity with the integrated voice mail is required on i/M7xx 

e-voicemail 1 i One per AXSeries site where e-voicemail is required. Do not forget LDAP directory 

licenses, where e-mail addresses are entered. 

i2070 1 i One per attendant console declared on the site (Windows i2070 attendant console) 

Aastra Dialer / 1 i One per Dialer or i2052 supervision. For the soft-phone feature, please order an IP 

i2052 CTI 

license – see later – Also required to supervise call pits from i2070. 

XML messaging 1 i One per channel on each site interfaced with UCP IP (for the ports declared as 

interface 

voice messaging groups). These licenses are included in UCP IP 2.0 packs 

- a pool of licenses per site containing an integrated CSTA server (so, connected to 

CSTA sessions 1 i 

a CSTA application) 

- May be replicated N times for securing or traffic capacity increase 

- License one by one, depending on the number of required CSTA sessions. 

- One per site containing an SAE internal server 


- includes: 

IAE - Hospitality 1 i Forwarding SAE: management of forwarding by SAE (incl. forwarding to voice 

mail) 

+ Multi-users SAE: read/modify through SAE the users number at head of a 

multiline/multi-directory number, including round-robin DDI

24 

Options 

R5.3 

Quantity to 

be ordered 

Monosite 

Multisite 

IAE – Hostel 1 i 

IAE – Extended 

ACD 

1 i 

Remarks 

+ Personal code SAE: read/modify through SAE the user’s personal code + 

locking through SAE of the outgoing network calls for a phone: the user must then 

enter the code to be able to perform an outgoing call. 

+ Pre-payment SAE: see/credit/erase through SAE of a pre-payment account, 

or to modify through SAE the tax value. 



- includes: 

Forwarding SAE: management of forwarding by SAE (incl. forwarding to voice 

mail) 



- includes: 

SURVOP SAE: See through SAE dynamical information of grouped lines, 

see/modify through SAE the parameters of grouped lines, of the state of a phone, 

of greeting services, of fictive waiting times. 

+ Super-groups SAE: See and modify through SAE the composition of a supergroup 

+ Greeting SAE: See and modify through SAE the priority levels of a 

greeting/attendant service 

+ Forwarding SAE: management of forwarding by SAE (incl. forwarding to 

voice mail) 

+ Break-in 

+ CDR Tickets >128 bytes 

Break-in 1 n One per site where break-in is required 

DISA 1 i One per site where some DISA numbers are declared 

V24-IVR interface 1 i One per site equipped with a V24 Voice messaging or IVR 

Q23 / extended 

Q23 IVR 

interface 

CDR Tickets > 

128 bytes 

1 i 

1 n 

One per site equipped with an analog Q.23 or Q.23 extended Voice messaging or 

IVR 

One per site where it is needed. In general, if required, on all sites of the multisite. 

Note: i : indicates that only one license is required or more depending on the “Remarks” column 

n = Number of site(s) using the feature 

3.5 IP licenses (audio) 

An IP license is required each time an IP or DECT-IP phone logs on the Aastra 5000. 

An IP phone connected a multi-line subscribing count for one. 

Most of SIP Aastra 67xxi phones include a conference bridge to provide the 3 parties conference 

feature. This feature requires no addition license, as the conference is performed on one line (do not 

require a second line on the phone). 

Associated IP phones connected on the same subscribing require as many IP licenses as the 

number of IP phones connected.

In R5.4, there are 3 types of IP licenses (audio) 

- The Mobile IP Aastra license 

o A6xxd, A142d and other DECT mobiles on Aastra DECT/IP base stations 

- The Audio IP Aastra license, for all Aastra IP/SIP wired phones and for VoIP channels of the 

applications : 

o i740, i760, i780, 5360ip, 5370ip, 5380ip 

o 6730i, 6731i, 6735i, 6737i, 6739i, 6751i, 6753i, 6755i, 6757i. 

o Audio Blustar Client softphone / Audio Blustar for PC softphone (additional Blustar 

Client license is required) 

o i2052 VoIP (Soft-phone) 

o ACP IVR 

o ACP conference bridge 

o TWP soft-phone 

o TWP media server (for the greeting messages of the « Rules » module) 

o TWP, ACP, i2070 or AS 7900 call pit. 

i2070 is able to supervise 56 users by default. Then a call pit should be 

configured for each 56 users more, with a maximum of 224 supervised users. 

Moreover, Dialer/i2052 CTI (VTI-XML) licenses are required to supervise these call 

pits from the i2070 application. 

o UCP IVR channel 

o UCP fax server channel 

o For UCP-IP ports defined as voice messaging groups, use XML messaging licenses 

provided in the UCP 2.0 packs 

o Terminals unlocked by Mobile IP Aastra license 

- The Generic IP license, which include the three others and allow also the connection of some 

other SIP wired or wireless phones and AMC. 

It is then possible to order exactly the type of IP license required, or possibly order Generic IP 

licenses, when the type of IP extension to be connected is unknown. 

Example: 

I order an AXS R5.4, with 4 x analog phones, 20 x SIP 6753i phones and 5 x 5370ip phones 

I already have 2 SIP Aastra licenses for free with the AXS. 

I order 23 Audio IP Aastra licenses, with the AXS. 

25 

Generic Audio IP 

DRG22i, AMCC 

Other phones/applis. (3rd party) 

Aastra Audio IP 

67xxi, 53xxip 

ACP/TWP/UCP VoIP 

BSC (requires a BSC license) 

Mobile IP 

DECT-IP (OMM)

Example: 

I order an AXS R5.4, with 4 x analog phones, 2 x 6731i phones and 20 other IP phones, which type is 

still not defined. 

I already have 2 SIP Aastra licenses for free with the AXS. 

I order 20 more Audio IP Aastra licenses, with the AXS. 

3.6 IP Video license 

The Aastra IP video license is required to use Aastra Video terminals : BluStar 8000i and Blustar for 

PC in Video configuration (on per terminal). 

Note: The Generic IP license only addresses the IP audio terminals, not the BluStar 8000i. 

The BluStar 8000i also requires the Video codec license and we recommend also the G.722 codec 

license. 

For more details, see the Product Guide: BluStar 8000i 

3.7 BluStar Client license 

The BluStar Client/Blustar for PC soft-phone requires a BluStar Client license and : 

- an Audio IP Aastra (or IP Generic) license for Audio softphone use 

- a Video SIP Aastra license for Audio/Video softphone use 

For more details, see the Product Guide: BluStar Client. 

3.8 Virtual TDM license 

In multisite, this license allows to declare a user on site A, even when the user has a TDM digital 

phone connected on another site (site B). 

This requires on site A, a virtual TDM license. 

Moreover, this license includes a Dual-homing license (see after). 

3.9 Dual-homing licenses on R5.3 

The dual-homing feature allows an automatic re-connection of IP pones or TDM digital phone on 

another site, in case they lose the connection with the first site (site or network out of order). 

This feature requires a license for each IP phone to be backed-up. 

The IP dual-homing license applies whatever is the type of phone used that supports this feature. 

The IP dual-homing license is linked to the site where the subscriber is declared (for IP phones this 

means on the same site than the IP license itself). You require as many licenses as phones for which 

you want the dual-homing feature. 

Note: In the case of the A5000 Server duplex, the dual-homing license is not required on the back-up 

server, it is automatically supported. 

Example: 

I have 100 subscribers on site A. I want dual-homing feature for 30 of these subscribers, with a backup 

on site B. 

I order 30 dual-homing licenses with the #ID of site A. 

26

In the Aastra Management Portal of the site where the IP subscribers are declared, I indicate the IP 

subscribers which profit by the dual-homing feature and I indicate for each one, the site on which it it 

can be backed-up (this, in the limit of the number of IP dual-homing licenses I have). 

The 1 st site will indicate to the back-up site the list of subscribers that this back-up site will be able to 

support in case of problem. 

subscriber 3010 

dual homing – site 2 

Crossed back-up 

It is possible to define a complete crossed back-up between site A and site B 

N IP subscribers declared on site A, M IP subscribers declared on site B. 

N dual-homing licenses on site A, M dual-homing licenses on site B. 

The subscribers of site A are configured with site B as their back-up site 

The subscribers of site B are configured with site A as their back-up site 

Note: For IP phones, M+N should be smaller or equal to the maximum of IP subscribers that s site can 

support 

Example: M+N

28 

Finally, I order an A5000 duplication kit. I must also order 200 duplex IP licenses for my back-up 

server. 

3.12 Directory licenses 

The directory module performing the interface with the A5000 LDAP directory has to be activated at 

the minimum on one the sites of the multisite (and on some other sites if redundancy of this interface 

is required, or for load sharing) 

It is through the directory module that all requests to browse the directory will go: call by name, CNID, 

e-mail address search for e-voicemail feature. This module plays some kind of proxy role. 

Sites of the multisite which would have not this directory module activated, automatically communicate 

with other sites to be able to provide these features.. 

On each site where the directory module is activated, directory licenses are required, to be able to 

perform the call by name, CNID and e-voicemail feature. If this site detects that the number of entries 

in the LDAP directory is under the number of directory licenses, these features will be disabled. 

In the LDAP directory: 

- Each internal entry (user), and each external entry (contact) counts for 1 (including 

abbreviated numbers) 

- Forbidden numbers are not counted for licensing. 

- A user with several phones (associated phones) counts for 1. 

- A multi-users phone counts for as many entries as the number of users of the phone. 

- In case of a hunting group, 1 license should be added for the head of the hunting group. 

- A virtual phone (for call pits, or TWP supervision) counts for 1. 

- In case of round-robin DDI numbers (hotels, hospitals), each DDI number counts for 1, even if 

all are not used simultaneously. 

Physically the Aastra LDAP directory (or a replication) may be on 

• Aastra X Series: then limited to 3000 entries, 

• Aastra 5000: then limited to 80 000 entries, 

• Aastra Management 7450: then limited to 80 000 entries, or 200 000 for installed base (park) 

management. 

Note: 

• If the number of entries (and licenses) required is beyond 3000 entries, then the LDAP 

directory database should be placed on an A5000 or an AM7450 

3.13 UCP IP messaging 

UCP IP face to 

- Aastra 5000 requires 

o For each VoIP port declared as a voice messaging group: one XML messaging 

interface license per port. This license is included in the UCP 2.0 packages 

o For each other type of UCP IP VoIP port (IVR port, or fax server port): one IP 

proprietary or Generic IP license is required. 

- Reminder : face to R4.2, requires 

o For each type of UCP IP VoIP port of any type (voice messaging group, IVR port, or 

fax server port) : one IP license is required. 

3.14 TAPI 

The TAPI offer is described in the chapter 64 of the Aastra 5000 R5.3 Product Guide

If a maximum of 4 TAPI users on Windows OS are required, a Direct TAPI solution may be used, 

without TAPI gateway. In that case, order 

TAPI Open Suite Direct R3.2 - AHT0169A, which is well suited for 1 to 4 users 

In the other cases, it requires 

o The TAPI gateway AHT0168A (software provided with an USB dongle) 

o + TAPI Open Suite IP licenses depending on the number of users : see the price list 

There is no TAPI license required on the A5000 sites. 

3.15 Round-robin DID (Hostel/Hospitals) 

When the number of DID is not enough for the whole customers or patients, the round-robin DID 

feature may be used. A DID number is assigned to each user requiring one, then frozen for a defined 

period before allowing to reuse it for somebody else. 

In order to perform this feature, you require 

- an external application (Front office or billing application) to manage the DID numbers 

- The Hospitality license (Hospital SAE) to interface the application 

- Corresponding directory licenses (see §3.12) 

Note: on Aastra 5000, it is no more required to use some digital ports or supplementary IP licenses to 

manage SDA assignment as it was the case on the NeXspan range. 

3.16 i2070 (Attendant console) 

The i2070 attendant application requires different type of licenses 

- i2070 license: one per console declared on the site 

- IP proprietary license (or Generic IP) 

The i2070 attendant application is able to supervise 56 users by default. Then a call pit should be 

configured for each 56 users more, with a maximum of 224 supervised users. 

o from 57 to 112 subscribers supervised : 1 call pit 

o from 113 to 168 subscribers supervised : 2 call pits 

o from 169 to 224 subscribers supervised : 3 call pits 

Each call pit requires 

- either one IP subscribing with an IP proprietary (or Generic IP) license 

- Dialer/i2052 CTI (VTI-XML) license. 

each of these call pits required and « Dialer/i2052 CTI » (VTI/XML) license to be supervised from 

the i2070 application 

3.17 Media Server (A5000 Server) 

The Media Server of the A5000 Server provides the following features 

- Music, announcements, vocal guides 

- Voice messaging (simple or unified) 

- IVR 

- 3 party conference. 

The « Media Server Channel » license opens the access to the Media Server in term of number of 

simultaneous communications. 

The next table helps to assess the number of channels required depending on the features and 

usage. 

29

The dimensioning for the IVR is depending directly on the nature of service provided. Moreover, to use 

this feature the IVR license is required. 

Regarding music, announcement or guides for users declared on the A5000 Server, it is possible, 

by configuration, either to use the local voice resources of the media server or the resources on some 

gateways of the multisite. In the table, it is supposed that the local resources of the Media Server are 

used. 

Regarding the voice messaging, 3 levels of usage are proposed in the table: low, medium, high. To 

open the integrated voice messaging feature, do not forget, Simple (regular) mail box and/or unified 

voice mail box licenses per user. 

Regarding the 3 party conference, SIP 67xxi are not concerned as they have an embedded 

conference bridge in the phone. The dimensioning is so far for the other phones declared ont the 

A5000 Server. 

Service 

Nb 

of uses 

30 

Music 

announcement 

guides 

Voice 

messaging 

Low 

usage 

Voice 

messaging 

Medium 

usage 

Voice 

messaging 

High 

usage 

3 party 

conference 

(Out of SIP 

Aastra 67xxi) 

50 4 2 4 6 6 Depends on the use 




1 000 14 7 14 21 18 Depends on the use 


















3.18 e-voicemail 

Media Server dimensioning (number of channels) – for information 

The e-voicemail license is required to profit by this feature which sends a copy of the voice mail 

(« .wav » file) to the e-mail server. 

Since R5.3, 

- The part number of this license for an AXS is BHW1857A 

- The part number of this license for an AXL/AXD/A500 is BHW1858A 

For R5.1 and R5.2, 

- The part number of this license for an AXS/AXL/AXD/A500 is BHW1858A 

IVR

4. How to order software licenses 

Fill the order: 

For a new system, we recommend to us Aastra Plan. In the order you may add: 

� The list of part numbers of software licenses and the quantity for each. 

How to order supplementary software licenses (extension): 

You may send an order to Aastra ADV services or use the AKOP online tool. 

Access to the AKOP tool is protected and you should have an account prior to use it. 

31 

In both case you need: 

� The part number of the software license 

� The #ID of the system (server or gateway) where this license will be used (ID key or #ID 

of the dongle or i-button) 

� The mail address where this license should be sent 

� The part number of the licensed customer (name or code created by the reseller) 

Note: delay to get a new key is very short 

• Immediately on the online tool (AKOP) 

• within 48H by fax to the Aastra sales department (Administration des Ventes) 

5. Credits 

After receipt and unlocking of a software feature erroneously, or if there is a change in the site 

concerned, you may require some credits to the Aastra sales department. 

These credits will be allowed only after dongle or i-button has been returned. 

6. UCV board standard replacement 

The i-Button simplifies the process to replace an UCV motherboard UCVS or UCVL. 

• UCV board replacement by a board from the reseller stock 

- During the replacement the i-button of the board to be replaced is removed and then 

placed on the new UCV board. 

- The UCV board which is out of order may be replaced by Aastra (See Spare and repair 

price list) 

7. License move 

The software licenses are linked to the identification of a system (ID i-button or dongle), and cannot be 

moved to another system, by default. 

For instance, a Generic IP license of an Aastra XD is linked with this system, and cannot be moved to 

another, by default. 

However, to facilitate the evolutions, it is possible to ask for a commercial exemption, in order to move 

some licenses for a given customer. 

For instance, centralization of licenses on a site of the multisite.

In such a case, information to be provided with the order is 

- list and quantity of licenses to be moved 

- ID of the origin system and ID of destination system 

- Reasons of the move 

- Identity of the end customer 

Moreover, the APR0156A service part number should be ordered (see Aastra price list). 

Some additional price may be required by Aastra when, in the Aastra price list, the licenses moved are 

more expensive on the target system than on the origin system. 

Also, if the destination site is an A5000 Server in a release more recent than the origin site (whichever 

type), Aastra may ask for the price of migration of the IP and SIP trunk licenses on A5000 Server (see 

Price List). 

Aastra keeps the right to allow or not this licenses move, case by case. 

8. Virtual TDM to IP terminal migration 

For specific case of migration from Virtual TDM (with subscriber already centralized on A5000 server) 

to IP terminals on the same A5000 server, 86F00079AAA-A reference (one per user) has to be used 

to benefit of a cheaper price than Audio IP extension licenses. 

32

F – Hardware maintenance: spare parts 

In order to reduce the onsite maintenance delays, it is possible to stock some spare parts. Spare parts 

are proposed in the Price list. 

Spare parts: 

- Mother boards 

- Compact Flash memory cards 

- Extension boards 

- Power supply 

- VADS fan racks (for simplex XD/AXD) 

- Cover front planes for empty slots 

- Plastic lockers (to fix the boards) 

The following table gives the compatibility of the spare parts with the AXSeries gateways. 

Note: the Compact Flash cards supported by Aastra X Series are exclusively proposed on the Aastra 

Price list. 

Compatibility R5.3 Mother board 

33 

AXS-6 Yes UCV1S/UCV2S 

AXS-12 Yes UCV1S/UCV2S 

Other 

mandatory 

board 

EXT1S- 

6/EXT2S-6 

EXT1S- 

12/EXT2S-12 

AXS Yes UCV1S/UCV2S EXT1S/EXT2S 

AXS 

ext. box 

Yes 

RUCVS or 

RUCTS 

Compact 

Flash 

2GB or 

4GB 

2GB or 

4GB 

2GB or 

4GB 

ADPCM 

on 

mother 

board 

EIP on 

mother 

board 

Yes Yes 

Yes Yes 

Yes Yes 

No No No No 

AXL Yes UCV1L/UCV2L No 4GB No Yes 

AXL 

ext. box 

Power 

supply 

ADS150X 

or ADS100X 

ADS150X 

or ADS100X 

ADS150X 

or ADS100X 

ADS150X 

or ADS100X 

ADS300X or 

ADS350X 

Yes 

RUCVL 

or RUCTL 

No No No No 

ADS300X or 

ADS350X 

ADS300XD 

AXD Yes UCV1D/UCV2D I-UCVD** 4GB No Yes or*** 

ADS350XD 

Yes 

RUCVD 

or RUCTD** 

No No No No 

ADS300XD 

or*** 

ADS350XD 

** see NeXspan => A5000 gateways migration chapter for more details 

*** : Be careful : do not mix the two types of power supply inside a given AXD box 

UCV2 requires R5.3 SP1 or R5.2 SP3 

EIP4 requires R5.3 SP1 minimum 

EIP64 requires UCV2 and R5.3 SP1 minimum 

AXD 

ext. box 

AXSeries spare parts 

Fan rack 

No 

No 

No 

No 

No 

No 

VADS 

AXD simplex 

VADS 

AXD simplex

6. Standard replacement of UCV motherboard with its key 

The i-Button simplifies the replacement process of the UCV-S or UCV-L board 

• Replacement of the UCV board out of order by a new board from the reseller stock 

- The replacement in customer premises is done by removing the i-button from the out of 

order board and plugging of this i-button on the new board. 

- The reseller may ask for a standard replacement to the CDR (repair centre). 

- The CDR sends the new board as soon as it receives the fax 

- The reseller sends back the out of order board, to the CDR. 

Note: 

- UCV1 board is compatible since R5.1 

- UCV2 requires R5.3 SP1, and is compatible with R5.2 SP3 

G – Demo packs 

To allow resellers be able to launch some demonstration or lab tests, Aastra proposes some demo 

packs. 

These packs are 

- Limited to the only usage of lab test or demonstration platform 

- Non extensible 

- Provided in limited quantities for each reseller. 

The content of each pack is presented in the table below. 

The idea is to allow the capacity to demonstrate all the features. 

Some software subscription part numbers are also provided (for free), to be ordered with the demo 

pack. 

34 

Demonstration Packages and tools 

Description qty PART NUMBER 

A5000 Server R5.4 - demo pack – physical or virtualized BHT1341BDEX 

DVD SOFT + DOC A5000 R5.4 1 

R5.4 A5000 Software license 1 

Identification key 1 

Generic IP license 5 

i2052 CTI license 5 

CSTA license 5 

Directory license (100 entries) 1 

SIP Trunk license 2 

Extended ACD (ACD+Hotel+Long CDR) license 1 

Hospitality license 1 

Listening and break-in license 1

35 

VoIP ciphering license 1 

Media Server License 2 

Unified Voice messaging 1 user 2 

IVR 1 

G.722 Codec 1 

G.729 Codec 1 

Other Codecs 1 

Video Codec 1 

BluStar softphone license 2 

IP Video user license 2 

Software subscription 3 years - A5000 Server Demo Pack AHE0120A 

A5000 Server R5.3 duplex - demo pack - physical or virtualized BHT1342BDEX 

DVD SOFT + DOC A5000 R5.4 1 

R5.3 A5000 Software license 1 


Duplication license 1 





SIP Trunk license 2 



Listening and break-in license 1 




IVR 1 

G.722 Codec 1 

G.729 Codec 1 


Video Codec 1 



Software subscription 3 years - A5000 Server Demo Pack AHE0120A 

A5000 Server R5.4 demo pack for HP Procurve zl module BHT1259BDEX 

USB key with SOFT + DOC A5000 R5.4 1 

R5.4 A5000 Software license 1 






SIP Trunk license 2

36 



Listening and break-in license 1 


HP Procurve zl module license 1 



IVR 1 

G.722 Codec 1 

G.729 Codec 1 


Video Codec 1 



Aastra X Series R5.4 demo pack BHT0587BDEX 

AXS12 R5.4 2T0+2T0/S0+8Z+4I 1 

VOIP board for UCV - 8 channels (EIP8) 1 

e-voicemail AXS/AXL/AXD License 1 

IVR AXS/AXL/AXD license 1 

BVI interactivity AXS/AXL/AXD License 1 

DISA AXS/AXL/AXD License 1 

CSTA License 5 

extended ACD License 1 

Hospitality License 1 

SIP Trunk 1 Simultaneous communication License 2 

VoIP Encryption License 1 

Generic IP License 3 

SIP Aastra IP License 2 


Directory 100 records License 1 

i2070 attendant License 2 

Aastra AXS Integration service 1 

Personalized language 1 (to be confirmed in the order) 1 

Personalized language 2 (to be confirmed in the order) 1 

G.722 Codec 1 

G.729 Codec 1 


Video Codec 1 



Software subscription 3 years - AXSeries Demo Pack AHE0121A

R5.1 to R5.4 upgrade 

R5.1 to R5.4 migration may be applied to 

- Aastra XS6 (AXS6), Aastra XS12 (AXS12), Aastra XS (AXS) 

- Aastra XL (AXL) 

- Aastra XD (AXD) 

- Aastra 5000 Server 

AXSeries 

Regarding the Aastra X Series gateways, the R5.1 to R5.4 upgrade kit is composed of 

- The R5.4 software key which includes the basic features and the additional licenses already 

acquired in R5.1 (all the software licenses acquired in R5.1 stay available after the upgrade). 

The G.729 codec and “other codec” licenses are included in the migration kit. 

- The new 4GB Compact Flash card (quantity = 2, when AXD duplex) 

The 4GB Compact Flash card is provided to replace the existing one on the gateway motherboard. 

This replacement is 

- Mandatory when migrating to R5.4 with more than 100 users (100 voice mail boxes). 

The replacement of the Compact Flash is performed with a back-up restore process of all the data, 

including the voice messages in the integration voice messaging application. This process takes 

around 20 minutes per gateway. 

There is no other hardware impact, when upgrading an AXSeries gateway from R5.1 to R5.4. 

When the gateway is under software subscription, please indicate the fact that it is under software 

subscription in the order, and the migration kit will be billed at the price of the Compact Flash. 


Regarding the Aastra 5000 Server, it is required to use the CentOS or RedHat 6.2 64 bits Linux OS. 

When the configuration is unchanged, the hardware server may be kept if it is compatible with CentOS 

pr RedHat 6.2 64 bits, for instance the Dell servers previously proposed by Aastra : PE2950-III, R200, 

R210, R300, R310 and R410 are compatible, except PE860). For more details on the upgrade 

process, see the technical documentation. 

The R5.1 to R5.4 simplex Aastra 5000 Server (virtualized or not) upgrade kit is composed of 


acquired in R5.1, except the IP licenses and SIP trunk licenses (see below) 


To retrieve the IP licenses on Aastra 5000 Server R5.4 when upgrading from R5.1, it is mandatory to 

order the upgrade of the IP license (quantity : as many as IP licenses in R5.1). The type of the 

Generic IP or Mobile IP is unchanged after the upgrade, the IP proprietary and SIP aastra licenses are 

replaced by Audio IP Aastra licenses. 

To retrieve the SIP Trunk licenses on Aastra 5000 Server R5.4 when upgrading from R5.1, it is 

mandatory to order the upgrade of the SIP Trunk license (as many as SIP Trunk licenses in R5.1). 

The R5.1 to R5.4 duplex (back-up server) Aastra 5000 Server (virtualized or not) upgrade kit is 

composed of 


acquired in R5.1 (the IP licenses and SIP trunk licenses are freely upgraded to R5.4) 

- An USB dongle for duplex use (the former USB dongle should be sent back to Aastra). 

37

If the Aastra 5000 server is under software subscription, the upgrade kit is for free. Please mention 

the fact that it is under software subscription, in the order. 







AXSeries 


















or RedHat 6.2 64 bits , for instance the Dell servers previously proposed by Aastra: PE2950-III, R200, 



The R5.2 to R5.4 simplex Aastra 5000 Server upgrade kit is composed of 






Generic IP or Mobile IP is unchanged after the upgrade, the IP proprietary and SIP Aastra licenses are 



mandatory to order the upgrade of the SIP Trunk license (as many as SIP Trunk licenses in R5.2). 

The R5.2 to R5.4 duplex (back-up server) Aastra 5000 Server upgrade kit is composed of 

38

39 











AXSeries 

















or RedHat 6.2 64 bits , for instance the Dell servers previously proposed by Aastra: PE2950-III, R200, 



The R5.3 to R5.4 simplex Aastra 5000 Server upgrade kit is composed of 





Generic IP or Mobile IP is unchanged after the upgrade, the IP proprietary and SIP Aastra licenses are 



mandatory to order the upgrade of the SIP Trunk license (as many as SIP Trunk licenses in R5.3).

The R5.3 to R5.4 duplex (back-up server) Aastra 5000 Server upgrade kit is composed of 





NeXspan to R5.4 migration 

The migration to R5.4 concerns 

- The NeXspan Communication Server (NCS). 

- The NeXspan S (XS) 

- The NeXspan L (XL) 

- The NeXspan D (XD) 

A - Migration from NCS to A5000 R5.4 

If you want to make a NeXspan Communication Server (NCS) evolve and transform it in an Aastra 

5000 server R5.4, you require 

- The Linux CentOS or RedHat ES 6.2 64 bits Operating system 

(NCS ran on Windows, Aastra 5000 Server R5.4 runs on Linux 6.2) 

- The R5.4 software release key 

The price of the migration depends on 

- The number of IP subscribers (IP licenses) on the NCS server when upgrading 

- The release of the NCS to be upgraded : R4.2, or R4.1 or below 

To perform the migration, you should order: 

- The part number of the software migration kit which contains 

- 1 DVD-ROM including 

- the Aastra 5000 software to be installed on Linux CentOS or RedHat ES 6.2 64 bits 

- the Aastra 5000 technical documentation 

- 1 Identification key to identify the A5000 server (dongle different from the NCS one) 

- The software key that unlocks the R5.4 release and the licenses included or acquired 

40 

- The number of upgrades of NCS IP licenses (from the NCS release to R5.3). 

- this allows to transform the NCS IP licenses in R5.4 Generic IP licenses, on the A5000 

server. 

- This number should be lower or equal to the number of IP licenses present on the NCS, 

before the upgrade. 

Note: all software licenses present on the NCS (directory, CSTA, etc.) stay acquired after the upgrade. 

The G.729 codec and “other codec” licenses are included in the migration kit. For more details, see 

chapter C – software licenses. 

The order for migration of NCS to R5.4 should indicate the #ID of the NCS USB dongle, in order for 

Aastra to be able to provide an R5.4 key including the previously acquired software licenses. 

� The NCS USB dongle will be returned to Aastra within one month, after the upgrade kit delivery. 

If not, Aastra will send an invoice for the full A5000 server price, instead of the migration price. 

Example: 

to migrate one NCS R4.1 with a « 100 IP subscribers » license, I order

- The NCS to A5000 Server software upgrade kit 

- 100 x « migration of IP license NCS R4.2 or below to R5.4 » 

I join to my order the #ID on the NCS USB dongle. 

After the migration, and within one month, I will send back to Aastra the NCS USB dongle. 

To upgrade a duplicated NCS to R5.4, you should process the same way 

- For the main server on one hand 

- For the back-up server on the other hand. 

For the back-up server, the migration of IP licenses is for free. Please underline the fact that it is a 

back-up (duplex) server inn the order. 

41

B - Migration of NeXspan S12/S/L/D to Aastra X Series 

AXS12AXS/AXL/AXD 

1. Prerequisites 

To transform a NeXspan gateway to an Aastra X Series gateway, it is required at the minimum to 

change the motherboard and upgrade the software. 

A migration order toward an R5.4 gateway should include 2 part numbers at the minimum: 

- The part number for the hardware migration kit. 

- And the part number for the software migration kit. 

The i-button of the NeXspan XS12, XS, XL or XD is reused on respectively the Aastra X Series 

AXS12, AXS, AXL or AXD. 

All features or licenses acquired on a NeXspan system are transferred in the new gateways when 

upgrading to R5.4. 

For more details see chapter C – Software migration. 

2. Hardware migration 

The hardware migration will be performed as an exchange in advance. Aastra X Series are sent to the 

customer. NeXspan components will be sent back to Aastra within one month. 

In case of an active software subscribing (software evolution maintenance), only the hardware 

migration has to be paid. The software migration kit is included in the maintenance contract. 

NeXspan C systems do not evolve in R5.x. The R4.2 is the last software release of NeXspan C. 

What should be replaced? 

The following table summarizes what should be replaced on the hardware point of view. 

For each type of box, components that are mandatory to replace are grouped in the hardware 

migration kit. 

Please check, in the LCI documentation of the latest software release, the detailed release of the 

hardware boards and backplanes supported. 

XC 

Box 

Main 

box 

Extension 

box 

Main 

box 

Extension 

box 

Main box Extension 

box 


box 


XS12/XS/XS-e* XL XD Simplex XD Duplicated P.S. 

XD duplex 

box 

Box NE yes* yes* option option option option option option option option 

Backplane NE N/A N/A Note Note N/A N/A N/A N/A N/A N/A 

Motherboard NE yes* yes* yes option yes option yes option** yes option** 

Duplex motherboard N/A N/A N/A N/A N/A N/A N/A N/A N/A yes option** 

I-UCT board N/A N/A N/A N/A N/A option N/A option N/A yes N/A 

Power supply NE yes* yes* option option option option option option option option 

Duplex Power supply NE N/A N/A N/A N/A N/A N/A option option option option 

Extension boards N/A option option option option option option option option option option 

Front panel N/A option option option option option option option option option option 

Battery box NE option option N/A N/A N/A N/A N/A N/A N/A N/A 

Extension box cable NE NA yes NA no N/A no N/A no N/A no 

yes 

* the new AXS box is provided with the power supply and the motherboard 

** the+D26 R-UCVD allows the remote identification (Info page) and the hot plug of the extension box 

mandatory replacement obligatoire 

Note Mandatory replacement if the backplane is older than HJ4630AC01 

option replacement only to change the colour 

no replacement not required 

NE non evolutive : not available R5.1 

N/A not applicable 

42

3. NeXspan C 

No possible migration. NeXspan C does not evolve in R5.x. The R4.2 is the last software release of 

NeXspan C. 

4. NeXspan S12/S-E/S to Aastra XS12/S-E/S 

Migration of the main box 

For NeXspan S12, S-E or S migration to AXS12, AXS-E or AXS R5.4, it is required to change: 

The software (R5.4): present on the Compact Flash included in the hardware migration kit 

The software release license (R5.4) : included in the software migration kit 

The motherboard (the new one includes the new 4GB compact flash): 

included in the hardware migration kit 

The box: included in the hardware migration kit 

The power supply: included in the hardware migration kit 

These components are in the migration kits. 

If it is required to fix the box, the AXS fixation kits should be ordered in addition. 

Extension box migration 

There was no extension box on NeXspan S12. 

In case of an XS extension box, those parts should also change in the extension box: 

The motherboard: included in the hardware migration kit 

The box: included in the hardware migration kit 

The power supply: included in the hardware migration kit 

The extension box cable: included in the hardware migration kit 

If it is required to fix the box, the AXS fixation kits should be ordered in addition. 

5. NeXspan L to Aastra XL 

Main box migration 

For NeXspan L migration to AXL R5.4, it is required to change: 

• The software (R5.4) : included on the Compact Flash in the hardware migration kit 

• The software release license (R5.4) : included in the software migration kit 

• The motherboard including the new 4GB CF (which is included in the hardware migration kit) 

• The Backplane in the case it is not compatible. Since R5.1, it is required at the minimum 

HJ4630AC01. Otherwise, a new backplane BHJ4630A should be ordered in addition. 


The extension box of NeXspan L is compatible with R5.4. It is not mandatory to change it. 

However, the minimum hardware release for the backplane is HJ4630AC01. In case the backplane is 

older than that, it should be replaced: a new backplane BHJ4630A should be ordered. 

Regarding the R-UCTL mother board: 

43

- If technical release is minimum HJ4613ACxx, it is compatible with an AXL extension box, no need 

to change it. 

- Otherwise, it should be changed by an R-UCVL 

The R-UCVL board is also compatible with a NeXspan L extension box. 

6. NeXspan D to Aastra XD 

Main box migration 

For NeXspan D simplex migration to AXD R5.4, it is required to change: 

• The software (R5.4) : included on the Compact Flash in the hardware migration kit 

• The software release license (R5.4) : included in the software migration kit 

• The motherboard including the new 4GB CF (which is included in the hardware migration kit) 

For NeXspan D simplex with duplicated power supply migration to AXD R5.4, it is required to 

change: 

The R5.4 software 

The R5.4 software release license 

The motherboard including the new 4GB CF 

For NeXspan D duplex migration to AXD R5.4, it is required to change: 

The R5.4 software 

The R5.4 software release license 

The two motherboards including the new 4GB CF 

Note: if it is then required to transform the simplex mode to a duplex mode, it is then mandatory to 

replace the iUCVD board by the new iUCVD board (black one) part number BHJ4855A. 


The extension box of NeXspan D is compatible with R5.4. It is not mandatory to change it. 

For NeXspan D extension box migration to AXD R5.4, it is required to replace: 

The R-UCTD mother board by an R-UCV-D (see price list for this board) 

The R-UCV-D provides the remote identification (Info page) and the possibility to hot plug the 

extension box (cable between main and extension box). 

The R-UCVD board is also compatible with a NeXspan D extension box. 

44

7. What should be sent back to the Repair Center (CDR) 

The hardware migration will be performed as an exchange in advance. Aastra X Series are sent to the 

customer. NeXspan components will be sent back to Aastra within one month. 

For an XS: 

The box 

The motherboard without i-button 

The power supply 

For an XL: 

The motherboard without i-button 

For an XL: 

The motherboard(s) 

The iUCTD without i-button 

If in the one month delay, the NeXspan components are not sent back to the repair center (CDR), an 

invoice will be sent for the migration kits at the price of a new gateway (price list). 

8. Migration of the extension boards 

The RJ45 extension boards of NeXspan XS/XS12/XS-E, XL and XD are compatible with Aastra X 

Series R5.4. It is not mandatory to change them. 

Note: Firmware and hardware components may have evolved since R3.1. Please check the minimum 

technical hardware baseline (release) of the board before using it on R5.4 (see hereafter). 

45

List of boards compatible with R5.4 

46 

Board Description Part number 

Subscribers boards 

LA16 rj 16 analogue extensions HJ4431A 

LA16-8 rj 8 analogue extensions HJ4431B 

LA8-rj 8 analogue extensions HJ4714A 

LH16 rj 16 analogue extensions with message lamp HJ4830A 

LH16-8 rj 8 analogue extensions with message lamp HJ4830B 

Minimum 

baseline* for 

A5370 & A5380 

compatibility 

LM8 rj 4 digital extensions + 4 analogue extensions HJ4726A HJ2781AC09 

LN8 rj 8 digital extensions HJ4715A HJ2764AC09 

LN16 rj 16 digital extensions HJ4475A HJ4475AC04 

LN16-8 rj 8 digital extensions HJ4475B HJ4475BB04 

Other boards 

CA1 rj 4 V24/V10 asynchroneous ports + cable 

HT7852A 

HJ4722A 

CP1 rj 2 circuit-packet boards HJ4721A 

CS1 rj 2 X25 synchronous ports + cable 

HT7853A 

HJ4720A 

LD4 rj 4 T0 / S0 / DECT BS interface HJ4741A 

LD4NX rj 4 T0 / S0 / DECT BS interface 

HT8009A 

HJ4699A 

LI1 rj 2 tie lines + cable 

HT7854A 

HJ4718A 

LR4d rj 4 analogue network ports, (+ tone detection.) HJ4717F 

LR4d rj 4 LRA (+ tone detection) Spain HJ4717L 

LR4d rj 4 LRA (+ tone detection) Germany HJ4717M 

LR4d rj 4 LRA (+ tone detection) Brazil HJ4717N 

LR4d rj 4 LRA (+ tone detection) Mu law HJ4717R 

LR4d rj 4 LRA (+ tone detection) Holland/Poland HJ4717Z 

LT2X rj 1 ISDN PRI or MIC port HJ4738A 

MUM rj i MUX board 

HT7847A 

HJ4723A 

PT2X rj IP gateway board HJ4724A/B/C 

IPS rj 

SIP access board 

(since R5.1: SBC NAT traversal feature only) 

AHJ0004A 

* The baseline syntax is « XNN »: where 

o « X » is a letter that identifies the hardware baseline 

o « NN » is a number that identifies the Printed Circuit Board (PCB) 

Example: if minimum baseline is C04, 

A board with C04, C05 or D05 is accepted 

A board with B05 or D03 is not accepted 

Stocko format 

When migration of a NeXspan XL or XD (grey box) with Stocko format boards, to R5.1, R5.2, R5.3 or 

R5.4, you may keep the Stocko extension boards. This is also true for the XL and XD extension boxes 

(2XL, 3XL, 2XD, 3XD).

Stocko format extension boards are not compatible with Aastra X Series boxes (black boxes). 

You cannot keep the Stocko boards on NeXspan XS when migrating to R5.1, R5.2, R5.3 or R5.4 as 

this migration implies the replacement of the box by an AXS one (black box). In case of migration of 

NeXspan S, you must remove Stocko extension boards, and may replace by RJ45 extension boards. 

IPS board 

On Aastra X Series, the SIP interface (signaling proxy) is integrated in the mother board. The IPS 

boar cannot be used for this feature on Aastra X Series. However, the IPS board may be used for 

SBC (Session Border Controller) role. 

9. Color change through standard replacement 

In addition to mandatory hardware evolution, it is possible to ask for a color change, for esthetical 

reasons. This concerns the boxes, extension boards, battery boxes, and fixation kits. 

This is performed though exchange in advance with the Repair Centre (CDR): see the repair price list. 

See the “Hardware migration” table to check all equipment that may optimally be replaced to change 

the color. 

Please check the minimum baseline (hardware release) of the extension boards before ordering a 

replacement. 

The baseline syntax is « XNN »: where 

o « X » is a letter that identifies the hardware baseline 

o « NN » is a number that identifies the Printed Circuit Board (PCB) 

Example: if minimum baseline is C04, 

A board with C04, C05 or D05 is accepted 

A board with B05 or D03 is not accepted 

47

List of boards compatible with the color change service 

48 

Board Description Spare parts 

System boards 

XD connection board (must be replaced by an 

IUCT-D 

I-UCVD to support the AXD duplex feature) 

Subscribers boards 

Minimum baseline* 

to allow color 

change 

HJ4855B A03 

LA16 rj 16 analogue extensions HJ4431A A02 

LA16-8 rj 8 analogue extensions HJ4431B A02 

LH16 rj 8 analogue extensions HJ4830A A01 

LH16-8 rj 16 analogue extensions with message lamp HJ4830B A01 

LM8 rj 8 analogue extensions with message lamp HJ4726A A01 

LN16 rj 4 digital extensions + 4 analogue extensions HJ4475A B03 

LN16-8 rj 8 digital extensions HJ4475B A02 

Other boards 

CA1 rj 4 V24/V10 asynchronous ports + cable 

HT7852A 

HJ4722A 

A01 

CS1 rj 2 X25 synchronous ports + cable 

HT7853A 

HJ4720A 

A01 

LD4NX rj 4 T0 / S0 / DECT BS interface 

HT8009A 

HJ4699A 

J03 

LI1 rj 2 tie lines + cable 

HT7854A 

HJ4718A 

A01 

LR4d rj 4 analogue network ports, (+ tone detection.) HJ4717F A01 

LR4d rj 4 LRA (+ tone detection) Spain HJ4717L B01 

LR4d rj 4 LRA (+ tone detection) Germany HJ4717M B01 

LR4d rj 4 LRA (+ tone detection) Brazil HJ4717N B01 

LR4d rj 4 LRA (+ tone detection) Mu law HJ4717R B01 

LR4d rj 4 LRA (+ tone detection) Holland/Poland HJ4717Z B01 

LT2X rj 1 ISDN PRI or MIC port HJ4738A A01 

PT2X rj IP gateway board HJ4724A/B/C A01 

9.5. Fixing kits (wall or rack mounting) 

The fixing kit for AXL (main or extension box) is identical to the one of the NeXspan L (main or 

extension box), only the color changes. The black fixing kit is proposed as spare part in the Price list. 

The fixing kit for AXD (main or extension box) is identical to the one of the NeXspan D (main or 

extension box), only the color changes. The black fixing kit is proposed as spare part in the Price list. 

Note: The fixing kit for AXS6/AXS12/AXS (main or extension box) is not compatible with the one of 

the NeXspan S12/S (main or extension box). The new black extension kit for AXS6/AXS12/AXS must 

be ordered in addition to the hardware migration kit, when fixing (rack mounting) is required.

C – Software migration 

1. Applications and Aastra 5000 R5.4 

Please see Ordering Guide chapter 10 for Application and A5000 R5.4 compatibility matrix. 

2. Migration of the software and licenses, to R5.4 

2.1. Principles 

The R5.4 software is provided on the AXS/AL/AXD gateways motherboard, or on a DVD-ROM or USB 

key in the case of the Aastra 5000 Server. 

On Aastra 5000, the software locking is different from NeXspan. A unique key is required to open 

both the software release and also the optional software licenses acquired on the system (gateway or 

server). 

When you perform the migration of one site, you will retrieve all the software licenses previously 

acquired and so, present in the previous release. 

To get additional licenses, you should order them, in addition to the migration itself, using the R5.4 

price list (see software licenses chapter). 

Exceptions: 

2.2. IP Licenses 

During migration, the R3.x or R4.x « IP licenses» are transformed in R5.4 «Generic IP licenses». This 

is notably the case for the 10 free IP licenses available in R3.x or R4.x 

Example: 

On an R4.1 XS, I had 100 IP licenses (including the 10 free IP licenses). 

With the software migration kit, I will get an R5.4 key including 100 Generic IP licenses. 

2.3. NCS to A5000 Server 

Regarding the NCS to A5000 server migration, you should order the « migration of IP licenses », in a 

sufficient number. This number should be below or equal to the number of IP licenses already 

acquired on the NCS. 

Example: 

On an NCS R4.2, I had 500 IP licenses (including the 10 free IP licenses). 

I require only 400 IP licenses in R5.3. 

I order the NCS to A5000 software migration kit 

+ 400 * migration of the IP license R4.2 to R5.4 

With the software migration kit, I will get an R5.4 key including 400 Generic IP licenses 

2.4. Integrated voice mail, Multisite, extended LCR, graphical MMI, Basic key 

The « integrated voice mail », « Multisite », « Extended LCR» and « graphical MMI » are not locked on 

Aastra 5000. 

The R4.2 « basic » key is simply transformed in 10 generic IP licenses when migrating to Aastra 

5000. 

2.5. Directory on NeXspan XS12XS/XL/XD 

The directory on XS12/XS/XL/XD R3.x or R4.x includes 2000 entries. 

49

On Aastra 5000 the directory is locked on AXS12/AXS/AXL/AXD. When ordering the migration of an 

XS12/XS/XL/XD to AXS12/AXS/AXL/AXD R5.4, the 2000 directory entries will be available in the 

Aastra 5000 software key. 

2.6. i2052 CTI 

Up to R4.2 release of NeXspan, i2052 CTI licenses (beyond 5 licenses) are linked to the #ID of the 

i2052 server (SDS software component). 

Since R5.1, i2052 CTI licenses are on the A5000 server or gateway (#ID of the A5000 server dongle 

or of the gateway i-button). 

You should provide the #ID of the i2052 SDS server, if you want to retrieve the previously acquired 

i2052 CTI licenses. 

2.7. G.729 codec and other codec 

Up to R5.2 these features where not locked, they were available. Thus, when migrating to R5.3, G.729 

Codec and « Other codec » licenses are included in the migration kits. 

D- How to order a migration NeXspan to R5.4 

Preparing a migration order requires 

� To perform a software/hardware inventory: 

Platforms to be upgraded (mono-site or multi-site network): type of platform, boxes, 

extension boxes, FMEVO daughter boards, software release. 

� To deduce the list of hardware and software migration kits required (see previous chapters) 

� To define possibly the change of color, if required (to preserve to visual harmony of the system) 

� To deduce the list of replacements of equipment to change the color 

By a hardware inventory: boxes, extension boxes, extension boards, fixation kits, batteries 

boxes, etc. 

� To list possible hardware extension required (extension boards, daughter boards) 

� To list possible software extension required 

� To dimension these requirements 

� To deduce the quantity of software additional licenses to be order for each site. 

Make an order: 

Order the hardware and software migration kits of each site, 

Please provide the #ID of the dongle or i-button of the system to be upgraded 

50 

Order possibly hardware/software extensions, 

still providing the #ID of the dongle or i-button of the site on which they apply. 

It is recommended to make an order grouping on the same order fill: 

The R5.4 hardware migration kit 

The R5.4 software migration kit (provide the #ID of the dongle or i-button) 

Possibly some color changes (standard replacement) 

Possibly some extension boards or daughter boards 

Possibly some additional software licenses (provide the #ID of the dongle or i-button) 

� One order per site (gateway or server), this will reduce the risk of mistake. 

---- END OF THE DOCUMENT ----

ORDERING GUIDE System - Aastra 5000 - R5.4

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?