Administrator Guide: Aastra L35 / Aastra L36 / Aastra RFP 35 configuration and provisioning

Please note that due to limitations in the current version of the Aastra firmware, the Aastra DECT equipment cannot be configured automatically from within the SMP.
With version 3.0-RC3 of the RFP firmware included in the Aastra phone support v1.2.0+ module it is possible to auto provision the phones, but the OMM still has to be configured manually.
In a future firmware version, Aastra will provide the possibility to auto-configure its platform. This will greatly simplify the end-to-end configuration steps.

Administrator Guide: Aastra L35 / Aastra L36 / Aastra RFP 35 configuration and provisioning

Goal of the document and intended audience

This document describes the configuration steps for the Aastra IP Base Station RFP L35 IP (indoor) or Aastra IP Base Station RFP L36 IP (outdoor) with Aastra phone support v1.2.0+ module and Aastra 6xxd handsets. This document does not explain the physical installation nor does it provide site-survey guidelines.

Intended audience: installation and service delivery teams

Mitel licensing

When do I need a license?

Past OMM v. 5.xx, you only need a license if you are configuring a Cluster made of more than 5 RFPs

How to order a new license?

Small clusters (<= 5RFPs)

For clusters up to 5 RFPs, you will need to request a PARK ID online, simply follow the guide below and use the integrated OMP feature in order to:

