User Manual Device Manager in Unite Connectivity Manager, TD 92855EN

User ManualDevice Manager

TD 92855EN

08 January 2018 / Ver. P

TD 92855EN


User Manual

Device Manager

About this document

This document describes the Device Manager application, that is used for administration of

devices.

TD 92855ENUser Manual

Device Manager

Contents

1. Device Manager ............................................................................................................. 1

1.1 Basic Terminology ................................................................................................... 1

2. The Device Manager GUI ............................................................................................... 2

2.1 Sort and Filter the List............................................................................................. 2

2.2 Tabs ......................................................................................................................... 2

2.3 Logging on to Device Manager ............................................................................... 8

3. Initial Configuration of Devices.................................................................................... 9

3.1 Import Parameter Definition File............................................................................. 9

4. Software Management ............................................................................................... 14

4.1 Import Software Files ............................................................................................ 14

4.2 Delete Software Files ............................................................................................ 15

4.3 Upgrade Software of a Device............................................................................... 15

4.4 Restart of Devices ................................................................................................. 17

4.5 Device Properties................................................................................................... 17

5. App Management........................................................................................................ 19

5.1 Manage Apps in Device Manager .......................................................................... 19

5.2 Manage Apps on Devices ...................................................................................... 20

5.3 View Apps on a Single Device................................................................................ 22

6. Language Management .............................................................................................. 23

6.1 Import Language files for Devices......................................................................... 23

6.2 Delete Language File for Devices ......................................................................... 23

6.3 Upload a Language to a Device ............................................................................. 24

7. Company Phonebook and Contacts ........................................................................... 25

7.1 Company Phonebook Management ...................................................................... 25

7.2 Contacts Management .......................................................................................... 26

8. Template Management............................................................................................... 28

8.1 Create Parameter Template................................................................................... 28

8.2 Create a Parameter Template from a Number ...................................................... 29

8.3 Create QR Code from Template ............................................................................. 30

8.4 Rename Template.................................................................................................. 31

8.5 Copy Template ....................................................................................................... 31

8.6 Edit Template ........................................................................................................ 32

8.7 Delete Template .................................................................................................... 32

8.8 Upgrade Template ................................................................................................. 32

8.9 Apply Template ..................................................................................................... 33

8.10 Import Templates from File ................................................................................. 34



Device Manager

8.11 Export Templates to File...................................................................................... 34

9. Number Management ................................................................................................. 35

9.1 Create Numbers..................................................................................................... 35

9.2 Save a Number to Database.................................................................................. 35

9.3 Enter/Edit Number Information ............................................................................ 36

9.4 Associate Number with Device.............................................................................. 36

9.5 Delete Number....................................................................................................... 37

9.6 Rename Number.................................................................................................... 37

9.7 Copy Number ......................................................................................................... 37

9.8 Export Numbers to a File ....................................................................................... 38

9.9 Import Numbers from File ..................................................................................... 38

10. Device Management ................................................................................................. 39

10.1 Add Devices......................................................................................................... 39

10.2 Delete Device....................................................................................................... 39

10.3 Replace Device..................................................................................................... 40

10.4 Assign Number to Device .................................................................................... 40

10.5 Enter Device Information .................................................................................... 41

10.6 Factory Reset....................................................................................................... 41

10.7 Synchronize Device ............................................................................................. 41

10.8 Lock Device.......................................................................................................... 41

11. Certificate Management........................................................................................... 43

11.1 Manage Certificates for Ascom Myco Handsets ................................................. 43

11.2 Manage Certificates for Ascom i62 VoWiFi Handsets......................................... 44

12. Parameter Settings ................................................................................................... 46

12.1 Working with Parameters ................................................................................... 46

12.2 Edit Parameters for a Number ............................................................................ 47

13. File Management....................................................................................................... 49

13.1 Package Files ....................................................................................................... 49

13.2 Parameter Definition Files................................................................................... 49

13.3 Software Files ...................................................................................................... 50

13.4 Language Files..................................................................................................... 51

13.5 Company Phonebook Files .................................................................................. 51

14. Number and Device Limitations .............................................................................. 53

14.1 Number of Devices in Device Manager ............................................................... 53

14.2 Products Managed by Unite Admin .................................................................... 53

14.3 View Number of Licensed Devices ...................................................................... 54

14.4 Examples of Limits .............................................................................................. 54

15. License Management ................................................................................................ 57

15.1 License Upgrade Alternatives ............................................................................. 57



Device Manager

16. Other Settings .......................................................................................................... 61

16.1 Enable/Disable New Devices ............................................................................... 61

17. Baseline Management .............................................................................................. 62

17.1 Enable/Disable Baseline ...................................................................................... 62

17.2 Set Up Baseline.................................................................................................... 62

18. Related Documents................................................................................................... 66

19. Document History ..................................................................................................... 67

Appendix A. Device Manager Keyboard Shortcuts....................................................... 69

Appendix B. Overlapping Number Plan in Device Manager......................................... 71

Appendix C. Troubleshooting ......................................................................................... 72



Device Manager

1. Device Manager

1. Device Manager

NOTE: Features described in this document might be unavailable because they are not

supported by your devices. A feature can also be unavailable if a device is not selected

(features appear dimmed on the menu until having a device selected).

The Device Manager can manage large sets of devices and contains a solution for:

• Centralized software upgrade on a set of devices

• Centralized configuration of devices

• Central database storage for all device settings

• Upgrade of license for devices

In the Device Manager, much of the work is done with Devices, Numbers and Templates.

1.1 Basic Terminology

This section gives a brief description of the basic terminology in the Device Manager

App: application installed on a smart phone.

Device: can be a charger, a handset, or a fixed device (IP-DECT Access Points and

IP-DECT Gateway) that can be connected to the Device Manager.

Number: the complete settings for a single device.

Template: general settings for a specific device type.

Parameter

definition file:

a file including all possible settings for a certain device type. Templates

are created from parameter definition files.

Package file: a file that can contain other files, such as parameter definition files,

software files and template files.

08 January 2018 / Ver. P 1


Device Manager

2. The Device Manager GUI


The Device Manager window has a menu bar (1), a toolbar (2) and a work area (3). The

toolbar has different tabs and when a tab is selected the available device types will be

shown in the left hand pane of the work area. The right pane of the work area shows

devices, numbers, apps, templates, and licenses already configured.

Figure 1. Device Manager window area.

The upper part of the work area has search fields with different search criterias for each tab.

2.1 Sort and Filter the List

By default, the lists are sorted as follows:

• Devices tab – sorted by Device ID

• Numbers tab – sorted by Number

• Apps tab – sorted by Name1

• Templates tab – sorted by Name

• Licenses tab – sorted by Device ID

To sort the list by any other column, click the appropriate column heading. To reverse the

sort order, click the column heading again. The sorting order is indicated by an up or down

arrow in the column heading.

By default, the list in each tab shows all available Devices, Numbers or Templates, but it is

possible to filter the list by selecting the desired device type in the left hand pane of the

work area.

2.2 Tabs

The information in Device Manager is shown in different tabs:

• Devices tab

• Numbers tab

• Apps tab2

• Templates tab

1.This tab is not applicable for IMS3.

2.This tab is not applicable for IMS3.



Device Manager


• License tab

In each of these tabs, specific information is shown in lists about devices, numbers, apps,

templates, and licenses. Some of the information overlaps, for example Device ID, which is

tied to both a specific device and to a specific Number.

The operations that can be done in the Device Manager are done from these tabs and from

the menu. Different menus are accessible in the different tabs.

2.2.1 Devices Tab

Figure 2. The Devices tab.

The Devices tab shows all devices configured at the site in a detailed list. The following

columns are displayed on each row:

• Description – description of the device.

• Device ID – the unique identifier of the device

• Software version – shows the version of the software in the device

• Device type – the device model

• Parameter version – Depending on which device type used, one of the following can be

shown:

- shows the version of the parameter definition in the device. If the version is shown in

red, no supporting parameter definition is found the Device Manager. If the version is

shown in dark red, a compatible parameter definition is found, but it does not have the

same parameter definition version as the device.

- shows whether if the parameter definition in the device is found in the Device

Manager. If "OK" is shown, the supporting parameter definition file is found in the

Device Manager.

• Online – shows if the device is logged in to the Device Manager. The symbol

indicates a logged in device.

• Latest number – shows the latest known Number for a device

The columns order can be changed and the application will keep the changes.

• IP address – shows the IP address of the latest logged in device (e.g. VoWiFi handset or

IP-DECT Master). In the case a IP-DECT handset logs in Over the Air (OTA), the IP address

of the IP-DECT Master where the handset is registered is shown.

• Serial number – shows the serial number of the latest logged in device.



Device Manager


• Status – shows the following status:

NOTE: A software download from Device Manager should be done on one device to start

with. If successful, the remaining devices can be updated in one operation.

Error log

An Error log is created if software or apps cannot be downloaded to or deleted from a

device(s). If a file cannot be downloaded or deleted, the icon is shown in the Status

column. To view the error in detail, click Error(s) on XX device(s).

Note that the Error log contain errors for all devices indicated with the icon shown in the

Status column.

To remove entries in the Error log, select the check boxes next to the entries and then click

the Clear button.

NOTE: If you download the software or the app an additional time and the download is

completed, the error will be deleted automatically.

2.2.2 Numbers Tab

Figure 3. The Numbers tab.

– indicates that the latest file download is in progress. Additionally, a

progress bar is also shown when the file is being downloaded.

– indicates that the latest file download is pending or requested.

– indicates that the latest software download is scheduled or retrying to

download the file again.

– indicates that the latest file download failed or is aborted (a red broken

arrow). If the download failed, the icon is also shown. See Error log for

more information.

– indicates that download of file(s) failed or deletion of file(s) failed. See

Error log for more information.

– indicates that the latest file download is completed (no symbol is shown).

– indicates that the device is locked.



Device Manager


The Numbers tab shows all Numbers configured at the site in a detailed list. The following

columns are displayed:

Description: description of the number

Number: the unique identifier of the Number. The identifier is unique for

that device type

Device type: the device model the Number is intended for

Parameter version: Depending on which device type used, one of the following

information can be shown:

– shows the version of the parameter definition in the device. If

the version is shown in red, no supporting parameter definition is

found the Device Manager. If the version is shown in dark red, a

compatible parameter definition is found, but it does not have the


– shows whether if the parameter definition in the device is found

in the Device Manager. If "OK" is shown, the supporting parameter

definition file is found in the Device Manager.

Device ID: the unique identifier of the device that the Number is associated

to

DECT Master: the IP address of the IP-DECT Master where the device is

registered. Only applicable in IP-DECT systems. See also Appendix

B for additional information.

Device interface: the IP address of the Device Handler the interface (for example IP-

DECT or VoWiFi) is communicating with. The Device Handler is the

application between the interface and the Device Manager.

See also Appendix B for additional information.

Online: shows if the device the Number is associated to is online. The

symbol indicates an online device

Status: shows the parameter synchronization status. A Number can also

be queued for synchronization. Several different indications are

used, for example Synchronizing, Sync queued, Save queued,

Synchronized, etc.

When the Number is offline, the database status is shown;

Synchronized or Not synched.

Saved: shows if the Number’s parameters have been stored in the

database. The symbol indicates that the parameters have

been stored

Last login: shows the date and time the device was last online in Device

Manager/logged in to Device Manager

Last run template: indicates which template that was last run for that Number



Device Manager


2.2.3 Apps Tab

Figure 4. The Apps tab

Column Description

Icon: Shows whether if the app is imported to Device Manager or only

installed on device(s). This column is used in combination with the

Status column.

The icon shows an app only installed on device(s), i.e. the app

has not been imported to Device Manager. If the app is imported to

the Device Manager, the app’s icon is shown instead.

Name: Shows the name of the app

Version: Show the version of the app. Each app with a certain version is shown

on one row, which means that an app with several versions is shown

on several rows, but with different versions.

Installs: Shows the number of devices the app with a certain version are

installed on.

Status: Shows whether if the app is imported to Device Manager or only

installed on device(s). If no information is shown in this column, the

app is imported to the Device Manager. If the app only is installed on

the device, Only available on device is shown. This column is used in

combination with the Icon column.



Device Manager


2.2.4 Templates Tab

Figure 5. The Templates tab

The Templates tab shows all templates in a detailed list. The following columns are

displayed:

• Name – the name of the template

• Parameter version – Depending on which device type used, one of the following can be

shown:

- shows the version of the parameter definition in the device. If the version is shown in

red, no supporting parameter definition is found the Device Manager. If the version is

shown in dark red, a compatible parameter definition is found, but it does not have the


- shows whether if the parameter definition in the device is found in the Device

Manager. If "OK" is shown, the supporting parameter definition file is found in the

Device Manager.

• Device type – the device model the template is intended for

2.2.5 Licenses Tab

Figure 6. The Licenses tab



Device Manager


The Licenses tab shows all devices configured at the site in a detailed list. The following

columns are displayed:

• Device ID – the unique identifier of the device

• Device type – the device model

• Online – shows if the device is connected to the Device Manager. The symbol

indicates that the device is online

• Serial number – the number identifying the device hardware

• Number – The Number associated with the device.

• Software version – shows the version of the software in the device

• Status – shows the license synchronization status for the device as follows:

- "OK" means that the device has been updated with the license information obtained

from the Device Manager.

- “Sending” means that Device Manager is sending license information to the device.

- “Server failure” means that there is some kind of error with the communication

between Device Manager and the license server.

- “License too old” – The device has a newer license than the one in Device Manager. A

refresh has to be done.

- “Needs update” – An attempt to move a license from one device to another has been

made, but the latest license does not exist in the device.

2.3 Logging on to Device Manager

NOTE: When an attempt is made to start the Device Manager, a dialog window is displayed

with a warning that the program’s digital signature cannot be verified. The text is

displayed in the language used in the computer’s operating system. Click “Run“ (or

the equivalent term in the operating system language).

NOTE: Ten clients can be logged in at the same time, but to avoid conflicts make sure that

only one at a time is updating Numbers.

1 Log in to the module.

2 Enter User name and Password and click the OK button.

3 Click the Device Manager button on the start page.

4 Enter your User ID and Password and the OK button.

2.3.1 Closing the Device Manager

• From the File menu, select Exit.



Device Manager

3. Initial Configuration of Devices


This section applies to new devices that shall be configured the very first time. It is assumed

that the devices only have factory settings from the manufacturer. The initial settings and

the recommended sequence in which they should be completed are illustrated below.

Figure 7. Initial configuration of devices

Figure 8. Initial configuration of Ascom Myco devices

3.1 Import Parameter Definition File

A parameter definition file (.def) is tied to a certain device type and includes the parameters

that can be configured for that device type.

There are two ways of importing parameter definition files to the Device Manager:

• Import definition files manually

• Import definition files automatically (applicable for Ascom Myco™ handsets only)

3.1.1 Import Definition File Manually

1 From the File menu, select File management.

2 Click the Parameter definition tab and then click the Add button.

Create templates

with common

settings for each

device´type

Import parameter

definition- or

package

file for each

device type

Add devices

Add numbers

for each

device and

apply template

Associate

numbers with

devices

Create template

with common

settings for the

device type

Add numbers

for each

device and

apply template

Associate

numbers with

devices

Import parameter

definition file

by logging in a

Ascom Myco device

Add

additional

devices



Device Manager


3 Select the parameter definition file (.def) to be imported and click the Open button.

The .def file is normally included in a package file (.pkg) distributed by your supplier.

You can also select the .pkg file to import the .def file.

4 Click the Close button.

3.1.2 Import Parameter Definition File Automatically

Each Ascom Myco handset has a parameter definition file installed that includes the

parameters for all applications installed on the handset. If the applicable parameter

definition file not exists in the Device Manager, the file will be imported automatically to the

Device Manager when the handset logs in.

3.1.3 Create Template with Common Settings

This section describes how to create a template including common settings that can be

applied to the device’s numbers later on.

1 Click the Templates tab.

2 From the Template menu, select New.

3 Select which device type the template should be applicable for from the Device type

drop-down list.

4 Select which parameter definition version the template should be based on from the

Parameter version drop-down list.

The parameter definition version determines which parameter settings that are

available for your device type. It is recommended to select the latest parameter

definition version to obtain full compatibly with the device.

NOTE: This option might be disabled for some device types. In that case, all imported

parameter definitions for that device type will be used when the template is created.

5 Enter an appropriate name of the template in the Name text field

6 Click the OK button.

The Edit template window opens showing the parameters organized in a tree structure in

the left pane, with the parameters in the current node in the right pane. Clicking the icon

will give a short description of selected parameter. In addition, see also the manual for the

device for more information about the parameter.

7 Select the parameters to be saved in the template by selecting the check box to the

left of each parameter. Change the parameters to the desired values.



Device Manager


In the Edit template window, the following color coding is used:

8 When all needed parameters have been configured, click “OK” to save the settings.

3.1.4 Add Devices

This section describes how to add devices by entering Device IDs of the devices. The Device

ID is unique for each device and can be found on the device’s box or in the device’s GUI.

Depending on which device to be added, the following Device ID should be entered:

• For DECT handsets, enter the IPEI number

• For VoWiFi handsets, Ascom Myco handsets, and chargers; enter the MAC address

NOTE: In order to simplify input when handling many devices, a barcode reader can be used

to read the barcode on the device’s box. The barcode reader should send a carriage

return after each ID, but it is not necessary. If carriage return is not sent, it is

necessary to click “Create” after each read item.

1 Click the Devices tab.

2 From the Device menu, select Add device.

3 From the Device type drop-down list, select which device type to be added.

Color Description

Black Normal

Dark blue Parameter has been edited during the current session

Purple The parameter is included in the template (checked)

Red Value not valid

Turquoise The value differs from the default value



Device Manager


4 Select the same parameter definition version used when you created the template for

your device type in the Parameter version drop-down list.

5 Enter Device ID for the device manually in the Device ID text field. A barcode reader

can also be used to add the Device ID.

The "Continuous registration" check box can be used to select whether the “Create

devices” dialog window shall close after clicking “Create” or if it shall still be open.

6 Click the Create button.

Repeat 3 to 6 if more devices are to be created, otherwise click the Close button.

3.1.5 Create Numbers and Apply Template

This section describes how to create numbers to be associated with the devices later on. In

addition, the common settings will also be applied to the numbers through the template you

created earlier.

1 Click the Numbers tab.

2 From the Number menu, select New.

3 From the Device type drop-down list, select which device type the number(s) is

created for.

4 From the Parameter version drop-down list, select the same parameter definition

version used when you created the template and added the devices.

5 From the Template drop-down list, select which template to be applied to the

number(s).

6 Enter the prefix (if needed) to be added to the number(s) in the Prefix field.

7 Select one of the following options:

• To create a single number, select the Single option and enter the number.

• To create a range of numbers, select the Range option. Enter the start number

and end number.

NOTE: The maximum range that can be added at a time is 100 numbers.


3.1.6 Associate Numbers with Devices

This section describes how to associate the devices with the numbers you created earlier.

Because the numbers contain the common settings, the devices will also be configured with

these settings when associating the numbers to the devices. You can only associate one

number at the time.



Device Manager



2 Select the number to be associated with a device.

3 From the Numbers menu, select Associate with device.

4 Select the device to be configured with the selected number.


When the number is associated to the device, the device ID of the device is shown on the

same row as the number. When the device with the corresponding device ID is online in the

Device Manager, the common settings are transferred to the device.

Repeat steps 2 - 5 to associate additional numbers to other devices.



Device Manager

4. Software Management


This section describes the management of software files in the Device Manager and also

how to upgrade the software of a device.

4.1 Import Software Files

Before being able to upgrade a device with new software, the software files applicable for

the device must be imported to the Device Manager. The software files are distributed by

your supplier.


2 Click the Software tab.

The following columns are displayed:

• Device type – the device model the software is applicable for.

• Version – the version number of the software file. Used to determine which

software file is the most recent.

• Parameter version – Shows the version of the parameter definition compatible

with the software. If the version is shown in red, no supporting parameter

definition is found the Device Manager. If the version is shown in dark red, a

compatible parameter definition is found, but it does not have the same

parameter definition used by the software.

NOTE: This column is not applicable for all device types, which means that the

column might be empty for these device types.

• Software type – shows if the software type is a boot software1 or a firmware.

• File – the name of the imported software file

• Size – the size of the imported software file

3 Click the Add button. The Import files window opens.

4 Select the software files to be imported.

Only files with a corresponding extension are shown, such as .bin and .pkg.

5 Click the Open button and then click the Close button.

6 If needed, continue with 4.3 Upgrade Software of a Device on page 15.

1.Currently, boot software is only applicable for fixed devices.



Device Manager


4.2 Delete Software Files

The software files that no longer will be used can be deleted from the Device Manager.



3 Select the software to be deleted.

4 Click the Delete button.

5 To confirm the deletion, click the Yes button.

4.3 Upgrade Software of a Device

1 Select the Devices tab.

2 Make sure that the devices to be upgraded are online in the Device Manager. A

should be shown for your devices.

3 Select the device(s) that are to be upgraded. It is possible to select several devices,

but only devices of the same device type can be selected.

NOTE: A software upgrade from Device Manager should be done on one device to start with.

If successful, the remaining devices can be updated in one operation.

TIP: By using Ctrl and/or Shift it is possible to select several devices simultaneously.

4 From the Device menu, select one of the following:

• Upgrade software, or

• Upgrade boot software (applicable for IPBS or IPBL only).



Device Manager


5 Depending on where the software file to be used is located, select one of the

following:

• Available files – select if you want to use a compatible software file that has

been imported to the Device Manager. In the drop-down list, select which

software to use.