get a "PARK ID request file"
upload the file on the PARK server (https://parkmanager.mitel.com/pm/parks/fetch.xhtml)
download the "PARK ID request answer file"
load the file in your OMP
If the OMP has direct access to the internet, this can be done without downloading the PARK ID request file

Large clusters (> 5 RFPs)

In this case you have to buy a voucher, this must be done through logistics since vouchers are items we can buy from our Mitel reseller.

You must know that:

Vouchers account for "up to X RFPs", so you have to order carefully
Each size available sizes are listed here
One voucher for 50 RFPs is cheaper than two vouchers for 20 RFPs

... so, if you have a cluster made of 40 RFPs, it is better to buy a voucher for 50. If you have a cluster of 51 RFPs, consider buying a voucher for 50 and another for 20, except if you plan on upgrading past 70 RFPs later, then already order two vouchers for 50 RFPs, etc...

Activating vouchers should normally be done through our mitel.connect account. However, due to an issue at Mitel regarding linking pre-existing customers to our account, you won't be able to do it that way. In order to activate a voucher, you must contact one of our contacts at Mitel, or you can also ask Logistics to do it when they receive your order from Mitel. Mitel is reachable on +3226860900

Upgrade a license

For clusters up to 5 RFPs, upgrade to version 6.X and follow the procedure above (How to order a new license - Small clusters). For clusters > 5 RFPs, contact mitel before upgrading your system Visit the following page and follow instructions it contains to generate the license key you'll need to use.

For information related to licensing check documentation KB_System_Update.pdf in attachment, page 12.

TAD license activation for large clusters (Deprecated since version 6.X)

Please note that the TAD activation is only needed when you want to configure more than 5 radio fixed parts (multi - RFP) in a cluster. More information can be found in the SIP-DECT_rn_en_3.0_For_NA_installations.pdf attachment below.

Navigate to license.aastra.de
Click on SIP-DECT
Click on Generation of Licenses
Click on Generate License
Select SIP-DECT in the dropdown menu
Enter 3 MAC addresses of RFP's that you will use for the cluster
- If you configured a second OMM for active standby, use the MAC address of the standby OMM as second MAC address
Add the version which can be found on the web interface of the OMM RFP
Add the PARK ID that you used for the OMM
Add the TAD ID that can be found on the OMM CD
Download the license in .xml format and upload it on the OMM by using the OMM portal configurator (license tab)

New installations

Before you start

Before you start, make sure you have the following equipment and information:

Aastra IP Base Station RFP L35 IP (indoor) or Aastra IP Base Station RFP L36 IP (outdoor) (referred to in this document as "Base Station" or "RFP")
Aastra 6xxd handset(s) (referred to in this document as "Handset")
Fixed IP address from the customer's IP range to be assigned to the Base Station
Only for SIP-DECT versions below version 6.00: OpenMobility CD with PARK ID (needed for the OMM license) and TAD ID - needed if you want to configure more than 2 (OMM v. <=5.x) radio fixed parts in a cluster
OpenMobility CD is not required anymore with SIP-DECT 6.0 or later

Step by step configuration steps

SMP Configuration

In the SMP navigate to: Advanced > Modules configuration
Install the "Aastra Phone Support Module" version 1.2.0+: this will install the necessary TFTP images on the SOP needed to support the Aastra Base Station and Aastra Handsets.
For each Handset create an "Aastra 6xxd DECT phone" resource (corresponding to your model).
Assign each Handset to an extension. Due to a limitation in the Aastra firmware the combination of the first and last name of the extension cannot be longer than 19 characters.
Apply your changes to send the configuration changes to your SOP.

Configuration of the Aastra IP Base Station RFP L35 IP or Aastra IP Base Station RFP L36 IP

OMC Configuration

NB : In case of VLANs / subnets, this part of the configuration can be done locally thanks to a small PoE switch ( [laptop]>---<[Switch]>---<[RFP] ) but you'll have to move the RFP to prod VLAN / subnet afterwards for the second part of the configuration.

Connect the Base Station to the network. If the network has no POE support an additional power supply is needed to power the Base Station (USB, Aastra recommended charger, ...).
First do a factory reset using the OpenMobility Configurator. You can find the OM Configurator in the attached files below.
1. Using the OpenMobility Configurator, click on the "Scan" button in the right menu to perform a scan on the network to detect the RFP's.
2. Check the "Get configuration after detecting an rfp" checkbox
3. Fill out the "User" and "Password". Default values are 'omm' for both username and password
  - User: omm
  - Password: omm
4. When the "scan req ok" message is shown, select the RFP to configure (using the MAC address as the identifier) If the scan return the error: "Timer Expired", check that the windows firewall is well deactivated. In windows, you can also verify the security parameters of Java which can be found in control panel.
5. In the list check the RFP which you want to factory reset or configure
6. Click the "Factory reset" button in the left menu
7. Wait until the Base Station displays a slowly blinking red/orange led
After resetting the Base Station fill out the RFP configuration parameters
1. Select the RFP you want to configure
2. Click Edit configuration in the right menu
3. General tab :
  - Use local config: yes
  - IP address: the fixed IP address of the Base Station
  - Net Mask: the IP netmask of the Base Station
  - Router: gateway_IP.
4. OpenMobility tab :
  - OMM address: the fixed IP address of the Base Station (or OMM IP address if in cluster configuration).
  - 2nd OMM address (Optional): the fixed IP address of the failover OMM if present.
  - TFTP server address: the IP of the SOP to which the Base Station will be connected
  - TFTP file name: iprfp3G.dnld
  - DNS addresses (Optional): DNS servers IP addresses separated by spaces
5. Other tab :
  - ( VLAN : optional ) In the dropdown box near new, "VLAN ID" and click "New". The new parameter now appears in the parameter list. Click on the parameter, and fill in with the VLAN number in the input above "Change", followed by a click the "Change" button.
6. Click "OK" to keep your configuration.
7. Click the "Send Configuration" button in the right menu
You can always view the full current configuration of the selected RFP by clicking on "Edit configuration"

OMP / Web interface configuration

NB : This can be done either through OMP or in your web browser. However, some options are only found in the OMP. Start with it then move to the web interface if you feel more comfortable with it but first make sur you enable "Advanced" in the header, on the top of the page.

Download OMP below (OMPVX.jar in attached files, if you receive an unexpected error when logged in you can always try a different version). The OMM Portal (OMP) can also be downloaded from the web-interface, top right corner of the screen
Fill out the "IP address" with the address configured previously. Fill out the "User Name" and "Password"
After you have changed both passwords, proceed to the "System > Basic settings" menu
- General tab
  - System name: Enter a system name
  - Remote access: Check to allow remote SSH Access
  - Tone Scheme: Select the country code
- DECT tab
  - This part should be done only if you want a free license for less than 5 RFP, otherwise put the PARK you received.
  - PARK: Click Configure PARK a popup will be opened.
    - Click on *Online Park Request" to request the park from Mitel Server. This will fetch the park automatically if you have configured DNS servers and the RFP has access to the Internet. If it fails, perform the following:
    - Download the park request file.
    - Visit https://parkmanager.mitel.com/pm/parks/fetch.xhtml to request a new park. Download it
    - Import PARK file.
  - DECT authentication code (optional): A code entered here provide a default DECT Authentication Code for each new created handset
  - Regulatory Domain: Select 'EMEA'
  - Encryption (optional): Can be enabled if DECT encryption is supported by the handsets.
  - Auto-create on subscription: enable it
  - Portable part user login type: Select LoginID
- WLAN tab
  - Regulatory domain: Select your country code
- Software update URL
  - Configure specific source: enable it
  - Protocol: TFTP
  - Port:: enter a custom port or check "use default port"
  - Server: Enter the SOP IP address
"System > Advanced settings" menu
- Dect phones firmware tab:
  - Activate firmware update: enable it
- Net parameters tab
  - ToS for voice packets: Enter the TOS value for RTP packets (optional)
  - ToS for signalling packets: Enter the TOS value for SIP packets (optional)
"System > SIP" menu
- Basic settings tab:
  - Proxy server: Enter the SOP IP address (Primary SOP if in Active-Active mode)
  - Registrar Server: Enter the SOP IP address (Primary SOP if in Active-Active mode)
  - Registration Period: 180
  - Outbound proxy server: Enter the SOP IP address (Primary SOP if in Active-Active mode)
- Advanced settings tab:
  - Registration retry timer: 180
  - User agent info: Select checkbox
- RTP settings:
  - Preferred codec 1: G.711-A-law
  - Preferred codec 1: G.711-u-law
  - Preferred codec 3, 4: set to "None"
- Backup Settings: (For active-active support)
  - Secondary proxy server: Enter the IP address of the secondary SOP
  - Secondary proxy port: Enter the SIP port of the secondary SOP
  - Secondary registrar server: Enter the secondary SOP IP address
  - Secondary registrar port: Enter the SIP port of the secondary SOP
  - Secondary outbound proxy server: Enter the secondary SOP IP address
  - Secondary outbound proxy port: Enter the SIP port of the secondary SOP
"System > Data management" menu
- User data import tab:
  - Activate: enable it
  - Protocol: Select 'TFTP'
  - Server: The IP of the SOP to which the Base Station will be connected
  - Path: Type in "aastra" without the quotes When you login with ##extension and you receive "User Data Import Failed" on the web-interface please verify following limitation ( Due to a limitation in the Aastra firmware the combination of the first and last name of the extension cannot be longer than 19 characters.)
"Base Stations" menu
- From there Go to the Web Interface
- The base you just configured with OMC should be visible, so all you'll have to do for it is edit the configuration (pencil icon on the left)
- For any additional base, click on Capturing unconfigured DECT base stations "Start"
  - General Settings tab:
    - MAC address: enter the MAC address of the Base Station
    - Name: enter the location of the Base Station
    - Site: the geographical site ID
  - DECT Settings tab:
    - DECT Cluster: the cluster ID (if you plan to make multiple bases work together as part of one cluster - default is 1)
    - Preferred synchronization source: If you know which RFP will be in the center of your environnement, you can enable it for this RFP
    - Reflective environment: enable it only in case of metallic walls, ... that could prevent a proper propagation of the signal
  - Click "OK"
"DECT Phones" menu
- If there's no green "V" mark next to the subscription in the tasks area, click on "subscription" to enable it * Up until here
"System features > General Settings" menu
- FAC number and prefix for alarm triggers fill in '#' without the quotes and press OK
"System features > Feature access codes" menu
- User login enable it, and fill in '#' without the quotes
- User logout enable it, and fill in '*' without the quotes
"System features > Directory" menu
- If you have LDAP Server installed you can provide the directory to the phones
- Click on create in the "Tasks" area
- General settings
  - Active select this option
  - Name ldap
  - Search base dc=directory
  - Search type Surname
  - Display type Surname, given name
- Server settings
  - Server insert the SOP IP.
  - Port 389
  - Server search timeout 10
  - Press "OK"
"System features > Directory (comp.mode)" menu
- Click on New in the "Tasks" area
  - Active select this option
  - Type select LDAP
  - Name ldap
  - Protocol select HTTP
  - Server name insert the SOP IP
  - Port 389
  - Search type select Surname
  - Display type select Surname, given name
  - Server search timeout 10
  - Press "OK"

Connect the handset to the OMM RFP

The registration of an AASTRA DECT phone consists of two steps. The first step is to connect the DECT phone with the AASTRA base station. Normally this should only be done once. To connect a DECT phone with the AASTRA base station

Connect to the web-interface of the base station by entering the ip address of the base station in your browser
Enter the credentials (Username: omm)
Navigate to DECT phones, select on Start for "Subscription with configured IPEIs"
The base station will now accept connections from new DECT phones
There should be a green V displayed next to Subscription allowed and Auto create on subscription
Wildcard subscription has to be disabled!

Now we are able to connect the DECT phone with the OMM RFP:

On the phone menu, navigate to "Menu > System > Subscriptions > New System"
Press "OK"
Auth. Code: enter the "DECT authentication code". (the DECT authentication code can be found on the web-interface of the base station in System, System settings)
Press "Subscription"

Your handset should be running firmware version 4.0 before you are able to login. Verify if your handset is running firmware 4.0 if logging in fails or seems to hang for a long time. The handsets should upgrade automatically when they are running an older version after the subscription step. However there is no visual indication of this on the handset and it can take a considerable amount of time (it is known to take over 4 hours). Verify in the web interface of the OMM if there are handsets upgrading their firmware. The web interface is available from your browser at http://

To register the extension on the DECT phone:

Dial ## followed by the extension that you configured on the SMP. Ex: '##733'
Enter the admin pincode of the extension (which can be found in the Extension Parameters > Advanced View, by default "1234").
Press "OK"

To de-register an extension on the phone:

Dial #* followed by the extension that you configured on the SMP. Ex: '#*733'.
Enter the admin pincode of the extension (which can be found in the Extension Parameters > Advanced View, by default "1234").
Press "OK"

Extended configuration - multi-RFP

You can use additional base-stations (RFP) to extend your network. You should consider following points:

All RFP must be placed in the wireless range of at least one other RFP. The DECT signalling and synchronization is spread through the wireless. Avoid situation when the loss of one RFP isolate the rest of the RFP network.
There is one RFP that runs OMM (and one standby if defined), other RFP are just antenna's
Only one OMM licence (PARK code) is required

You have 3 possibilities to add additional RFP

one by one. Not suitable with more than 3 RFP to configure
auto-configuration : fill in some config files and push it

Extended configuration - multi-RFP - One by one

Configuration:

Configure the first RFP with OMM as described in the "Configuration of the Aastra IP Base Station RFP L35 IP or Aastra IP Base Station RFP L36 IP" section, don't forget the factory reset at the beginning!
On the additional slave RFP:
- Also reproduce the points described in the "Configuration of the Aastra IP Base Station RFP L35 IP or Aastra IP Base Station RFP L36 IP" section but with the following settings:
  - IP address: the fixed IP address of the slave RFP
  - OMM IP address: the fixed IP address of the master (active) RFP who has OMM installed
  - 2nd OMM IP address: the fixed IP address of the second RFP if you installed OMM on multiple RFP's for an active-standby setup. If you don't use Active-Standby, do NOT add this parameter!
- Don't access to the base station with OMM Portal or web access
On the first OMM RFP:
- Go to the OMM portal (via OMM.jar or web access)
- Go to "radio fixed part" section and add a new RFP:
  - mac-address: second (slave) RFP mac
  - name: choose a name for the base station
  - Paging area: Select paging area 0
  - DECT activated: enable it
- Click "OK", the web interface should display the Radio Fixed part entry
Via the webpage of the RFP OMM in "radio fixed part" section, you will see a new entry in the list and see its status:
- active: "V", synchronous: "V"
  - the RFP is recognised and recognise other RFP. DECT communication and roaming are available.
- active: "V", synchronous: "X"
  - No sync with neighbors, but the RFP had been ones connected with OMM. This state can happen when OMM or RFP has just restarted. If this state stays longer, consider hardware or network issue.
- active: "X", synchronous: "-"
  - Inactive: Air interface not powered on, or hardware error.
- active: "-", synchronous: "-"
  - RFP is configured but had never been connected to the OMM
- active: "-", synchronous: "magnifying glass"
  - Searching. The RFP has lost the sync with its neighbors. No DECT communication. If it lasts longer that's indicating a bad location of the RFP.

Extended configuration - multi-RFP - Auto-configuration

You must take all MAC addresses. You can - take it on the box , then you fill in a csv (see below rfp.csv for example )

You can submit all information there : ntp server, OMM server, tftp server ....

- On OM configurator, click on "Load Config" (choose the rfp.csv) - Then, Click on "Send Config" - done

- you plug in the RFP's and with OM_configurator - click on "Save RFPs", save it with a csv extension. - open the csv fill in with all correct information (see rfp.csv for example ) - click on "Load Config" ( choose the rfp.csv) - Click on "send config"

When it's done or in the same time, you must fill in another csv file for OMM ( see rfpexport.csv for example )

Fill all field with correct information : MAC Address, name, etc....

Go to OMM, click on "Radio Fixed Parts"
click on "enrollment"
click on "File to import" and select your rfpexport.csv
select all and click on "add all"

All RFPs are going to have 3 green lights. If you don't have any handset configured, the middle green light is going to blink in red.

Verification

If everything is configured correctly the Base Station shows 3 green LEDs. If the handset is not configured correctly or does not find the Base Station, it shows a blinking red LED.

Debug

The OMP java software accesses the OMM base station trough port 12622.

Update an existing installation

Here we document the upgrade process from version 3.X to 6.X

The upgrade process will always depends on the firmware version that's installed on your OMM. You will need to upgrade if you have one of the following cases:

You have received a handset which has an more recent version than the firmware version of your OMM.
You have received an RFP which have a recent version than the firmware version of your OMM.
You need to continue getting assistance from Mitel on your installation.

To verify version installed:

On an RFP/OMM:

:~$ ssh omm@

Welcome to IP RFP OpenMobility SIP-DECT Version 2.1

Mar 10 2011 12:26:42
Release

last reset cause: hardware reset (Power-on reset)

On the handset:
1. Menu > System
2. Select Version info

Which version in which module

The correspondence between firmware and module version is as following:

Firmware 3.x is included in module version <= 2.2.4
Firmware 5.X is included in module version >= 2.3.0
Firmware 6.0 is included in module version 2.5.0
Firmware 6.2 is included in module version 2.5.1

The advice is to always use the latest version in the range.

The upgrade process to release 6.x or 8.x

This upgrade process is based on page 8 of this document written by Mitel operators.

Requirements

Upgrade from release 3.0 or lower to 6.0 require an intermediate upgrade step e.g. to 5.0.

In that case you will need to request a license upgrade twice (see Upgrade a license).

from 3.x to 5.x,
and from 5.x to 6.x

For upgrades from release 6.x to 8.1, refer to:

OMP issue with java and SIP DECT 8.0

Since Oracle changed its licensing model in 2019, Java JRE and Java JDK now require a license for commercial use. To launch OMP.jar or OM_Configurator.jar for SIP DECT 8.0 SP1 and below, Oracle Java can be replaced with OpenJDK.
So you have 2 options:

install the OpenJDK
or upgrade to SIP DECT 8.1 (recommended)

A non convential way to use OMP is to use the .exe of 8.1 available here

Pre-upgrade

Ensure that you have right version of module have been installed on your sop or that right firmware can be located in the tftp server defined for the OMM.

Perform a backup

Before each upgrade, please perform a backup of the database.

Go to System
Select DB Management
In the Manual export tab click save to download the configuration file on your computer.

Run upgrade

Once you have the right version in the tftp server and have performed backup, you can now start the update.

Go to System
Select System settings
Click either update (or restart) button located in the right corner of the page.

Attention: If you get a prompt, before clicking OK ensure that the checkbox is not checked. Otherwise you will crash all the system.

To see the upgrade progression. Go to the OMM web interface and you will see status of all RFP's located in the system. Once the upgrade has finished, all RFP's should have status Active and Connected.

By launching the upgrade of the Master OMM, you will launch the upgrade of all RFPs of the system.

To check if the upgrade has been performed, connect to your OMM via ssh, you will get your omm version displayed after the connection.

If the OMM version is > 3 you can check the upgrade progress by using the setc command.

Upgrading handset

In normal case after upgrade, all handsets will subscribe on the OMM. If that's not the case, it means there's a configuration issue with the handset. To fix that perform the following:

Go in the menu
***76#
DOA settings > Master System

Active-Active redundancy

Configure a standby OMM

It is recommended to have an Active-Active OMM setup (configure a backup OMM server). This can be done during the OMC step (OMC configuration)

Configure SOP2 as backup SIP server

Upgrade the SDRA phone resources towards version 1.3.0
Configure SOP1 and SOP2 in the phone resource
On the OMP (this can not be configured on the web interface), configure the backup SIP server (System -> SIP -> Backup settings -> Secondary proxy server/Secondary registrar server/Secondary outbound proxy server)