TIP: If your file is not available in the drop-down list, you can import it by clicking

the Import button.

• Enter URL – select if the software file is stored on an external server and should

not be imported to the Device Manager. In the text field, enter the path to the

software file.

TIP: It is recommended to use this option when upgrading devices with large

software files.

6 In the Upgrade section, select when the device should be upgraded:

• Immediately – select to start the upgrade immediately

• Later (server time zone) – select to schedule the upgrade. Click the button below

this option to select when the upgrade should be made.

NOTE: If the time zone at your current location differs from the time zone used by

the module, select date and time that follows the time zone in the module.

For example:

The current date and time at your current location are 20 May 2014 12:00 (GMT)

and the current date and time in the module are 20 May 2014 10:00 (GMT -

02:00). The upgrade should be performed 20 May 2014 20:00 (GMT) meaning

that "20 May 2014 18:00" (GMT -02:00) should be selected in this case.

7 In the Activate new software section, select when software should be activated in

the devices:

• Immediately – activates the software immediately.

• When idle – activates the software when the device is in standby.

• When idle in charger1 – activates the software when the device is in standby

and put in chargers.

• After manual restart – activates the software when the user device restarts the

device.


The software will be downloaded to the device. For some device types, a progress bar in the

Status column for the device shows the progress of the download.

NOTE: If you want to cancel the upgrade, select Cancel current upgrade from the Device

menu.

The device will restart automatically after a successful download, except when After

manual restart has been selected.

NOTE: A switched off device is upgraded when restarted.

1.Not applicable for fixed devices.



Device Manager


NOTE: It is possible to upgrade the software on several devices of the same device type

simultaneously using the Baseline function, see 17. Baseline Management on page

62.

4.4 Restart of Devices

Devices can be restarted if needed. This feature, for example, can be used if you want to

perform a controlled restart of several devices simultaneously.


2 Select the devices you want to restart.

3 From the Device menu, select Restart device.

4 Select when the restart request should be sent to the devices.

• Immediately: the request is sent to the devices directly

• Later (server time zone): the request is sent to the devices on a specified date and

time.

NOTE: If the time zone at your current location differs from the time zone used by

the module, select date and time that follows the time zone in the module.

For example:

The current date and time at your current location are 20 May 2014 12:00 (GMT)

and the current date and time in the module are 20 May 2014 10:00 (GMT -

02:00). The upgrade should be performed 20 May 2014 20:00 (GMT) meaning

that "20 May 2014 18:00" (GMT -02:00) should be selected in this case.

5 Select when request should be activated, that is, when the devices should be

restarted.

• Immediately: The devices are restarted directly

• When idle: The devices are restarted when the devices are in idle mode.

• When idle in charger: The devices are restarted when they are put in a charger

and are in idle mode.


4.5 Device Properties

You can view a device’s properties that shows the following:

• Device information: shows Device ID, Device type, current installed software version etc.

• Current uploads to the device: shows if there is any current upload of software, language,

apps etc. An upload can be cancelled by clicking the Cancel button.



Device Manager


• Scheduled events: shows if there is any scheduled event (such as restart of device). An

event can be cancelled by clicking the Cancel button.

Figure 9. Example of device properties



Device Manager

5. App Management

5. App Management

NOTE: This tab is not available in IMS3.

This section describes the management of app files in the Device Manager and also how to

manage the apps on Ascom Myco handsets.

Figure 10. The Apps tab showing apps.

5.1 Manage Apps in Device Manager

This section describes how to import and delete apps in the Device Manager. An app that is

imported or deleted in the Device Manager is not installed or deleted in the device

connected to the Device Manager.

Column Description

Icon: Shows whether if the app is imported to Device Manager, or only

installed on device(s). This column is used in combination with the

Status column.

The icon shows an app only installed on devices, i.e. the app has

not been imported to Device Manager. If the app is imported to the

Device Manager, the app’s icon is shown instead.

Name: Shows the name of the app

Version: Show the version of the app. Each app with a certain version is shown

on one row, which means that an app with several versions is shown

on several rows, but with different versions.

Installs: Shows the number of devices the app with a certain version are

installed on.

Status Shows whether if the app is imported to Device Manager or only

installed on device(s). If no information is shown in this column, the

app is imported to the Device Manager. If the app only is installed on

the device, Only available on device is shown. This column is used in

combination with the Icon column.



Device Manager

5. App Management

5.1.1 Import App to Device Manager

Before an app can be installed on a device, the app has to be imported to the Device

Manager. After the app is imported, you can select which devices the app should be installed

on.

1 Click the Apps tab.

2 From the App menu, select Import.

3 Select the app file to be imported. The following app files are supported: .apk and

.apkg.

5.1.2 Delete App in Device Manager

If you delete an app from the Device Manager, it can no longer be installed on a device.

However, the app is not deleted from the device.

NOTE: If the app is included in a baseline, you cannot delete the app from Device Manager.


2 Select the app to be deleted in list.

3 From the App menu, select Delete.

4 Click Yes to confirm the deletion.

5.2 Manage Apps on Devices

This section describes how to manage apps on several devices simultaneously by installing,

replacing or deleting apps.

One app at the time can be managed and only one version of the app can exists on a device

at the time.


2 Select the app to be managed in the application list. If several app versions are

available, make sure that you select the correct app version.

3 From the App menu, select App management.

A dialog window shows all Ascom Myco devices and whether if they have the selected app

with a certain version installed.



Device Manager

5. App Management

Figure 11. 1. App Management dialog window

• Device with the selected app version installed (1).

• Device with app installed, but another version than the selected one (2).

• Device without the selected app installed (3).

5.2.1 Install New App or Update App Version

This section describes how to install a new app on devices, or update the app version

installed on the devices. If the app version is to be updated, the previous version will be

uninstalled on the device.

TIP: You can filtering the list to show which devices that have/have not the app installed by

selecting corresponding option in the drop-down above the list.

1 Click the check box for each device the app should be installed on.

2 Click the Install button.

5.2.2 Delete App from Device

This section describes how to delete an app with a certain version installed on devices.

TIP: You can filtering the list to show which devices that have the app version installed by

selecting corresponding option in the drop-down above the list.

1 Click the check box for each device the app version should be deleted from.

NOTE: You can only delete an app with the same version as the selected one.



Device Manager

5. App Management


5.3 View Apps on a Single Device

This section describes how to view apps installed on a single device.


2 Select the device which apps to be viewed.

3 From the Device menu, select List apps.

Column Description

Icon Shows whether if the app is installed on the device only or if

the app also is imported to Device Manager.

If the app is installed on the device and also imported to

Device Manager, the app’s icon is shown.

If the app only is installed on the device, the icon is

shown.

Name Shows the name of the installed app.

Version Shows the version of the app.



Device Manager

6. Language Management


6.1 Import Language files for Devices

For adding a new language to a device, a language file (.lng) distributed by your supplier

must be imported to the Device Manager and then uploaded to the device.

NOTE: Spaces or other unsafe URL characters must not be included in the name of the

language file. If unsafe characters are included in the name it cannot be uploaded to

handset with Advanced charger.


2 Click the Language tab.

3 Click the Add button. The Import files dialog opens.

4 Select the language file(s) to be imported.

5 Click the Open button and then click the Close button.

6 To apply the language for a device, see 6.3 Upload a Language to a Device on page

24.

6.2 Delete Language File for Devices

The language files that no longer will be used can be deleted from the Device Manager.



3 Select the language to be deleted.



Device Manager



5 To confirm the deletion, click Yes button.

6.3 Upload a Language to a Device

If supported by the device, additional languages can be uploaded to the device.

NOTE: Upload of languages is not available when IMS3/Unite CM is in Demonstration mode.


2 Select the device(s) to upload a language to. It is possible to select several devices,

but only devices of the same device type can be selected.

3 From the Devices menu, select Upload language.

4 Do one of the following:

• If needed; import the language file (.lng) to be used by clicking Import button,

and locate the file. From the Available files drop-down list, select which language

to upload.

• Enter the URL where the language file is located.

5 Click the OK button. The language is uploaded to the device.

NOTE: It is also possible to upload a language on several devices of the same device type

simultaneously using the Baseline function, see 17. Baseline Management on page

62.



Device Manager

7. Company Phonebook and Contacts


7.1 Company Phonebook Management

7.1.1 Import Company Phonebook files

If the device supports the Company Phonebook feature, it is possible to import a phonebook

file to the Device Manager for later use.

1 From the File menu, click File handling.

2 Click the Company Phonebook tab.

3 Click the Add button.

4 Select the company phonebook files to be imported.

5 Click the Open button.

7.1.2 Delete Company Phonebook File

1 From the File menu, click File handling.


3 Select the company phonebook to be deleted.


5 To confirm the deletion, click Yes button.



Device Manager


7.1.3 Upload Company Phonebook to Device

Company phonebook can be uploaded to supporting devices. A Company phonebook

contains entries that cannot be edited by the user of a device.


2 Select the device(s) to upload a company phonebook to. It is possible to select

several devices, but only devices of the same Device type can be selected.

3 From the Device menu, select Upload company phonebook.

4 Select which company phonebook to upload.

5 Click the OK button. The company phonebook is uploaded to the device.

7.2 Contacts Management

7.2.1 Import Contacts

NOTE: The number for the device must be saved, see 9.2 Save a Number to Database on

page 35.

Import Contacts From File

A file containing contacts can be imported to Device Manager and synchronized with a

device. This can for example be useful when you want to transfer contacts from legacy

devices to newer devices.

When importing the file, the device’s contacts (if any) are overwritten by the contacts in the

file. Additionally, the import works only if the device can store all contacts included in the

file. For example; if the file contains 100 contacts, the device must have support for storing

at least 100 contacts.

If needed, the number of contacts in the file can be changed by using Excel or other

compatible application.


2 Select a number.

3 From the Number menu, select Import contacts and then From file.

4 Find and select a file containing contacts (.txt or .csv). Click the Open button.

The contacts in the imported file are synchronized with the device.

Import Contacts From Number

You can make a copy of a device’s contact list and paste it to another device’s contact list

directly. This means that the contact list do not need to be saved on for example your

computer.



Device Manager


NOTE: The import works only if the receiving device can store the entire contact list of the

device you are importing from. For example; if the contact list contains 100 contacts,

the receiving device must have support for storing at least 100 contacts.


2 Select the device’s number you want to copy contacts from.

3 From the Number menu, select Import contacts and then From number.

4 Select the device’s number you want to paste the contacts to.

5 Click the OK button. The contacts are now imported to the device.

7.2.2 Export Contacts

You can make a copy of a device’s contact list that can be used as backup. The contact list

can also be imported to another supporting device later on (see Import Contacts From File

on page 26).


2 Select the device’s number you want to export contacts from.

3 From the Number menu, select Export contacts.

4 Enter a descriptive file name and click the Save button.



Device Manager

8. Template Management


By using a template, the same configuration can easily be applied to many devices

simultaneously. Templates are also an efficient way to give good control over which changes

that are applied to each device.

Your supplier can provide example templates for different PBXs. The device will have full

functionality towards the PBX even without such a template.

8.1 Create Parameter Template

It is usually desirable to create a customized parameter template that can be applied to all

devices of a certain device type.

1 Select the Templates tab.

2 From the Template menu, select New.

3 From the Device type drop-down list, select which device type the template should

be applicable for.

4 From the Parameter version drop-down list, select which parameter version the

template should be based on. The parameter version determines which parameter

settings that are available for your device type. It is recommended to select the latest

parameter version to obtain full compatibly with the device.


parameter definitions for that device type will be used when creating the template.

5 In the Name text field, enter an appropriate name of the template.


The Edit template window opens showing the parameters organized in a tree structure in

the left pane, with the parameters in the current node in the right pane. Clicking the icon

will give a short description of selected parameter. In addition, see also the manual for the

device for more information about the parameter.

Select the parameters to be saved in the template by selecting the check box to the left o

each parameter. Change the parameters to the desired values.



Device Manager


In the Edit template window, the following color coding is used:

7 When all needed parameters have been configured, click OK to save the settings.

8.2 Create a Parameter Template from a Number

It is also possible to create a template from a Number in the Device Manager. All parameters

included in the Number are saved in the template.

1 Select the Numbers tab.

2 Mark the Number in the list you want to use.

3 Right-click the Number and select Use as template.

4 Enter a name for the template.


The Edit template dialog window opens showing the parameters organized in a tree

structure in the left pane, with the parameters in the current node in the right pane. Clicking

the icon will give a short description of selected parameter. In addition, see also the

manual for the device for more information about the parameter.

Color Description

Black Normal


Purple The parameter is included in the template (checked)

Red Value not valid




Device Manager


6 A drop-down list is shown in the bottom left corner. This setting decides which

parameters that shall be copied from the Number.

• No parameters – Deselects all check boxes, no parameters will be applied to the

Number when running the template.

• Non default parameters – Selects only the parameters that are not using the

default values. Only these parameters will be applied to the Number when

running the template.

• All parameters – Selects all check boxes (all parameters). All parameters will be

applied to the Number when running the template. If selected, the

synchronization time will be longer.

• Custom parameters – If the options above are not applicable, you can customize

which parameters to be included in the template. E.g. if a mix of non-default

parameters and default parameters shall be included in the template, you have to

select each parameter manually. If so, "Custom parameters" is shown in the drop-

down list to indicate that selection of parameters has been customized. "Custom

parameters" is not an option, only an indication.

7 If needed, change the parameters to the desired values.

8.3 Create QR Code from Template

All parameters that have been selected in a template can be exported as a Quick Response

(QR) code. A device with QR code reader can then scan the QR code to apply the parameter

settings in the device.

The parameters exported to the QR code are encrypted. The number of parameters that can

be included in a QR code is device dependent. If the number of parameters exceeds the limit,

the QR code cannot be created. If so, a warning dialog appears when trying to create the QR

code.


2 Select the template which you want to create a QR code for.

3 From the Template menu, select Create QR code.



Device Manager


8.3.1 Copy QR Code

The QR code can be copied and then pasted into an appropriate application (for example in a

mail application). This can be useful if you want to share the QR code with others (for

example, users of devices).


2 Select the template which you want to create a QR code for.

3 From the Template menu, select QR code.

4 Click the Copy to clipboard button.

5 Paste the QR code into an application that can handle images.

8.4 Rename Template


2 Select the template you want to rename.

3 From the Template menu, select Rename.

4 Enter a new name in the New name text field.


The new name appears in the list in the Templates tab.

8.5 Copy Template

This section describes how to create a new template based on another template. The

parameters copied from "old" template can later on be edited in the new template.


2 Select the template you want to copy. The selected row is highlighted.

3 From the Template menu, select Copy.

4 Enter a new name in the New name text field.


The new template appears in the list in the Templates tab.



Device Manager


8.6 Edit Template

This section describes how to change parameters included in a template.

The template might include parameters that are not applicable for all devices of a certain

device type. However, the template can still be applied to all devices of that device type, but

the devices might discard parameters that are not applicable.


2 Select the template you want to edit.

3 From the Template menu, select Edit.

4 Edit the parameters that shall be edited.


8.7 Delete Template


2 Select the template you want to delete.

3 From the Template menu, select Delete.

4 To confirm the deletion, click Yes.

8.8 Upgrade Template

This section describes how to add new parameters to an existing template by changing the

parameter version the template is based on.

NOTE: This option might be disabled for some device types. In that case, the template is

updated automatically if new parameters exist in the device, that logs in to Device Manager.

NOTE: In order to upgrade a template, the new parameter version must have the same major

version as the old parameter version. For example, upgrading from 25.8 to 25.9

works, but not upgrading from 25.8 to 26.x.


2 Select the template you want to upgrade.

3 From the Template menu, select Upgrade.

4 Select the parameter version the template should be based on.




Device Manager


8.9 Apply Template

This section describes how to apply a template containing parameter settings to a number.

There are two ways to apply the template.

Apply Template to Numbers (Scenario 1)


2 Select the template you want to use.

3 From the Template menu, select Apply to.

4 If needed, select search parameters or click the Show all button.

5 Select Number(s) to apply the template on.


Apply Template to Numbers (Scenario 2)


2 Select the Number(s) you wish to apply the template to.

3 From the Number menu, click Apply template.

4 Select a template.


If the parameters in the database have been edited but not yet sent to the device it is

indicated with “Not synched” or “Update queued”.

If the Number has not been associated with a device, it is now possible to do so. Connect a

device and associate it with a Number in the database. The parameters will automatically be

sent from the Device Manager to the device. See 9.4 Associate Number with Device on page

36.



Device Manager


8.10 Import Templates from File

This section describes how to import templates to the Device Manager. This feature can be

used when you for example want to use the same template used in another Device Manager.

Additionally, the import can also be used when your supplier provides an updated template

for your device.

If there is a naming conflict when importing a template, the new template is saved with a

number added to the file name.

1 From the File menu, select Import and then Templates.

2 Select the template files to be imported (*.tpl) and click the Open button.

The Template(s) is imported.

8.11 Export Templates to File

This section describes how to export template(s) to a file. This feature can be used if you

want to make a backup of the template, and/or want to import the template to another

Device Manager later on.


2 Select the template (or templates).

3 From the Template menu, select Export.

The Export Templates dialog appears. By default the file will be saved in the My documents

folder with the name Templates.tpl. You can select another name and folder.

4 Click the Save button.



Device Manager

9. Number Management


Numbers work as a placeholder for all settings made for a device in the Device Manager. This

means that all settings have to be associated with a number to be able to synchronize the

settings with a device later on.

9.1 Create Numbers


2 From the Number menu, select New.

3 In the Device type drop-down list, select which device type the number(s) is created

for.

4 In the Parameter version drop-down list, select the parameter version the number

shall be compatible with.


parameter definitions for that device type will be used when creating the number.

5 If you have a template you want to apply to the numbers, select which template to be

applied in the Template drop-down list.

6 In the Prefix field, enter the prefix (if needed) to be added to the number(s).

7 Select one of the following options:

• To create a single number, select the Single option and enter the number.

• To create a range of numbers, select the Range option. Enter the start number

and end number.

NOTE: The maximum range that can be added at a time is 100 numbers.


9.2 Save a Number to Database

When connecting a device with a number to the Device Manager, the number will by

default1 be saved. If not using this setting, the number has to be saved manually. A saved

number makes it possible to configure the device without having the device connected. Any

configurations made for a device’s number will be synchronized with the device when it is

connected again.

1.The number will be saved automatically if the Automatically enable new devices check box is marked. See 16.1 Enable/

Disable New Devices on page 61



Device Manager



2 Select the device´s number to be saved.

3 From the Number menu, select Save.

9.3 Enter/Edit Number Information

It is possible to enter information of a number, for example the user of the number.


2 Select number.

3 From the Number menu, select Enter description.

4 Enter an appropriate description and click the OK button to save the setting.

9.4 Associate Number with Device

This section describes how to associate devices with numbers. Because the numbers work as

a placeholder for all settings made for devices, the devices will also be configured with these

settings when associating the numbers with the devices. You can only associate one number

at the time.


2 Select the number to be associated with a device.

3 From the Number menu, select Associate with device.

4 Select the device to be configured with the selected number.


When the number is associated to the device, the device ID of the device is shown on the

same row as the number.



Device Manager


Figure 12. Example of a number associated to a device.

Repeat steps 2 - 5 to associate additional numbers to other devices.

9.5 Delete Number


2 Select the Number you want to delete.

3 From the Number menu, select Delete.

4 Click the Yes button to confirm the deletion.

9.6 Rename Number

This section describes how to change an existing number to new one. It is not possible to

change to a number that already exists.


2 Select the number you want to rename.

3 From the Number menu, select Rename.

4 In the New prefix text field, enter a new prefix (if needed)

5 In the New number text field, enter a new number.


9.7 Copy Number

This section describes how to copy parameter settings and device type belonging to a

certain number to a new number. This is useful when settings are to be copied to one new

number at the time.


2 Select the number you want to copy.

3 From the Number menu, select Copy.

4 In the New prefix text field, enter a new prefix (if needed)





Device Manager


9.8 Export Numbers to a File

This section describes how to export numbers from the Device Manager. This feature is used

when you want to move numbers between Device Managers. The parameter settings for

each number are also included in the file. The file can then be used when producing new

devices for the customer.


2 Select the numbers to be exported.

3 From the Number menu, select Export.

The Export Numbers dialog appears. By default the file will be saved in the My documents

folder with the name EliseSite.xcp. You can select another name and folder.

4 Click the Save button.

9.9 Import Numbers from File

This section describes how to import numbers to the Device Manager. This feature is used

when you want to move numbers between Device Managers. The parameter settings for

each number are also included in the file.

If there is a number conflict when importing the numbers, an error message is displayed.

1 From the File menu, select Import and then Numbers.

2 Select the number files to be imported (*.xcp) and click Open.

The number(s) is imported.



Device Manager

10. Device Management


All settings made in the Device Manager need to be associated with a certain device to be

able to transfer the settings to the device. Beside the settings, software upgrade, factory

reset etc. can also be made for the device.

10.1 Add Devices

This section describes how to add devices that are not connected to any system and can

therefore not log on to the Device Manager. In this case, the devices can be added in

advanced by entering the Device IDs of the devices. The Device ID is unique for each device

and can be found on the device’s box or in the device’s GUI.

Depending on which device to be added, the following Device ID is to be entered:

• For DECT handsets, enter the IPEI number

• For VoWiFi handsets, Ascom Myco handsets, and chargers; enter the MAC address

NOTE: In order to simplify input when handling many devices, a barcode reader can be used

to read the barcode on the device’s box. The barcode reader should send a carriage

return after each ID, but it is not necessary. If carriage return is not sent, it is

necessary to click “Create” after each read item.


2 From the Device menu, select Add device.

3 In the Device type drop-down list, select which device type to be added.

4 In the Parameter version drop-down list, select the parameter version to be used by

your device type.


parameter definitions for that device type will be compatible when creating the

device.

5 In the Device ID text field, enter Device ID for the device manually, or by using a

barcode reader.

The Continuous registration check box can be used to select whether if the Create

devices dialog window shall close after clicking “Create” or if it shall still be open.

6 Click the Create button.

Repeat 3 to 6 if more devices are to be created, otherwise click the Close button.

10.2 Delete Device




Device Manager


2 Select the device you want to delete.

3 From the Devices menu, select Delete.

4 Click the Yes button to confirm the deletion.

NOTE: A device that is online cannot be deleted.

10.3 Replace Device

NOTE: This feature is not applicable for fixed devices.

If a device shall be replaced with a new device, the replaced device’s number and settings

can be transferred to the new device. The new device must be of the same device type as

the replaced one.

NOTE: Certificates (if any) are not transferred to the new device. These have to be imported

to the device, see 11. Certificate Management on page 43.

1 If the device to be replaced is still working, make sure that it is synchronized:

• In the Devices tab, right-click the device to be replaced

• Select Go to number.

• Check that status of the device’s number shows Synchronized.

2 Switch off the device to be replaced. The device is shown as offline after a while.

3 Connect the new device to the Device Manager.

4 Associate the new device to the Number associated to the old device according to the

instructions in 9.4 Associate Number with Device on page 36. The Number will no

longer be associated with the old device.

10.4 Assign Number to Device


A number can be assigned to a device, that has not yet been assigned a number in Device

Manager. This can be used if parameters have been changed on the device prior to

connection to Device Manager.


2 Select the device you want to assign a Number for.

3 From the Devices menu, select Assign number.




Device Manager


5 In the New prefix text field, enter prefix if used (optional).


The new Number appears in the list in the Numbers tab.

NOTE: Some devices need to be restarted for the new numbers to be shown.

10.5 Enter Device Information

Information of a device can be entered. For example, the description can be used to describe

a user of a device.


2 Select the device.

3 From the Device menu, select Enter description.

4 Enter an appropriate description and click OK to save the setting.

10.6 Factory Reset

Factory reset means that the device parameters will be reset to factory settings. The

Number in the database that is associated with the device will not be affected.

NOTE: The device must be online.


2 Select the device(s) to be reset.

3 From the Device menu, select Factory reset.

4 Click Yes to confirm the deletion.

10.7 Synchronize Device

When parameters have been changed in a device, the device is synchronized with the

Number saved in the database. When a device is being synchronized, parameters that have

been changed in the device are uploaded to the Device Manager and parameters that have

been changed in the Device Manager are sent to the device. If a parameter has been

changed in both the device and the Device Manager, the setting made in the Device

Manager will take precedence.

When a device is connected to the system running the Device Manager and if the Number is

saved and it has a parameter definition, the device is automatically synchronized.

While synchronizing, a progress bar and a text is shown in the Numbers view.

10.8 Lock Device

NOTE: This feature is applicable for Ascom Myco handsets only.

You can lock a device to prevent unauthorized usage of it. This can for example be used if

the device is lost. If one tries to use the locked device, he/she needs to enter a password to

be able to unlock the device. The password is set in the Device Manager by the

administrator.




Device Manager


2 Select the device(s) to be locked.

3 From the Device menu, select Lock device.

4 Enter the password required to unlock the device(s). The complexity (e.g. big letters

and special characters) of the password is determined by the settings in the

device(s).

5 Enter the text to be shown on the locked devices’ display. The text can for example

inform the user that he/she has to contact the administrator to obtain the password.

6 Click OK to lock the device(s).

"Device locked" is now stated for the locked devices in the Status column.

10.8.1 Unlock Device from Device Manager

A device that has been remotely locked from Device Manager can only be unlocked from the

device’s GUI. The device is unlocked by logging in to the device by using the password

configured in the Device Manager. Refer to the device’s documentation.



Device Manager

11. Certificate Management


Certificates are used for authentication between handsets and systems (e.g. WLAN and IP-

PBX). Authentication is the process of verifying the identity of handsets and systems. This

can be used to ensure that only communication between trusted handsets and a trusted

system can be established.

There are two types of certificates than can be imported to the handsets:

• Trusted certificate: All certificates the handset should trust are imported to the

handset’s Trust list. When a system sends its certificate to authenticate itself to the

handset, the handset controls if the certificate is trusted. The system’s certificate or one

that trusts the system’s certificate can be imported.

• Application certificate: An application certificate is the one the handset uses to

authenticate itself by sending the certificate to the system. Depending on how the

system is configured, it might control if the application certificate is trusted.

11.1 Manage Certificates for Ascom Myco Handsets

11.1.1 Import Certificate

NOTE: Import of nested certificates (i.e. certificate chains) is not supported.


2 Select the device which certificates to be managed.

3 From the Device menu, select Manage certificates.

4 Click the Trusted list tab or the Application certificates tab depending on which

certificate to be imported.

5 Click the Browse button and locate the certificate file to be imported. The following

certificate formats are supported: .cer, .der, .crt, .pem, .p12, and .pfx.

6 If the certificate is passport protected, an Enter Password dialog appears. Enter the

password and then click the OK button.

A Confirm Certificate window opens showing the details of the certificate.

7 Import the certificate to the device by clicking the Yes button.

If needed, repeat step 3 - 7 for importing additional certificates.

11.1.2 View Certificate Details


2 Select the device which certificates to be viewed.



certificate to be viewed.

5 Select the certificate to view by clicking the icon next to the certificate.

A Certificate details window appears.

11.1.3 Remove Certificate


2 Select the device which certificates to be removed.




Device Manager



certificate to be removed.

5 Select the certificate to remove by clicking the corresponding Remove button.

6 Confirm the deletion by clicking the Yes button.

11.2 Manage Certificates for Ascom i62 VoWiFi Handsets

11.2.1 Import Certificate

NOTE: Import of nested certificates (i.e. certificate chains) is not supported.


2 Select the number which certificates to be managed.

3 From the Number menu, select Manage certificates.


certificate to be imported.

5 Click the Browse button and locate the certificate file to be imported. The following

certificate formats are supported: .cer, .der, .crt, .pem, .p12, .pfx, and .p7b.

6 If the certificate is passport protected, an Enter Password dialog appears. Enter the

password and then click the OK button.

A Confirm Certificate window opens showing the details of the certificate.

7 Import the certificate to the handset by clicking the Yes button.

If needed, repeat step 3 - 7 for importing additional certificates.

NOTE: Additional settings for certificates might be needed in the handset, refer to the

handset documentation.

NOTE: If a handset is factory reset or if the handset is replaced, any certificates associated

with the handset’s number have to be re-imported to the Device Manager. If not, the

certificates will not be downloaded to the handset. Simply remove the certificates and

import them again.

11.2.2 View Certificate Details


2 Select the device which certificates to be viewed.



certificate to be viewed.

5 Select the certificate to view by clicking the icon next to the certificate.

A Certificate details window appears.

11.2.3 Remove Certificate


2 Select the device which certificates to be removed.



certificate to be removed.



Device Manager


5 Select the certificate to remove by clicking the corresponding Remove button.

6 Confirm the deletion by clicking the Yes button.



Device Manager

12. Parameter Settings


12.1 Working with Parameters

The Edit Parameter window shows a set of parameters that be edited for a number.

Figure 13. The Edit parameters window

1 Shows a parameter group in the tree structure.

2 Shows a parameter item included in the parameter group.

3 Shows the parameters for the selected item in the tree structure. The parameter list

has one column with the parameter name and another column shows the parameter

value.

4 Clicking the icon will give a short description of the selected parameter. In

addition, see also the manual for the device for more information about the

parameters.

12.1.1 Dynamic List of Parameter Items

NOTE: This feature is only applicable for Ascom Myco handsets.

A parameter item can be added multiple times if needed. E.g. if there is only one Network

item in the tree structure and you want to configure an additional network, you can add an

additional Network item to the list.



Device Manager


Figure 14. Dynamic list in Edit parameters dialog window.

1 Shows a dynamic list with added parameters.

2 Shows parameter items added to the dynamic list

3 Shows an empty dynamic list (no parameter items added). An empty dynamic list is

black

Add parameter item

1 Right-click a dynamic list indicated by the icon .

2 Select Add Entry.

When adding a parameter item, it becomes purple.

Repeat the steps above if you want to add additional parameter items.

Delete parameter item

1 Right-click a parameter item.

2 Select Delete Entry to remove the item from the tree.

Repeat the steps above if you want to remove additional parameter items.

12.2 Edit Parameters for a Number

This section describes how to edit parameters for a number. The parameters are

synchronized with the device with corresponding number when the device becomes online

in the Device Manager.


2 Select the number which parameters to be edited.

3 From the Number menu, select Edit.



Device Manager


4 Change the parameters to the desired values.

In the Edit parameters window, the following color coding is used:

5 Click OK to save the changes.

Color Description

Black Normal


Red Value not valid


Purple A parameter item has been added to a dynamic list



Device Manager

13. File Management

13. File Management

This section describes the files that can be imported to the Device Manager.

13.1 Package Files

A package file may include different types of files, e.g. software files, parameter definition

files and/or template files. If the package does not include a certain file, it can be imported

separately.


2 Click either the Parameter definition tab or the Software tab.

3 Select the package file (.pkg) to be imported and click Open.

The files included in the package are now imported. If needed, click the Parameter

definition tab or Software tab to view the corresponding imported files (if any). If

template(s) has been imported, it can be viewed by clicking Close and then selecting the

Template tab.

13.2 Parameter Definition Files

Add files

A definition file (.def) is tied to a certain device type and includes the parameters that can

be configured for that device type. The definition files are distributed by your supplier.

NOTE: Each Ascom Myco handset has a parameter definition file installed. If the same file

does not exists in the Device Manager, it is imported automatically to the Device

Manager when the handset logs in.


2 Click the Parameter definition tab.

3 Select the definition file (.def) to be imported and click Open.

Delete files

NOTE: You cannot delete parameter definition files used by Ascom Myco handsets. These

files are deleted automatically in the Device Manager when they are not used by any

handset.




Device Manager

13. File Management

2 Click the Parameter definition tab.

3 Select the files to be deleted and click Delete.

4 Click Yes in the Delete files dialog.

13.3 Software Files

Add files

Before being able to upgrade a device with new software, the software files applicable for

the device must be imported to the Device Manager. The software files are distributed by

your supplier.



The following columns are displayed:

• Device type – the device model.

• Version – the version number of the software file. Used to determine which

software file is the most recent.

• Parameter version – shows the version of the parameters in the definition file.

Used to determine compatibility with device software.

• Software type – shows if the software type is a boot software1 or a firmware.

• File – the name of the imported software file.

3 Click Add. The Import files window opens.

4 Select the software files to be imported.

Only files with a corresponding extension are shown, such as .bin and .pkg.

5 Click Open and then click Close.

Delete files



3 Select the software file to be deleted.

4 Click Delete.


1.Currently, boot software is only applicable for fixed devices.



Device Manager

13. File Management

13.4 Language Files

Add files

For adding a new language to a device, a language file (.lng) distributed by your supplier

must be imported to the Device Manager and then uploaded to the device.

NOTE: Spaces or other unsafe URL characters must not be included in the name of the

language file. If unsafe characters are included in the name it cannot be uploaded to

handset with Advanced charger.



3 Click Add. The Import files dialog opens.

4 Select the language file(s) to be imported.


Delete files



3 Select the language file to be deleted.

4 Click Delete.


13.5 Company Phonebook Files

Add files

If the device supports the Company Phonebook feature, a phonebook file can imported to

the Device Manager for later use.





Device Manager

13. File Management

3 Click Add.

4 Select the company phonebook files to be imported.


Delete files



3 Select the phonebook file to be deleted.

4 Click Delete.




Device Manager

14. Number and Device Limitations


14.1 Number of Devices in Device Manager

The number of devices that can be managed in the Device Manager depends on number of

licensed devices. For products where messaging users can be configured, each messaging

user gives 2 licensed devices.

NOTE: If "Max. No. of Devices" license is enabled, you will get the number of devices defined

in the license regardless of number of messaging users.

For products where messaging users cannot be configured, you will get the number of

devices defined in the "Max. No. of Devices" license.

Table 1.

14.2 Products Managed by Unite Admin

For products that can be managed by Unite Admin, messaging users are managed from

Unite Admin. For each configured messaging user in Unite Admin, the number of licensed

devices is increased by 2 in the product.

Table 2.

Example

Pre-requisites:

• You have a license that allows to manage 20 messaging users in Unite Admin, but no

users have been configured yet.

• Max. No. of Devices is disabled for Unite CM/Unite CS

• A Core license (Unite CM only) or a Unite System (Unite CS only) is added in respectively

product.

In respectively Core/Unite system license, 20 licensed devices are included. When an 11th

messaging user is configured in Unite Admin, the number of licensed devices is increased by

2 (in this case to 22 devices).

Table 3.

Product Messaging user configuration Max. No. of devices license

IMS3 No Yes

Unite CM Yes Yes

Unite CS Yes Yes

Product Unite Admin support

IMS3 No

Unite CM Yes

Unite CS Yes

No. of configured messaging users in

Unite Admin

No. of licensed devices in Unite CM/

Unite CS

0 - 10 20

11 and more 22 and more



Device Manager


14.3 View Number of Licensed Devices

1 From the Start page, click Configuration.

2 Click Other and then Advanced Configuration.

3 Click Troubleshoot and then System Information.

In the Device Manager section, the maximum number of licensed devices is shown.

14.4 Examples of Limits

In this example, the Device Manager in Unite CM/Unite CS/IMS3 allows you to add 100

devices and 250 numbers.

Example 1

In this case 90 devices and 200 numbers have already been added, which means that 10

more devices and 50 more numbers can be added, see table below.

If you try to add more devices and/or numbers than allowed, a dialog appears to inform you

about the maximum numbers/devices that can be added.

This issue can be solved by either adding another license including more devices/users, or by

deleting devices and numbers in the Device Manager.

Example 2

In this case 100 devices and 250 numbers have already been added, which means that no

more devices or numbers can be added, see table below.

If an additional device is logs in the Device Manager, either by placing it in an advanced

charger or via Over-the-Air, this device will automatically be disabled. The Device ID of the

disabled device is highlighted with red color under in the Devices tab, see Figure 15.

Figure 15. Disabled device indicated by a red highlighted Device ID.

Disabled devices with numbers are also shown in the Numbers tab. The Device ID is

highlighted with red color and Device disabled is also shown, see Figure 16.

Allowed Added Remaining

100 Devices 90 Devices 10 Devices

250 Numbers 200 Numbers 50 Numbers

Allowed Added Remaining

100 Devices 100 Devices 0 Devices

250 Numbers 250 Numbers 0 Numbers



Device Manager


Figure 16. Disabled device indicated by a red highlighted Device ID and the status Device

disabled.

A disabled device cannot be configured such as edit parameters, associate with device,

import contacts etc. To enable the device, another device must first be disabled or deleted.

See Disable and Enable Devices or Delete and Enable Devices for more information.

Disable and Enable Devices

If the maximum number of allowed devices have been exceeded, a device needs to be

disabled before you can enable another device.

NOTE: It is only possible to disable one device at every 60 seconds. If you are trying to

disable two devices after each other within this time period, a dialog window appears.

Figure 17. Failed to enable/disable device.

1 Select the Devices tab

2 Select the device to be disabled.

3 From the Device menu, select Disable device.

The Device ID of the disabled device turns red.

4 Select the device to be enabled.

5 From the Device menu, select Enable device.

The Device ID of the enabled device turns black.

Repeat step 2 - 4 to disable/enable additional devices.

Delete and Enable Devices

It is possible to delete devices that are not online and then enable another devices until

maximum allowed devices are reached. If you are trying to enable more devices than

allowed, a dialog window appears.



Device Manager


Figure 18. Too many devices enabled.

1 Select the Devices tab

2 Select the device(s) to be deleted.

3 From the Device menu, select Delete.

4 Select the device(s) to be enabled.

5 From the Device menu, select Enable device.

The Device ID(s) of the enabled device(s) turns black.



Device Manager

15. License Management


This section describes the device licensing features that can be made using Device Manager.

In Device Manager, device licensing offers a possibility to view, manage and upgrade

licenses of devices. In the Licenses tab, devices are listed. If a device is selected in the list, the

status of the license options for the selected device is displayed.

Note that some tasks include using the license web and the details of how to work with the

license web are not described here.

The following features are described:

• Upgrade licenses, “Import” and “Export”

• Manual synchronization of licensing information, “Refresh”

• Move license from one device to another

• View license options

• Filter license options

The following licensing features are not done in Device Manager and are therefore NOT

described is this document:

• How to work with the license web

• How to purchase licenses

• Manual license upgrade in the device

See Function Description, Product Licensing Overview, TD 92677GB.

15.1 License Upgrade Alternatives

These are the alternatives for upgrading licenses on devices:

• Automatic license upgrade

Used when the Device Manager has an Internet connection to access the license server,

see 15.1.1 Automatic license upgrade.

• License upgrade using export/import

Used when the Device Manager does not have an Internet connection, see 15.1.2 Export

and Import Licensing information.

• Manual license upgrade

Used to enter the license key manually in the device, see the manual for the device. In

this case, Device Manager is not used.

15.1.1 Automatic license upgrade

NOTE: This feature requires an Internet connection. The communication is done via HTTPS

and normally via port 443.

The first time a device logs in the Device Manager asks the license server for the latest

license for the device. When the device logs in at a later time, there is no automatic check for

licenses. If changes have been made, a manual upgrade must be done by selecting Refresh,

see 15.1.6 Refresh on page 60.

In order to get a purchased license for a device, a connection with the license server is made.

Device Manager automatically receives the serial number from the device, sends it to the

license server which returns a license key that Device Manager sends to the device. The



Device Manager


device upgrades and the correct license information is shown in Device Manager and the

device.

15.1.2 Export and Import Licensing information

In order to upgrade licenses on devices when the Device Manager does not have an Internet

connection to the license server, the following is done:

• The information needed for licensing of a device is exported from the Device Manager to

a file, see Export Licensing information on page 58.

• The file is used to purchase license upgrades on the license web

(https://www.ascom-ws.com/Licenses).

• From the license web, a license file containing the license keys for the device is generated

• The license file is imported to the Device Manager, see Import Licenses on page 58

• The Device Manager communicates the license key (included in the license file) to the

device

• The device upgrades according to the license options

Export Licensing information

The information needed for licensing of a device can be exported to a file. This file can be

used to generate licenses for the device.

1 Select the Licenses tab.

2 Select the device(s) that shall be licensed.

3 From the License menu, select Export.

4 Enter an appropriate name of the file and click Save.

Import Licenses

After a license has been purchased, a file containing the license information can be

generated from the license web. This license file can be imported to the Device Manager.

1 From the File menu, select Import and then Licenses. A File Browser window

appears.

2 Select the license file(s) to be imported (*.xml) and then click Open.

15.1.3 View license options

It is possible to view which license options that exist on a device.


2 Select a device.

In the bottom of the work area, the available license options of the device are listed and

whether the options are enabled or not.

15.1.4 Filter license options

It is possible to search and select devices which have same license options. The selected

devices can be upgraded with additional licenses by exporting a product information file to

the License Web (see Export Licensing information on page 58). The advantage to select

devices with same license options is that additional licenses can be applied for the devices

simultaneously.


2 Click the Advanced find button.



Device Manager


3 Under Device types, select device(s).

4 Under Option filters, select the status of the license option(s) that shall be common

for the selected devices.

• Ignore - show all devices independent of license options.

• Enabled - show devices with a certain license option enabled.

• Disabled - show devices with a certain license option disabled.

The search result is updated directly when selecting devices and license options. In addition,

the icon is also displayed next to the Advanced find button to indicate that the search

result is filtered.

5 When clicking Close, the filtered search result will still be displayed. When clicking

Reset, the filter is removed and all devices are displayed.

15.1.5 Move License

This feature can for example be used if your device is broken and you want to move the

license to another device.


NOTE: This feature requires an Internet connection to access the license server.


2 Select the device whose license shall be moved. The selected row is highlighted.

3 From the License menu, select Move license. The Move license dialog window

appears.

4 Select the device that shall receive the license. Click “OK”.

If no devices are shown in the Move license window, there are no devices that are

selectable to move the license to.

If the device type of the device that received the license is still unchanged in the Device

Manager, select this device and do the following:

5 From the License menu, select Refresh to complete the transfer of the license. The

device type of the device is now updated in Device Manager.



Device Manager


15.1.6 Refresh

If a device is already registered in Device Manager and new license has been purchased from

the license web, the information needs to be updated. By doing a Refresh, the device license

information in Device Manager is synchronized with the information in the license server

and transferred to the device.

NOTE: This feature requires an Internet connection to the license server.


2 Select device(s).

3 From the License menu, select Refresh to complete the transfer of the license. The

device type of the device is now updated in Device Manager.

15.1.7 Remove Devices from the License View

This command removes devices from the Licenses tab view.


2 Select the device(s) that shall be removed from the list. The selected row(s) are

highlighted.

3 From the License menu, select Remove device.

4 Click Yes.



Device Manager

16. Other Settings

16. Other Settings

16.1 Enable/Disable New Devices

By default, when a new device logs in, it is automatically enabled and saved in the Device

Manager.

NOTE: The number of devices that can be managed simultaneously is license dependent. If

logging in more devices than allowed, they will be disabled in the Device Manager. The

devices must be enabled in order to configure them.

When a single Unite CM/Unite CS/IMS3 is used, the Automatically enable new devices

function should normally be enabled.

When Device Management is distributed over multiple Unite CM/Unite CS/IMS3 in a system,

the function should be disabled. If the function is enabled, devices will be saved on all Unite

CM/Unite CS/IMS3s running device management. This will cause synchronization problems

and the logged in devices will consume license positions on each Unite CM/Unite CS/IMS3.

1 From the Options menu, select Preferences.

2 Select whether if new devises should be disabled or enabled by checking or clearing

the Automatically enable new devices check box, respectively.

3 Click OK.



Device Manager

17. Baseline Management


Baseline can be used to apply software, languages etc. to all devices simultaneously of a

certain device type. This is useful when many handsets should be managed.

The following can be managed for respectively device via baseline:

17.1 Enable/Disable Baseline

1 From the Options menu, select Preferences.

2 Select whether the baseline is to be disabled or enabled by selecting or clearing the

Use device baseline configuration check box, respectively.


17.2 Set Up Baseline

This section describes how to set up what to be included in the baseline for a certain device

type. All settings in the baseline will be applied to the devices when they become online in

the Device Manager.

1 From the File menu, select Baseline.

2 If baseline management is disabled (indicated by a red bar in the top of the window),

enable the baseline management by clicking Click to change. When the baseline

management is enabled, the bar becomes green.

Ascom Myco Other Handsetsa

a. DECT and VoWiFi handsets.

IPBS/IPBL

Software (firmware) Yes Yes Yes

Boot software Yes Yes No

Template Yes Yes No

Language Yes Yes No

Certificate Yes No No

Apps Yes No No



Device Manager


3 Select device type, which the baseline should be managed for, in the left pane.

4 Depending on what to be included in the baseline, continue with the steps below.

17.2.1 Manage Software, Bootware, Template and Language

1 Select what to be included in the baseline by selecting the applicable check box(es).

2 In the corresponding drop-down list, select the file to be used. For template and

language files, the percentage of compatible devices is shown.

NOTE: If the files are not available, they can be imported by clicking the Import

button.

3 Save the baseline by clicking the OK button.

17.2.2 Manage Apps

1 Select the apps to be included by clicking the corresponding check box(es).

NOTE: If the files are not available, they can be imported by clicking the Import

button in the right upper corner.



Device Manager



17.2.3 Manage Certificate

All certificates the handset should trust can be imported to the handset’s Trust list. When a

system sends its certificate to authenticate itself to the handset, the handset controls if the

certificate is trusted. The system’s certificate or one that trusts the system’s certificate

should be imported.

NOTE: Application certificates cannot be managed via baseline. They have to be managed

from the Devices tab, see 11.1.1 Import Certificate on page 43. Additionally, import of

nested certificates (i.e. certificate chains) is not supported.

1 Click the Add button.

2 Locate the certificate to be imported and click the Open button.

The following certificate formats are supported: .cer, .der, .crt, .pem, .p12, .pfx, and

.p7b.

3 If the certificate is protected, enter the password and click the OK button.

4 The information about the certificate appears. If this is the correct certificate, click the

Yes button.



Device Manager


5 Repeat steps 1 - 4 to add additional certificates.


View certificate

• Details of an added certificate can be viewed by clicking the icon next to the

certificate.

Remove Certificate

1 Remove a certificate by clicking the Remove button next to the certificate.


17.2.4 Baseline Reset

If you have set up a baseline, you can reset devices according to the settings, software, and

language included in the baseline. The baseline reset can also be used if you only want to

apply the baseline to few devices of a certain device type.


2 Select the device(s) the baseline is to be applied to. You can only select devices of the

same device type.

3 From the Devices menu, select Reset to baseline.

4 Confirm by clicking the Yes button.



Device Manager

18. Related Documents

18. Related Documents

Configuration Manual, Unite Connectivity Manager TD 92735EN

Configuration Manual, Unite Communication Server TD 92761EN

Configuration Manual, IMS3 TD 92762EN



Device Manager

19. Document History


For details in the latest version, see change bars in the document.

Version Date Description

A 10 June 2011 First released version.

B 27 June 2011 Updates in chapter 7.2.1 Import Contacts on page 26

C 19 December 2011 See change bars in the document.

D 16 May 2012 Updated:

1.1 Basic Terminology on page 1

4 File Management in Device Manager on page 13

4.3 Upgrade Software of a Device on page 15

8. Template Management on page 28

9. Number Management on page 35

10. Device Management on page 39

4.3 Upgrade Software of a Device on page 15

6.3 Upload a Language to a Device on page 24

15.1.5 Move License on page 59

E 12 November 2012 Added:

Appendix B. Overlapping Number Plan in Device

Manager on page 71

Updated:

4.3 Upgrade Software of a Device on page 15: note

regarding how many devices that can be upgraded

simultaneously added.

F 21 November 2013 Added:

3. Initial Configuration of Devices on page 9

17.2.4 Baseline Reset on page 65

Updated:

7.2 Contacts Management on page 26: Note

regarding compability when copying contacts added.

4.5 Certificate Handling for Handsets on page 21:

Updated due to GUI has been changed.

14. Number and Device Limitations on page 53:

updated to also apply IMS3

Structural changes in the entire document

G 28 April 2014 Appendix C updated. See change bar for more

information.

H 28 August 2014 4.3 Upgrade Software of a Device on page 15:

Clarified that server time zone is used when

scheduling an upgrade.

4.4 Restart of Devices on page 17: New chapter.

I 12 November 2014 8.4.1 Import Certificate on page 32: Supported

certificate formats added.

Appendix C. Troubleshooting on page 69: Updated



Device Manager


J 08 January 2015 5. App Management on page 19: New chapter

11. Certificate Management on page 43: Certificate

handling for Ascom Myco added.

2.2.3 Apps Tab on page 6: New chapter

10.8.1 Unlock Device from Device Manager on page

42: New chapter

17. Baseline Management on page 62: Certificate and

apps in baseline added.

4.5 Device Properties on page 17: New chapter

4.3 Upgrade Software of a Device on page 15:

Clarified that large files should be stored on external

server instead of importing the files.

K 23 April 2015 2.2.1 Devices Tab on page 3: Status icon updated.

8.3 Create QR Code from Template on page 30: New

chapter.

L 28 August 2015 13. File Management on page 49, 4.1 Import Software

Files on page 14, 6.1 Import Language files for Devices

on page 23 and, 7.1 Company Phonebook

Management on page 25: Screen shots updated due

to new Size column.

M 16 November 2015 8.2 Create a Parameter Template from a Number on

page 29: Clarified the use of "Custom parameter"

(UCM-2635).

11.2 Manage Certificates for Ascom i62 VoWiFi

Handsets on page 44: Note added regarding that

certificates have to be imported again when replacing

a device (UCM-1444).

N 01 February 2016 11.1.1 Import Certificate on page 43: support for

".p7b" certificates removed (UCM-2838).

O 20 October 2016 14. Number and Device Limitations on page 53:

Clarified how licensing of devices works (UCM-3057).

1. Device Manager on page 1: Clarified that features in

Device Manager is device dependent (UCM-3063).

P 08 January 2018 Appendix C. Troubleshooting on page 72: Added a

workaround to apply parameter settings to a Number

instead of a device (UCM-3212).

Version Date Description



Device Manager

Appendix A. Device Manager Keyboard Shortcuts


The following table shows the shortcuts that can be used in the Device Manager.

A.1 General

A.2 Devices

A.3 Numbers

A.4 Templates

Shortcut Description

Ctrl + H Open the File management window

Ctrl + B Open the Edit Baselines window

Ctrl + Tab Switch tab

Alt + F4 Close the application


Ctrl + N Add a new device

Enter Upgrade the selected device(s)

Delete Delete the selected device(s)

Ctrl + F Find a device

Ctrl + Enter Open the Properties window for the selected device


Ctrl + N Add a new Number

Enter Edit the selected Number

Ctrl + C Copy the selected Number

F2 Rename the selected Number

Ctrl + S Save the selected Number to the database

Delete Delete the selected Number from the database

Ctrl + F Find a Number


Ctrl + N Add a new template

Enter Edit the selected template

Ctrl + C Copy the selected template

F2 Rename the selected template

Delete Delete the selected template

Ctrl + F Find a template



Device Manager


A.5 Licenses


Delete Remove the selected device(s) from the license view

Ctrl + F Find a device



Device Manager

Appendix B. Overlapping Number Plan in Device Manager

Appendix B. Overlapping Number Plan in Device Manager

Several systems that have overlapping number plans can be connected to one and same

Device Manager. This means that different devices with same number and same device type

can be managed in the same Device Manager simultaneously.

If a device logs in, and the device’s number already exists in the Device Manager, the Device

Manager must determine if the device is the same device or another one according to the

following rules:

• If the number and device ID match one already, it is assumed to be the same device.

• If the number matches one already, but the device ID differs, the Device Manager

compares the IP addresses of the Device Handlers and the IP addresses of the DECT

Masters (if available). If the IP addresses are the same, the device is considered to be the

same. In this case, the device ID will be updated in the Device Manager.

• If the number matches one already, but the device ID differs, the Device Manager

compares the IP addresses of the Device Handlers and IP addresses of the DECT Masters

(if available). If the IP addresses are not the same, the device is considered to be another

one.

Figure 19. Two different handsets with same number and device type

logging in to the same Device Manager in an IP-DECT System.

In Figure 19, the handset (registered in System A) with number 100 and device type Device

A logs on to the Device Manager. The Device Manager register the IP address of the IP-DECT

Master (10.30.10.1) where the handset is registered. Additionally, the IP address of the

Device Handler (10.30.10.3) the IP-DECT Master is connected to is also registered (1).

Another handset (registered in System B) with the same number and device type wants to

log on to the Device Manager (2). In this case, the handset’s device ID (20) does not match

the already logged in handset’s device ID (10), and therefore the Device Manager compares

the IP addresses of the Device Handlers and also compares the IP addresses of the IP-DECT

Masters. The handset in System B uses another IP-DECT Master and Device Handler, and is

therefore considered to be another handset. The handset in System B will now be logged in

as another handset and the IP addresses of the Device Handler and the IP-DECT Master are

also registered in the Device Manager. The result is that two different handsets with same

number and device type are visible in the Device Manager.

Note that the Device Manager only is enabled on one Unite CM/IMS3. The Device Manager

communicates (3) with the Device Handlers.

IP-DECT Master 10.30.10.1

Device type: Device A

No.: 100

Device ID: 20

Device type: Device A

No.: 100

Device ID: 10

System A

IP-DECT Master 10.30.10.2

System B

(1)

Device Manager

Device Handler

10.30.10.3

Device Manager

(disabled)

Device Handler

10.30.10.4

Unite CM 10.30.10.4Unite CM 10.30.10.3

(2)

(3)(3)



Device Manager

Appendix C. Troubleshooting


Fault Probable cause Action or comment

Authentication methods

(e.g. EAP) using

certificates do not work

on a replacement i62

handset with same

number.

When replacing a i62

handset, only parameters are

transferred to the

replacement handset.

However, the Device Manager

faulty indicates that

certificates have been

transferred to the

replacement handset with

the same number.

1. Go to the Number tab.

2. Select the replacement

handset.

3. Select Number > Manage

Certificates.

4. Remove all certificates.

5. Import the certificates.

The certificates will be

downloaded to the

replacement handset when it

goes online.

It is not possible to edit

any parameters after

logging on to the system.

The user is logged on as

auditor.

Close the browser session

and re-login on as admin or

sysadmin.

The system does not have

the correct time.

– Configuration error, no time

server configured.

– The time server is

configured but is offline

– The web browser is

selected as time source but

the time has not been set by

the user.

Configure the system to

connect to a time server.

Restore connection to time

server.

Set the time via the advanced

configuration.



Device Manager


Device does not show up

in the Device Manager

-The connected interface (for

example DECT) is not up and

running

Check the status of the

interface. Starting up mode is

indicated during start of

applications. If an application

has lost connection to a

required resource it is

indicated as application

problem mode. An

Application problem is always

shown as a persistent fault in

the Status log in IMS3/Unite

CM.

NOTE: If the information on

the Configuration page

shows Normal mode, it is not

necessary to check the

System information.

1. Click “Configuration” on

the start page.

2. Select Other Settings >

Advanced Configuration in

the menu on the

Configuration page.

3. Click “Troubleshoot”

button on the Advanced

Configuration page.

4. Select “System

information” in the menu.

An advanced charger

does not come online in

the Device Manager in a

system with “Service

discovery” enabled.

– The charger parameters for

Service Discovery are not set.

– The service discovery

parameter “Domain Name” is

not unique in the IP network

domain.

– The advanced charger and

the Device Manager are

located in two separate IP

networks that prevents the

service discovery request.

Use PDM to set the

parameter in the charger and

in the Device Manager so that

they match.

Use PDM to reconfigure the

advanced charger. Make sure

that there is only one Device

Manager with the used

“Domain Name”.

Use PDM to disable service

discovery in the advanced

charger and to set the IP

Address to the Device

Manager.




Device Manager


• The charger logs out

immediately after login

and does not come online

again. The charger is

configured in another

Device Manager or in

PDM.

The charger is already saved

in the Device Manager that

the administrator wants it to

use. The Advanced Charger

parameter in the desired

Device Manager is pointing to

another Device Manager

(service discovery or IP

address) which causes the

charger to log out and

connect to another Device

Manager after completed

synchronisation.

– Before connecting the

advanced charger to the LAN,

make sure that if the

advanced charger is saved in

the desired Device Manager it

has parameters that points

to the correct Device

Manager.

– Delete the saved charger

from the Device Manager

before connecting the

charger to the LAN.

• Some devices report

device busy in the Device

Manager when the user is

trying to change device

parameters.

The device is occupied with

some action that the device

cannot combine with

parameter synchronisation.

No action needed. The Device

Manager will synchronize the

changes when possible.

• Not possible to start a

software download for

some specific device

types.

The device type is included in

a baseline and manual

software download is

therefore disabled.

– Disable the baseline

feature.

– Exclude the device type

from the baseline.

Software download is

stuck in pending.

– The device is not online.

Software download will start

when device gets online.

– Multiple devices are

currently being updated.

Connect the handset to the

Device Manager either via a

advanced charger or via a

DECT system supporting OTA.

There is a limitation in the

Device Manager on the

number of simultaneous

software downloads. All

devices are placed in a queue

and will be upgraded in time.

No action needed. Download

will start in time.

File downloads retrying. The device is currently

unavailable (device out of

range, network problem)

No action needed. The

download will start when the

device comes in range again.

Software downloads

rejected.

The device is already updated

with a new software but not

yet restarted on the new

software. This is due to

selected activation time in

previous software update i.e.

“When idle in charger” or

“After manual restart“.

Restart the device manually

and restart the download.




Device Manager


Software in Device Not

Recognized/

Synchronization Fails

The parameter definition file

is not compatible with the

device.

In the Devices tab, check the

parameter version for the

device. If the parameter

version is highlighted with

red, a package file (.pkg)

including the software file

and definition file with that

parameter version, must be

imported to the module. See

4.1 Import Software Files on

page 14.

Software downloads are

aborted.

Wrong file selected for

download to devices

(External web server).

– Make sure that the URL to

the desired software is

correct and retry.

– Make sure that the file is

intended for that device.

Low software download

performance to handset

inserted in charger.

The charger is not connected

to the Device Manager (not

online in the Device

Manager). The handset is

online only via OTA.

Configure the advanced

charger so that it connects

and logs on to the correct

Device Manager.

Communication failure to

device.

The device did not respond in

an expected way. The reason

could be temporary

communication problems

caused by coverage problems

or network problems.

Repeat the action after a

while to see if it is possible to

communicate with the

device.

No connection available

for the Device Manager

GUI.

– Max number of Device

Manager GUI’s has been

reached.

– The Device Manager server

side is restarted due to

reconfiguration.

– The Device Manager is

temporarily unavailable due

to restore of database.

– The network is preventing

the GUI from connecting to

the server.

Close the other Device

Manager GUI to open new. A

maximum of three Device

Manager GUIs can be

connected.

No Action, the server will be

up within a few minutes.

No Action, the server will be

up soon.

No action.

All devices log out after

restore of a backup.

The backup is older than the

device “online status report

timeout.”

No action. All devices will re-

login within “online status

report timeout.” (See device

handling).

Software files cannot be

deleted.

The files are included in a

baseline.

Remove the files from the

baseline configuration. Delete

the files.




Device Manager


The parameter version is

displayed in bright red in

the Device Manager GUI.

There are no compatible .pkg

files imported to the system.

Import a .pkg file suitable for

the device. The .pkg file is

provided by the supplier.

The parameter version is

displayed in dark red in

the Device Manager GUI.

The version of the

imported .pkg files are not

100% compatible with the

device.

Import a .pkg file suitable for

the device. The .pkg file is


The parameter version of

the Number in the

Numbers tab is higher

than in the parameter

version of the device in

the Devices tab.

The device has been

downgraded to a previous

software version with lower

parameter version.

No action needed. This is not

an error. The parameter

version will be the same after

a software upgrade has been

performed on device.

No numbers are visible of

the selected device type

in the Number tab.

The search field is red.

Current search returns no hit.

Alter search or use "show all"

to reset search to default.

"Go to device" is disabled

for a device in the device

view.

The selected device has no

number associated to it.

– Assign a new number to

the device.

– Associate a new or existing

number to the current device.

"Create QR code" is

disabled for a template.

– You have selected a

template for a device type

that does not support QR

codes.

– The parameter definition

the template is based on

does not support QR code.

–

– Create a template based on

a newer parameter definition.

The handset is not visible

in the Number tab.

– The handset has no number

associated.

– The device is offline and

not saved as number.

Assign or associate a number

to the device.

Bring the device online. Save

the number in order to make

it possible to edit the number

when it is offline.

Number creation of

desired device type is not

possible.

The .pkg file for the desired

device type is not imported

to the Device Manager.

Import the .pkg file for the

desired device type. The file is


It is not possible to apply

a template at creation of

new number.

No compatible template for

the desired device exists.

Create a new template or

upgrade an existing template

and retry.

A handset logs out when

placed in an advanced

charger

The device manager

configurations in the IPBS

and the advanced charger are

not the same.

Delete the saved instance of

the advanced charger in the

Device Manager. Use PDM to

reconfigure the advanced

charger so that it will log on

to the correct device

manager. Connect the

advanced charger to the LAN.




Device Manager


The DECT handset does

not log on to the device

manager OTA.

– The Domain ID is not set

correctly in the IP-DECT

system.

– The system does not

support service discovery.

Reconfigure it to match the

device manager Service

Discovery parameter Domain

ID.

Erase the Domain ID in the

IPBS and set the IP address to

the Device Manager under

Advanced Settings > Device

Management.

When trying to manage

the license for a device,

the status is changed to

“server failure”.

The firewall has closed port

number 443 for https

communication.

Reconfigure the firewall to

allow https communications

via port 443.

Active Faults in the IMS3/

Unite CM shows Device

Manager: Running-

application problem (Error

relay: Database init in

progress) is shown after

software upgrade of the

IMS3/Unite CM.

You have upgraded the Unite

CM/IMS3 to a software that

uses another database

structure for the Device

Manager than the previous

installed software version.

The IMS3/Unite CM needs to

re-configure the database

used by the Device Manager

after the upgrade.

The time it takes to re-

configure the database

depends on number

of parameters, devices,

phonebook entries, and

numbers saved in the

database.

NOTE: If you have many

devices, it can take several

hours to re-configure the

database.

Import Contacts from

Number fails (from d62 to

i62)

The Unite CM has been

upgraded from software

version 3.0.4 to 4.x or

greater, and the

configuration has been

restored after the upgrade.

The IMS3 has been upgraded

from software version 3.31

or greater, and the

configuration has been

restored after the upgrade.

The solution is to import

contacts from a d62 DECT

handset to an i62 VoWiFi

handset.

1) Re-import the package

files used for the d62 and i62

handsets. The versions of the

definition files included in the

package files must be the

same as the prior imported

files. See 4.1 Import Software

Files on page 14.

2) Import contacts from

number. See 7.2.1 Import

Contacts on page 26




Device Manager


It takes time to load a

Java application.

Additionally, “Running

this application may be a

security risk” appears

when running a Java

application.

The module is not connected

to Internet meaning that the

Ascom certificate, used to

sign the Java application,

cannot be verified.

If the module do not have a

connection to Internet, you

can disable the verification of

the certificate.

1. Open Java Control Panel in

Windows.

2. Click the “Advanced” tab.

3. Under Perform Certificate

revocation checks on”, click

“Do not check”.

“The connection to this

website is untrusted”

appears when open a Java

application.

An HTTPS connection is used

but, the certificate used to

identify that website is not

trusted.

Consult the IT department to

install a trusted certificate on

the computer(s) used to

access the Device Manager.

The Number is displayed

in dark red and the

following message is

shown: "This device's call

number has been

manually updated from

the device. Parameters

will be applied to the

device instead of the

number."

The extension number has

been manually changed in

the device via its Login menu.

No action is required because

it works as intended, but if

you want to apply parameter

settings for a specific Number

again, there is a workaround.

1. Delete subscription from

the handset (unsubscribe

system).

2. Unsubscribe the number

from the IP-DECT system

(done in the IP-DECT system).

3. Delete the number in

Device Manager.

4. Re-subscribe the handset

to IP-DECT system.

5. Log in the user on the

newly subscribed handset.

After login, the number

associated with user appears

in the handset. Additionally,

the number is shown in black

in Device Manager and

parameter settings will be

applied to the number

instead of device.

