0% found this document useful (0 votes)
394 views118 pages

Ascom Myco Smartphone CM 93072EN R

Uploaded by

dale.patrick
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
394 views118 pages

Ascom Myco Smartphone CM 93072EN R

Uploaded by

dale.patrick
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 118

CONFIGURATION MANUAL

Ascom Myco
CONFIGURATION MANUAL
Ascom Myco

Trademarks
Ascom Myco™ is a trademark of Ascom (Sweden) AB.

Android™, Google™, Google Play™ and other marks are trademarks of Google, LLC.

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

Abbreviations and Glossary


Abbreviations

1G, 2G, 3G, 4G Common naming of the generations of mobile communication evolution.

802.11a Standard for transmission rates up to 54 Mbps, operates in the 5 GHz


spectrum.

802.11b Standard for transmission rates up to 11 Mbps, operates in the 2.4 GHz
spectrum.

802.11d Standard for regulatory domains.

802.11e Standard that defines Quality of Service (QoS) for WLAN.

802.11g Standard for transmission rates up to 54 Mbps, operates in the 2.4 GHz
spectrum.

802.11i Standard for security improvements for 802.11.

802.11n Standard for transmission rates up to 100 Mbps, operates in the 2.4 GHz and 5
GHz bands.
802.1D IEEE MAC Bridges standard (interworking for 802.11 among others).

802.1X IEEE standard for port-based Network Access Control (authentication).

AC Authentication code. Configured on a DECT Base station and required for


subscribing a handset to a DECT system.

Ad-hoc WLAN A WLAN between two wireless capable devices (normally PCs), where no
Access Point (AP) is involved.

AES Advanced Encryption Standard

ALS Acoustic Location Signal


A loud audio signal used for localizing the handset.

AP Access Point
APN Access Point Name.
Base Station
Common name for IPBS, DECT Base Station (BS3x0) and TDM-DECT Base
Station.
BSS Basic Service Set
BSSID Basic Service Set Identifier
CCX Cisco Compatible Extension

Cellular GSM/3G.
DECT Digital Enhanced Cordless Telecommunications

Global standard for cordless telephony.

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

Unite Device Manager The Unite Device Manager (Unite DM) is a server-based application built into
the Unite Module. It is used for managing devices, such as editing parameters
and upgrading devices remotely in medium and large VoWiFi systems.

DHCP Dynamic Host Configuration Protocol


A protocol for automating the configuration of computers and handsets that
use TCP/IP.
DNS Domain Name Server
DSCP Differentiated Services Code Point

QoS on the Internet Layer used both for WLANs and LANs.

DTIM Delivery Traffic Indication Message

EAP Extensible Authentication Protocol


EAP-FAST EAP-Flexible Authentication via Secure Tunneling

EAP-TLS EAP-Transport Layer Security

ELISE Embedded Linux Server


ESS Extended Service Set

WLAN with multiple APs sharing the same SSID.

ESSID Extended Service Set Identifier

The identifying name of a WLAN. It identifies an AP and distinguishes WLANs


from one another. An ESSID is one type of SSID (BSSID is the other).

GMS Google Mobile Services

It is a suite of apps and services provided by Google, such as Google Play,


Gmail or Google Chrome.

GSM Global System for Mobile Communication (often called 2G).

IP Internet Protocol

Global standard that specifies the format of datagrams and the addressing
scheme. This is the principal communications protocol in the Internet Protocol
suite.
IPDI International Portable DAM (DECT Authentication Module) Identity. See IPEI for
more information.
IPEI International Portable Equipment Identity

IPEI/IPDI is needed to enable network subscription of the handset. At delivery


of the handset, IPEI and IPDI are the same and either can be used for network
subscription. If one handset is replaced with another using the Easy
replacement procedure the IPDI is exchanged and IPEI and IPDI are no longer
the same. If the IPEI and the IPDI differ, the IPDI is used for network
subscription.

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

IM Interactive Messaging

Makes it possible to access information from an application and control the


information by selecting an option received in a message.

LAN Local Area Network


License Authorization to upgrade the handset to another variant.

MAC Medium Access Control

In IEEE 802 LAN/MAN standards, the MAC sublayer is the layer that controls
the hardware responsible for interaction with the wired, optical, or wireless
transmission medium.
Micro-SIM A SIM card standard with a smaller form factor compared to a full-size SIM, or
a mini-SIM card.
NFC Near Field Communication

A set of communication protocols that enable two devices to establish


communication by bringing them within close proximity of each other.

NTP Network Time Protocol


OTA Over-the-Air
Overflow menu The overflow menu (or the options menu) is a menu that appears if additional
options are available. The menu allows for options beyond those included in
the regular user interface of the application. The overflow menu is typically
located in the top right-hand corner of the action tool bar. The menu is
represented by a stack of three squares.

PARK Portable Access Rights Key. Used for DECT system identification.

PBX Private Branch Exchange


A telephone system within an enterprise that switches calls between local
lines, and allows all users to share a certain number of external lines.
Also referred to as Call Manager.

PEAP Protected Extensible Authentication Protocol

A protocol that encapsulates the Extensible Authentication Protocol (EAP)


within an encrypted and authenticated Transport Layer Security (TLS) tunnel,
correcting deficiencies in EAP.

PRI Primary Rate Interfaces

PTT Push-To-Talk
PUN Physical Unit Number.

QoS Quality of Service

Defines to what extent transmission rates, error rates, and so on are


guaranteed in advance.

RSSI Received Signal Strength Indication

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

RTLS Real Time Locating System

RTS Request-To-Send

Shared Phone The shared phone feature enables a personal user number with associated
alerts, conversations and an optional SIP number for calling, regardless of
what handset is in use by that user.

SIM Subscriber Identity Module.

SIP Session Initiation Protocol

SIP is a signaling protocol used for initiating, maintaining, and terminating real-
time sessions that include voice, video, and messaging applications. SIP is
used for applications of Internet telephony for voice and video calls, in private
IP telephone systems, in instant messaging over IP networks, and in mobile
phones calling over LTE, Voice over LTE (VoLTE).

SSID Service Set Identifier


STA Station

Client in a Wi-Fi network.


Unite
Name of Ascom IP-based protocol for handling events, messages, and alarms.

Unite Admin A Windows-based application used for configuration and administration of


users, locations, integrations and applications in the Ascom Unite system.

Unite CS Unite Communication Server


A server that handles communication interfaces, message routing, activity
logging, and other essential messaging services. It is a software-only product
installed on a Linux server.
Unite CM Unite Connectivity Manager
A gateway that handles communication interfaces, message routing, activity
logging, and other essential messaging services. It is installed on ELISE3
hardware.
UP 6 User Priority 6

A user priority for wireless QoS at the MAC Layer. UP can take the values 0–7,
with 0 being the lowest and 7 the highest priority.

URI Uniform Resource Identifier.


URL Uniform Resource Locator
VoIP Voice over IP
VoWiFi Voice over WiFi

It is a system running VoIP over WLAN.

VoWLAN Voice over WLAN


Wi-Fi A family of radio technologies that is commonly used for implementing a
WLAN.
Used generically when referring to any type of IEEE 802.11 network.

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

WLAN Wireless Local Area Network

A type of LAN in which data is sent and received via high-frequency radio
waves rather than cables or wires. The most common radio technology used
for a WLAN is WiFi, implementing the IEEE 802.11 standards.

WMM WiFi MultiMedia


WPA/WPA2 WPA and WPA2 mixed mode

WPA/WPA2 mixed mode operation permits the coexistence of WPA and


WPA2 clients on a common SSID.

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

Contents
1 Introduction to Configuration Manual............................................................................................... 1
1.1 Caution and Notes ..............................................................................................................2
2 Pre-Installation...............................................................................................................................3
2.1 VoWiFi and DECT System IP Addresses ................................................................................3
2.2 Configure Access Point Names (APN)....................................................................................4
3 Installation of Handsets ................................................................................................................. 6
3.1 Setup Handsets in the Device Manager.................................................................................6
3.1.1 Device Manager Prerequisites ................................................................................7
3.1.2 Create a Network Template ....................................................................................7
3.1.3 Create a Common Template ...................................................................................8
3.1.4 Create Numbers and Apply the Network and Common Template ...............................9
3.2 Install and Configure Handsets ........................................................................................... 10
3.2.1 Easy Deployment................................................................................................. 10
3.2.2 QR Code Installation and NFC................................................................................ 11
3.2.3 Manual Installation ................................................................................................13
3.2.4 Subscribe Handset to DECT System .......................................................................13
3.2.5 Assign Number to Handset ....................................................................................14
3.2.6 Enable the Ascom Myco Launcher User Interface ....................................................14
3.2.7 Show Hidden Apps ...............................................................................................14
3.2.8 Configure the Handset ..........................................................................................14
3.2.9 Google® Mobile Services (GMS) Configuration 1 .......................................................14
3.2.10 Shared Phone...................................................................................................... 15
3.2.11 Central Phonebook .............................................................................................. 18
3.2.12 Company Phonebook........................................................................................... 18
3.2.13 Hunt Group Name................................................................................................ 18
3.3 Using Templates to Setup a Handset .................................................................................. 19
3.3.1 Save Handset Settings as a Template .................................................................... 19
3.3.2 Edit a Template or Check Template Settings .......................................................... 19
4 Maintenance and Management..................................................................................................... 21
4.1 Handset Management ....................................................................................................... 21
4.2 Handset Maintenance........................................................................................................ 21
4.2.1 Add Certificates to the Handset.............................................................................22
4.2.2 Remove Certificates from the Handset...................................................................22
4.2.3 Upgrade or Downgrade the Handset Software .......................................................22
4.2.4 Upgrade the Handset Functionality Using a License................................................23
4.2.5 Prepare a GMS Handset Version for a Factory Reset ..............................................25
4.2.6 Perform a Factory Reset .......................................................................................26
4.2.7 Encrypt Data on the Handset ................................................................................27
4.2.8 Replace Handsets................................................................................................27
4.2.9 Change Handset Number .....................................................................................28
4.2.10 Update Parameters ..............................................................................................29
4.3 Network Maintenance .......................................................................................................29
4.3.1 Perform a Security Upgrade..................................................................................29
4.3.2 Create a Configuration Backup .............................................................................30
5 Handset Configuration ................................................................................................................. 31
5.1 Admin Settings Menu in the Handset ..................................................................................32
5.1.1 Admin Settings ....................................................................................................32
5.1.2 Ascom Settings....................................................................................................32

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

5.2 Network ...........................................................................................................................32


5.2.1 Select a Wi-Fi Network for the Handset..................................................................33
5.2.2 Add a Wi-Fi Network Through the Device Manager .................................................33
5.2.3 Add a Hidden Wi-Fi Network Through the Handset .................................................35
5.2.4 Configure the Handset for Wi-Fi Networks .............................................................36
5.2.5 Preferred Mobile Network Type ............................................................................39
5.2.6 Access Point Names ............................................................................................39
5.2.7 Enable Cellular Data (Caution)...............................................................................40
5.3 DECT Subscriptions............................................................................................................41
5.3.1 Access DECT Subscriptions Menu ..........................................................................41
5.3.2 Switch on the DECT Chipset ..................................................................................41
5.3.3 Add a New Subscription ........................................................................................41
5.3.4 Add a Subscription Using Easy Registration ...........................................................42
5.3.5 Edit a DECT Subscription ......................................................................................42
5.3.6 Select a DECT Subscription ..................................................................................43
5.3.7 Unsubscribe from a DECT System .........................................................................43
5.3.8 Log In to an Extension Number .............................................................................43
5.3.9 Log Out from an Extension Number .......................................................................44
5.4 Ascom Messaging .............................................................................................................44
5.4.1 Advanced security ...............................................................................................45
5.5 Services ...........................................................................................................................46
5.5.1 Add New Service .................................................................................................46
5.6 Alarm- and Multi-Function Button........................................................................................48
5.6.1 Set the Long Press or Multi-Press Actions ..............................................................49
5.6.2 Automatic Call after Alarm ....................................................................................49
5.6.3 Use Top Button for Third Party Apps......................................................................49
5.6.4 Man-Down & No-Movement Alarm........................................................................ 50
5.7 Location Services ............................................................................................................. 50
5.7.1 Basic Location ..................................................................................................... 51
5.7.2 Configure Ascom IR Location ...............................................................................52
5.7.3 Configure the Handset for a Cisco/Ekahau RTLS Solution ........................................53
5.7.4 DECT Base Station Positioning..............................................................................53
5.8 NFC .................................................................................................................................54
5.9 Third-Party Integration .......................................................................................................54
5.10 App Customization ............................................................................................................54
5.10.1 Visibility ..............................................................................................................54
5.10.2 Show Notification on Top Display ..........................................................................55
5.10.3 Google Mobile Services (GMS) Customization ........................................................55
5.11 Shortcut Customization......................................................................................................55
5.11.1 Shortcut Name ....................................................................................................55
5.11.2 Order..................................................................................................................56
5.11.3 Shortcut Type......................................................................................................56
5.11.4 Shortcut Component Name ..................................................................................56
5.11.5 Shortcut Service Name.........................................................................................56
5.12 Troubleshooting................................................................................................................57
5.13 Display .............................................................................................................................57
5.13.1 Font Size.............................................................................................................57
5.13.2 Owner ID/Name...................................................................................................57
5.13.3 Sleep Timeout .....................................................................................................57
5.13.4 Rotate Top Display...............................................................................................58
5.13.5 Top Display Alert Formatting.................................................................................58

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

5.13.6 Charging Screen..................................................................................................58


5.14 Sound ..............................................................................................................................59
5.14.1 Ringtones............................................................................................................59
5.14.2 Dialing Tone Patterns ...........................................................................................59
5.14.3 Notification Sound ...............................................................................................59
5.14.4 Vibrate When Ringing ..........................................................................................59
5.14.5 Dial Pad Touch Tones ..........................................................................................59
5.14.6 Touch Sound.......................................................................................................59
5.14.7 Screen Lock Sound ..............................................................................................59
5.14.8 Hearing Aid Compatibility .................................................................................... 60
5.14.9 Start-Up Connection Failure Sound....................................................................... 60
5.14.10 Vibrate for Incoming Message During Call............................................................. 60
5.14.11 Minimum Volume ................................................................................................ 60
5.14.12 Message Volume ................................................................................................. 61
5.15 Languages ....................................................................................................................... 61
5.16 Date and Time .................................................................................................................. 61
5.17 Security............................................................................................................................62
5.17.1 Admin Password..................................................................................................62
5.17.2 Make Passwords Visible .......................................................................................62
5.17.3 Password Policy...................................................................................................62
5.17.4 Disable Camera ...................................................................................................64
5.17.5 Screen Lock Type ................................................................................................64
5.17.6 Automatic Lock Time............................................................................................65
5.17.7 Power Button Instantly Locks ................................................................................66
5.17.8 Notifications on Lock Screen................................................................................66
5.18 Telephony ........................................................................................................................66
5.18.1 Emergency Numbers for Device Without SIM .........................................................66
5.18.2 Power Button Ends Call ........................................................................................67
5.18.3 Default Call Priority ..............................................................................................67
5.18.4 Default Call Carrier...............................................................................................67
5.18.5 Call Setup Notification Type..................................................................................67
5.18.6 Ascom VoIP.........................................................................................................68
5.18.7 Microphone Gain ..................................................................................................71
5.18.8 Voicemail .............................................................................................................71
5.19 Push-To-Talk ....................................................................................................................72
5.19.1 Use Alarm & Multi-Function Button ........................................................................72
5.19.2 Configure a PTT Group Call ..................................................................................72
5.20 DECT Suppl. Services ....................................................................................................... 73
5.20.1 DECT Supplementary Services in Device Manager ................................................. 73
5.20.2 DECT Supplementary Services on the Handset ...................................................... 74
5.21 DECT Frequency .............................................................................................................. 74
5.22 In Charger ........................................................................................................................75
5.22.1 Mute When Docked .............................................................................................75
5.22.2 Clear Messages When Docked .............................................................................75
5.22.3 Clear Images When Docked..................................................................................75
5.22.4 Unite Logout User When Docked ..........................................................................76
5.22.5 Send Status When Docked ...................................................................................76
5.23 Site Survey Tool for DECT ..................................................................................................76
5.24 Unite Login .......................................................................................................................76
5.24.1 Phone Mode........................................................................................................76
5.24.2 Number of Recent Users ...................................................................................... 77

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco

5.24.3 Days to Remember Recent Users .......................................................................... 77


5.24.4 Enable User Availability Status .............................................................................. 77
5.24.5 Login Reminder ................................................................................................... 77
5.24.6 Credentials Type ................................................................................................. 78
6 Related Documents......................................................................................................................79
7 Document History ...................................................................................................................... 80
Appendix A Easy Deployment..........................................................................................................88
A.1 Prerequisites ....................................................................................................................88
A.2 WLAN Discovery ...............................................................................................................89
A.3 Unite CM/Unite CS Server Discovery.................................................................................. 90
A.4 Parameter Download......................................................................................................... 91
A.5 Using Easy Deployment Together with Client Certificate Distribution ..................................... 91
A.6 Ports .............................................................................................................................. 102
A.7 Alert Categories .............................................................................................................. 103

TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Introduction to Configuration Manual Ascom Myco

1 Introduction to Configuration Manual


This document describes features and settings for the following handset versions of the Ascom Myco
Smartphone:
• Ascom Myco 2 Wi-Fi and DECT (GMS or non-GMS)
• Ascom Myco 2 Wi-Fi and Cellular (GMS or non-GMS)
• Ascom Myco Wi-Fi
• Ascom Myco Wi-Fi and Cellular
The Myco is referred to as the "handset" in the manual, and especially marked with "Ascom Myco 2 only",
"GMS version only", "Wi-Fi only", "DECT only", or "Cellular only", whenever the functionality differs between
handset versions.

The Wi-Fi and DECT version of the handset enables voice communication in different kinds of wireless
systems:
• Voice over Wi-Fi (VoWiFi)
• Digital Enhanced Cordless Telecommunications (DECT)
The Ascom Voice over Wi-Fi (VoWiFi) system provides wireless IP-telephony, messaging, and alarm
functions to enterprise LANs. Using third-party WLAN products, hardware and software developed in-house,
the system enables data and voice transmission together with seamless roaming.

Figure 1. The Ascom Myco in a Wi-Fi System

The Digital Enhanced Cordless Telecommunications (DECT) system provides wireless DECT telephony.
Using Ascom DECT base stations, WLAN products, hardware and software developed in-house, the system
enables alarms, messaging and voice transmission together with seamless roaming.

If the handset is used in DECT environment, the Wi-Fi connection is still required for updating parameter
definitions and for data transmission, for example, IM images, WiFi certificates, firmware upgrades, company
phonebook, and applications.

The handset can operate either in the VoWifi mode or in the DECT mode. If the DECT chip is
switched on, it is not possible to make VoIP calls.

1 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Introduction to Configuration Manual

Figure 2. The Ascom Myco in a DECT System

This document provides guidelines on how to install and configure handsets in an Ascom Myco system. The
document describes the settings needed to make the handset function in a Wi-Fi, DECT or Cellular system,
and is targeted at the following personnel:
• System Administrator
• Service Technician
The handset is first configured using Easy Deployment or other installation methods. The Device Manager
application in the Unite Connectivity Manager/Unite Communication Server (Unite CM/Unite CS) supports
managing the handsets centrally using a web interface, without the need to collect the handsets. The Unite
Admin (on a server, or as a Desktop/Laptop installation running on Windows, database portable between
clients) is needed for license management, user management, and static integration configuration.

The handset behavior can be customized to suit each user profile. It is recommended that the reader has
basic knowledge of the Ascom VoWiFi or DECT system, basic knowledge of handset registration in the PBX,
and also cellular and Android functionality.

1.1 Caution and Notes


Please read and adhere to all of the cautions listed throughout this manual.

Warning

Is provided to outline items that if not followed, may result in death or serious injury to the
patient or damage to the equipment.

Caution
Is provided to alert the user that special care should be taken for the safe and effective use of
the handset.

Is provided when additional general information is available.

TD 93072EN / 08 October 2020 / Ver. R 2


CONFIGURATION MANUAL
Pre-Installation Ascom Myco

2 Pre-Installation
The tasks in this chapter are mainly applicable in VoWiFi systems. Some tasks may also be
applicable in a Cellular system or in a DECT system only.

Before installing handsets in a VoWiFi system, make sure to prepare with these steps:
• Set up chargers and charge the handset batteries before the installation starts.
• Have a number plan available for the handsets.
• Check that the IP addressing plan is set up to support the amount of handsets to be deployed.
It is assumed that some, or all, of the following components (depending on system configuration) are
available:
• DECT base stations (for using the handset in DECT environment). These are the devices that provide
radio coverage on the location and DECT wireless handset registration on the PBX.
• DHCP Server. A DHCP server allows devices to request and obtain an IP address from a server that has
a list of addresses available for assignment. If the WLAN does not have access to a DHCP server, a list of
static IP addresses is necessary.
• Unite CM/Unite CS. The Unite CM/Unite CS handles all communication between the handsets and its
built-in Device Manager. Before installing the handset, make sure the Unite CM/Unite CS IP address is
available.
• Unite Admin (either the desktop version (Unite Admin Desktop), or the server based version (Unite AM).
• VoIP Gateway. This is the gateway for ISDN Primary Rate Interfaces (PRI) in the Ascom VoWiFi and DECT.
It serves as a link between traditional telephony and VoWiFi or DECT telephony.
For efficient administration of a VoWiFi system with several handsets, the use of the Device Manager
included in the Unite CM/Unite CS is strongly recommended.

Also refer to the following sections when:


• Handling many different IP addresses, see 2.1 VoWiFi and DECT System IP Addresses, page 3.
• Configuring Access Point Names (APN) for a cellular handset, see 2.2 Configure Access Point Names
(APN), page 4.

2.1 VoWiFi and DECT System IP Addresses


If the handset is used in DECT environment, without access to a Wi-Fi network, no information about system
IP addresses is necessary. In this case, operations that require data transmission such as remote firmware
upgrade, application installation, sending images will not be available on the handset.

To configure the handsets, enter the IP addresses in the table below:

Device IP Address/Number/Port Required

VoIP Gateway 1 If used

IP-PBX If used
Subnet Mask 2 If used
Unite CM/Unite CS (incl. Number Yes
plan)

NTP Server address3

3 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Pre-Installation

DNS Server address 4


VoIP settings 5 Yes (for VoWiFi only)

Central Phonebook If used


Syslog server If used

DHCP range

Unite Admin Desktop Yes

Unite AM server 6 Yes


APN 7
1. The VoIP Gateway is not needed if an IP-PBX is used.
2. Only required if no DHCP is used, that is, static IP is used.
3. Depending on system configuration.
4. Only required if no DHCP is used, that is, static IP is used.
5. Gatekeeper IP address or SIP proxy IP address used to access the PBX.
6. Only required if no Unite Admin Desktop is used. Refer to the Unite AM documentation for other requirements than the IP
address.
7. Only required for Cellular variant. Configure for new, and not pre-configured operator only.

The Unite CM/Unite CS can be used to set up personal login accounts to the Device Manager. The
Unite CM/Unite CS is also used to manage advanced messaging.

The Unite Admin is used to map the users to the handsets.

2.2 Configure Access Point Names (APN)

Only required for the Cellular variant, and if mobile data is desired

The Access Point Names (APN) are pre-configured, and usually not needed to be changed. Only when
changing the Micro-SIM card to a new operator, and when the operator is not shown in the pre-configured
APN list, perform as follows:

Data must be enabled.

Recommended settings: Preferred network type: 3G, Data roaming: OFF.

Device Manager
1. Select Network → Mobile networks → Access Point Names.
2. Right click Access Point Names, and then click Add entry.
3. Click the APN entry.
4. Set the applicable parameters.

Handset Admin Menu


1. For access information, see 5.1 Admin Settings Menu in the Handset, page 32.
2. Select More (under WIRELESS & NETWORKS). The Wireless & networks menu opens.
3. Select Cellular networks → Network operators. The Mobile network settings menu opens.

TD 93072EN / 08 October 2020 / Ver. R 4


CONFIGURATION MANUAL
Pre-Installation Ascom Myco

4. Select the desired operator.


5. If the desired operator is missing in the list, go back to the Cellular networks setting menu, and select
Access Point Names. Tap to open the Edit access point menu. Enter the settings for the APN.

5 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Installation of Handsets

3 Installation of Handsets
This chapter describes how to install and setup handsets. The recommended way to setup and configure
handsets is through the Device Manager included in Unite CM/Unite CS. The handsets can be installed
using different methods, depending on how the system is configured.
A handset can be used without a Unite CM/Unite CS, but only with limited functionality. Unite CM/
Unite CS is required for features such as alert and message handling, and the Ascom Myco
Launcher handset interface. Refer to 3.2.3 Manual Installation, page 13. For details on how to setup
a handset without using the Device Manager in Unite CM/Unite CS.

Installation Steps
The following steps are common for all installation methods when using Unite CM/Unite CS. These steps
doesn't necessarily have to be performed in the order described here.
1. Create templates in the Device Manager application in Unite CM/Unite CS, one with network settings
and another with common settings, see 3.1.2 Create a Network Template, page 7 and 3.1.3 Create a
Common Template, page 8.
2. Create Numbers and apply the templates, see 3.1.4 Create Numbers and Apply the Network and
Common Template, page 9. If used, apply the application certificate(s), see 4.2.1 Add Certificates to the
Handset, page 22.

Distinguish between trusted server (root) certificates, and application certificates.

3. If used, prepare and store certificates for authentication/encryption (to the WLAN) individually in the
Device Manager for each handset.
4. Start one of the three installation processes described in 3.2 Install and Configure Handsets, page 10.
5. After connecting to the Unite CM/Unite CS, assign a number to the handset, see 3.2.5 Assign Number
to Handset, page 14.
6. Enable the Ascom Myco Launcher on the handsets (if not automatically enabled during the installation
process), see 3.2.6 Enable the Ascom Myco Launcher User Interface, page 14.
7. For DECT only. Subscribe handsets to the DECT system manually or use the Easy registration feature,
see 3.2.4 Subscribe Handset to DECT System, page 13.

3.1 Setup Handsets in the Device Manager


Follow the steps in this section to setup handsets in a Unite CM/Unite CS through the Device Manager. The
steps doesn't necessary have to be performed in the order written here, and can be done after the handset
installation steps in 3.2 Install and Configure Handsets, page 10.

If the handset is used without a Unite CM/Unite CS, follow the applicable steps in 3.2.3 Manual
Installation, page 13 instead.

TD 93072EN / 08 October 2020 / Ver. R 6


CONFIGURATION MANUAL
Installation of Handsets Ascom Myco

Figure 3. Handset configuration using the Device Manager in Unite CM/Unite CS.

IP AP W i-FiAccess Point

Device Manager C lient


in Unite CM

3.1.1 Device Manager Prerequisites


The prerequisites for using the Device Manager in Unite CM/Unite CS to setup handsets are:
• The handset has a functional WLAN/3G association.
• The Unite CM/Unite CS is updated to support the Unite Admin Desktop (or Unite AM server):
− A websocket category for the Ascom Myco device type exists in the Unite CM/Unite CS (Configura-
tion → Messaging → Categories → Category Description: Websocket Messaging Interface, Service:
WS).
Even if the handset is operating in DECT mode, the WS option must be selected to enable
messaging.

− The device type "Myco" is created.


• The handset users are mapped in the Unite Admin Desktop (or Unite AM server):
− The Device type: Ascom Myco exists in the Unite Admin Desktop (or Unite AM server) (Devices &
Numbers → Device type → Add the device "Myco").
− The Unite CM/Unite CS is added in the Unite Admin Desktop (or Unite AM server) (Module address →
Password → Add).
− The users are added in the Unite Admin Desktop (or Unite AM server) (Users → Add user → Enter User
Name & No).
• The handset has the correct settings (configured in the Unite Admin Desktop (or Unite AM server)) to
access the Device Manager:
− A configured number to be used as an identity to log in to the Unite system.

If a configured number is missing, the handset will still be logged in as a "device".

− The network address (IP address or host name) of the Unite CM/Unite CS.

3.1.2 Create a Network Template


Refer to 3.3 Using Templates to Setup a Handset, page 19 for further details on how to work with templates.

Create one template that contains the network parameters (including the security settings). If desired,
additional parameters can be set, for example VoIP settings, and the IP address to the Unite CM/Unite CS. It

7 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Installation of Handsets

is also recommended to enable the Ascom Myco Launcher parameter in this template, see 3.2.6 Enable the
Ascom Myco Launcher User Interface, page 14.
Installing a trusted server and/or application certificate cannot be done using a template, but must
be done separately for each handset. Refer to 4.2.1 Add Certificates to the Handset, page 22.

The template must be created, and applied, to prevent the Unite CM/Unite CS from restoring the
parameters to default during the first synchronization.
1. Open a web browser and enter the IP address to the Unite CM/Unite CS (or the NetBIOS name "elise-
xxxxxxxx" if the port is open in the Unite CM/Unite CS).
2. Click on Device Manager. You may be prompted to log on to the Device Manager.
3. Select the Templates tab, right-click, and select New. The New template window is opened.
4. In the Device type drop-down list, select Ascom Myco.
5. In the Name field, enter a descriptive name for the template.
6. Click OK.
7. Set the following network parameters:
Only select the parameters that are to be modified. If all parameters are selected, the system
performance decreases.

− Network settings 2 (Network → Wi-Fi).


− VoIP settings 3 (Telephony → Ascom VoIP).
− Syslog settings 4 (if any) (Troubleshooting → Syslog).
− Unite settings5 (Ascom Messaging).
− Ascom Myco Launcher 6 (Ascom Messaging).
− DECT parameters 7 (DECT Suppl. services).
The IP-address to the Unite CM/Unite CS (Device Manager) in the template (Ascom
Messaging > Unite interface address), can either be set, or left blank, in which case the
server discovery process is used at every startup, see A.3 Unite CM/Unite CS Server
Discovery, page 90.
− Click OK to save the template.

3.1.3 Create a Common Template


Create another template with the common handset settings applicable to all handsets (exclude the
parameters and security settings configured in the Network template).

This template can, for example, contain hidden menu items in the display, sound volumes, and in charger
functionality.

2. All required system settings for the WLAN. For example SSID and Security mode. If using a security mode that requires
certificates, also use an NTP server, to assure the correct time in the handset, as certificates only are valid within a certain time.
3. For example VoIP protocol (SIP), or SIP proxy IP address used to access the PBX.
4. The parameter "Enable syslog" must be enabled in order to set the "Syslog IP address".
5. IP address and password (if any) to the Unite CM/Unite CS.
6. Enable the use of the Ascom Myco Launcher user interface on the handset.
7. For DECT version only. For DECT version only. See DECT Suppl. Services.

TD 93072EN / 08 October 2020 / Ver. R 8


CONFIGURATION MANUAL
Installation of Handsets Ascom Myco

The parameters that are not part of the template are left unchanged on the handset.

1. Open a web browser and enter the IP address to the Unite CM/Unite CS (or the NetBIOS name "elise-
xxxxxxxx" if the port is open in the Unite CM/Unite CS).
2. Click Device Manager.
3. Select the Templates tab, right-click, and select New.
4. In the Device type drop-down list, select Ascom Myco.
5. In the Name field, enter a descriptive name for the template.
The parameter version of an installed handset is visible under the Numbers tab or the Devices tab.
6. Set the specific parameters.
Select the check box of each parameter that you want to be part of this template, and enter the proper
value.
Only select the parameters that are to be modified. The number of parameters the template
contains affects the time it takes to apply it to the handsets.

See also section 3.3 Using Templates to Setup a Handset, page 19.

3.1.4 Create Numbers and Apply the Network and Common Template
Create a range of numbers, and apply the network template, and the common template, that were created
previously the Device Manager application in the Unite CM/Unite CS.

Caution
Avoid to add numbers for handsets that are already configured and functional. These
handsets already exist in the system, although not saved in the Device Manager, and this
overwrites the existing parameter settings of the handsets!

Create Number
1. Open a web browser and enter the address to the Unite CM/Unite CS.
2. Click Device Manager.
3. Select the Numbers tab, right-click, and select New. The New numbers window opens.
4. In the Device type drop-down list, select Ascom Myco.
5. In the Prefix field, enter the numbers' prefix (if needed).
6. Create a range of numbers by selecting the Range option. Enter the start call number, and the end call
number in the fields, respectively. Click OK.

The maximum range that can be added at a time are 100 numbers.

Apply Template
1. In the Numbers tab, select the handset(s) you want to apply the template to.
2. Right-click and select Apply template.
3. Select the network template you want to apply, and click OK. The applied template is shown in the Last
run template column (rightmost in the Numbers tab).

9 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Installation of Handsets

The number of parameters the template contains, affects the time it takes to apply it to
handsets.

4. Verify the handset selection made in step 1 of Apply Template, page 9. Then right-click again and
select Apply template.
5. Select the common template you want to apply, and click OK. The applied template is shown in the
Last run template column (rightmost in the Numbers tab). (It overwrites the previously applied network
template name).
If the 802.1x security protocol with EAP-TLS or EAP-PEAP/MSCHAPv2 is used, also include the
server certificate, and select which application certificate to use. The application certificates
must be installed first by editing each Number. Application certificates cannot be distributed
using a template, as they are individual. Refer to 4.2.1 Add Certificates to the Handset, page
22.
A template can also be applied on several handsets simultaneously (of the same device type) using the
Baseline function. Refer to the Configuration Manual, Unite Communication Server, TD 92761EN and
Configuration Manual, Unite Connectivity Manager, TD 92735EN.

3.2 Install and Configure Handsets


The handsets can be installed through one of the following methods:
• Easy Deployment
− With the Easy Deployment method, the handset is automatically installed in the Unite CM/Unite CS
using a staging WLAN (AWS-INIT). The handset automatically connects to this staging WLAN the first
time it starts up. This is the recommended method to use for handset installation, especially when a
large number of handsets are installed.
− Refer to 3.2.1 Easy Deployment, page 10.
• QR code installation and NFC
− The handset can be installed in the Unite CM/Unite CS by scanning a QR code that provides the
necessary parameters. Use this method if the AWS-INIT staging WLAN is unavailable.
− Refer to 3.2.2 QR Code Installation and NFC, page 11.
• Manual installation
− The slowest and least efficient installation method is manual installation through the handset settings
menu. Use this method if the other two methods are unavailable, or if the handset are used without a
Unite CM/Unite CS.
− Refer to 3.2.3 Manual Installation, page 13.

Unite CM/Unite CS is required for handset features such as alert and message handling, and
the Ascom Myco Launcher interface.

3.2.1 Easy Deployment

Use this procedure if the handset is required to use a certificate to access the WLAN.

Easy Deployment is the recommended procedure of using the Central Device Management/Server
(Unite CM/Unite CS) for deployment and configuration of WLAN and Unite parameters. The requested

TD 93072EN / 08 October 2020 / Ver. R 10


CONFIGURATION MANUAL
Installation of Handsets Ascom Myco

WLAN parameters and the Unite system information is distributed automatically to the handset, using a
DHCP server (and optionally using the Ascom Service Discovery Protocol).

With Easy Deployment, it is very important that the building of the number plan and the parameters
are correct.

Handsets are automatically installed by Easy Deployment, if the following is fulfilled:


• The LAN and VoWiFi system is configured for Easy Deployment, see Appendix A Easy Deployment, page
88.
• The handset is not associated to any network (SSID).
• The Call ID (endpoint number), that is, the phone number of the handset is decided.
If the WLAN system uses a 802.1x security protocol that requires certificates for authentication/
encryption to the WLAN, the certificates must be prepared and stored individually in the Device
Manager for each number, before starting Easy Deployment, see 4.2.1 Add Certificates to the
Handset, page 22.

Easy Deployment does not automatically provide the handset with a DECT subscription. If the handset
operates in DECT environment, subscribe the handset to the DECT system manually or use the DECT Easy
Registration feature. See 3.2.4 Subscribe Handset to DECT System, page 13.

3.2.2 QR Code Installation and NFC


Quick installation and setup can be done by scanning a QR code, if Easy Deployment is unavailable. The
Setup QR code is created through the Device Manager and should contain all the parameters necessary to
install the handset in the system.

NFC can be used to share scanned deployment data with other Ascom Myco 2 GMS handsets. In this way it
is possible to avoid using the Android Setup Wizard for initial setup of the GMS for each handset. Note that
a Google Play account, if wanted, needs to be added manually.

Create a Setup QR Code


1. Create a template in the Device Manager with only the most necessary parameter settings (for example
the Network and Ascom Messaging settings), refer to 3.1.2 Create a Network Template, page 7.
2. Right click the template and choose Create QR code.
The QR code can be scanned directly from the screen. To print the QR code, click the Copy to
clipboard button, and paste it into a graphics editor or word processor.

Scan the QR Code with an Ascom Myco Handset


1. Locate the Setup app on the handset, and tap to open it.
2. Turn the handset horizontally and position the handset so that the QR code fits within the scanning
window in the center of the screen.

11 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Installation of Handsets

3. If the scan is successful the Setup app closes automatically and the text Deployment data applied
successfully appears on screen.

Scan the QR Code with an Ascom Myco 2 Handset


1. Locate the Setup app on the handset, and tap to open it.
2. Turn the handset horizontally and position the handset so that the QR code fits within the scanning
window in the center of the screen.
3. Choose between tapping on:
− Use for this device to use the scanned deployment data to set up the handset. If the deployment is
successful the Setup app closes automatically and the text "Deployment successful" appears on the
screen.
− Share code to share the scanned deployment data with other GMS handset versions by using NFC.
Instructions for sharing code appear on the screen, see Figure 4. Instructions for sharing code by
using NFC, page 12. If the deployment is successful on the handset getting the shared deployment
data, the text "Deployment successful" appears on the screen of that handset.

Figure 4. Instructions for sharing code by using NFC

Step 1 Step 2 Step 3

If you attempt to scan a QR code right after the boot of a factory reset handset (instead of waiting
a suggested two minute period), the device may fail to perform its Wi-Fi authentication and the
handset may become blacklisted in the Access Point. This is not due to a synchronization failure,
since data will still be synchronized with the handset. The issue, sometimes indicated with the text
"Some of the applications doesn't respond in time", can be resolved with a handset restart and
another reading of the QR code about two minutes after device boot.

To make a DECT handset fully operational by scanning a QR code, ensure that it includes the setting for
enabling the DECT chipset and that the Easy registration feature is enabled on the DECT system. If these
conditions are not met, subscribe the handset to the DECT system manually. See 3.2.4 Subscribe Handset
to DECT System, page 13.

TD 93072EN / 08 October 2020 / Ver. R 12


CONFIGURATION MANUAL
Installation of Handsets Ascom Myco

3.2.3 Manual Installation


You can setup a handset using the standard Android settings in the Admin settings view in the handset.
Use this installation method if one of the following is true:
• All other installation methods are unavailable.
• No Unite CM/Unite CS is used in the system.

Unite CM/Unite CS is required for features such as alert and message handling, and the Ascom
Myco Launcher handset interface.

The installation procedures described in this section does not provide the handset with a DECT subscrip-
tion. If the handset operates in DECT environment, subscribe the handset to the DECT system manually or
use the DECT Easy Registration feature. See 3.2.4 Subscribe Handset to DECT System, page 13.

In a System with a Unite CM/Unite CS


To install the handset manually in a Unite CM/Unite CS, do the following:
1. In the Settings app on the handset App view, tap Admin settings, and enter the admin password
(default "40022").
2. Set the following parameters:
− Network settings 8 (WIRELESS & NETWORKS).
− VoIP settings 9 (Ascom settings → Telephony → Ascom VoIP)
− Unite settings 10 (Ascom settings → Ascom Messaging)
TIP: If certificates are required to connect to the WLAN, they can be imported directly to the handset
using an USB cable, refer to 4.2.1 Add Certificates to the Handset, page 22.
3. Open the Device Manager and follow the steps in 3.1 Setup Handsets in the Device Manager, page 6.
4. Assign a number to the handset, see 3.2.5 Assign Number to Handset, page 14.

Without Unite CM/Unite CS


Without a Unite CM/Unite CS all parameters has to be set manually in the Admin settings menu on the
handset.
1. In the Settings app on the handset App view, tap Admin settings, and enter the admin password
(default "40022").
2. Set all applicable parameters in the Admin settings and Ascom settings menus (refer to5 Handset
Configuration, page 31).

The Ascom Myco Launcher user interface cannot be enabled without a Unite CM/Unite CS.

3.2.4 Subscribe Handset to DECT System


To use the handset in DECT environment, subscribe it to a DECT system in one of the following ways:
• Manually using the DECT system PARK and access code.
• Automatically using the Easy Registration feature.
Refer 5.3 DECT Subscriptions, page 41 for details.

8. All required system settings for the WLAN, for example SSID and Security mode.
9. VoIP protocol (SIP), or SIP proxy IP address used to access the PBX.
10. IP address and password (if any) to the Unite CM/Unite CS.

13 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Installation of Handsets

3.2.5 Assign Number to Handset


The handset can be assigned a number in two different ways, either through the Device Manager or directly
through the Ascom Myco launcher user interface. Make sure the number is ready and configured in the
Unite CM/Unite CS before assigning it to a handset, see 3.1.4 Create Numbers and Apply the Network and
Common Template, page 9.

Assign a Number Through the Device Manager


In the Device Manager, do one of the following:
• On the Devices tab, right click on the handset and choose Assign number.
• On the Numbers tab, right click on the number and choose Associate with device.

Directly Through the Handset


When a handset without number starts up with the Ascom Myco launcher enabled, the user will be
prompted to setup a number for the handset. Enter a number to assign it to the handset.

The handset must be connected to a Unite CM/Unite CS when assigning it a number.

3.2.6 Enable the Ascom Myco Launcher User Interface


The Ascom Myco Launcher parameter must be enabled on the handset to replace the default Android
launcher with the customized Ascom user interface. The Ascom user interface is required to use the alert,
alarm, conversation, and services functionality on the handset. When the Ascom Myco Launcher is enabled,
access to the Android settings is protected by an admin password. It is recommended to enable this
parameter in the templates used in Easy Deployment/QR Code Installation to automatically enable the
Ascom Myco Launcher directly during the handset installation. Refer to 5.4 Ascom Messaging, page 44 for
instructions on how to enable the Ascom Myco Launcher parameter for the handset.
The Ascom Myco Launcher User Interface must be enabled before installing certificates on the
handset.

3.2.7 Show Hidden Apps


In the handset, there are apps that are shown by default, and also apps that are hidden by default. The
hidden apps can be made visible through the device manager. Refer to 5.10 App Customization, page 54
for instructions on how to show hidden apps.

3.2.8 Configure the Handset


The handset can be configured either through the Device Manager or directly through the Ascom settings
menu on the handset. Some parameters can only be set through the Device Manager. Refer to 5 Handset
Configuration, page 31 for details.

3.2.9 Google® Mobile Services (GMS) Configuration 11


Google Mobile Services (GMS) is a suite of apps and services provided by Google. Without a Google Play
account, Google apps are only updated along with Myco firmware updates. Updating Google apps is not

11. Only available for Ascom Myco 2, Google version.

TD 93072EN / 08 October 2020 / Ver. R 14


CONFIGURATION MANUAL
Installation of Handsets Ascom Myco

possible from the Ascom Device Manager. With a Google Play ™. Account, Google apps are updated
automatically on the handset.

Google stipulates that the initial setup of the GMS is carried out on each individual handset, using the
Android Setup Wizard (SUW). The setup process includes the following steps:
• Language selection: Select the default language to be used on the handset.
• Wi-Fi network selection: Select the Wi-Fi network that the handset should connect to. Once the Wi-Fi
network has been selected, and the password for it has been entered, the handset will verify the
connection and search for any Google related updates.
• Add personal Google account: The user is given the option to add a Google account to the handset by
entering email/phone number and a password for that account. There is also an option to create a new
Google account directly on the phone. Adding a Google account is optional and can be skipped by
clicking on SKIP. 12
• Enter name of the handset user: By entering the first and last name of the user, the handset is able to
personalize some apps.
• Option to enable screen lock: If the user clicks on NEXT, a pop-up will warn the user of the dangers of
not activating a screen lock. The options available in response to this message are DON’T SKIP and
SKIP ANYWAY.
The final part of the SUW involves setting up Google Services with the following options/check boxes:
• Use Google's location service - Helps apps determine location. Sends anonymous location data to
Google even when no apps are running.
• Help improve location services - Scans for Wi-Fi networks even when Wi-Fi is off.
• Help improve your Android experience - Diagnostics and usage data is sent to Google.
To avoid using the SUW for initial setup of the GMS for each handset, a quick installation for
several handsets can be done by using QR codes and NFC, refer to3.2.2 QR Code Installation and
NFC, page 11. Note that if a Google Play account is wanted, this must be added manually.

3.2.10 Shared Phone


The shared phone feature enables a personal user number with associated alerts, conversations and an
optional SIP number for calling, regardless of what handset is in use by that user. The feature promotes
privacy since alerts, conversations and call logs are automatically purged when a new user logs into the
handset. Any handset that is configured as a shared phone, can be used by any user with a personal login
in the system, thereby facilitating the management of handsets.

Alerts, conversations and call logs are personal for each user. They are not synced between handsets, but
they are purged when a new user logs in. Nothing else is included in the personal login (i.e. not settings,
personal contacts, apps etc).
Non-shared user login requires the following setting in the UCx: Require user login = Yes. User
login on shared phones does not require this setting to be set to Yes.

Prerequisites
To set up a handset as a shared phone, Unite CS, version 1.3.1 or later, is required. In addition, the handset
needs to be configured in Unite AM. The configuration is the same as for a non-shared handset with the

12. Optional

15 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Installation of Handsets

exception that the SIP credentials can be used if the user is to have a personal SIP phone number or the
Shared — Device ext. mode is selected. 13

Set up a Shared Phone in the Device Manager


1. Open the Device Manager in the Unite CM/Unite CS.
2. On the Numbers tab, select the handset you want to set up as a shared phone.
3. Right-click and select Edit Parameters.
4. Navigate to Login → Phone mode and select one of the following options:
− Shared — Personal ext. The dial number is associated with a particular user. The user logs in to a
shared phone and can be called by the user’s personal extension number.
− Shared — Device ext. The dial number is associated with a particular device based on the SIP
credentials configured on the handset. The user logs in to a shared phone and can be called by the
extension number configured for the current device.
Select the Personal / Temporary option to switch the handset to the non–shared mode.

5. For the Shared — Device ext. option, complete the Messaging ID field with the identification number
to associate the device with a messaging number. The value must match the one configured in the
Unite Admin application for the profile that will be used for the current shared device.
6. Click OK.
The handset will then disappear temporarily from the Device Manager while the new settings are
implemented. Once the handset shows up in the Device Manager again, it will display shared as the
Number for the handset.
All handsets that are configured as shared phones will display the value shared in the Number
column in the Device Manager. To locate a specific handset, use the Device ID. On the handset,
the Device ID can be found under Settings → About phone: Wi-Fi.

Enable Badge Login to a Shared Phone


Badge login is an additional login method based on the NFC technology and is used to simplify login to a
Ascom Myco 2 shared handset. If this method is available and configured in the system, the user can log in
to the handset using their badge card and the personal PIN code. When the user is logged in and the
handset is locked, the personal PIN is used to unlock the handset.

The badge login feature requirements:


• Ascom Myco 2 is configured in the shared phone mode.
• Ascom Myco 2 hardware capabilities include the NFC support.
The badge login feature should be used for logging in to a shared phone. Badge login to a
personal handset is not supported.

1. Open the Device Manager in the Unite CM/Unite CS.


2. Navigate to NFC and enable the NFC support. Refer to 5.8 NFC, page 54.
3. On the Numbers tab, select the handset configured as a shared phone.
4. Right-click and select Edit Parameters.

13. The SIP Endpoint ID and SIP password are limited to a total length each of fifty unicode characters.

TD 93072EN / 08 October 2020 / Ver. R 16


CONFIGURATION MANUAL
Installation of Handsets Ascom Myco

5. Navigate to Login → User login → Additional login methods and do one of the following:
− Select NFC only to enable login using a badge card.
− Select None to disable additional login methods. The user will have to manually enter their login
credentials.
6. Navigate to Login → User login → Lock screen with personal PIN and do one of the following:
− Select Yes if after successful login the user must use their personal PIN to unlock the locked
handset. This option is recommended to prevent unauthorized access to the handset.
− Select No if after successful login the user can swipe the screen to unlock the locked handset.
7. Navigate to Login → User login → Allow user to add empty card and do one of the following:
− Select Yes to enable the user to assign a badge to the user account so that the user can log in to
the Myco handset using their badge.
− Select No if only the administrator can assign a badge to a user account to enable badge login.
8. Navigate to Login → User login → Allow user to log in without PIN and do one of the following:
− Select Yes to enable the user to log in to the Myco handset using their badge without entering their
PIN.
Caution
Allowing this option may result in a hazardous situation where an unauthorized person
that gets hold of a badge and a Myco may accept alerts without acting properly, thus
potentially impacting patient safety.

− Select No if the user must enter their PIN when they log in to the Myco handset using their badge.
9. Navigate to Security → Screen Lock Type and select PIN or Password for secure access to the handset.
This setting enables the badge login lock screen. Refer to 5.17.5 Screen Lock Type, page 64.

Set up SIP Calling as Fallback without Requiring a Login


In the Device Manager (Telephony → Ascom VoIP), there is no need to set the Endpoint ID and password if
personal SIP calling is enabled, since that will change depending on the user that is logged into the handset.
However, if it is to be possible to use the handset for calling, even though no user is logged in, the Endpoint
ID and the password needs to be set in the Device Manager. This will provide a fall-back if no user is logged
in (this also allows for emergency calling). If a user logs in, however, the manually entered Endpoint ID and
password will be overruled by the configuration set in Unite AM for that user id.

Set up Shared Phone on the Handset


• On the handset, go to Settings → Admin settings → Login → Phone mode.
• Select the value Shared to set up the handset as a shared phone.

Setup Shared Phone after a Factory Reset


After doing a factory reset, the handset will display a shared phone start screen. On this screen, the user of
the handset can check the box Shared Device, after which, the handset can be used by several users, each
with their own personal user id. The shared phone start screen is only displayed if the handset has not
already been configured for shared (or personal / temporary) use in the Device Manager.

17 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Installation of Handsets

Purge of User Information at Login


The login procedure for a shared handset is the same as when performing a regular user login. When a new
user logs in, alerts, conversations and call logs are automatically purged from the handset 14.

3.2.11 Central Phonebook

This is a system dependent feature.

If the network is equipped with a messaging server with a phonebook service, the Central Phonebook on
that server can be accessed from the handset. For information of configuration of the Central Phonebook,
see the Configuration Manual, Unite Connectivity Manager, TD 92735EN and Configuration Manual, Unite
Communication Server, TD 92761EN.

3.2.12 Company Phonebook


It is possible to create a Company Phonebook that is administered centrally and uploaded to the handset
from the Device Manager. If this feature is used, entries from Contacts and Company Phonebook are
merged. The Company Phonebook entries are locked and cannot be edited in the handset.

Perform the following steps:


1. Create a company phonebook file, see Create a Company Phonebook File , page 18.
2. Import the company phonebook file to Device Manager, see User Manual, Device Manager,
TD 92855EN.
3. Upload the company phonebook file to the handset, see User Manual, Device Manager, TD 92855EN.
If a new company phonebook file is created and added to a handset, the old company phonebook
is removed meaning that the previous company phonebook entries on the handset are deleted.

Create a Company Phonebook File


The company phonebook file (.cpb) is normally created from an Excel file using a script to extract the
information and create the phonebook file (.cpb). The Excel file, “Company Phonebook.xls“, is delivered
from your supplier.

The following characters are accepted in the handset number field in the phonebook file, but are ignored
when the phonebook file is created: “(“, “)“, “-“ and “ “ (space).
To keep compatibility with other handsets supporting the company phonebook feature, such as
the Ascom i62 VoWiFi handset and the Ascom d63 DECT handset, it is recommended to have a
maximum length of 24 characters in each field of the company phonebook file.

3.2.13 Hunt Group Name


Ascom Myco users can identify an incoming hunt call by the hunt group name displayed on the handset.
The feature does not require any specific setup in Ascom environment but it should be configured on the
PBX. The PBX must support the SIP Diversion Indication standard.

14. If the same user logs in on the same handset again, for instance after replacing the battery on the handset, the data is kept on
the handset.

TD 93072EN / 08 October 2020 / Ver. R 18


CONFIGURATION MANUAL
Installation of Handsets Ascom Myco

If a hunt call is transferred, the number of the call originator is shown instead of the hunt group
name.

3.3 Using Templates to Setup a Handset


It's possible to select a handset in the Device Manager, and directly change one, or several, configuration
parameters, and by using a template, the same configuration can easily be applied to many handsets
simultaneously. Templates are also an efficient way to control the changes applied to each handset.

Templates enable configuration of all aspects of a handset, from ringtones, to in charger functionality.

Please find all details of Templates in the User Manual, Device Manager, TD 92855EN.

3.3.1 Save Handset Settings as a Template


Parameter settings of a single handset can be saved as a template. Either to be used as a backup for
restoring the configuration of the handset at a later stage, or to apply the same settings to a number of
handsets.
Only configuration data is saved. Certificates and other personal data is excluded.

1. Open the Device Manager in the Unite CM/Unite CS.


2. On the Numbers tab, select the handset you want to save as a template.
3. Right-click and select Use as template. Enter a descriptive template name. The Edit template window
opens.
4. Edit the template parameters as follows:

The number of parameters the template contains affects the time it takes to apply it to the
handsets.

For a Handset Backup


By default, all parameters are selected, and saved when clicking OK. If desired, exclude parameters by
clearing the check box next to the parameters.

For Use on Other handsets


If this template is to be applied to other handsets, exclude the following user specific parameters by
clearing the check box next to the parameter:
− Owner ID/name (Display) - a text string displayed in the charging screen to identify the handset.
− Endpoint ID (Telephony → Ascom VoIP) - the phone number/name of the user registered in the SIP
PBX.
If changed from default values, you might want to exclude other user parameters like font size, sleep
time-out (under Display), or language (under Languages). Then these parameters are restored to
default values in the template.
5. Click OK.

3.3.2 Edit a Template or Check Template Settings


To add, or remove one or more parameters in an existing template, do as described below. This is a way to
see the set template parameters. They are shown in the color magenta.

19 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Installation of Handsets

1. Open the Device Manager in the Unite CM/Unite CS.


2. On the Templates tab, select the template to edit.
3. Right-click and select Edit.
4. Edit the parameter(s), then click OK to save the changes. Click Cancel if you just wanted to check the
parameters.

TD 93072EN / 08 October 2020 / Ver. R 20


CONFIGURATION MANUAL
Maintenance and Management Ascom Myco

4 Maintenance and Management


This chapter describes how to manage and maintain handsets in a system. For details on the configuration
settings available for the handsets, refer to 5 Handset Configuration, page 31.

This chapter includes the following topics:


• 4.1 Handset Management, page 21
• 4.2 Handset Maintenance, page 21
• 4.3 Network Maintenance, page 29

4.1 Handset Management


Two types of handset management can be used, centralized management and local management.
Centralized management is the recommended method to setup and configure a larger number of handsets
in a system.

Centralized Management (Over-the-Air)


With centralized management handsets are managed over-the-air (OTA) using the Device Manager
application in the Unite CM/Unite CS. The Device Manager can install, upgrade, and configure a large
amount of handsets simultaneously. Parameter changes are updated OTA over Wi-Fi/3G. As the configura-
tion is OTA, there is no need to collect handsets to configure them.

To initially get centralized management to work, the Unite CM/Unite CS network address (the IP address, or
the host name) must be configured in the handset. This can be done either automatically through Easy
Deployment, QR Code Installation, or manually through the handset's Admin settings view. Refer to 3
Installation of Handsets, page 6.

Use templates when configuring handsets. The same configuration can the easily be applied simultaneously
to a large number of other handsets. Refer to 3.3 Using Templates to Setup a Handset, page 19.

Local Management

As local management requires physical access to all handsets, it is not recommended as the main
configuration method.

Local management, using handset display menus (Admin and Ascom settings) can be used to configure the
handsets if a quick change of a parameter value is needed, for example in a lab environment or during a
test installation. Refer to 3.2.3 Manual Installation, page 13.

4.2 Handset Maintenance


In an existing Wi-Fi or DECT system, it is important to be able to replace handsets, install new handsets, and
exchange faulty handsets when needed.

The recommended procedure is to use a template with basic network settings for log in, and then import
the rest of the settings by the common template(s) made in Device Manager in Unite CM/Unite CS (refer to
3.1 Setup Handsets in the Device Manager, page 6 for detailed instructions).

It is also important to be able to upgrade system parameters and security settings in the handsets.

21 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Maintenance and Management

4.2.1 Add Certificates to the Handset


If certificates are required to connect to the WLAN, they must be added to the handset, either through the
Device Manager, or by using a USB cable. Certificates cannot be added using a template. The Ascom Myco
Launcher User Interface must be enabled before installing certificates on the handset.
The following certificate formats are supported: .cer, .der, .crt, .pem, .p12, and .pfx. When possible,
always use the Device Manager to transfer certificates to the handset. Certificates added or
removed through the handset might not synchronize correctly with the Device Manager.

Transfer Using the Device Manager


1. On the Devices tab, right-click the handset and select Manage certificates.
2. On the Trust list tab, or on the Application certificates tab, click Browse and select the certificate to
import.
3. Click Yes to confirm the certificate. The certificate is added to the Manage certificates list, and can be
removed with the Remove button.

Transfer Using a USB Cable

Transfer with a USB cable is only recommended for handsets that hasn't yet been connected to a
Unite CM/Unite CS.

1. Connect the handset to a PC with a USB cable.


2. Copy the certificate from the PC to a suitable folder on the handset's internal storage.
3. On the handset, go to Admin settings → Security. Tap Install from SD card.
4. Browse to the folder the certificate was copied to, and tap the certificate. A window called Name the
certificate is shown.
5. Enter a name for the certificate in the Certificate name field.
6. In the Credential use drop-down list, choose Wi-Fi.
7. Tap the OK button to install the certificate on the handset.
8. To verify the certificate, check the Trusted credentials menu, see View Certificates on the Handset,
page 22.

View Certificates on the Handset


Certificates used on the handset can be viewed from the Admin settings → Security → Trusted credentials
menu. Note that even if a certificate is disabled from this menu, it remains in the system and will still be
used for the handset. Always use the Device Manager to remove certificates from the handset, refer to
4.2.2 Remove Certificates from the Handset, page 22.

4.2.2 Remove Certificates from the Handset


Use the Device Manager to remove certificates from the handset.
1. On the Devices tab, right-click the handset and select Manage certificates.
2. On the Trust list tab, or on the Application certificates tab, click Remove to remove a certificate.

4.2.3 Upgrade or Downgrade the Handset Software


The handset software is upgraded through the Unite CM/Unite CS Device Manager. It is possible to
downgrade a handset to an older version, however, this may cause interoperability issues.

TD 93072EN / 08 October 2020 / Ver. R 22


CONFIGURATION MANUAL
Maintenance and Management Ascom Myco

Firmware version 14.X.X and later supports migration between Ascom Myco 2 GMS and non-GMS versions.

Caution
All handset data including user data is permanently deleted and cannot be recovered in case
of software downgrade or migration between GMS and non-GMS versions. The handset is not
operational during this process: no messages, alarms, or calls are available.

A software file can be imported directly to the Device Manager, or be accessed from an external web server.

By Importing a Software File


1. Open the Device Manager in the Unite CM/Unite CS.
2. On the Devices tab, select the handsets to be upgraded.
3. Right-click and select Upgrade software.
4. In the Available software drop-down list, select the desired software file (.bin).
If needed, click Import to import the software file. Locate the software file (.pkg), and click Open.
5. In the Upgrade and Activate new software sections, select when to upgrade and activate the software.
6. Click OK.
For software downgrade or migration between GMS and non-GMS versions, the handset shows the
Android maintenance screen and requires pressing the Volume down button to confirm a factory reset.
This will delete all data from the handset and start the migration process. If no button is pressed or any
other button is pressed, the migration or downgrade is cancelled, and the handset restarts with the
current firmware version, configuration, and user data.
TIP: Several handsets (of the same device type) can be upgraded simultaneously using the Baseline
function. Refer to the Configuration Manual, Unite Connectivity Manager, TD 92735EN and Configuration
Manual, Unite Communication Server, TD 92761EN.

Through an External URL

A web server is needed.

For a quick upgrade of the handset software using an external URL, do the following:
1. Store the .pkg file on a desired location on the web server, and copy the URL.
2. Open the Device Manager in the Unite CM/Unite CS.
3. On the Devices tab, select the handsets to be upgraded.
4. Right-click and select Upgrade software.
5. Select the Enter URL: radio button and paste the URL.
6. In the Upgrade and Activate new software sections, select when to upgrade and activate the software.
7. Click OK.

4.2.4 Upgrade the Handset Functionality Using a License


A license move, from one handset to another, requires internet access from the Unite CM/Unite CS
server. A handset can be re-licensed up to 99 times.

23 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Maintenance and Management

It is recommended that you read the Function Description, Product Licensing Overview before reading this
section. You learn how to view current license(s), purchase license(s), and the technical solution of the
upgrading alternatives described below.

Users can upgrade a handset by downloading a license.

The following license is available:


• Barcode scanning license
There are three alternatives to upgrade a handset:
• Automatic upgrade, see Automatic License Upgrade, page 24.
• License upgrade using import/export, see License Upgrade Using Import/Export, page 24.
• Manual upgrade, see Manual License Upgrade, page 25.

Automatic License Upgrade


Use this option if the Unite CM/Unite CS has an internet connection to the License Server.
1. Open the Device Manager.
The first time the handset logs on to the Unite CM/Unite CS, the license key is automatically
downloaded to the handset, go to step 3).
2. If the handset is logged on to the Unite CM/Unite CS after the first time, no automatic check for
licenses is done. Synchronize the Unite CM/Unite CS and license server as follows:
− Select the Licences tab.
− Right-click the handset in the list.
− Select Refresh.
The license key is downloaded to the handset.
3. The handset restarts. See also 4.2.4 Upgrade the Handset Functionality Using a License, page 23 to
view the handset's license option(s).

License Upgrade Using Import/Export


Use this option if the Unite CM/Unite CS has no internet connection to the License Server. A product
information file (.XML) must first be exported from the Unite CM/Unite CS, and then imported to the License
Web.
1. Open the Device Manager:
− Select the Licences tab.
− Right-click the handset(s) in the list.
− Select Export.
− Save the file on a computer with an internet connection to access the License Web later on.
2. In a web browser, enter the address to the License Web: https://www.ascom-ws.com/licenses
The License Web is used for:
− Importing the product information file
− Viewing/Purchasing the license(s) for the handset(s)
− Downloading the license file containing the license key(s) for the handset(s)
See the online help on the License Web or Function Description, Product Licensing Overview for
information on how to use the License Web.
3. When the license file (.XML) containing the license key(s) is downloaded from the License Web, select
File → Import → Licences in the Unite CM/Unite CS to import the file.

TD 93072EN / 08 October 2020 / Ver. R 24


CONFIGURATION MANUAL
Maintenance and Management Ascom Myco

4. When the file is imported, the license key(s) is downloaded to the handset(s), and the handset restarts.
See also 4.2.4 Upgrade the Handset Functionality Using a License, page 23 to view the handset's
license option(s).

Manual License Upgrade


Use this option if the serial numbers of the handset cannot be exported to a file. The serial number(s) must
be manually entered in the License Web to get the corresponding license key for the handset. The license
key must also be manually entered in the handset. See the online help on the License Web, or the Function
Description Licensing Overview for information on how to get a license key.

If several handsets are upgraded, it is recommended to use License Upgrade Using Import/Export, page 24.

The license key is added using the Admin settings view in the handset, see 5.1 Admin Settings Menu in the
Handset, page 32 for information on how to activate the Admin settings view.
1. Tap the Settings app on the handset.
2. Select Admin settings, and enter the admin password if required (default "40022").
3. Select Ascom settings.
4. Select Enter license key.
5. Enter the license key without blanks.
6. Tap Done.
If the license key is valid, the License key accepted dialog window is shown, and the handset restarts.

Move License
It is possible to move a license to an unlicensed handset. Any optional licenses follow. For example, a
barcode scanner license can be moved from a handset with a broken display to an unlicensed handset. The
broken handset can then be sent for repairs.

An internet connection to the license server is needed.

To move a license using the Device Manager application:


1. On the Licenses tab, select the licensed handset (must be online).
2. On the License menu, click Move license.
3. In the Move license dialog window, select the unlicensed handset and click OK.
Both handsets are restarted.
4. If the unlicensed handset is currently shut down:
− Switch on the handset.
− On the Licenses tab, select the handset.
− In the License menu, click Refresh.
− The handset is restarted.

4.2.5 Prepare a GMS Handset Version for a Factory Reset

Only applicable to the Ascom Myco 2, GMS handset version.

25 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Maintenance and Management

To avoid any issues with Android Factory Reset Protection (FRP), please follow the instructions below. Once
the Factory Reset Protection has been removed, it is possible to perform a factory reset of the handset.

Check If Android Factory Reset Protection Is Turned On


Check if any Google accounts have been registered on the handset by looking under Settings → Admin
Settings → Accounts → Google Account. Then go into Settings → Admin Settings → Security → Screen Lock
and verify if screen lock is enabled. If there is a Google account associated with the handset, and the
screen lock is also activated, then the handset has Factory Reset Protection turned on.

Turn Off Factory Reset Protection


Remove Google Account
1. Go into Settings → Admin Settings → Accounts → Google Account.
2. Tap on the Google account that you wish to remove.
3. Tap on the overflow menu at the top-right of the screen.
4. Select Remove account and confirm by tapping on the button Remove account in the dialogue window
that opens.
Repeat the procedure for any additional accounts on the handset.

Turn off Screen Lock


1. Go into Settings → Admin Settings → Security.
2. Tap on the entry Clear Credentials and confirm by tapping on OK in the dialogue window that opens 15.
3. Tap on Screen lock (under Settings → Admin Settings → Security).
4. Tap on None and confirm by tapping on OK in the dialogue window that opens.
5. Enter the admin password when prompted to do so.
Once both the Google account(s) is removed and the screen lock is disabled, it is possible to do a factory
reset of the handset.

4.2.6 Perform a Factory Reset


When a handset factory reset is performed, all handset configuration parameter settings are restored to
default values. For example the PBX subscriptions, contacts, messages, downloaded language, apps, and
certificates are removed. The software and licenses are left intact.

If the handset has been saved in a Unite CM/Unite CS, the saved parameters are reapplied to the factory
reset handset when connecting to the Unite CM/Unite CS.

Factory Reset Using the Device Manager (Unite CM/Unite CS)


1. Open the Device Manager in the Unite CM/Unite CS.
2. On the Devices tab, select the handset to be factory reset.
3. In the Device menu, select Factory reset. Alternatively, right-click the handset and select Factory reset.
4. In the Reset devices window, click Yes. The handset restarts, and is remotely reset to factory settings.

15. Please note that this will also delete all stored credentials that are used to access the Wi-Fi networks that are set up on the
handset.

TD 93072EN / 08 October 2020 / Ver. R 26


CONFIGURATION MANUAL
Maintenance and Management Ascom Myco

Factory Reset Using the Handset


It's possible to factory reset a handset using the standard Android settings as follows:
1. Open the Settings app, and select Admin settings.
2. Select Backup & reset (under PERSONAL). The Backup & reset menu opens.
3. Select Factory data reset.

4.2.7 Encrypt Data on the Handset


The accounts, settings, downloaded apps and their data, media, and other files stored on the handset can
be encrypted. If the handset is encrypted, the user needs to type in a PIN or password every time the
handset is powered on.

The handset can only be decrypted by performing a factory reset.

1. Open the Settings app, and select Admin settings.


2. Select Security (under PERSONAL). The Security menu opens.
3. Select Encrypt phone, and tap the Encrypt phone button to start the encryption process.

Caution
Encrypting a handset usually takes an hour or more. The handset must have a fully charged
battery, and stay connected to a charger until the encryption process is complete. If the
encryption process is interrupted, some or all of the data on the handset will be lost.

Encryption will delay the startup of the handset with several minutes.

4.2.8 Replace Handsets


A faulty handset can be replaced with a new handset. The handset registered in Unite CM/Unite CS, is
associated with its device type, device ID, and extension number. During the replacement procedure, the
faulty handset's device type and extension number are associated with the new handset's device ID.

Data Included in a replacement transfer


All user parameters are replaced.

Data excluded in a Replacement Transfer


The following is not replaced:
• Contacts (entered by the user)
• Call list
• Messages
• Downloaded languages
• Certificates

27 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Maintenance and Management

Prerequisite
The network template must be applied to the new handset(s), including the IP-address to the Unite CM/
Unite CS. See 3.1.2 Create a Network Template, page 7.

To transfer the last stored settings in the Unite CM/Unite CS from the faulty handset to the new handset, do
the following:
1. If the faulty handset is online in the Device Manager, switch off the handset to make it offline.
2. Take a new handset prepared with the network settings (including the IP-address to the Unite CM/
Unite CS).
3. Enter the number and leave the password blank. Press Login.
The new handset is automatically updated from the Unite CM/Unite CS, and might restart depending on the
parameter settings.

Replace and Move Licenses

1. Make sure that the faulty handset is saved in the Device Manager (indicated by a check mark in the
Saved column). If the handset is not saved, right-click on the broken handset in the Numbers tab, and
select Save.
2. Switch the faulty handset off. The handset appears as offline in the Device Manager.
3. Take an unlicensed new handset prepared with the network settings (including the IP-address to the
Unite CM/Unite CS).
4. Enter the number and leave the password blank. Press Login. The handset is now online in the Device
Manager.

5. Make sure that the new handset is saved in the Device Manager (indicated by a in the Saved
column. If the handset is not saved, right-click on the new handset in the Numbers tab, and select Save.
6. Switch the new handset off. The handset appears as offline in the Device Manager.
7. Switch the faulty handset on. The handset appears as online in the Device Manager.
8. In the Device Manager, select the Licenses tab.
9. Right-click on the faulty handset, and select Move license.
10. In the Move license window, select the handset that should receive the license. Click OK.
11. The faulty handset restarts. Switch the faulty handset off. The handset appears as offline in the Device
Manager.
12. Switch the new handset on. The handset appears as online in the Device Manager.
13. In the Device Manager, select the Licenses tab. Right-click on the new handset, and select Refresh.
The new handset is automatically updated from the Unite CM/Unite CS and restarted. The last stored
settings and licenses for the faulty handset in the Unite CM/Unite CS are transferred to the new handset.
In DECT environment, the old handset must be logged out from the extension number. If it is not
possible to log out from the handset menu, it can be done on the DECT system.

After the old handset is logged out, the new handset must be subscribed to the DECT system and
logged in the extension number.

4.2.9 Change Handset Number


The handset number can be changed, while still keeping all the other settings in the handset:
1. Open the Device Manager.

TD 93072EN / 08 October 2020 / Ver. R 28


CONFIGURATION MANUAL
Maintenance and Management Ascom Myco

2. On the Numbers tab, select the handset to be updated with a new number.
3. In the Number menu, select Rename, or right-click the handset and select Rename.
4. If a new prefix is needed, enter the new prefix in the New prefix: field.
5. Enter the new number in the New number: field
Important

Make sure that the new number does not exist in another system. If several handsets
have the same number, their settings overwrite each other when synchronizing with
Unite CM/Unite CS

6. Click OK. The new number is synchronized with the handset when connected OTA to Unite CM/
Unite CS.

4.2.10 Update Parameters


This is the general procedure to change, or update parameters using the Unite CM/Unite CS. The update
starts when the handset is idle, and does not interrupt an ongoing call

Only select the parameters that are changed, if all parameters are selected, the system
performance decreases.

1. Open the Device Manager.


2. Create a new template with only the parameters to be changed.
3. Select the numbers that should be updated and apply the template.
The handsets are automatically updated from the Unite CM/Unite CS.

4.3 Network Maintenance


4.3.1 Perform a Security Upgrade
An upgrade, or change of the WLAN password/authentication using the Unite CM/Unite CS is performed as
follows:
Important

Change the handset settings before changing the AP settings. Else, synchronization of new
settings with existing handset settings, cannot be performed.

TIP: Leave one AP with the old configuration to allow switched off handsets to receive the updates when
they are turned on. Bring the handset to that APs coverage area.
1. Open the Device Manager.
2. Create a new template with the new security settings.
− Security mode 16
3. Apply the new template to the handsets.

At this time, the handsets have no access to the WLAN system.

4. The handsets are automatically updated from the Unite CM/Unite CS and restarted.

16. All required settings for the WLAN. For example User name, Password, Regulatory domain etc.

29 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Maintenance and Management

The handsets are now able to access the WLAN.

4.3.2 Create a Configuration Backup


It is recommended to have a backup of the handset configurations, and of the site.

Data Included in a Configuration Backup


The following is included in a configuration backup:
1. Handset parameters
2. Numbers (that are saved in the Device Manager)

Data Excluded in a Configuration Backup


The following is excluded in a configuration backup:
• Apps
• Software
A detailed description of the configuration backup procedure can be found in the User Manual, Device
Manager, TD 92855EN.

TD 93072EN / 08 October 2020 / Ver. R 30


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

5 Handset Configuration
The handset requires some settings to function in the Wi-Fi or DECT system. Most of the parameters can be
configured using either the Device Manager application in the Unite CM/Unite CS, or directly from the
Ascom settings menu in the handset. Specific Android related settings can only be configured through the
Android Admin settings in the handset (see 5.1.1 Admin Settings, page 32).

This chapter describes available settings for the handset. First handset specific menus, then network and
handset settings. All settings described can be configured through the Device Manager or the Ascom
settings menu in the handset, if not stated otherwise.

For more information about each parameter, use the Online Help available in the Device Manager. Click the
question mark icons located on the right side of the parameters in the Edit parameters view.
The locations or parameter names used in the Device Manager/Ascom settings menu may differ
slightly depending on the handset software version.

TIP: All settings starting with an asterisk in the Device Manager/Ascom settings menu, for example
*Ringtones, can also be set by the handset user directly from the basic settings menu in the handset. Refer
to the User Manual, Ascom Myco Smartphone for information about the basic settings menu.

This chapter includes the following sections:


• 5.1 Admin Settings Menu in the Handset, page 32
• 5.2 Network, page 32
• 5.3 DECT Subscriptions, page 41
• 5.4 Ascom Messaging, page 44
• 5.5 Services, page 46
• 5.6 Alarm- and Multi-Function Button, page 48
• 5.7 Location Services, page 50
• 5.8 NFC, page 54
• 5.9 Third-Party Integration, page 54
• 5.10 App Customization, page 54
• 5.11 Shortcut Customization, page 55
• 5.12 Troubleshooting, page 57
• 5.13 Display, page 57
• 5.14 Sound, page 59
• 5.15 Languages, page 61
• 5.16 Date and Time, page 61
• 5.17 Security, page 62
• 5.18 Telephony, page 66
• 5.19 Push-To-Talk, page 72
• 5.20 DECT Suppl. Services, page 73
• 5.21 DECT Frequency, page 74
• 5.22 In Charger, page 75
• 5.23 Site Survey Tool for DECT, page 76

31 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

• 5.24 Unite Login, page 76

5.1 Admin Settings Menu in the Handset


In addition to the settings the user can change, the handset has a hidden Admin settings menu for system
administrators that contains both Android and Ascom settings. This menu usually requires a password to
access (the default password is "40022").

The Admin settings menu contains the following two sections:


• The Android settings section with standard Android parameters (5.1.1 Admin Settings, page 32).
• The Ascom settings section with most of the parameters that can be set through the Device Manager
(5.1.1 Admin Settings, page 32).
To enter the Admin settings menu:
1. On the App view, tap the Settings app.
2. Tap Admin settings.
3. Enter a password if required (default "40022").

5.1.1 Admin Settings


The Android settings section contain standard Android parameters used to configure the handset look and
behavior. Many of these parameters cannot be configured from the Device Manager.

In addition to the look and behavior settings, the following are also accessed through the Admin settings
menu:
• Wi-Fi/Network - 5.2 Network, page 32.
• Factory reset - 4.2.6 Perform a Factory Reset, page 26.
• Encrypt phone - 4.2.7 Encrypt Data on the Handset, page 27.
• Site survey - Refer to the Troubleshooting Guide, Ascom Myco Smartphone, TD 93128EN.

5.1.2 Ascom Settings


The Ascom settings menu contains most of the parameters that can be set through the Device Manager,
with some differences described below.

On the Admin settings menu, tap Ascom settings to enter the Ascom settings menu.

The following settings differ between the Ascom settings menu and the Device Manager:
• Network parameters are set in the Admin settings menu, see 5.1.1 Admin Settings, page 32.
• Enter license key - License keys are added through the Ascom settings menu, see 4.2.4 Upgrade the
Handset Functionality Using a License, page 23.
• Diagnostics - A menu with different diagnostic tests that can be used to test the handset hardware, refer
to the Troubleshooting Guide, Ascom Myco Smartphone, TD 93128EN.
• About phone - Information about the handset hardware and software, can also be reached through the
Basic settings menu.

5.2 Network
The Wi-Fi/mobile network connections are configured through the Network menu in the Device Manager, or
the Android admin settings menu in the handset (5.1.1 Admin Settings, page 32).

TD 93072EN / 08 October 2020 / Ver. R 32


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

TIP: When installing a handset in the Wi-Fi network for the first time, the automatic Wi-Fi network selection
setting (default) also supports the Easy Deployment handset installation process (where a staging WLAN
with a predefined SSID and security profile automatically is used). Refer to Appendix A Easy Deployment,
page 88 for details about Easy Deployment.

5.2.1 Select a Wi-Fi Network for the Handset


Wi-Fi networks can be selected manually fro the handset Android admin menu.

To connect to a Wi-Fi network using the handset:


1. In the WIRELESS & NETWORKS section of the Android admin menu, tap Wi-Fi.
2. Select a Wi-Fi network in the list to connect to.
TIP: Networks using hidden SSID are not shown in this list and must be added manually, refer to 5.2.3 Add
a Hidden Wi-Fi Network Through the Handset, page 35.

To connect to a Wi-Fi network using the Device Manager:


• If the network details has not yet been added to the handset configuration, refer 5.2.2 Add a Wi-Fi
Network Through the Device Manager, page 33.

5.2.2 Add a Wi-Fi Network Through the Device Manager

Important

Wi-Fi must be enabled on the handset when syncing Wi-Fi networks from the Device Manager.

It is recommended to only configure one active Wi-Fi network for the handset. The network used
for Easy Deployment - AWS-INIT - is the default network on the handset. If another network is
configured, it will be used instead of AWS-INIT, and AWS-INIT will be removed. Removing all
networks on the handset will revert back to the default network - AWS-INIT.
1. Select Network → Wi-Fi → Wi-Fi Networks. Right click on Wi-Fi Networks, and select Add entry. A new
entry called Network appears at the end of the list.

Write the Network Name (SSID)


1. Select the just created Network entry. Its dynamic parameter setting fields opens.
2. In the SSID field, enter the name of the network which the handset shall associate to.
The SSID is case-sensitive. Up to 32 characters (capital, number, or special character) are allowed. The
network name is shown in the network selection menu on the handset.

Select Security Mode


The WLAN system can be configured to use various encryption and/or authentication schemes.
The use of extensive encryption/authentication schemes can cause incidents of dropped speech
during handover due to the time to process the authentication.

1. In the Security mode drop-down list (Network → Wi-Fi → Wi-Fi Networks → Network X), select one of
the following:
− Open (default) - No authentication is required.
− WPA-PSK & WPA2-PSK - A WPA/WPA2 pre-shared key pass phrase is required.
− PEAP-MSCHAPv2 - Requires a trusted (CA) certificate for authentication.

33 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

− EAP-TLS - Requires a trusted (CA) certificate to authenticate the WLAN, and application (client)
certificates to present to the WLAN for client authentication.
− EAP-FAST - Requires identity authentication, but no certificates.
2. If a security mode other than Open is chosen, follow the instructions in the applicable section below:

WPA-PSK & WPA2-PSK


If WPA-PSK & WPA2-PSK is chosen as the security mode, do the following:

In the Password field, enter the password for the pre-shared key (PSK).
The password is case-sensitive. Between 8 and 64 characters (capital, number, or special
character) must be entered.

PEAP-MSCHAPv2
If PEAP-MSCHAPv2 is chosen as the security mode, do the following:
1. Ensure that the handset is online.
2. Import the trusted certificate:
On the Devices tab in the Device Manager, right-click the handset and select Manage Certificates. In
the Trust list tab, click Browse and select the trusted certificate to import.

Important

The following certificate formats are supported: .cer, .der, .crt, .pem, .p12, and .pfx.
When possible, always use the Device Manager to transfer certificates to the handset.
Certificates added or removed through the handset might not synchronize correctly with the
Device Manager. For more information about certificates, refer to 4.2.1 Add Certificates to the
Handset, page 22.

3. Select Network → Wi-Fi → Wi-Fi Networks → Network X.


4. In the Identity field, enter the ID for EAP authentication.
The identity is used when an EAP-method requiring identity and password is enabled. The parameter
specifies the complete logon identity of the user, or NAI (network access identifier). It may include a
realm for RADIUS proxy. The form of an identity containing a Windows domain and a realm is DOMAIN
\user@realm.
5. If an anonymous identity is needed, enter the ID in the Anonymous identity field.
6. In the Password field, enter the password for the EAP authentication.
It depends on the server, if the password is case-sensitive. Also how many characters that are
needed, and their type (capital, number, or special character).

7. In the Trusted certificate field, select the trusted certificate for EAP methods that verifies the identity of
the Wi-Fi network.
Trusted certificates are also referred to as CA certificates.

EAP-TLS
If EAP-TLS is chosen as the security mode, do the following:
1. Ensure that the handset is online.
2. Import the certificates:

TD 93072EN / 08 October 2020 / Ver. R 34


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

On the Devices tab in the Device Manager, right-click the handset and select Manage Certificates. In
both the Trust list and Application certificates tabs, click Browse and select the certificates to import.

Important

The following certificate formats are supported: .cer, .der, .crt, .pem, .p12, and .pfx.
When possible, always use the Device Manager to transfer certificates to the handset.
Certificates added or removed through the handset might not synchronize correctly with the
Device Manager. For more information about certificates, refer to 4.2.1 Add Certificates to the
Handset, page 22.

3. Select Network → Wi-Fi → Wi-Fi Networks → Network X..


4. In the Identity field, enter the ID for EAP authentication.
The identity is used when an EAP-method requiring identity and password is enabled. The parameter
specifies the complete logon identity of the user, or NAI (network access identifier). It may include a
realm for RADIUS proxy. The form of an identity containing a Windows domain and a realm is DOMAIN
\user@realm.
5. In the Trusted certificate drop-down list, select the trusted certificate for EAP methods that verifies the
identity of the Wi-Fi network.
Trusted server (root) certificates are also referred to as CA certificates.
6. In the Application certificate drop-down list, select the application certificate for EAP methods that
verifies the identity of the application or user.
Trusted certificates are also referred to as user, or client certificates.

EAP-FAST
If EAP-FAST is chosen as the security mode, do the following:
1. In the Identity field, enter the ID for EAP authentication.
The identity is used when an EAP-method requiring identity and password is enabled. The parameter
specifies the complete logon identity of the user, or NAI (network access identifier). It may include a
realm for RADIUS proxy. The form of an identity containing a Windows domain and a realm is DOMAIN
\user@realm.
2. If an anonymous identity is needed, enter the ID in the Anonymous identity field.
3. In the Password field, enter the password for the EAP authentication.
It depends on the server, if the password is case-sensitive. Also how many characters that are
needed, and their type (capital, number, or special character).

5.2.3 Add a Hidden Wi-Fi Network Through the Handset

Important

When a network with a hidden SSID is added through the handset, that network must be the
only network configured in the handset.

1. In the WIRELESS & NETWORKS section of the Android admin menu, tap Wi-Fi.
2. Tap on the overflow menu at the top-right part of the screen.
3. Select Add network.
4. Enter the network details, and tap Save to add the hidden Wi-Fi network to the handset.

35 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

5.2.4 Configure the Handset for Wi-Fi Networks


This section describes the parameters available when configuring the handset for Wi-Fi networks.

Frequency Band
The handset can be set to exclusively use either the 2.4 GHz or the 5 GHz frequency band, or to automati-
cally pick the frequency band with the strongest signal strength.
If the frequency band selection is set to automatic (default), and the default channels are used, the
handset will choose a band when connecting to the system, and not change that band until
restarted. It is not recommended to use automatic frequency band selection when using Ekahau
location, refer to 5.7.3 Configure the Handset for a Cisco/Ekahau RTLS Solution, page 53.

Device Manager:
1. Select Network → Wi-Fi.
2. In the Frequency band drop-down list, select one of the following:
− Automatic (default)
− 2.4 GHz only
− 5 Ghz only
Handset admin menu:
1. Tap WIRELESS & NETWORKS → Wi-Fi → Menu icon → Advanced.
2. Tap Wi-Fi frequency band and select one of the following:
− Auto
− 5 Ghz only
− 2.4 GHz only

Regulatory Domain
The wireless spectrum regulatory domain defines which region's rules the handset should comply to. If
World mode (802.11d) is set (default), the handset listens for a beacon containing 802.11d formatted region
information, before transmitting anything (this requires 802.11d support and configuration from the
infrastructure).

The handset gets its regulatory settings from the AP. If this is not supported by the AP it has to be
configured for the handset as follows:

Device Manager:
1. Select Network → Wi-Fi → Regulatory domain.
2. In the Regulatory domain drop-down list, select one of the following:
− World mode (802.11d) (default)
− ETSI
− Japan
− USA
Handset admin menu:
1. Tap WIRELESS & NETWORKS → Wi-Fi → Menu icon → Advanced.
2. Tap Wi-Fi regulatory domain and select one of the following:
− World mode

TD 93072EN / 08 October 2020 / Ver. R 36


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

− ETSI
− Japan
− USA
To comply with EU and US regulations, the Wi-Fi regulatory domain is not to be changed by the
user. An administrator password is therefore required to access this setting on the handset
(Settings → Admin settings → Wi-Fi → Advanced (drop-down from the overflow menu at the top-
right of the screen) Wi-Fi regulatory domain). The Wi-Fi regulatory domain can only be changed
by an administrator.

Enabled Channels
Defines which 802.11 channels to enable when scanning for APs.
A regulatory domain may further limit which channels the handset uses. It's not possible to scan all
38 channels on both 2.4 and 5 GHz without reconfiguring the handset. An all channel site survey
must be done using two separate site surveys, one for each frequency band.

Table 1 Bands and Channels used by Wi-Fi a-radio

Frequency Band Channels

Non DFS 5.150 - 5.250 MHz 36,40,44,48

Non DFS (US only) 5.725 - 5.845 MHz 149,153,157,161, 165

UNII-1 5.150 - 5.250 MHz 36,40,44,48

UNII-2 5.250 - 5.350 MHz 52,56,60,64

UNII-2 Extended 5.470 - 5.725 MHz 100, 104, 108, 112,116, 120, 124,
128, 132, 126, 140

UNII-3 5.825 - 5.835 MHz 149,153,157,161–

Device Manager:
1. Select Network → Wi-Fi.
2. In the Enabled channels field, enter channels to scan (separated by commas). For example one of the
following combinations:
− 1,6,11 - Recommended channels to use when using 2.4 GHz.
− 6 - Forced to use one channel only.
− 1,6,11,36,40,44,48,149,153,157,161,165 (default)
Handset admin menu:
1. Tap WIRELESS & NETWORKS → Wi-Fi → Menu icon → Advanced.
2. Tap Wi-Fi channels and select the channels to use. For example one of the following combinations:
− 1,6,11 - Recommended channels to use when using 2.4 GHz.
− 6 - Forced to use one channel only.
− 1,6,11,36,40,44,48,149,153,157,161,165 (default).

37 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

The handset supports both 802.11a/n radio (5 GHz) and 802.11b/g/n radio (2.4 GHz), but it cannot
use them simultaneously. If both automatic frequency band selection and the default channels are
used, the handset will always use the frequency band it chose the first time it connected to the
system.

Enable 802.11n

802.11n cannot be disabled if the frequency band is set to automatic (see Frequency Band, page
36).

Support for 802.11n is enabled by default. If this leads to compatibility issues in the system 802.11n can be
turned off as follows:

Device Manager:
1. Select Network → Wi-Fi.
2. In the Enable 802.11n drop-down list, select:
− Yes (default)
− No
Handset admin menu:
1. Tap WIRELESS & NETWORKS → Wi-Fi → Menu icon → Advanced.
2. Tap Wi-Fi 802.11n to enable/disable support for 802.11n.

Deauthenticate on Roam

This parameter cannot be set through the handset settings menu.

When enabled, the handset will upon roam leave the current AP by transmitting a deauthentication frame.
When disabled (default), the handset will upon roam notify the current AP that it is going into power-save
mode, and then perform the roam. This may help the Wi-Fi infrastructure to avoid deallocating resources for
the client.
1. Select Network → Wi-Fi.
2. In the Deauthenticate on roam drop-down list, select:
− Yes
− No (default)

Roaming Methodology

This parameter cannot be set through the handset settings menu.

This enables alternatives for the roaming algorithm and RSSI measurements.

When 802.11 roaming is selected (default), the roaming is initiated and controlled solely by the client. Use
system-aided roaming for systems, or deployments, where the BSS follows the client, for example, for the
Extricom architecture.
1. Select Network → Wi-Fi.
2. In the Roaming methodology drop-down list, selec
− 802.11 roaming (default)

TD 93072EN / 08 October 2020 / Ver. R 38


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

− System-aided roaming

Captive Portal Detection


This parameter enables/disables the search for a captive portal.

Enabled (Yes): The handset will attempt to connect to the internet and, depending on the response,
determine whether there is a captive portal that requires an action before a connection can be established.
If the current connection does not have internet access, the handset may try to use another connection, e.g.
cellular, to establish a connection to the internet.

Disabled (No): the handset will not look for a captive portal response and instead assume that it has an
active internet connection. The handset will remain on the selected network even if it does not have
internet access.
1. Select Network → Wi-Fi.
2. In the Captive portal detection drop-down list, select:
− Yes (default)
− No
This parameter replaces the previous URL parameter Wi-Fi captive portal. In systems where the
captive portal URL has been changed, Captive portal detection must now be set to No for the
same behavior.

5.2.5 Preferred Mobile Network Type

Only applicable for the cellular handset version.

Set which mobile network type the handset should use.


1. Select Network → Mobile network.
2. In the Preferred mobile network type drop-down list, select from the following mobile network types
to use on the handset:
− 3G only (default)
− 3G (preferred) and 2G
− 2G only

Caution
2G cannot be used for both voice and data traffic simultaneously. To use data dependent
functions such as Unite messaging while in a call, 2G must be used together with a Wi-Fi
network connection. If the handset is used without a Wi-Fi network connection, the 3G only
setting must be used.

5.2.6 Access Point Names

Only Access Point Names applicable for the cellular handset version.

Defines a specific APN to use.

39 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

Add an APN
Device Manager:
1. Select Network → Mobile networks → Access Point Names.
2. Right click Access Point Names, and then click Add entry.
3. Click the APN entry.
4. Set the applicable parameters.

Handset admin menu:


1. Tap WIRELESS & NETWORKS → More → Cellular networks → Access Point Names.

2. Tap
3. Set the applicable parameters.

Preferred APN
Choose which of the configured APNs to use.

Device Manager:
1. Select Network → Mobile networks.
2. In the Preferred APN drop-down list, select an APN.

Handset admin menu:


1. Tap WIRELESS & NETWORKS → More → Cellular networks → Access Point Names.
2. Tap an APN in the list.

5.2.7 Enable Cellular Data (Caution)


Only applicable for the cellular handset version. Disabling or enabling cellular data does not have
any effect on GSM-calls.

Caution
If there is no Wi-Fi connection configured on the device, and cellular data is disabled, the
device will be unable connect to Unite CM/Unite CS (and will not be visible in the Device
Manager).

Do the following to disable cellular data for the handset:

Device Manager:
1. Select Network → Mobile networks.
2. In the Enabled cellular data (caution) drop-down list, select No.

Handset admin menu:


1. Tap WIRELESS & NETWORKS → More → Cellular networks.
2. Uncheck the Data enabled box.

TD 93072EN / 08 October 2020 / Ver. R 40


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

5.3 DECT Subscriptions


If a DECT system is available, the DECT feature can be enabled for voice calls on the handset. To enable
the DECT feature, it is necessary to switch on the DECT chipset, subscribe the handset to a DECT system
and log in to an extension number. For more information about DECT system configuration, refer to the
IPBS, IPBL, and IPVM Installation and Operation Manual (10.1.X), TD 92579EN.

5.3.1 Access DECT Subscriptions Menu


DECT subscriptions can be added through the Ascom settings menu for system administrators. This menu
usually requires a password to access.

To access the Subscriptions menu, do the following:


1. Go to the Ascom settings → DECT menu.
2. Tap Subscriptions.
In the Subscriptions menu DECT subscriptions can be added, edited, or removed.

5.3.2 Switch on the DECT Chipset


Before managing DECT subscriptions, enable the DECT chipset.
1. In the Admin Settings menu, go to Subscriptions.
2. Swipe the slider to the right to enable DECT subscriptions.

5.3.3 Add a New Subscription


A subscription means a wireless connection between a handset and a DECT system. After the handset is
subscribed to the system, logging in to the extension number becomes available. This will be necessary to
make and receive calls.

A subscription can be added automatically using the Easy registration feature.

Adding a subscription manually requires the PARK code and the system access code. The Portable Access
Rights Key (PARK) code is used to identify the DECT system and the access code is used to verify the
subscription.

To subscribe a handset, it must be in the range of the DECT system.

To add a subscription, do the following:

Before managing DECT subscriptions, enable the DECT chipset.


1. Go to Subscriptions menu.
2. Tap the properties icon to go to the Add new Subscription menu.
3. Type in the name for the subscription in the corresponding box with the keyboard or leave the field
empty to get the system name from the IP-DECT system.

The name of the subscription cannot contain the following symbols: ( ) [ ] - + ? ! " "

4. Type in the park code and the access code in the corresponding boxes with the keyboard.
5. Tap Subscribe.

41 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

If the subscription was added successfully, the Subscribe complete message will be shown. The name
of a new subscription will appear in the list of subscriptions.

If a park code or access code is entered incorrectly, a warning message Subscription failed.
Please try again appears on the front display. Try to double check the data entered into the boxes to
avoid problems with adding a subscription. If the problem persists after reentering the data, it might be a
system error.

5.3.4 Add a Subscription Using Easy Registration


A handset can subscribe to a DECT system automatically if the following requirements are fulfilled:
• The DECT system is configured for Easy Registration, refer to the Installation and Operational Manual for
your DECT system.
• The handset's extension number and IPEI are registered in the DECT system, see the Installation and
Operational Manual for your IP-DECT system. To learn the handset IPEI number, see View DECT IPEI
number.
• The handset is not subscribed to any systems and is located in the range of one DECT system.

View DECT IPEI Number


IPEI is needed to enable network subscription of the handset. It is used for subscribing a handset to a DECT
system using the Easy registration feature. The IPEI number can be found in text and bar code on the
handset box and in the handset label. It is also available in the Ascom settings menu.
1. Go to the Admin settings menu.
2. Tap About phone and go into the IPEI section.

The IPEI number is also displayed on the Add new Subscription screen. Refer to the 5.3.3 Add a
New Subscription, page 41.

Subscribe a Handset Using Easy Registration


1. Switch on or reboot the handset.
If the DECT chipset is enabled, the handset starts to search for DECT systems and will subscribe to the
system when it is found. To cancel the subscribing process, go to the Subscriptions menu, tap the Plus
icon and tap Cancel. If the handset is successfully subscribed, a notification is shown on the bottom of
the screen.
Alternatively, disable and re-enable the DECT chipset to start the Easy Registration process.

If no system is found within 2 minutes or if Cancel is tapped, no subscription is added.

Multiple DECT systems may cause interference issues for Easy Registration. If the first attempt of
Easy registration fails, repeat the procedure.

The extension number can be viewed in the handset by navigating to the Subscriptions menu.

After the handset is successfully subscribed to a DECT system using Easy Registration, it will be automati-
cally logged in to the extension number.

5.3.5 Edit a DECT Subscription


Subscriptions can be renamed for an easier identification of the location.

TD 93072EN / 08 October 2020 / Ver. R 42


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

1. Go to the Subscriptions menu, refer to the 5.3.1 Access DECT Subscriptions Menu, page 41.
2. Tap properties icon to the right from the selected subscription to reveal additional options.
3. Tap Rename.
4. Type in a new name for the subscription using the keyboard.
The name of the subscription cannot contain the following symbols: ( ) - + ? ! " " and be
duplicated to any existent subscription names.

5. Tap OK to confirm the change.

5.3.6 Select a DECT Subscription


To make and receive calls the user should be in the range of a DECT system and the handset should be
logged in a proper extension number. If more than one DECT subscriptions were added, it is possible to
select manually which subscription to use on the current location or to enable the automatic search feature.

If there is only one subscription in the handset, it will be selected automatically, no automatic search is
available.
1. Go to the Subscriptions menu, refer to the 5.3.1 Access DECT Subscriptions Menu, page 41.
2. Select a subscription from the list or tap Auto for automatic search.

5.3.7 Unsubscribe from a DECT System


Subscriptions can be deleted for security and control purposes.

Before the subscription can be deleted, it should be logged off.

To unsubscribe, follow the steps below:


1. Go to the Subscriptions menu, refer to the 5.3.1 Access DECT Subscriptions Menu, page 41.
2. Select the subscription for deletion and tap the properties icon to the right from it.
3. Tap Unsubscribe.
4. Tap Unsubscribe to confirm deleting the selected subscription.
If the subscription is deleted successfully, a notification Subscription deleted from device will
appear at the bottom of the screen.

5.3.8 Log In to an Extension Number


Logging in to an extension number is required for making and receiving calls and using messaging on the
handset. The following parameters are needed: the master ID of the DECT system master base station, the
dial number to be assigned to the handset and the access code. To log in to the subscription, do the
following:
1. Go to the Subscriptions menu, refer to the 5.3.1 Access DECT Subscriptions Menu, page 41.
2. Select an active subscription with the mark "Not logged in".
3. Tap properties icon to the right from the selected subscription to reveal additional options.
4. Tap Login. The handset will display a login screen.
5. Enter the master ID in the Master ID box.
6. Enter the number in the Number box.

43 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

7. Enter the access code in the Access code box.

The Access code box can be left empty if it is not configured on the DECT system.

8. Tap Login.
− If the data are entered correctly and logging in has been successful, a notification Login
complete! will appear on the screen.
− If a wrong master ID, number, or access code is entered, a notification Login failed. Invalid
login details or unauthorized device will appear on the screen. Return to the Subscrip-
tions menu and repeat the steps 5 - 8 above.

5.3.9 Log Out from an Extension Number


To remove a number from a DECT subscription, log out from the subscription.
1. Go to the Subscriptions menu, refer to the 5.3.1 Access DECT Subscriptions Menu, page 41.
2. Select the subscription for logging out from the system.
3. Tap Logout.
4. Enter the access code in the Access Code box.
5. Tap Logout.
− If the data are entered correctly and logging out has been successful, a notification Logout
complete! will appear on the screen.
− If a wrong access code is entered, a notification Logout failed. Invalid Access code will
appear on the screen. Return to the Subscriptions menu and repeat the steps 1 - 5 above.

5.4 Ascom Messaging


Ascom Myco supports messaging in WiFi, DECT, and mixed WiFi and DECT environment. DECT messaging
is used for transferring alarms, notifications, messages, and status information. IM images, WiFi certificates,
firmware upgrades, company phonebook and applications cannot be transferred via DECT. In mixed WiFi
and DECT environment, the both interfaces are used for messaging to provide redundancy functionality.
If a handset in DECT mode is roaming between DECT base stations and messaging traffic exceeds
the supported limit, messages may be delivered with delays.

In DECT environment, Ascom Myco can receive broadcast messages that are displayed as notifications. A
DECT broadcast message can be represented as a chat message if it was sent by a user through a
broadcast number. This number can be configured in the system to broadcast messages received from
users.
Warning

Broadcast messages must not be used for sending medical alerts.

The parameters related to the Unite CM/Unite CS connection are set in the Ascom Messaging menu. To set
the connection to a Unite CM/Unite CS, do the following:
1. Select Ascom Messaging.
2. In the Unite interface address field, enter the network address to the Unite interface.

TD 93072EN / 08 October 2020 / Ver. R 44


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

The format of the address must be a fully qualified domain name: ip|hostname.domain[:port]
[/path].
TIP: The default port is 443.
3. In the Authentication shared key field, enter the shared key for the HTTP Basic Authentication used
for the Unite websocket interface.

The default shared key is "changethis".

4. The Endpoint Number/Address field shows the number, or address that is registered for this handset
in the Unite interface (if already configured).
5. In the Server validation drop-down list, select the server validation type of the Unite websocket
connection:
− Trust all (default) - All servers are trusted by default.
− Only trusted - The server credentials are always checked before a connection attempt.

Only trusted is not recommended if the Unite interface address entered in step 2 is an IP
address.

6. In the Client validation drop-down list, select the client validation type of the Unite websocket
connection:
− Any (default) - All client credentials are accepted for the websocket connection.
7. In the Use Ascom Myco Launcher drop-down list, select Yes to enable the Ascom Myco Launcher user
interface on the handset.

This parameter cannot be set through the handset settings menu.

TIP: The Ascom Myco Launcher replaces the default Android launcher and adds customized functionality
such as alert and conversation handling to the handset.

5.4.1 Advanced security


If Ascom Myco is used in public networks, a reverse proxy can be configured for advanced security reasons.
A reverse proxy handles communication between Ascom Myco handsets in public networks and the Unite
CM server in a private network. The handset makes requests directly to the reverse proxy, and the data
from the Unite CM server is returned to the clients as though it originated from the reverse proxy server
itself. The Unite CM server remains unreachable from public networks.

By default, Ascom Myco uses port 443 for the secure HTTPS connection to the reverse proxy. The reverse
proxy redirects the HTTPS request to port 33003 of the Unite CM server that is used for WebSocket
communication.

If Ascom Myco is used in pure DECT or mixed DECT and WiFi environment, the IP DECT Master basestation
uses the IP address configured on Ascom Myco handsets and sends requests to port 10217. The IP DECT
Master is connected to the private network, however it will send requests to the reverse proxy if it is
configured on Ascom Myco handsets. To process these requests, the reverse proxy should be configured
to enable TCP forwarding from port 10217 to port 10217 on the Unite CM server.

The reverse proxy can be used for more secure HTTPS connections. The Unite CM server does not support
client certificate validation, but this feature can be configured on the reverse proxy server. Figure illustrates
the process.

45 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

Figure 5. Reverse proxy connection diagram

For more information about reverse proxy configuration, refer to System Description, Ascom Myco Cellular.

5.5 Services
Services are launched through the My Services app on the handset. Up to ten groups, containing up to
three services each, can be added as handset shortcuts to perform specific actions. Each service can be
either a URI Action (Uniform Resource Identifier), a Call action, or a Data Send action.

The different actions can be used to:


• URI actions - Open an app or web page.
• Call actions - Call a predefined number.
• Data Send action - Send data to communicate with external equipment.

5.5.1 Add New Service


Follow the steps below to add one or more services to the handset:

Add Services Group


1. Select Services > Groups. Right click on Groups, and select Add entry. A new entry called Group
appears at the end of the list.
2. Select the newly created group entry. In the Title field, enter the group name. The group name is
shown in the services list in the My Services app on the handset.

TD 93072EN / 08 October 2020 / Ver. R 46


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

Add Services
1. Expand the newly created group entry, and select Services. In the Number of services field, enter 1, 2,
or 3, depending on the number of services the group should contain.
2. Expand Services, and select Service 1, 2, or 3. In the Title field, enter the service name. The service
name is shown in the My Services app when the group is expanded.
3. In the User Confirmation drop-down list, select if the user must confirm the service, before executing
it:
− Required
− Is not required (default) - No confirmation is required.
Choose one of the following sections depending on the action to be used:

If a URI Action Should Be Used


1. Select Uri Action. In the Launch Uri field, enter the URI to launch on service execution.
2. In the Content type drop-down list, select a content type that match the information given by the URI:
− Text and/or HTML (default)
− Png image
− Gif image
− Video
− Text and/or CSS
− Audio

If a Phone Call Should Be Placed


1. Select Call Action. In the Call Digits field, enter the number.
2. In the Start call drop-down list, select one of the following:
− Start call (default) - The call starts immediately at service execution.
− Enter dial-mode - The Phone App opens so the user can enter a number manually.

If Data Should Be Sent


1. Select Data Send Action. In the Initial Data field, enter the data.
2. Expand Data Send Action, and select Input Fields. In the Number of input fields field, enter 1, 2, or 3.
3. Expand Input Fields, and select Input Field 1, 2, or 3. In the Input Field Title field, enter the title to be
displayed above the input field.
4. In the Input Field Type drop-down list, select the type of data to be sent:
− None (default)
− Numeric
− Alphanumeric
− Date
− Time
− List
5. In the Default Value field, enter a value to be displayed in the input field by default.
6. In the Hint field, enter a text used as a hint to what type of data to enter.

47 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

7. If desired, enter a string in the Prefix field. These characters are added before the Default Value.
8. If desired, enter a string in the Suffix field. These characters are added after the Default Value.
9. In the Required drop-down list, select one of the following:
− Required - The field is required, and must be filled with data.
− Not Required (default) - The field can be left empty.
10. If desired, repeat the steps 3) to 9) for the other input fields.

5.6 Alarm- and Multi-Function Button


The button on the top of the handset can be used to send out a personal alarm, or to trigger a function. It
can also be configured to be used by third-party apps.
If the button is used by third-party apps, no other functionality can be configured for the button,
refer to 5.6.3 Use Top Button for Third Party Apps, page 49.

The alarm/function can be activated by a user in two different ways:


• Single long press (0-5 sec)
− Press and hold the top button.
• Multiple presses (2, 3 or 4 times)
− Press the top button multiple times under a short period of time.

If the time for the single long press is set to 0, the handset can not have a multi-press function.

A handset can be configured to have two different alarm/functions, one for long press and one for multi-
press (if not used as a Push-to-Talk button). The following actions can be set:

Phone Call
Automatically dial a predefined number (no alarm is sent out).

Test Alarm
Send out a test alarm. Test alarms are handled differently depending on the system.

Push-Button Alarm
Send out a personal alarm (two different personal alarms can be configured). The functionality triggered by
the personal alarms is system dependent.
If a personal alarm is not delivered within five minutes, the sender receives a notification about
delivery failure and the alarm is permanently removed from the queue. To configure the notifica-
tion failure text, see 5.6.1 Set the Long Press or Multi-Press Actions, page 49.

Push-to-Talk Button
Press and hold to activate the handset microphone during a Push-to-Talk group call. No other button
functionality can be configured when used as a Push-to-Talk button, refer to 5.19.1 Use Alarm & Multi-
Function Button, page 72.

TD 93072EN / 08 October 2020 / Ver. R 48


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

5.6.1 Set the Long Press or Multi-Press Actions


Choose the actions to be performed when a user long press or multi-press the top button.

Select Alarm & Multi-function button → Long press/Multi-press.

In the Function drop-down list, select one of the following:


• Not used (default)
• Phone Call
− Enter a phone number in the Phone number field to be called when the button is pressed.
• Test alarm
− Enter a text in the Alarm sent text field to be displayed on the device when the button is pressed (up
to 24 characters). The default text is "Test alarm".
− Enter a text in the Alarm send failure text field to be displayed on the device if a test alarm failed to
be sent (up to 24 characters).
• Push-button alarm 1, 2
− Enter a text in the Alarm sent text field to be displayed on the device when the button is pressed (up
to 24 characters). The default text is "Personal alarm".
− Enter a text in the Alarm send failure text field to be displayed on the device if a personal alarm failed
to be sent (up to 24 characters).

5.6.2 Automatic Call after Alarm


Before configuring automatic calls, setup the alarm actions in 5.6.1 Set the Long Press or Multi-
Press Actions, page 49.

The handset can be configured to automatically call a predefined number after an alarm has been sent.

Do the following to setup automatic calls:


1. Select Alarm & Multi-function button. Enter a phone number in the Number for call after alarm field to
be called when an alarm is sent from the handset (maximum 24 characters).
2. Select Alarm & Multi-function button → Long press/Multi-press. In the Automatic call after alarm
drop-down list, select one of the following:
− Off - Default, no automatic call will be made for this alarm type.
− Normal - A normal call is placed.
− Loudspeaker - Loudspeaker mode is used by default during the call.
− Monitoring - A one-way "hidden" call where the called party can listen in but cannot communicate
with the calling handset.

5.6.3 Use Top Button for Third Party Apps


If the handset has a third-party app that can use the top button for input, do the following to enable top
button access for third-party apps:
If third-party top button access is enabled, all other button functionality (for example push button
alarm) is disabled.

Select Alarm & Multi-function button. In the Use top button for third party apps drop-down list, select Yes
to use the top button for third-party app functionality.

49 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

5.6.4 Man-Down & No-Movement Alarm


The Man-down alarm reacts if the handset is tilted (default 45°) from the vertical for a predefined period of
time (default 7 seconds). The No-movement alarm will react if no movement is detected during a predefined
period of time (default 30 seconds).

Man-Down Alarm
Do the following to configure the man-down alarm for the handset:
1. Select Alarm & Multi-function button → Man-down & No-movement. In the Man-down alarm drop-
down list, select On to activate the no-movement alarm.
2. In the Man-down detection time field, enter a delay in seconds between the detection of man-down
and the warning phase (default 7 seconds).
The handset will not enter the warning phase if tilted back up during the delay. The shortest delay that
can be set is 5 seconds, and the longest is 120 seconds.
3. In the Man-down warning angle drop-down list, select the deflection angle of the device for man-down
detection (low 45 degrees or high 60 degrees). Man-down is detected when the angle of the device is
tilted below that value (default 45 degrees).
4. In the Warning phase duration field, enter the number of seconds the warning phase pop-up should
be shown on screen before an alarm is sent out (default 7 seconds).
The warning phase should be long enough to give the user opportunity to cancel the man-down alarm.
The shortest period that can be set is 1 second, and the longest is 120 seconds.
Man-down tracking can also be activated from the Personal security app on the handset, refer to
the User Manual, Ascom Myco Smartphone, TD 93066EN for further instructions.

No-Movement Alarm
Do the following to configure the no-movement alarm for the handset:
1. Select Alarm & Multi-function button → Man-down & No-movement. In the No-movement alarm drop-
down list, select On to activate the no-movement alarm.
2. In the No-movement detection time field, enter a delay in seconds between the detection of no-
movement and the warning phase (default 30 seconds).
The handset will not enter the warning phase if moved during the delay. The shortest delay that can be
set is 5 seconds, and the longest is 120 seconds.
3. In the Warning phase duration field, enter the number of seconds the warning phase pop-up should
be shown on screen before an alarm is sent out (default 7 seconds).
The warning phase should be long enough to give the user opportunity to cancel the no-movement
alarm. The shortest period that can be set is 1 second, and the longest is 120 seconds.
No-movement tracking can also be activated from the Personal security app on the handset, refer
to the User Manual, Ascom Myco Smartphone, TD 93066EN.

5.7 Location Services


Three types of location are supported:
• A basic location solution that gives an approximate location using GPS/cellular network (cellular handset
version only).

TD 93072EN / 08 October 2020 / Ver. R 50


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

• Ascom IR Location, which enables location tracking via IR-beacons.


If the IR Site Survey tool is installed, the Ascom Myco 2 handset can be used for deploying
Ascom IR beacons.

• A personal security solution that gives a more accurate location using a third-party Real-Time Location
System (RTLS) solution (not available in DECT environment).
• A location solution that gives an approximate location using DECT network (for handsets in DECT mode
only).

The following RTLS solutions are supported:


• Cisco RTLS Solution
To use the Cisco RTLS solution, use a Cisco Mobility Services Engine. The handset must also be
configured to use an RTLS, see 5.7.3 Configure the Handset for a Cisco/Ekahau RTLS Solution, page 53.
• Ekahau RTLS Solution
To use the Ekahau RTLS solution, an Ekahau software must be installed in the system. The handset must
also be configured to use an RTLS, see 5.7.3 Configure the Handset for a Cisco/Ekahau RTLS Solution,
page 53.
For additional information about RTLS location, see the Function Description, Location in Ascom VoWiFi
System, or the Configuration Notes, Ekahau RTLS.

5.7.1 Basic Location

Basic location is applicable for the cellular handset version only.

The handset can be configured to use either GPS or cellular location, or both combined. The location data
is sent in personal alarms and in location messages that are requested by the system. It can be used by
third-party apps installed on the handset, such as navigation apps.
1. In Device Manager, select Location services.
2. In the GPS location drop-down list, choose one of the following options:
− Off to disable GPS and cellular location.
− Device only to enable GPS location only. This option is not recommended because it requires more
time to provide location data.
− Battery saving to enable cellular location only. This option is available for GMS handsets only.
− High accuracy to enable both GPS and cellular location. This is the recommended option because it
provides efficient and fast location detection with best accuracy.
If the High accuracy option is applied on a non-GMS handset, only GPS location is enabled
and location detection is functioning in the Device only mode.

3. If GPS location is enabled, complete the GPS polling interval field with a number of minutes. 5 is the
default value. The polling interval starts after the handset has sent an alarm or a location response.
During this interval, the handset is still obtaining location coordinates and can provide them to the
server on request. If during the polling interval the handset receives a location request or a new alarm
is raised, the interval timer is restarted and location data remains available. When the polling interval is
over, the handset stops tracking location and deletes the collected GPS data.

51 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

The basic location settings does not affect the performance of an RTLS service.

5.7.2 Configure Ascom IR Location

Only available for Ascom Myco 2.

To enable the handset to use the Ascom IR Location feature, do the following in the Device Manager:
1. Select Location services → Location.
2. In the IR Location drop-down list, select Enable (default: Disable).
3. In the Special location drop-down list, you can select either Enable or Disable (default: Disable).
When enabled, the handset will send location information when entering the range of a location device
with immediate alarm transmission enabled.
4. In the IR short range drop-down list you can select Enable (default: Disable).
Short range mode reduces the impact that sunshine or incandescent light has on the IR coverage area.
It is typically used when large glass areas are present at a site. If short range mode is not used at these
sites, the coverage area will differ between day and night.

5.7.2.1 Zone Presence Configuration


The Zone presence feature tracks handset location with IR beacons making zones. When entering a zone,
the handset sends a message with location history to the system. If Zone presence is enabled, the location
message is sent at handset startup even if the handset is not in the range of any zone.

The handset is considered to have left the zone if:


• The handset has not detected any IR beacon used for Zone presence for a certain period configured
with the Out of zone time (seconds) parameter.
• The handset has detected another IR beacon used for Zone presence.
The handset sends location update if
• The handset has detected another IR beacon used for Zone presence.
• The handset has not left the zone, but the period configured with the Zone update time (minutes)
parameter has expired.
Two Zone presence setups are possible:
1. All IR beacons are used for Zone presence. The Zone presence behavior is always applied.
2. A group of IR beacons used for Zone presence is making a zone range. If the handset detects an IR
beacon related to the zone range, the Zone presence behavior is applied. If the handset detects an IR
beacon that is not related to the zone range, the default Ascom IR location behavior is applied.
To enable and configure Zone presence, perform the following steps:
1. In Device Manager, navigate to Location Services → Zone Presence.
2. For IR Location select Enabled.
3. For Enable zone location select Enabled.
4. In the Out of zone time (seconds) field enter the period after which the system will consider that the
handset has left the zone if it is not detecting an IR beacon anymore.
5. In the Zone update time (minutes) field configure the recurrent period when the handset sends
location update.

TD 93072EN / 08 October 2020 / Ver. R 52


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

6. If the Zone Range option is disabled, each IR beacon is considered as an individual zone. To limit the
number of IR beacons that should be used for Zone presence, select Enabled for Zone range. The
Zone range feature requires a filter that will define what IR beacons are making zones:
− In the Zone filter field enter the starting value for IR beacon IDs in the zone range, for example,
A200. The possible value range for the Zone filter field is 0000-FFFF (hexadecimal), the default
value is 0000.
− In the Zone filter mask field enter a 4–digit value using F for significant bits in an IR beacon ID and 0
for other bits. For example, enter FF00 to determine a zone range between A200 and A2FF — all
beacons ID starting with A2 will be included. The possible value range for the Zone filter mask field
is 0000-FFFF (hexadecimal), the default value is 0000.
The zone filter mask is calculated in a similar way as a subnet mask is defined in an IP network. The
system performs the following check to define if the beacon belongs to the zone range:
− Performs the logical bitwise AND operation on each pair of the corresponding bits of the IR beacon
ID and Zone filter mask. if a bit in the mask is equal to 0, the result is 0, for example:
0x1204&0xFF00=0x1200
− Compares the result of the operation with the Zone filter value. If the values are equal, the IR
beacon is related to the zone range and is used for Zone presence.
Example. For zone range 0x0000-0x0FFF (4096 different zones are possible), the Zone filter is
0x0000 and the Zone filter mask is 0xF000
− IR beacon ID 0x1204 does not belong to the zone range: 0x1204 & 0xF000 = 0x1000.
− IR beacon ID 0x0030 belongs to the zone range: 0x0030 & 0xF000 = 0x0000.
− IR beacon ID 0x0F40 belongs to the zone range: 0x0F40 & 0xF000 = 0x0000.

5.7.3 Configure the Handset for a Cisco/Ekahau RTLS Solution


To enable the handset to use an RTLS solution, do the following:
1. Select Location services → Wi-Fi location.
2. In the Location scanning drop-down list, select Enable.
3. In the Scanning interval field, set the time between the scanning periods 17 (default 10 seconds).
4. In the Scans per scanning period drop-down list, select how many scans that should be performed
during each scanning period 18 (default 1 scan).
If the Ekahau RTLS solution is used, also perform the next step:
5. In the Ekahau network address field, enter the address to the Ehahau RTLS. The address can be input
as either an IP address, or as a URI. The default Ekahau RTLS port (8552) is used if no port is given in
the network address.
Only APs on the same frequency band as the handset are scanned and sent to Ekahau. It's
recommended to configure the handsets for a specific frequency band (2.4GHz or 5GHz), and not
use the default automatic frequency band setting when using Ekahau location. Refer to Frequency
Band, page 36.

5.7.4 DECT Base Station Positioning


The approximate location of a handset can be sent with an alarm or location update. The handset evaluates
the field strength ratio of the individual radio Base Stations and sends the best-rated Base Station ID to

17. Note that closer scanning periods, and a larger number of scans per period, will shorten the battery life.
18. Only available for Ascom Myco 2.

53 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

indicate the approximate location of the handset. To enable DECT Base Station Positioning, perform the
following steps:
1. In Device Manager, navigate to Location services → DECT positioning .
2. Enable the Base Station Positioning option.
The Base Station Positioning option is also available on the handset in the Admin Settings →
Ascom Settings → Location services → DECT positioning menu.

5.8 NFC
The Ascom Myco handset is equipped with an NFC implementation, making it possible to use the handset
for NFC related tasks. The Ascom Myco NFC solution consists of an NFC chip in the handset and NFC
antenna in the battery of the handset.
The NFC antenna is incorporated into the handset’s original battery. Replacing the battery with
anything else than an original Ascom Myco battery will render the NFC function unusable.

To configure the use of NFC on the handset, do the following in the Device Manager:
1. Select NFC.
2. In the NFC drop-down list, choose between:
− Yes (default).
− No

NFC applications for the Ascom Myco handset are built with the standard Android API.

5.9 Third-Party Integration


These parameters are used when integrating a third-party app into the Ascom Myco launcher, replacing
parts of it's functionality.

Refer to the third-party app documentation for detailed instructions.

5.10 App Customization


The app customization settings can only be accessed through the Device Manager. If the settings
are accessed via the handset (Settings → Admin settings → Ascom settings → App customization)
the user will see an empty screen.

The default available apps can be shown or hidden through the App customization settings. The apps can
be set to have their notifications displayed or not displayed on the top display.

5.10.1 Visibility
Defines if an available app is visible or hidden.
1. Select App customization → Applications.
2. Expand the Applications folder to show the list of available apps.
3. Select the app to hide or show. In the Visibility drop-down list, choose between:
− Visible (default)

TD 93072EN / 08 October 2020 / Ver. R 54


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

− Hidden

5.10.2 Show Notification on Top Display


Defines if applications’ notifications are displayed on the top display or not.
If the Ascom Myco Launcher is enabled, see 3.2.6 Enable the Ascom Myco Launcher User
Interface, page 14, only notifications from the Unite system are displayed on the top display.

1. Select App customization → Applications.


2. Expand the Applications folder to show a list of available apps.
3. Select an app. In the Show notification on top display drop-down list, choose between:
− Yes
− No (default)

5.10.3 Google Mobile Services (GMS) Customization

Only available for Ascom Myco 2.

The apps that are part of the GMS are managed under App customization → Applications just like any
other app. To be able to configure GMS apps, an Ascom Myco 2, GMS handset version is required.

5.11 Shortcut Customization

Only available for Ascom Myco 2

This feature and this group of parameters in the Device Manager will not be present unless the
Ascom Myco launcher is enabled, see 3.2.6 Enable the Ascom Myco Launcher User Interface,
page 14.

The shortcut drawer can contain 1-4 apps or services. The shortcut component along with the name, order
and type of the shortcut are set in the Device Manager. Users cannot add, edit, or delete apps or services
from the shortcut drawer.

The shortcut drawer is inactive unless a shortcut is added.

Add a Shortcut to the Shortcut Drawer


1. Select Shortcut customization → Shortcuts.
2. Right-click and select Add Entry.

Delete a Shortcut from the Shortcut Drawer:


1. Select Shortcut customization → Shortcuts.
2. Right-click on the Shortcut and select Delete Entry.

5.11.1 Shortcut Name


Defines the name of the shortcut, which is displayed below the shortcut icon in the shortcut drawer.

55 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

The text size in the names of the shortcuts in the shortcut drawer is the same as the size in the
App view. There is only one line available for the name of the shortcut, any additional text will be
truncated which is indicated with three dots on the handset.
1. Select Shortcut customization → Shortcuts → Shortcut.
2. In the Shortcut name field, type in the name of the shortcut.

The maximum number of characters that can be entered is 50.

5.11.2 Order
Defines the display order for the shortcut.
1. Select Shortcut customization → Shortcuts → Shortcut.
2. n the Order field, type in the number of the order for the shortcut (default “1”).

Lower numbers are placed to the left.

The maximum number that can be set is 4 and the minimum number that can be set is 1.

5.11.3 Shortcut Type


Defines the type of the shortcut.
1. Select Shortcut customization → Shortcuts → Shortcut.
2. In the Shortcut type drop- down list, choose the App or Service type of shortcut as needed.

5.11.4 Shortcut Component Name


Defines the application, which will be started when the user taps the icon in the shortcut drawer.
1. Select Shortcut customization → Shortcuts → Shortcut.
2. In the Shortcut component name drop-down list, choose between available app components (default
“No activity selected”).

5.11.5 Shortcut Service Name


Defines the service or service group, which will be started when the user taps the service icon in the
shortcut drawer.
1. Select Shortcut customization → Shortcuts → Shortcut.
2. To configure an individual service:
a. In the Shortcut service action drop-down list, choose Execute service.
b. From the Groups drop-down list, choose the required service group.
c. From the Service index drop-down list, choose the required service that is included to the selected
service group.
3. To configure a service group:
a. In the Shortcut service action drop-down list, choose Expand group.

TD 93072EN / 08 October 2020 / Ver. R 56


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

b. From the Groups drop-down list, choose the required service group. If the No group selected
option is chosen, the Services application will be opened without any group expanded.

5.12 Troubleshooting
The handset provides debug features and tools for collecting system, status, and DECT logs. For more
information, refer to Troubleshooting Guide, Ascom Myco Smartphone, TD 93128EN.

5.13 Display
The Display parameters are used to configure the handset screens and user interface. All settings starting
with an asterisk in the Device Manager, for example *Font size can also be set by the end user directly from
the settings view in the handset.

5.13.1 Font Size


Sets the font size used on the device.
1. Select Display → Font size.
2. In the Font size drop-down list, select one of the following four sizes:
− Small
− Normal (default)
− Large
− Extra large

5.13.2 Owner ID/Name


The Owner ID/Name of the handset is shown on the lock and charging screens.
1. Select Display → Owner ID/name.
2. Enter the identity of the handset user name.
Up to 50 characters (capital, number, or special characters) can be entered. The maximum text
length to avoid scrolling is the following:
• 30 characters for the lock screen.
• 13 characters for the charging screen.

If no other value is set, the default value is the Call ID/number of the handset.

5.13.3 Sleep Timeout


Sets the time for how long a handset can be inactive, i.e. the user does not touch the display or press any
buttons, before going into sleep mode.
1. Select Display.
2. In the Sleep timeout drop-down list, select the desired time:
− 15 seconds
− 30 seconds
− 1 minute (default)
− 2 minutes

57 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

− 5 minutes
− 10 minutes
− 30 minutes

For the longest battery time between charges, use the shortest convenient timeout.

This parameter does not set the time before the screen locks. For more information, see 5.17.6
Automatic Lock Time, page 65.

5.13.4 Rotate Top Display


The text on the top display can be rotated. If rotation is set to off (default) the text on the top display is
readable when the front of the handset is facing the user. Set the top display rotation parameter to on if the
handset is normally carried with the front away from the user.
1. Select Display.
2. In the Rotate top display drop-down list, select one of the following options:
− Off (default) - The text is readable when the front of the handset is facing the user.
− On - The text is readable when the front of the handset is facing away from the user.

5.13.5 Top Display Alert Formatting


Changes the formatting of the top display notification text.

This parameter only applies for notifications sent from the Unite system.

1. Select Display.
2. In the Top display alert formatting drop-down list, select one of the following formatting types:
− Automatic (default)
− Body
− Concatenated
− Subject and body

5.13.6 Charging Screen


When the charging screen is enabled, the handset displays a special charging screen application while
charging, or while docked.
1. Select Display → Charging screen.
2. In the Show Charging screen drop-down list, select:
− Yes (default)
− No
3. In the When to show drop-down list, select one of the following:
− While docked (default)
− While charging
− Both

TD 93072EN / 08 October 2020 / Ver. R 58


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

5.14 Sound
Different sounds for ringtones and notifications can be set in the handset. The dial pad touch tones, the
touch or screen lock sounds, or the incoming call vibration can be set to On (default) or Off as follows:

5.14.1 Ringtones
Sets the ringtone for incoming calls
1. Select Sound.
2. In the Ringtones drop-down list, select the ringtone to use for incoming calls (default Ascom Smile).

5.14.2 Dialing Tone Patterns


Use this parameter to change the dialing tone pattern sound when calling from the handset.
When the handset has a SIM card, it will always use the dial tone pattern from the SIM card's
country.

1. Select Sound.
2. In the Dial tone patterns drop-down list, select a country to use the dial tone pattern from that country.

5.14.3 Notification Sound


Sets the sound for notifications.
The notification sound is separate from the sounds used for alerts and messages. The sounds
used for alerts and messages cannot be changed.

1. Select Sound.
2. In the Notification sound drop-down list, select the sound to use for notifications (default Tethys).

5.14.4 Vibrate When Ringing


The handset can be set to vibrate when ringing (default yes).
1. Select Sound.
2. In the Vibrate when ringing drop-down list, select Yes (default) or No.

5.14.5 Dial Pad Touch Tones


Enable or disable if a tone should be played when the keypad for dialing is tapped (default yes).
1. Select Sound.
2. In the Dial pad touch tones drop-down list, select Yes (default) or No.

5.14.6 Touch Sound


Enable or disable if a sound should be played when making a screen selection (default yes).
1. Select Sound.
2. In the Touch sound drop-down list, select Yes (default) or No.

5.14.7 Screen Lock Sound


Enable or disable if a sound should be played when locking or unlocking the screen (default yes).

59 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

1. Select Sound.
2. In the Screen lock sound drop-down list, select Yes (default) or No.

5.14.8 Hearing Aid Compatibility


Hearing aid compatibility can be enabled for the handset. HAC compliant wireless phones are capable of
working with hearing aids that have a minimal immunity rating of at least 2.
1. Select Sound.
2. In the Hearing Aid Compatibility drop-down list, select Yes or No (default).

5.14.9 Start-Up Connection Failure Sound


Indicate with a sound when the connection to the Unite server fails during start-up. The sound volume for
the indication is the same as the regular sound volume on the handset.
1. Select Sound.
2. In the Start-up connection failure sound drop-down list, select Yes or No (default).

5.14.10 Vibrate for Incoming Message During Call


Use this parameter to change the behavior of the vibrator when an alert or message is received during an
ongoing call. The default behavior is to only vibrate when a priority 1 message is received. Messages
without vibration are indicated with (in-band) sound only.

Do the following to change what type of messages the handset vibrates for during an call:

Breakthrough messages will override this parameter value.

1. Select Sound.
2. In the Vibrate for incoming message during call drop-down list, select one of the following vibration
behaviors:
− Yes (vibrate for all messages)
− No (don't vibrate for any message)
− For priority 1 only (default)
− For priority 2 - 8 and above

5.14.11 Minimum Volume


It's possible to prevent the handset from being muted/silenced by specifying a minimum volume level for
ringtones and notifications. If a user tries to set the volume below the specified minimum level, the handset
will automatically set the volume back to the minimum level.
1. Select Sound → Volumes.
2. In the Minimum volume drop-down list, select one of the following volume levels:
− Silent (no restriction)
− Vibrator only (default 19 )
− Volume 1 - 7

19. Only the default value if the Ascom Myco launcher is enabled.

TD 93072EN / 08 October 2020 / Ver. R 60


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

5.14.12 Message Volume


Use this parameter to change the sound volume for incoming alerts and messages. By default, the message
indication volume is the same as the ring signal volume. The message indication volume can be changed to
a volume level separate from the ring signal volume, or silenced completely, if the Minimum volume
parameter allows this (refer to 5.14.11 Minimum Volume, page 60).
While in a call, the (in-band) message indication sound always has the same volume as the voice
stream.

Do the following to change the message indication volume:

Breakthrough messages and the Minimum volume parameter will override this parameter value.

1. Select Sound → Volumes.


2. In the Message volume drop-down list, select one of the following volume levels:
− Ring volume (default)
− Silent
− Volume 1 - 7

5.15 Languages
Defines the default operating language for the handset. If not set, the default language is English (United
States). This setting can be changed by the handset user.

Select Languages. In the Language drop-down list, select the language to be used.
Not all languages in the drop-down list are fully supported by the handset. For a list of supported
languages refer to the Data Sheet, Ascom Myco 2 Wi-Fi and DECT Smartphone, TD 93220EN or
theData Sheet, Ascom Myco 2 Wi-Fi and Cellular Smartphone, TD 93221EN.

5.16 Date and Time


In Date & time, time and date parameters can be configured.
1. Select Date & time. In the *Use 24-hour format, select Yes (default) or No.
2. In the *Choose date format drop-down list select one of the following:
The separator character depends on chosen locale, for example, in the US the separators are
"/" and in Sweden "-" (standard Android settings.)

− Regional (default)
− MM/DD/YYYY - For example 01/31/2015 (also called US).
− DD/MM/YYYY - For example 31/01/2015 (also called Europe).
− YYYY-MM-DD - For example 2015-01-31 (ISO 8601).
3. In the Automatic date & time drop-down list, select Enable (default) or Disable.
4. In the Automatic time zone drop-down list, select Enable (default) or Disable.
If Disable is selected, select a time zone from the Select time zone drop-down list. Default time zone is
London, Dublin (UTC+0:00).

61 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

Important

The Automatic time zone functionality is only applicable for the cellular handset version.
For the Wi-Fi only handset version, select a time zone in the Select time zone drop-down
list.

5. In the NTP server address field, enter the string to the time server. The handset's automatic date &
time is synchronized with the NTP server.
This parameter requires a reboot to take effect, and the Automatic date & time parameter to
be enabled. If the address is cleared a default NTP server address is used. The default
address is the address of an external NTP server. Firewalls might restrict access, and prevent
this functionality from working as intended.

5.17 Security
Use the Security configuration parameters to set the password policies for the handset.
The password polices can be set from either the handset, or through the Device Manager/third-
party MDM, but the strongest policies will always be used. To prevent password policy inconsisten-
cies, it's recommended to always set password policies from the same place.

5.17.1 Admin Password


Set the password required for accessing admin settings on the handset.
The default admin password is 40022. It is recommended to change this default password as soon
as possible.

5.17.2 Make Passwords Visible


Enable or disable if the last entered character in a password should be visible for a short period of time
when entering a password.
• Yes (default)
• No

5.17.3 Password Policy


Set the policy for how passwords should be used in the handset. The available parameters in this section
change depending on the Quality parameter choice.

Quality
Sets the password requirements for the handset.

The current password will remain until the user has set a new one.

1. Select Security → Password policy. In the Quality drop-down list, choose one of the following policies:
− Unspecified (default) - No requirements.
− Something - Requires a password, but no further requirements.
− Numeric - Password must contain numeric characters.

TD 93072EN / 08 October 2020 / Ver. R 62


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

− Alphabetic - Password must contain alphabetic characters (or other symbols).


− Alphanumeric - Password must contain both numeric and alphabetic characters (or other symbols).
− Complex - Password must contain at least one letter, one numerical digit, and one symbol.

Important

The Unspecified or Numeric option must be selected for shared phones if the badge login
feature is enabled.

Minimum Letters (Complex Only)


Sets the minimum number of letters required in the password (default 1). A value of 0 means there is no
restriction for the number of letters. The maximum number that can be set is 16.

Minimum Lower Case (Complex Only)


Sets the minimum number of lower case letters required in the password (default 0). A value of 0 means
there is no restriction for the number of lower case letters. The maximum number that can be set is 16.

Minimum Upper Case (Complex Only)


Sets the minimum number of upper case letters required in the password (default 0). A value of 0 means
there is no restriction for the number of upper case letters. The maximum number that can be set is 16.

Minimum Non-Letter (Complex Only)


Sets the minimum number of non-letter characters (numerical digits or symbols) required in the password
(default 0). A value of 0 means there is no restriction for the number of non-letter characters. The maximum
number that can be set is 16.

Minimum Numeric (Complex Only)


Sets the minimum number of numerical digits required in the password (default 1). A value of 0 means there
is no restriction for the number of numeric digits. The maximum number that can be set is 16.

Minimum Symbols (Complex Only)


Sets the minimum number of symbols required in the password (default 1). A value of 0 means there is no
restriction for the number of symbols. The maximum number that can be set is 16.

Minimum Length (Not Available for Unspecified or Something)


Sets the minimum allowed password length (default 4). The minimum length that can be set is 4, and the
maximum is 16.

Maximum Failed Password for Wipe


Setting this to a value greater than zero enables a built-in policy that will perform a handset wipe after too
many incorrect handset-unlock passwords have been entered (default 0). The maximum number or failed
password attempts that can be set is 50.

Expiration Timeout
Sets the password expiration time (default 0). The number set is the number of days it takes before the
password expires. A value of 0 means there is no password expiration. The maximum number of days that
can be set is 1000.

63 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

Maximum Time to Lock


Sets the maximum time in seconds the user is allowed to set as sleep timeout (default 0). A value of 0
means there is no restriction. The maximum number of seconds that can be set is 1800.

History Length (Not Available for Complex)


Sets the length of the password history (default 0). The user will not be able to enter a new password that is
the same as a password in the history. A value of 0 means there is no restriction. The maximum number of
passwords in the history that can be set is 100.

5.17.4 Disable Camera


The handset camera is enabled by default, but can be disabled to block the user from accessing the
camera functionality.

Important

Disabling the camera will also disable the barcode scanning functionality on the handset.

Do the following:
1. Select Security → Camera.
2. In the Disable camera drop-down list, select Yes to disable the handset camera, or No (default) to
enable it.
The Camera app icon will be visible to the user even after disabling the camera functionality, refer
to 5.10 App Customization, page 54 for instructions on how to hide app icons on the handset.

5.17.5 Screen Lock Type


Decides if the user needs to perform an action to unlock the handset.

The screen lock configuration can be set up on the handset, if it is not a shared phone, or in the Device
Manager. It is strongly recommended to set up the screen lock configuration using the PIN or Password
option in the Device Manager.

The Use device setting option enables screen lock configuration on the handset and in some cases can
result in an unsupported configuration.
1. Select Security → Lock screen.
2. In the Screen Lock Type drop-down list, choose between:
− Use device setting - The screen lock type is configured on the handset.

TD 93072EN / 08 October 2020 / Ver. R 64


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

The Use device setting option is automatically selected in the Device Manager after handset
upgrade to firmware version 12.X.X.

The Use device setting option is automatically selected in the Device Manager in the specific
cases after the Screen Lock Type configuration has been updated on the handset:
• From None, Swipe, or Password configured in the Device Manager to PIN configured on the
handset.
• From PIN configured in the Device Manager to Password configured on the handset.
Other changes performed on the handset do not affect the Screen Lock Type configuration in the
Device Manager.

The Use device setting option is not supported for shared phones.

• None - The screen lock feature is disabled. This option enables insecure access to the handset.
• Swipe - The user needs to swipe the screen to unlock the handset. This option enables insecure access
to the handset.
• PIN - The user needs to enter their PIN code to unlock the handset.
• Password - The user needs to enter their password to unlock the handset.
• Default (do not use) - The default option that must be changed during the screen lock type configuration.

5.17.6 Automatic Lock Time


If No is chosen, the screen locks after a set time when pressing the Power button, see 5.17.6
Automatic Lock Time, page 65.

Sets the time before the screen locks when the handset has gone into sleep mode.
1. Select Security → Lock screen.
2. In the Automatic lock time drop-down list, choose between:
− Immediately
− 5 seconds (default)
− 15 seconds
− 30 seconds
− 1 minute
− 2 minutes
− 5 minutes
− 10 minutes
− 30 minutes
This parameter does not apply if the handset is put to sleep via a press on the Power button and
the screen is set to instantly lock when the user presses the Power button, see 5.17.7 Power
Button Instantly Locks, page 66.
This parameter does not set the time for how long the handset can be inactive before going into
sleep mode. For more information, see 5.13.3 Sleep Timeout, page 57.

65 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

5.17.7 Power Button Instantly Locks


Decides if the screen should instantly lock when the user presses the Power button.
1. Select Security → Lock screen.
2. In the Power button instantly locks drop-down list, choose between:
− Yes (default)
− No
If No is chosen, the screen locks after a set time when pressing the Power button, see 5.17.6
Automatic Lock Time, page 65.

5.17.8 Notifications on Lock Screen


Sets the display of lock screen notifications.
1. Select Security → Lock screen.
2. In the Notifications on lock screen drop-down list, choose between:
− Show all notification content (default) - The user will be able to see all notifications and their content
on the lock screen.
− Show all notifications but hide sensitive content - Notifications are shown on the lock screen, but the
content is hidden so that only the name of the source of the notification is shown. For example,
Myco Launcher – Contents hidden is shown for all alerts.
− Do not show notifications – Notifications are not shown on the lock screen, but are still indicated
with sound and vibration from the handset.
If Show all notifications but hide sensitive content is chosen while the screen lock type is neither
PIN nor Password, the behavior will be the same as for “Show all notification content”.

The user is not able to see any alert information such as type or priority on lock screen when the
parameter is set to Show all notifications but hide sensitive content. It is not recommended to set
the parameter to Show all notifications but hide sensitive content or Don’t show notifications if
the handset is to be used to display information from connected medical devices.

5.18 Telephony
In Telephony, parameters related to phone calls can be set.

5.18.1 Emergency Numbers for Device Without SIM

Only applicable for Wi-Fi or DECT handsets and cellular handsets without SIM cards.

This parameter overrides Androids lookup of emergency numbers. Refer to the Device Manager online help
for further details.
1. Select Telephony.
2. In the Emergency numbers for device without SIM field, type the emergency numbers to use
(separated by commas).

TD 93072EN / 08 October 2020 / Ver. R 66


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

5.18.2 Power Button Ends Call

This function is only applicable for GSM/3G calls with the cellular handset version.

If enabled, the Power button (on the handset's upper left side) can be used to end an ongoing GSM/3G call.

Select Telephony. In the Power button ends call drop-down list, choose between:
• Yes
• No (default)

5.18.3 Default Call Priority


Sets the priority of phone calls. The call priority will be compared to priorities of Call setup messages (for
example an incoming PTT session) in order to decide what should happen when they are received. If an
incoming Call setup message has Answer mode set to Auto and higher priority than the ongoing call, the
incoming message will disconnect the ongoing call and connect the incoming Call setup instead.

Select Telephony. In the Default call priority drop-down list, choose between:
• Higher than any call setup (default)
• Priority 1-9
• Lower than any call setup
The handset will always reject incoming calls with a busy tone while in a call setup call, regardless
of the default call priority configured for the handset.

5.18.4 Default Call Carrier


Sets the preferred call carrier to be used for outgoing calls. If the preferred call carrier is unavailable at the
time of the outgoing call, the other call carrier will be used. This setting is only applicable if the device has a
valid cellular SIM card and a configured Ascom VoIP account.

Select Telephony → Prefer to call with. The options are:


• Ask for every call (default) – the user will be prompted every time an outgoing call is made.
• Ascom VoIP (Wi-Fi) – calls over Ascom VoIP are preferred when the device is connected to the
appropriate Wi-Fi network.
• Cellular (3G) – calls over 3G are preferred when the device has reception.
If you select Ask for every call, the dialog window will appear for every call. The user can hide this window
by doing one of the following:
• Change the default call carrier to Ascom VoIP or Cellular through Settings → Telephony → Prefer to call
with. The selected call carrier option will be set as default and the dialogue window will be hidden for all
future calls.
• In the dialog window that appears when an outgoing call is made, first check Always use this for
calls box and then select either Ascom VoIP or Cellular. This will set the selected call carrier option as
default and hide the dialogue window for all future calls.

5.18.5 Call Setup Notification Type


Sets the type of notifications to be used for Call setup messages. Select As call if the notification should be
indicated as an incoming call, or As alert if the notification should be indicated as an incoming alert.

67 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

Select Telephony. In the Call setup notification type drop-down list, choose between:
• As call (default)
• As alert

5.18.6 Ascom VoIP


The Ascom VoIP menu is used to configure parameters related to VoIP calls.

A protocol is a set of standard rules for data traffic required to send information over a communication
channel. Communication protocol is basically following certain rules so that the system works properly. The
handset only supports the SIP protocol.

SIP Transport
Defines the protocol (UDP, TCP or TLS) to use for SIP signaling. The TLS setting requires the PBX certificate
to be uploaded as a trusted server (root) certificate.

Allow SIP over 3G


Enables SIP calls over 3G when WiFi network is not available. If the user enters WiFi coverage during an
active SIP over 3G call, the call is not disconnected, the handset connects to WiFi network when the call is
finished.
1. Select Telephony → Ascom VoIP.
2. In the Allow SIP over 3G drop-down list, choose between:
− Yes
− No (default)

Primary SIP Proxy


Defines the primary SIP PBX by either an IP address, a domain name, or an IP address together with a port
number. If left blank, SIP telephony will be disabled.

Examples of valid formats are:


• 192.168.1.1
• proxy1.mydomain.com
• 192.168.1.1:5060
Domain names are resolved using DNS records, and refer either to a DNS A record (address record) or a
DNS SRV record (service record). While an A record is a single IP address, a SRV record originates from
multiple A records, of which the handset tries the two highest prioritized IP addresses it receives in the DNS
response when it registers with the primary SIP PBX.

If the handset fails to register with the primary SIP proxy, it can register with the optional secondary SIP
proxy.

Secondary SIP Proxy


Defines the optional secondary SIP proxy, which is used if the handset fails to register with the primary SIP
proxy. See definition examples in Primary SIP proxy above.

When the handset has connected to the Secondary SIP proxy, it continuously tries to reconnect to the
Primary SIP proxy.

TD 93072EN / 08 October 2020 / Ver. R 68


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

Listening Port
The port that the handset listens to for incoming SIP traffic (default 5060).

SIP Proxy ID
Defines the SIP proxy by a domain name.
If this parameter is set, the SIP message headers will contain this ID instead of what's entered in
the Primary/Secondary SIP proxy fields.

SIP Register Expiration


Defines the number of seconds for register expiration to the PBX (default 120).

Endpoint ID
Defines the identity to register with at the PBX, typically the phone number or name.
This parameter is only needed if the identity at the PBX differs from the Unite PUN. If left blank, the
Unite PUN will be used instead.

If shared phone is enabled, and the user receives SIP credentials from the server-side, this parameter will
be overridden by the user-specific SIP credentials. The received SIP credentials will then be used for the
duration of the login. When the user is logged out, the endpoint ID specified in this parameter will be used
again.

If shared phone is enabled, and the endpoint ID is specified, the handset can be used for SIP calling,
without requiring a login on the handset. For more information on shared phone, see 3.2.10 Shared Phone,
page 15.

Password
Defines the password to use when registering at the PBX.
If shared phone is enabled, the password can be overridden in the same way as the Endpoint ID
(more information above).

VoIP Phone Number


The phone number assigned to this SIP registration. Setting a VoIP phone number will override other
parameters that may specify the phone number of the device and give it a fixed number. The VoIP phone
number can be used by applications that require the phone number of the device.

If left blank, the value used for registration in the SIP PBX will be used as number, see description for the
Endpoint ID, page 69.

Codec Configuration
Defines which codec to use for speech (default G711 A-law). A codec encodes a stream or signal for
transmission. Codecs are often used in streaming media applications. This setting defines how to packetize
and compress the sound in a voice call.
1. Select Telephony → Ascom VoIP.
2. In the Codec configuration drop-down list, select the applicable codec:
− G.711 A-law (EU, and also more common in the rest of the world)

69 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

− G.711 u-law (US, especially North America, and Japan)


− G.722

Secure RTP Mode


When enabled, voice is sent over Secure RTP, if the other party also supports Secure RTP. This parameter
controls the encryption method offered by the handset, during negotiation setup of a secure RTP call
(default off).
1. Select Telephony → Ascom VoIP.
2. In the Secure RTP mode drop-down list, select the preferred SRTP encryption:
− Off (default)
− AES_CM_128_HMAC_SHAI_32
− AES_CM_128_HMAC_SHAI_80
− AES_CM_192_HMAC_SHAI_32
− AES_CM_192_HMAC_SHAI_80
− AES_CM_256_HMAC_SHAI_32
− AES_CM_256_HMAC_SHAI_80

Secure RTP Negotiation (visible If Secure RTP Mode Is Enabled)


Defines which style of SIP negotiation that should be used when deciding if a call should be set up using
Secure RTP (SRTP).
1. Select Telephony → Ascom VoIP.
2. In the Secure RTP negotiation drop-down list, select the preferred negotiation method:
− Retry with RTP (default) - Handset will offer an encrypted voice connection only but make a new
attempt without encryption if the call is rejected by the remote party.
− Offer SRTP and RTP - Both encrypted and non-encrypted voice connections will be offered and the
remote party can choose which to use. This parameter should be used to achieve compatibility with
SIP servers that only support one of these methods.

DTMF Type
Defines the path the DTMF signaling should take. If set to RFC 2833 (default), the DTMF signaling is sent in
the RTP stream (from handset to handset). If set to SIP INFO, the DTMF signaling is sent using SIP signaling
(through the PBX).

Hold Type
Defines which type of hold to send when the handset puts a call on hold. The selection depends on what
type of hold the PBX support.
1. Select Telephony → Ascom VoIP.
2. In the Hold type drop-down list, select the preferred hold type:
− inactive (default)
− sendonly
− sendonly with connection information 0.0.0.0

TD 93072EN / 08 October 2020 / Ver. R 70


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

MOH Locally
Play local Music on Hold if the remote part doesn't provide it.
1. Select Telephony → Ascom VoIP.
2. Select the MOH locally box to use the locally stored Music on Hold.
3. In the Hold type drop-down list, select inactive.

Direct Signaling
Defines whether calls originating from other sources than the configured SIP Proxy should be accepted or
redirected using "USE PROXY" message (default no).

Active Mode During Call


Defines whether the Wi-Fi shall use active mode during calls (default no). The default is to use the power
save mode U-APSD, which consumes less power than active mode.

5.18.7 Microphone Gain


It is possible to set the microphone gain offset to raise or lower the volume of the handset microphone. This
can be useful in unusually noisy/quiet environments, or in other environments with special requirements.

Caution
The handset is optimized to use with a 0 dB offset. Changing the offset may result in lower
sound quality when making a call.

To set the microphone gain offset, do the following:


1. Select Telephony → Microphone gain.
2. Change the microphone gain value for either VoIP or GSM/3G depending on the handset and system
used. A value between +6 dB and -25 dB can be set (default 0 dB).

5.18.8 Voicemail
If the handset is using a voicemail service, voicemail settings must be configured. If the handset is operating
Wifi or Wifi + Cellular mode, the vociemail settings are configured in the Telephony → Voicemail menu. If the
handset is operating in DECT mode, the voicemail settings are configured in the DECT Suppl. services
menu and the settings configured in Telephony → Voicemail are not applied. For handsets in DECT mode,
the number of new voice messages is not shown.

If the handset is used in Wi-Fi mode, do the following:


1. Select Telephony → Voicemail .
2. Enter the number of the voicemail service in either the VoIP voicemail number or the Cellular
voicemail number field, depending on the handset and the type of voicemail inbox.
3. If the system has a server responsible for Message Waiting Indication (MWI), enter the number to the
server in the Message centre number field.
If the handset is used in DECT mode, do the following:
1. Select DECT Supplementary services.
2. Enter the number of the voicemail service in the Voicemail field. The number can contain the number
of the voicemail service only or the number of the voicemail service with the user’s voicemail PIN for
automatic logon.

71 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

If the voicemail number contains the user’s voicemail PIN, the voicemail server may require
extra time to start processing it after connection to the voicemail service has been established.
The P (HEX50) character is used in the voicemail number to indicate a pause (2 seconds by
default) that should be taken by the DECT system before dialing the user’s voicemail PIN. For
example, if 667326PPP8767 is entered in the Voicemail field, the DECT system dials
voicemail service number 667326 and after a pause dials user’s voicemail PIN 8767. The
required number of pause characters depends on the PBX.
3. Tap OK.
The configuration of the DECT supplementary services must match the DECT supplementary
services configuration on the Base Station. The default values are normally uploaded from the
Device manager and do not need manual configuration.

5.19 Push-To-Talk
For further details about the Push-to-talk feature, refer to the Function Description, Push to Talk,
TD 92493EN.

Push-to-talk (PTT) group call provides instant voice connectivity to a group of devices. When a person in the
group wants to talk, the person taps and holds down a button to activate the microphone on the handset.

5.19.1 Use Alarm & Multi-Function Button


The Alarm/Multi-function button on the top of the handset can be used as a PTT button, if not configured for
any alarm functionality. Pressing and holding the PTT button during a PTT call session opens the
microphone for communication.

Do the following to configure the PTT button functionality:


1. Select Push-to-talk. In the Use Alarm & Multi-function button drop-down list, select one of the
following:
− Yes - Will be used as a PTT button during a PTT session.
− No (default) - Will not be used as a PTT button.
The Alarm & Multi-function button can only be used as a PTT button when no alarm functionality
has been configured for either long-press or multi-press.

5.19.2 Configure a PTT Group Call

PTT group calls can only be configured through the Device Manager.

PTT group call sessions can be initiated from the PTT app on the handset. Do the following to configure a
PTT session for the handset:
1. Select Push-to-talk → Sessions, right-click and choose Add entry. Select the created Push-To-Talk
session menu.
2. In the Session name field, enter a name for the PTT session.
3. In the Priority field, enter the priority for the PTT session (default "6"). The lower the number, the higher
the priority.
− 1: the PTT session will cancel an ongoing call immediately.

TD 93072EN / 08 October 2020 / Ver. R 72


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

− 2-9: the PTT session will disconnect an ongoing call after a 10 seconds delay if answer mode is set
to auto, and the priority is higher (i.e. has a lower number) than the priority of the ongoing call. See
5.18.3 Default Call Priority, page 67 for instructions on how to configure the default call priority.
4. In the Group number field, enter the group number to which the call setup for the PTT session should
be sent (groups are defined in Unite CM/Unite CS/Unite Admin).
5. In the Display text field, enter the text shown in the display during the PTT session.
6. In the PTT session signal drop-down list, select the type of signal the PTT session uses (default 2
beeps). The following signals can be used:
− Silent (no signal)
− Beeps (1-5 or 10 beeps)
− Siren
7. In the Conference number field, enter the call number to the conference bridge. The call number is
sent when a PTT session is initiated from or accepted by the handset.
8. In the Answer mode drop-down list, select which type of answer mode the handset should use for the
PTT session.
− Manual: the user must accept the session.
− Auto (default): the session will be setup automatically.
If there is an ongoing call with same or higher priority, the PTT call will only connect when
the user manually chooses to accept/join the PTT call, even if Answer mode is set to Auto.

9. In the Speaker mode drop-down list, select which speaker mode the handset should use for the PTT
session.
− Normal: the session starts with the speaker turned on.
− Loud (default): the session starts with the loudspeaker turned on.
10. Choose if the PTT notification should be indicated as an incoming call, or as an incoming alert, by
setting the parameter in 5.18.5 Call Setup Notification Type, page 67.

5.20 DECT Suppl. Services


The DECT supplementary services determine how to handle a call if for example busy or not answered by
the user. These settings are configured on the DECT Base Station and must be applied on the Myco
handset.

The supplementary services configuration can be applied from the Device manager or done manually on
the handset. The following syntax is used for code values of the supplementary services:

$ - Placeholder for user provided digits, e.g. a phone number

$# - Number of digits decided by end indicator #

$(N) - Number of digits decided by N

5.20.1 DECT Supplementary Services in Device Manager


If the DECT supplementary services are configured in the Device manager, they can be remotely applied to
a Myco handset or to multiple Myco handsets using a template.
The configuration of the DECT supplementary services must match the DECT supplementary
services configuration on the Base Station.

73 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

1. Open the Device Manager in the Unite CM/Unite CS.


2. Do one of the following:
− To update a template, on the Templates tab, select the template and right-click and click Edit.
− To update an individual handset, on the Numbers tab, select the number and click Edit.
3. Open the Dect supplementary services parameters.
4. Update the parameter values as required.
5. Click OK to save changes. If the settings of an individual handset have been updated, they will be
synchronized automatically. If a template has been updated, it must be re-applied to the handset. Refer
to Apply Template.

5.20.2 DECT Supplementary Services on the Handset


The default values are normally uploaded from the Device manager and do not need a manual configura-
tion. If required, the DECT supplementary services can be checked or updated on the handset.
The configuration of the DECT supplementary services must match the DECT supplementary
services configuration on the Base Station.

1. Go to the DECT Supplementary services menu.


2. To see parameters and values, scroll through the settings.
3. To update a value, tap the desired parameter and edit its value.
4. Tap OK.
The settings are applied on the handset and the handset configuration in Device Manager is updated.

5.21 DECT Frequency


The DECT frequency band is specific for different regions in the world. By default, frequency configuration
is done automatically on the handset. In special cases, a manual configuration might be needed. The
manual configuration is available when the following preconditions are fulfilled:
• No subscriptions have been added to the handset.
• The default frequency settings have not been changed.
• The factory reset is performed.
• The DECT chipset is turned on.
1. Go to the DECT Frequency settings menu.
2. Select the desired frequency band:
− Europe (1880-1900Mhz)
− US (1920-1930Mhz)
− Latin America (1910-1930Mhz)
− Brazil (1910-1920Mhz)
− Thailand (1900-1906Mhz)
3. Tap Back. Switch off and then switch on the DECT chipset.
The Frequency settings will become read-only. To enable the menu, perform a factory reset of the handset.

TD 93072EN / 08 October 2020 / Ver. R 74


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

5.22 In Charger
When the user places the handset in a desktop charger or charging rack, automatic operations, such as
muting, logout, clearing messaging or images, can be performed.

Caution
Settings configured in the In Charger section in Device manager are applied to handsets in
charging racks and desktop chargers.

5.22.1 Mute When Docked


If enabled, the handset is muted when placed in a desktop charger or charging rack. When the handset is
removed from the charger or charging rack, the previous sound settings are automatically restored.
1. Select In charger. In the Mute when docked drop-down list, select:
− Yes to enable mute when docked.
− No (default) to disable it.
This does not affect alerts with priority 1. These alerts will override the mute when docked setting.

5.22.2 Clear Messages When Docked


If enabled, all alerts and conversation messages are deleted when the handset is placed in a desktop
charger or charging rack. The handset will not receive any new alerts or conversation messages while
placed in the charger or charging rack.

Caution
Enable the Clear messages when docked parameter to be compliant with personal data
privacy regulations.

1. Select In charger.
2. In the Clear messages when docked drop-down list, select:
− Yes. This option is recommended for data privacy protection.
− No (default).

5.22.3 Clear Images When Docked


If enabled, images and videos are removed when the handset is placed in a desktop charger or charging
rack. The feature applies to images and video that are stored on the simulated SD, i.e. the camera app
default storage.
Images and videos taken with third-party apps are not affected as well as images and videos that
are synchronized to be stored on another platform, such as a cloud account.

1. Select In charger.
2. In the Clear images when docked drop-down list, select:
− Yes.
− No (default).

75 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

5.22.4 Unite Logout User When Docked


If enabled, the logged in user is logged out when the handset is placed in a desktop charger or charging
rack.
1. Select In charger.
2. In the Logout user when docked drop-down list, select:
− Yes to enable logout when docked.
− No (default) to disable it.

5.22.5 Send Status When Docked


If enabled, a special status message (IN_STORAGE_RACK) is sent to the Unite system when the handset is
placed in a desktop charger or charging rack.
1. Select In charger.
2. In the Send status when docked drop-down list, choose between:
− Yes.
− No (default).

5.23 Site Survey Tool for DECT


The site survey tool is used by technicians to plan base station locations for a DECT telephone system. With
the site survey tool you can determine the required number and positions of base stations. For information
about the site survey tool used for DECT network, refer to the Troubleshooting Guide, Ascom Myco
Smartphone, TD 93128EN.

5.24 Unite Login


The login functionality is enabled through the Unite CM/Unite CS configuration page, refer to the
Data Sheet, Unite Connectivity Manager, TD 92739EN.

The Login menu contains parameters used to configure the login functionality on the handset.

When login is enabled for the handset, users must log in to access features such as alert handling,
messaging, and My Services on the handset. Previously logged in user names can be stored in a recent
users list. The sections below describe the parameters used to configure this list.

5.24.1 Phone Mode


The phone mode parameter defines the usage profile for the handset. It is used by the server-side function-
ality to decide how to communicate with the handset, how the handset behaves, and how it is displayed in
the Unite Device Manager. It is also the parameter that dictates whether the handset is to be used as a
shared phone or not. For more information on shared phone, see 3.2.10 Shared Phone, page 15.
1. Select Login. In the Phone mode drop-down list, select:
− Personal / Temporary. The device has a fixed telephone number. Anyone with access to the user
login can login to the handset.
− Shared. Each user has a personal login, usually associated with their own telephone number. The
personal login can be used on any device that is setup as a shared device.

TD 93072EN / 08 October 2020 / Ver. R 76


CONFIGURATION MANUAL
Handset Configuration Ascom Myco

5.24.2 Number of Recent Users


Set the maximum number of recent user to be shown in the Recent users list on the User login screen. If set
to "0" the Recent users list is disabled on the handset.
1. Select Login. In the Number of recent users field, enter the number of recent users to be shown on the
handset (default "10").

The maximum number of recent users that can be set is "50".

5.24.3 Days to Remember Recent Users


Set the maximum number of days to keep a recent user in the Recent user list. If set to "0" the Recent users
list is disabled on the handset.
1. Select Login. In the Days to remember recent users field, enter the number of days to keep a recent
user in the Recent user list (default "31").

The maximum number of days that can be set is "31".

5.24.4 Enable User Availability Status

This parameter cannot be configured through the handset.

Defines if user availability status should be enabled for the handset. When enabled, the handset user can
set their current availability, for example "Available" or "Busy". The availability status can be used by server-
side functionality to decide how to communicate with the device, for example to avoid sending alerts to a
user with a "Busy" status.
The availability status sent from the handset is handled by an OAP client. The OAP client can also
be configured to remotely change the availability status on the handset, refer to the Function
Description, Ascom Open Access Protocol (OAP), TD 92215GB document.
1. Select Login. In the Enable user availability status drop-down list, select:
− Yes to enable availability status for the handset.
− No (default) to disable it.

5.24.5 Login Reminder


Defines if a login reminder should be enabled for the handset. The timer for the login reminder starts when
the handset is disconnected from a charging rack, is restarted, or when the user logs out from the handset.
The login reminder appears as a notification on the screen and is also announced by sound and vibration
from the handset.

The login reminder does not appear if the handset is placed in a charging rack.

1. Select Login.
2. In the Login reminder field, select:
− Yes (default) to enable a login reminder for the handset. In the Time for login reminder field, enter
the number of minutes before the login reminder appears (default “2”).

77 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Handset Configuration

− No to disable it.
The minimum number of minutes that can be set is “1”. The maximum number of minutes that can
be set is “10000”.

5.24.6 Credentials Type


Change this parameter to change the type of keyboard shown when the user is entering the login and
password.
Make sure that the keyboard used matches the password type used for the login functionality. This
parameter cannot be configured through the handset, therefore users cannot change the
keyboard type.
1. Select Login → User login.
2. In the Credentials type drop-down list, select one of the following keyboard types to use for the login
functionality:
− Alphanumeric
− Alphanumeric username, numeric password.
− Numeric username, alphanumeric password.
− Numeric.

TD 93072EN / 08 October 2020 / Ver. R 78


CONFIGURATION MANUAL
Related Documents Ascom Myco

6 Related Documents
Data Sheet, Ascom Myco 2 Wi-Fi and DECT Smartphone, TD 93220EN

Data Sheet, Ascom Myco 2 Wi-Fi and Cellular Smartphone, TD 93221EN

User Manual, Ascom Myco Smartphone, TD 93066EN

Troubleshooting Guide, Ascom Myco Smartphone, TD 93128EN

Data Sheet, Unite Connectivity Manager, TD 92739EN

Configuration Manual, Unite Connectivity Manager, TD 92735EN

Configuration Manual, Unite Communication Server, TD 92761EN

User Manual, Device Manager, TD 92855EN

Installation Guide, Ascom Unite Admin Desktop, TD 93083EN

System Description, Ascom VoWiFi System, TD 92313EN

System Description, Ascom Myco Cellular, TD 93104EN

Function Description, Ascom VoWiFi System, TD 92314EN

Function Description, Push to Talk, TD 92493EN

Function Description, IR Location System, TD 92179GB

Function Description, Location in Ascom VoWiFi System, TD 92607GB

Function Description, Product Licensing Overview, TD 92677GB

Function Description, Ascom Open Access Protocol (OAP), TD 92215GB

Configuration Notes, Ekahau RTLS, TD 92646GB

User Guide, Site Survey Tool, TD 92220GB

Installation and Operation Manual, Phonebook Service, TD 92360GB

Installation and Operation Manual, IPBS, IPBL and IPVM (10.1.X), TD92579EN

79 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Document History

7 Document History
Version Date Description

R 08 October 2020 General:


Editorial changes in the document.
Updated:
Note in 5.18.4 Default Call Carrier, page 67.

Q 26 September Updated:
2019 3.2.10 Shared Phone, page 15 to describe the Allow user to
log in without PIN and the Allow user to add empty card
options for shared phones.

P 29 April 2019 New:


3.2.13 Hunt Group Name, page 19
Updated:
5.4 Ascom Messaging, page 44 to add information on DECT
broadcast messaging.
5.7 Location Services, page 50 to add a note about the IR Site
Survey Tool application.
3.2.10 Shared Phone, page 15 to describe the device
extension option for shared phones.
5.22 In Charger, page 75 to specify the same handset
behavior in a desktop charger and charging rack.

O 14 December 2018 New:


5.7.4 DECT Base Station Positioning, page 53
5.7.2.1 Zone Presence Configuration, page 52
Updated:
5.22.2 Clear Messages When Docked, page 75
5.24.5 Login Reminder, page 77 3.2.10 Shared Phone, page 15
5.18.8 Voicemail, page 71 5.4 Ascom Messaging, page 44
3.2.2 QR Code Installation and NFC, page 11 3.1.1 Device
Manager Prerequisites, page 7
3.2.6 Enable the Ascom Myco Launcher User Interface, page
14
4.2.1 Add Certificates to the Handset, page 22
1 Introduction to Configuration Manual, page 1
4.2.3 Upgrade or Downgrade the Handset Software, page 22
5.18.6 Ascom VoIP, page 68
5.7 Location Services, page 50
5.7.1 Basic Location, page 51

TD 93072EN / 08 October 2020 / Ver. R 80


CONFIGURATION MANUAL
Document History Ascom Myco

N 20 August 2018 New:


5.4.1 Advanced security, page 45
Updated:
5.4 Ascom Messaging, page 44
Push-Button Alarm section in 5.6 Alarm- and Multi-Function
Button, page 48
5.13.2 Owner ID/Name, page 57 MOH Locally section in 5.18.6
Ascom VoIP, page 68.

M 21 June 2018 New:


5.17.5 Screen Lock Type on page 62.
Updated:
3.2.10 Shared Phone on page 17.
5.11 Shortcut Customization on page 53.
5.23 Site Survey Tool for DECT on page 73.
5.24.6 Password Type on page 73.

81 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Document History

L 14 May 2018 New:


3.2.4 Subscribe Handset to DECT System on page 15.
5.3 DECT Subscriptions on page 40.
5.12.4 DECT Logs on page 56.
5.20 DECT Suppl. Services on page 70.
5.21 DECT Frequency on page 71.
5.23 Site Survey Tool for DECT on page 73.
Updated:
1. Introduction Configuration Manual on page 1.
2. Pre-Installation on page 6.
2.1 VoWiFi and DECT System IP Addresses on page 6.
3. Installation of Handsets on page 8.
3.1.2 Create a Network Template on page 9.
3.2.1 Easy Deployment on page 12.
3.2.2 QR Code Installation and NFC on page 13.
3.2.3 Manual Installation on page 14.
3.2.9 Google® Mobile Services (GMS) Configuration on page
16.
4.2 Handset Maintenance on page 21.
4.2.8 Replace Handsets on page 27.
5. Handset Configuration on page 31.
5.18.1 Emergency Numbers for Device Without SIM on page 64.
6. Related Documents on page 76.
B.1.1 SIP (VoWiFi only) on page 98.
B.2 Voice Traffic (VoWiFi only) on page 98.
General:
Information about how to handle the handset in DECT
environment has been added throughout the document where
appropriate.

TD 93072EN / 08 October 2020 / Ver. R 82


CONFIGURATION MANUAL
Document History Ascom Myco

K 1 February 2018 New:


3.2.11 Central Phonebook on page 19.
3.2.12 Company Phonebook on page 19.
5.10.2 Show Notification on Top Display on page 52.
5.11 Shortcut Customization on page 53.
5.22.3 Clear Images When Docked on page 73.
5.22.5 Send Status When Docked on page 73.
Updated:
4.2.7 Encrypt Data on the Handset on page 27. Added note
about slow startup when the handset is encrypted.
5.8 NFC on page 52. Added note about NFC applications.
5.10 App Customization on page 52. Added information about
notifications on top display.
5.10.1 Visibility on page 52.
5.12.3 Debug on page 54. Added note about PCAP log files.
5.13.2 *Owner ID/Name on page 55. Added note about default
value.
5.13.5 Top Display Alert Formatting on page 56. Added note.
5.18.6 Ascom VoIP on page 66. Added information about the
parameter Allow SIP over 3G.
Appendix A. Easy Deployment on page 83. Added two notes
about Wi-Fi connection during Easy Deployment.

J 2 January 2018 New:


5.17.5 Automatic Lock Time on page 63.
5.17.7 Power Button Instantly Locks on page 64.
5.17.8 Notifications on Lock Screen on page 64.
5.24.5 Login Reminder on page 75.
Appendix C. Alert Categories on page 99.
Updated:
5.13.3 Sleep Timeout on page 55.

I 3 October 2017 New:


5.24.1 Phone Mode on page 74.
Updated:
5.2.4 Configure the Handset for Wi-Fi Networks on page 36.
Added info about captive portal detection parameter.
5.6 Alarm- and Multi-Function Button on page 47.
General:
Information about how to handle the shared phone feature has
been added throughout the document where appropriate.

H 26 June 2017 New:


4.2.5 Prepare a GMS Handset Version for a Factory Reset on
page 25.

83 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Document History

G 8 June 2017 New:


3.2.9 Google® Mobile Services (GMS) Configuration on page
16.
5.7.2 Configure Ascom IR Location on page 51.
5.8 NFC on page 52.
5.10.3 Google® Mobile Services (GMS) Customization on page
53.
5.18.4 Default Call Carrier on page 65.
Updated:
3.2.2 QR Code Installation and NFC on page 13.
5.2.2 Add a Wi-Fi Network Through the Device Manager on
page 33.
5.2.3 Add a Hidden Wi-Fi Network Through the Handset on
page 35.
5.4 Ascom Messaging on page 44.
5.10 App Customization on page 52.
Removed:
The parameters Active Network and Avoid Poor Connections
have been removed along with all information pertaining to it.
Information about lock-screen widgets has been removed.
The performance chapter has been removed.
General:
The entire document has been updated to include information
about Ascom Myco 2 hardware and related features, GMS
handset version and Lollipop updates.

F 14 October 2016 New:


5.2.6 Access Point Names on page 39.
5.2.7 Enable Cellular Data (Caution) on page 40.
5.9 Third-Party Integration on page 52.
5.14.2 Dialing Tone Patterns on page 57.
5.14.9 Start-Up Connection Failure Sound on page 58.
5.18.1 Emergency Numbers for Device Without SIM on page 64.
VoIP Phone Number on page 67.
• sendonly with connection information 0.0.0.0 on page 68.
Updated:
Text and layout fixes based on review feedback.
References to the Troubleshooting guide added throughout
the manual.
2.2 Configure Access Point Names (APN) on page 7. APN can
now be added through the Device Manager.
Removed:
Chapter 6 "Use Handset to Verify the VoWiFi System
Deployment" and Chapter 7 "Troubleshooting".

TD 93072EN / 08 October 2020 / Ver. R 84


CONFIGURATION MANUAL
Document History Ascom Myco

E 30 June 2016 New:


4.2.2 Remove Certificates from the Handset on page 22
5.14.10 Vibrate for Incoming Message During Call on page 58
5.14.12 Message Volume on page 58
6. Related Documents on page 76
Updated:
5.12.2 Status Logging on page 53
5.18.8 Voicemail on page 69
Other:
Added Android trademark information.
D 26 April 2016 New:
4.2.1 Add Certificates to the Handset on page 22.
4.2.7 Encrypt Data on the Handset on page 27
5.6.3 Use Top Button for Third Party Apps on page 49.
5.17.4 Disable Camera on page 62
5.18.8 Voicemail on page 69
5.24.4 Enable User Availability Status on page 74
5.24.6 Password Type on page 73
7.1.1 Setting up the handset for wireless Wireshark traces on
page 62
Updated:
3.2.3 Manual Installation on page 14. Added information about
using an USB cable to import certificates.
4.2.6 Perform a Factory Reset on page 26. Updated the
descriptions a bit.
5.1.2 Ascom Settings on page 32. Added a short description of
the diagnostics tool.
5.2 Network on page 32. Several changes/additions/rewritten
sections. Details about certificates, hidden SSID, server
validation, avoid poor connections, and automatic network/
frequency band selection.
5.4 Ascom Messaging on page 44. Note about when not to
use "only trusted".
5.6 Alarm- and Multi-Function Button on page 47. Third-party
app use.
5.7.3 Configure the Handset for a Cisco/Ekahau RTLS Solution
on page 51. Added a Note about frequency bands.

85 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Document History

D 26 April 2016 5.12.3 Debug on page 54. RPCAP and FTP upload details
added. Added Note about removing logs after use.
5.16 Date and Time on page 59. Note about Automatic time
zone.
5.17 Security on page 60. Details about password policies.
Added an IMPORTANT text to 5.17.4 Disable Camera on page
62.
5.18.3 Default Call Priority on page 65. Added Note about call
setup and busy tone.
5.24 Unite Login on page 73. Updated login functionality
description.
B.3 Other Services with Fixed Local Ports on page 98. Added
RPCAP TCP to the table
C 15 December 2015 Added:
3. Installation of Handsets on page 8 - Restructured and
rewritten. Many new sections added.
5.1 Admin Settings Menu in the Handset on page 32 - Detailed
instructions on how to configure the handset through the
handset admin menu added.
6.1 Site Survey Tool on page 61
Updated:
4. Maintenance and Management on page 21 - New title.
Moved sections from the old chapter 3 into this chapter
(management part).
5. Handset Configuration on page 31 - instructions for many
parameters updated/added.
Other:
Added link sections to the beginning of each chapter/section.

B 14 October 2015 Added:


The 5. Handset Configuration on page 31 chapter rewritten to
better reflect the parameter settings available in the Handset/
Device Manager, and several new sections where added to
the chapter.
Updated:
1.1 Abbreviations and Glossary Configuration Manual on page
2.
4.2.4 Upgrade the Handset Functionality Using a License on
page 23.
A.5.2 DHCP Vendor Options Explained on page 88.
Other:
General quality checks and text improvements.

A 2 April 2015 First version.

TD 93072EN / 08 October 2020 / Ver. R 86


CONFIGURATION MANUAL
Document History Ascom Myco

PA7 9 February 2015 Second draft.

PA2 7 November 2014 First draft.

87 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

Appendix A Easy Deployment


With the Easy Deployment process, a handset is installed by using a (staging) WLAN, with a predefined
SSID and security profile.
Easy Deployment can only be used in a 2.4 GHz staging WLAN. This is the default frequency band
of the handset, when switched on. Thereafter the production WLAN is used with any configured
channel and band.
Make sure to have the handset within Wi-Fi coverage from the beginning of Easy Deployment. If
not, the handset will fail to connect to the Unite CM/Unite CS.

If the handset fails to reach internet from Wi-Fi during Easy Deployment and switches to 3G, the
handset will fail to connect to the Unite CM/Unite CS. To avoid this, it is recommended to set the
parameter Captive Portal Detection to No, see 5.2.4 Configure the Handset for Wi-Fi Networks,
page 36.

TIP: Compared to i62 Easy Deployment, there are two changes: the VCI string ends with 3
(1.3.6.1.4.1.27614.2.3) instead of 2, the vendor Option 43 printable text needs to have wss:// before the IP
address (Printable text: \x01\x05Ascom\x02\x12wss://[IP address]).

A.1 Prerequisites
• The WiFi network needs at least one AP on the 802.11b/g radio, that allows access to the Unite CM/
Unite CS and uses the following default configuration, which cannot be changed:

SSID AWS-INIT
Security key: WPA-PSK / WPA2-PSK

WPA-PSK passphrase: AWS-INIT

• In the handset, all other network parameters must be at their default settings, which means for instance:

802.11 protocol: Automatic Wi-Fi network selection

802.11b/g/n channels: 1,6,11,36,40,44,48,149,153,157,161,165

World mode regulatory domain: World mode (802.11d)

• If it is used in the Unite CM/Unite CS server, the password to log in is needed.


• The Unite CM/Unite CS server port must be open and not blocked.
• No other networks than AWS-INIT are configured in the handset.
• The DHCP offer for the AWS-INIT network must include an IP address of an NTP server, to provide the
handset with the correct system time (needed for certificate validations).
The intended number to be used by a handset, is entered from the handset's keypad, after a
successful first access to the Unite server (Unite CM/Unite CS).

The Easy Deployment process, consists of three phases:


• WLAN discovery
• Unite CM/Unite CS server discovery
• Parameter download
The Easy Deployment process is illustrated in Figure 6. Easy Deployment, page 89.

TD 93072EN / 08 October 2020 / Ver. R 88


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

Figure 6. Easy Deployment

Unite CM
Device Manager

Secured port.
Local Area Network Only traffic to/from
Device Manager allowed
+ DHCP, NTP, ASDP

AP AP

Production WLAN Staging WLAN


(AWS-INIT)
1

A.2 WLAN Discovery


The WLAN discovery starts, when the new handset starts up. An already configured handset uses an entry
stored in Network X, and tries to associate with a WLAN, that uses the SSID, that once was configured in
the Network X.

If there is no WLAN network (SSID) configured in the handset, the handset tries to associate with a
predefined default WLAN with the SSID of AWS-INIT, on the 2.4 GHz frequency band on an AP running on
channel 1, 6, or 11, see (1) in Figure 6. Easy Deployment, page 89.

If the AWS-INIT is not connected to within ten seconds, the handset tries to connect to an open network. If
this also fails, these two alternatives are tried for ten seconds each, until succeeded.
It is not recommended to use an open network for staging, due to security reasons. The staging
network (AWS-INIT) should be set up to only allow traffic to/from the Unite CM/Unite CS, and
services for Easy Deployment (like DHCP, NTP, ASDP). This is to block other, than dedicated
clients, to use the network.

During this connection, a No network dialog window is displayed in the handset.


The WLAN discovery process stops, if any SSID of Network X is manually filled in using the
handset's Admin settings view.

The SSID can be seen in the handset's Admin settings view; in the App view, select Settings → Admin
settings and enter the admin password (default "40022"). Select Wi-Fi. The SSID (network name) that is
currently connected is shown as Connected.

If the green wireless network connection bars (up in the left of the handset display) comes and goes
alternately, the pre-shared key (PSK) on the AP is probably wrongly configured, and the handset cannot
connect to the AP. After a time-out, "No network" is shown in the handset display.

89 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

A.3 Unite CM/Unite CS Server Discovery


Once the handset has a WLAN connection, the second step is to automatically get the IP address to the
Unite CM/Unite CS which runs the Device Manager, see (2) in the figure above.

The two methods, on how to automatically get the IP address, are as follows:
• Using the vendor option functionality, Option 43 of a DHCP server
• Using the Ascom Service Discovery Protocol (ASDP) implemented in the handset
In both cases, the IP address received, is not saved, so this process is repeated on next startup, unless a
Unite CM/Unite CS IP address is set.

A.3.1 Server Discovery Using the DHCP Option 43


A DHCP server can be configured to return an Unite CM/Unite CS IP address, as a part of the DHCP
response to the handset, together with other needed DHCP parameters. The Unite CM/Unite CS IP address
is sent using Option 43 (Vendor Specific Data).

A DHCP request from a handset uses the Option 60 Vendor Class Identifier (VCI) to identify itself to the
DHCP server. (The VCI string: 1.3.6.1.4.1.27614.2.3, is the Object Identifier (OID) for the handset). By this, a
DHCP server can be configured to return an Unite CM/Unite CS IP address only to those clients that expect
it. Option 60 also allows different clients to use different settings in the Option 43, if there are multiple
clients in the network.

After the handset receives the (dynamic) IP address to the Unite server (Unite CM/Unite CS), it tries to login
to the Device Manager. The DHCP Option 43 is ignored, once the Unite CM/Unite CS IP address is
configured (static) in the Unite CM/Unite CS (in the Device Manager application).

Setting up Option 43 on a DHCP server, is not that very well documented, and not very known by network
administrators. There are many types of clients that can use this feature, for example, Cisco is using it for its
LWAP APs to find a WLAN controller to attach to.

Examples on how to configure and troubleshoot Option 43 on a Linux and Microsoft Windows 2003/2008
server, is found at the end of this appendix.

A.3.2 Server Discovery Using the Ascom Service Discovery Protocol (ASDP)
If the DHCP response does not contain a valid Unite CM/Unite CS IP address, the handset tries to find a
Unite CM/Unite CS server using the Ascom Service Discovery Protocol (ASDP) instead. An ASDP discovery
message is sent using UDP to the broadcast IP address, containing the MAC address of the handset.

A Unite CM/Unite CS server, configured to respond to ASDP discovery messages, responds with an ASDP
offer as a unicast UDP message sent to the handset.

The protocol allows each Unite CM/Unite CS to support different client services, and can separate different
types of handsets (VoWiFi and DECT) to be serviced by different modules. If there are multiple Unite CM/
Unite CS modules set up to support ASDP for WLAN, more than one response is received by the handset. A
single response is randomly selected (normally the modules that responds fastest.)

If no response is received, a new ASDP request is retransmitted periodically, and the IP address remains
unconfigured.

See the second section of A.5.1 The Ascom Service Discovery Protocol (ASDP) Explained, page 91, on how
to configure an Unite CM/Unite CS to support the handset as an ASDP discovery client.

TD 93072EN / 08 October 2020 / Ver. R 90


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

A.4 Parameter Download


After successfully receiving the Unite CM/Unite CS IP address, the handset tries to login to the Unite system.

The handset has, at this stage, no number stored internally, and does not know its identity in the Unite
system. When the dialog window Login: is displayed in the handset, enter the intended endpoint number
(that is, the phone number of the handset), that the handset uses to login to the Unite system.

Once a valid endpoint number is stored in the handset, the handset tries to login.

After a successful login, the handset is synchronized with the parameters stored in the Number record in
the Device Manager application (in the Unite CM/Unite CS, see (1) in the figure above:

Important

It is vital, that especially the WLAN network settings, are configured correctly, as the handset
receives a new set of parameters that contains the WLAN parameters for the production
WLAN. It is also important that, if using any WLAN security protocol that uses certificates, all
certificates (server/client) must be saved to each handset Number in the Unite CM/Unite CS
(Device Manager application). If the WLAN parameters are wrong, the handset cannot
associate with, neither the staging, nor the production WLAN, again.

If, by mistake, a wrong number is entered, when the dialog window Login: is displayed, make a factory reset,
see4.2.6 Perform a Factory Reset, page 26, and start over again.
If there are no Number records already configured in the Device Manager before the handset logs
in for the first time, do the following:

1. In the Device Manager, be sure to check and save the automatically created Numbers record by right-
clicking on the Number's entry.
2. Check in the created record, under Device → Unite → IP address, that the IP address for the Unite
system is correct. Then the handset can log in to the same Device Manager again.
TIP: The Device Manager's IP address can also be checked using the handset: In the handset's Admin
settings view, select Ascom settings → Ascom Messaging → Unite interface address.

A.5 Using Easy Deployment Together with Client Certificate Distribution


A.5.1 The Ascom Service Discovery Protocol (ASDP) Explained
A handset can find the Unite server (Unite CM/Unite CS), using the Ascom Service Discovery Protocol
(ASDP). The protocol is binary and uses Unite messaging.

For this purpose, a discovery message (BC) using the messaging protocol (Unite) is sent, using UDP to the
network's broadcast IP address. The discovery message contains the following data of the wanted service:

Client Description

Client class: PP
Client family WLAN

Client name: < MAC Address of the handset >


etc.
Service Wanted

91 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

Service family: ""

Service name: WGW


etc.

A Unite server (Unite CM/Unite CS) that receives this message, responds with an offer (UC) as an unicast
UDP message sent to the handset.

If more than one response is received by the handset, a single response is randomly selected. If no
response is received, a new request is retransmitted periodically, while the IP address to Unite CM/Unite CS
remains unconfigured.

Configuring Unite CM/Unite CS to Support WLAN Service Discovery Clients


For each module, the Ascom Service Discovery Protocol must be configured to support WLAN clients as
follows:
1. Log in to the module and select Configuration → Other → Advanced configuration.
2. Select WLAN System and enable Service Discovery.

Discovery Domain ID
By defining a Discovery domain ID, the Service Discovery servers are grouped accordingly. The Discovery
domain ID is configurable on both the server and the client, and only clients and servers with the same ID
can find each other. By using a separate Discovery domain ID, different types of clients can user their own
dedicated unit for device management
This feature is not implemented in the handset, and the Discovery domain ID must be left empty
on the server.

If the system uses multiple servers, at least one server must leave out the Discovery domain ID. If more than
one Unite CM/Unite CS is installed in the system, point the IP address of the second Unite CM/Unite CS, to
the first Unite CM/Unite CS.

Each Unite CM/Unite CS can also contain a Number record with the IP address, pointing to the Unite CM/
Unite CS that is dedicated to manage the handsets. But this is only recommended for a staging WLAN
(SSID), and only for initial handset configuration.

A.5.2 DHCP Vendor Options Explained


The Dynamic Host Configuration Protocol (DHCP) is described in the Request for Comments (RFC) No. 2131
and 2132. (The RFC is a publication of the Internet Engineering Task Force (IETF) and the Internet Society,
which are the principal technical development and standards-setting bodies for the Internet.)

Although the RFC 2132 describes the BOOTP options and vendor options, the document lacks examples on
how the vendor option 43 is used, configured, and troubleshot, for a network administrator.

The DHCP options described in the RFC 2132, can also, besides a DHCP server, also be used by a client.
An example, on how a handset sends a DHCP Discover message to a DHCP server during the boot process,
is shown in Figure 8. Example of a DHCP Acknowledge (Omnipeek trace), page 94:

TD 93072EN / 08 October 2020 / Ver. R 92


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

Figure 7. Example of a DHCP Discover message (Omnipeek trace)

In above figure, the numbered points illustrate the following:


1. The amount of options requested
2. The handset asks for Vendor options
3. The handset requests a specific set of Vendor options, by sending a Vendor Class Identifier (VCI)

93 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

Figure 8. Example of a DHCP Acknowledge (Omnipeek trace)

4. In Figure 8, the handset then sends a DHCP ACK, that confirms the settings the handset agreed upon
to use, like the "43 Vendor Specific Information". When comparing the, by the handset Requested
Options in the trace in Figure 7, it shows that not all requests were agreed upon by the DHCP server.
For example, the DHCP server does not acknowledge the options "42 Network Time Servers", "7 Log
servers", and an, by Omnipeek unknown, option "100". Some options are also added by the DHCP
server (without being asked for by the handset), for example, option 58, 59, 51, and 54, which are
compulsory.

TD 93072EN / 08 October 2020 / Ver. R 94


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

The Vendor 43 Option Field Explained According to the RFC


A DHCP server is configured with options prepared to supply clients with networking information that is
requested, by the clients. Either the options are entered in the IP address scope, or for all scopes.

Less known, is that a selected set of options based on the client type, can be sent to clients. This allows a
DHCP server to override the standard scope settings with other settings, which are unique for a specific
client type, or transmit dedicated values, that are not part of the DHCP standard.

These are called "vendor options", and they are sent to the client using option 43.

Adding vendor specific information to option 43, requires the use of tags (named fields), in the option 43
record. Such options are called "sub-options", and they are included in the DHCP offer as type-length-value
(TLV) blocks, embedded within Option 43. The definition of the sub-option codes and their related message
format is left to the vendors.

The Option 43 is used in WLAN by several vendors. Handset vendors use Option 43 to send specific values
to their family of handsets, and WLAN vendors use Option 43 to identify APs, and to find controllers (by
distributing IP addresses using option 43). A dedicated tag for a specific client is only identified by a client
which asks for it, and has a dedicated use for the tag. An example is the IP address to a WLAN controller,
which probably only APs can use.

To avoid having to send all option 43 codes with useless tags to all clients, the use of option 60, makes a
client identity itself as a specific client type. This type is then mapped to an entry in the DHCP server, which
contains the vendor 43 options for that type.

Option 60 is normally coded as an ASCII string, but can also be binary. The Option 60 is called Vendor
Class Identifier (VCI), and is defined by the manufacturer and programmed into the DHCP client of their
devices.

The following table lists some examples of Option 60 string values:

Vendor Device String Option 43 Returned


Value
Ascom Ascom Myco SH1 1.3.6.1.4.1.27614.2.3 Unite IP address

Aruba Aruba AP ArubaAP Loopback address of


Arubamaster controller
Cisco Cisco AP Cisco AP c1250 IP address of WLAN
controller

Option 43 Field Definition


The information in Option 43 is an opaque object of n octets, and the definition of this information is vendor
specific.

Option 43:

Code Length Vendor Specific Vendor Specific


Information Information
Element Element
43 (2b) n i2 i3 etc.

95 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

The code for the option is "43", and its minimum length is 1. The number i1 … etc refers to information bytes.
The length value n refers to the amount of information bytes in the field.

The value of the length octet does not include the two octets specifying the tag and length

Option 43 with "Encapsulated vendor-specific information":

Normally a vendor needs to have multiple parameters to be used for configuration of the clients. Then the
options are encoded using the "Encapsulated vendor-specific extensions". This format uses the TLV syntax
(type length value), and is described in RFC 2152. When "Encapsulated vendor-specific extensions" are
used, the information bytes 1-n have the following format:

Code Lengt- Data Code Lengt- Data Code Lengt-


(Tag) h Items h Items h

T1 n D1 D2 ... T2 n D1 D2 ... ... ...

The different information bytes, sub-options, are in daily language called "tags".

The tags codes are numbered options, created by the vendor like 01, 02, 83, 243 etc.

In the table above, the code for the option is "43", as well as the total length, are omitted.
Depending on the system that is used to configure the DHCP options, an administrator can enter
each sub-option separately, or enter all values in a single concatenated string. Since each value
contains a header, a length field, and the parameter itself, this can be difficult to enter correctly.
Some servers require the entry of values in the hexadecimal format, while others use ASCII strings.

For the handset, the option 43 sub fields are defined according to the following table:

Code Length Data Code Length Data Code


(Tag) Items Items Optional

01 5 Adcom 02 7–15 IP v4 255


address to
Unite CM/
Unite CS
(Device
Manager)
(dot-decimal)

The code 255 is used as an optional marker of the end of the vendor field.

When entering this information in a DHCP server, the administrator must observe that the field length of the
IP address can vary, depending on the amount of digits used. If, for example, using the address of 10.30.5.7,
the length is 6 numbers, plus 3 dot-separators in all 9 bytes. If using an IP address like 192.168.100.101, the
length is 15 bytes. Some server interfaces can assist in calculating the length.

Example:

To deploy a handset against an Unite CM/Unite CS, with IP address 10.30.4.120, the following data is to be
sent as option 43:

Hexadecimal: 01:05:41:73:63:6F:6D:02:11:77:73:73:3A:2F:2-
F:31:30:2E:33:30:2E:34:2E:31:32:30
Printable text: \x01\x05Ascom\x02\x11wss://10.30.4.120

TD 93072EN / 08 October 2020 / Ver. R 96


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

The first option in the OEM string (made bold in the table above), is used to verify that the data
received in the client, is for the WLAN handset, this is called a "magic number".

TIP: Search the internet for a tool that can assist in creating this string in Hexadecimal format.

Vendor Class Identifier (VCI)

Vendor/OEM Value

Ascom 1.3.6.1.4.1.27614.2.3

A.5.3 Config. Example - Linux Server Using DHCP Option 43


The following example is from an Ubuntu Linux server, and the information is entered in the "/etc/ltsp/dhcpd.
conf" file:

# Defining the option 43 with the proprietary sub-opcodes.

option space easy;

option easy.oem code 1 = string;

option easy.ims code 2 = string;

class "vendors" {

match option vendor-class-identifier;

vendor-option-space easy;

subclass "vendors" "1.3.6.1.4.1.27614.2.3" {

option easy.oem "Ascom";

option easy.ims "wss://10.30.4.120";

There are two options, configured as code1 and code 2, and both are defined as strings.

The server maps the string "1.3.6.1.4.1.27614.2.3", that was received from the handset using option 60, as
defined in the subclass paragraph.

Note that there is no need to describe the length of the fields.

A.5.4 Config. Example - MS Windows 2003 Server Using DHCP Option 43


The DHCP server in a Microsoft Windows Server system, is by default already configured with the Vendor
Classes seen in the table below, plus the DHCP standard options.

The standard options are used by all clients, while the Vendor class option adds/overrides options for
specific clients.

97 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

Name Options Used By VCL Clients Option 60


With Vendor
Class
Mapping

Microsoft Windows 1, 3, 6, 15, 31, 33, 43, 44, Windows 2000, and "MSFT 5.0"
2000 options (Overrules 46, 47, 121 and 249 higher
the other two) XP, Vista, Win7 and Win
8
Microsoft Windows 98 Windows 98 and "MSFT 98"
options Window ME

Microsoft options Windows 98, Me and "MSFT"


2000 clients

An administrator can add new Vendor classes as described in the section Define New Vendor Class to
Support Multiple Types of Clients in A.5.6 Advanced Config. of Option 60 and 43 Using a New Vendor
Class, page 99. But it is not possible to delete the Microsoft built in classes and the standard class.

The DHCP server is preconfigured with a list of normally used DHCP options. Any missing DHCP option can
be added as an administrator-defined option, either for each scope, or for the whole server.

A.5.5 Config. of Option 60 and 43 Using Standard DHCP Vendor Class


Adding the option 60 and 43 to the standard set of DHCP, at least for a lab environment this is a simple,
small and fast solution, but has the following drawback: There can only be one set of options configured per
scope, so having different vendor's equipment in the system, requires different scopes. For example,
lightweight APs and handsets may not use the same scope.

Option 43 should then contain a complete data set with all needed sub-options stored in a TLV format. This
is, in some literature, described as using the RAW format of option 43. The TLV format is best entered using
a data type of binary.
By configuring option 43 direct on the standard scope, any DHCP client is offered this value,
independent of the Vendor Class ID that is used by the client. Only clients who understand the
received string benefit from this value. Trying to solve this problem, by manually setting option 60
to a specific Vendor Class ID on the standard scope, has no effect. On a Microsoft DHCP server,
the Vendor class IDs are entered using a dedicated procedure, which allows the usage of Multiple
Vendor Classes. This is why option 60 is not listed as an option in the default standard DHCP class.
There is, therefore, no need to enter Option 60 values direct on a scope by creating a new option.

There are several documents on the internet that gets this process wrong.

Configuration of Option 43
the figure Figure 9. Option 43 using a standard DHCP vendor class, page 99 illustrates how to set a vendor
43 option on the standard DHCP class, which is feasible if only vendor option 43 is needed:

If set, this option 43 is also offered to client computers.


1. On the DHCP server, click the scope that the handsets should use, then right-click on Scope Options,
and select Configure Options.

TD 93072EN / 08 October 2020 / Ver. R 98


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

2. On the General tab (the default Standard DHCP class), scroll down, and select option 043 (which is the
Vendor Specific Info option).
3. In the data entry field, there are two ways of entering the information. Click to the left in the box, to
enter the string in binary, and to the right, to enter the string in ASCII. (It is possible to switch between
them.)
Enter the values, as described in previous sections. Make sure to enter the correct length of the values
in the TLV string.

Figure 9. Option 43 using a standard DHCP vendor class

TIP: If the length value is unknown, enter the TLV value as follows, as everything inside the parenthesis
is auto calculated using the "Auto-len" feature:
01 ("Ascom")02(wss://10.30.4.120)
Then click OK and save the new option 43.
4. Check that the options are entered correctly. Note that the Vendor class is "Standard", which means
that no specific class is used, and that the User class is "None", which means that it is the default user
class. The handset does not send any request with a user class filled in.
Do not enter the value 2b 14 (43 20), which is the option class and the total length. This is
added by the DHCP server, when this option is presented to the client.

5. Test the configuration. If the Option 43 is not working as expected, verify the behavior with a packet
capturing tool.

A.5.6 Advanced Config. of Option 60 and 43 Using a New Vendor Class


The recommended way of setting up Vendor options, is to use Vendor classes, instead of the Global
standard Default DHCP class. With this solution, option 60 is not configured as an option in a scope, instead
a Vendor class is created.

99 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

Microsoft uses a method that allows the administrator to set up the sub-options (that will be part of the
vendor options), as a complete set of sub-options, which are then concatenated to the 43 option string by
the server. Each sub-option (called "code") is defined with the sub-option numbers, as described by the
vendor. In the case of the VoWiFi handset, the sub-options are 01 and 02.
The DHCP server automatically calculates the length of each sub-option, and the total length of
the whole string, and attaches the option ID of "43" at the beginning of the string.

If option 43 is configured, using "code 43", the "code 43" option is added to the concatenated
string. Then double headers are added (one created by you, and one created by the system), and
the string is not functioning as intended.

Instead, fill in the created sub-options with correct values. The sub-options are then automatically concaten-
ated to the string, and creates an option 42 on the fly.

Define New Vendor Class to Support Multiple Types of Clients


To include the needed information for a handset, an administrator has to define a new vendor class as
follows:
1. Right click on the DHCP server object, and select Define Vendor Classes. Then click Add.
2. In the New Class dialog box, enter a descriptive name for the Vendor class. For example enter, in the
Display name: field: "Ascom Myco handset", and in the Description: field: "Option 43 for Easy
Deployment". These fields are only used for displaying information for the administrator. In the ID: field,
enter the VCI string (1.3.6.1.4.1.27614.2.3). Then click OK.
TIP: Click on the right side of the field to be able to write in ASCII.
The VCI string has to exactly match with the vendor specification, since it is used in the mapping of
the information sent from the handset in option 60 (case sensitive).

Configure Sub-Options for a Vendor Class in an MS Windows 2003 DHCP Server


The current sup-options string for the handset contains two codes (which in some documentation from
vendors, are referred to as "tags".) In order to build these two codes, they have to be defined as follows:
one with the value of Ascom, and one with the IP-address of the Unite CM/Unite CS (Device Manager
application).
1. Right click on the DHCP server and select Set Predefined Options.
2. Select the vendor class created earlier (in Define New Vendor Class to Support Multiple Types of
Clients, page 100) under Option class and click Add. The Option type window opens.
3. Enter a descriptive name for the first sub-option, for example enter, in the Name: field: "VoWiFi Vendor",
and in the Description: field: "Vendor Magic ID"
4. In the Data type: field, select Binary, to allow the entering of more than one byte.
5. In the Code: field, enter "001". Then click OK.
A predefined value (by selecting Edit Array) isn't needed to be entered here. It can be
preferred to be set per scope instead (explained below).

6. For the second sub-option, repeat the steps 1- 2 above.


7. Enter a descriptive name for the second sub-option, for example enter, in the Name: field: "Unite IP
address", and also copy it into the Description: field.
8. In the Data type: field, select Binary to allow the entering of more than one byte.

TD 93072EN / 08 October 2020 / Ver. R 100


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

9. In the Code: field, enter "002". Then click OK.


10. Add the two sub-options to a scope and assign the values needed as follows:
Right click on your scope, then select Scope Options > Configure Options.
11. Select the Advanced tab. In the Vendor class: field, select the new vendor class that was created in
Define New Vendor Class to Support Multiple Types of Clients, page 100 section (Ascom Myco
handset). Check the boxes for the two sub-options that appear ("001 VoWiFi Vendor" and "002 Unite IP
address".
In the User class: field, leave the "Default User Class".

12. Select the first sub-option 001 VoWiFi Vendor and enter the Vendor magic ID (Ascom or in Binary/Hex:
41:73:63:6F:6DE 73). Click to the left of the box for Binary code, and to the right for ASCII code.

Remove the 00 that is entered by default.

A length value (in Data: field) isn't needed to be entered here (as normally done, when
entering a TLV record).

Then click OK.


13. Select the second sub-option 002 Unite IP address and enter the UniteIP address in Binary/Hex or
ASCII. Then click OK.
14. Test the configuration by factory resetting a handset. If the configuration doesn't work, do a trace with
a sniffer to see why.
TIP: Install Wireshark on the DHCP server and filter on the "bootp" protocol, to view the packet
exchange when a handset is started up.

Configuration of DHCP Options in a Cisco Device Running the Cisco IOS DHCP Server
The Cisco IOS DHCP server only allows Option 43 definitions for one device type for each DHCP address
pool, so only one device type can be supported for each DHCP address pool. Complete these steps in
order to configure DHCP Option 43 for VoWiFi handsets:
1. Enter the configuration mode at the Cisco IOS command line interface (CLI).
2. Create the DHCP pool, which includes the necessary parameters, such as the default router and the
server name. This is an example DHCP scope:
ip dhcp pool <pool name>
network <ip network> <netmask>
default-router <default-router IP address>
dns-server <dns server IP address>
3. Add the Option 60 line with the following syntax:
option 60 ascii "VCI string of the handset"
Avoid raw DHCP Option 43 without the specification of a VCI. Raw DHCP Option 43 limits the
DHCP server to support a single device type for vendor specific information for each DHCP
scope. Also, every DHCP client receives the Option 43 values in a DHCP Offer, regardless of
whether the values are relevant to the device.
4. For the VCI string, use the value above. The quotation marks must be included.
Add the Option 43 line with the following syntax:
option 43 hex <hexadecimal string>

101 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

This hexadecimal string is assembled as a sequence of the TLV values for the Option 43 sub-option:
Type + Length + Value, as described above.

A.5.7 Easy Deployment and VLAN


In a VoWiFi system, the Unite CM/Unite CS used for configuration must be positioned in the Voice VLAN,
even if it is actually a data device (since the Voice and the Unite Messaging services cannot be separated
to two different SSIDs and thus not simply mapped to different VLAN in the AP/controller.

A mapping rule can, though, be created, that uses TCP/UDP port mapping, and connects the two services
to different VLANs, instead of mapping SSIDs.

VLANS are not defined in the 802.11 standard. To achieve the same traffic separation for example between
a Data and a Voice VLAN (and maybe including even a Deployment/Management VLAN), different SSIDs
are used which are mapped to different VLAN IDs in the AP/Controller. The WLAN system must, therefore,
be set up to support multiple SSIDs.

If using the AWS-INIT SSID on a single AP, make sure that the handset also can associate to the production
SSID, after it has received its full configuration from the Unite CM/Unite CS (Device Manager application
used for Easy Deployment.)

Remember that, when getting the production WLAN SSID, that it may be mapped to another VLAN, and that
the IP address is changed, and also, that the DHCP server options are served by another scope, or
eventually another DHCP server.

If using a deployment VLAN, you may be forced to have two Device Managers, or arrange for routing
between VLANs.

You may try using a direct configuration of option 60 and option 43 on a scope by scope basis, if your
system allows the separation of DHCP client devices to use independent scope ranges.

A.5.8 Troubleshooting Easy Deployment in an MS 2003/2008 DHCP Server


If you, by mistake, create a predefined DCHP option, and want to remove it, the server sometimes denies
this operation (even if you have created the DHCP option). This is indicated by a grey Delete button. In such
case, open a command prompt and use the "netsh" command as follows:

netsh dhcp server \\servername delete optiondef xx

where xx is the option number.

A.6 Ports
This appendix lists the TCP and UDP ports the handset listens on for incoming and outgoing traffic. The
information applies to firewalls, network devices, traffic shaping and third-party product settings.

A.6.1 Signaling
SIP (VoWiFi only)
The following port numbers are configurable through the Device Manager:

Application Direction Local Port Number

UDP outgoing 5060

incoming 5060

TD 93072EN / 08 October 2020 / Ver. R 102


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

TCP outgoing any free port

incoming 5060

TLS outgoing any free port

incoming 5060

A.6.2 Voice Traffic (VoWiFi only)


For a voice connection, one RTP and one RTCP port are used. A call therefore uses two free UDP ports
selected from the RTP port range. The RTP port range is, by default, from 16384 to 32767. The port range is
then used for SIP calls.

A.6.3 Other Services with Fixed Local Ports


Application Port Number and Direction

DNS UDP 53 OUT


DHCP UDP 68 OUT
Network Time Protocol (NTP) UDP synchronization 123 OUT

Unite traffic TCP 443/33003 OUT


Ekahau UDP (Configurable in the Device Manager) 8552 IN

RPCAP TCP 2002 IN


Software updates, applications and certificates 80/8080 OUT

A.7 Alert Categories


Categories can be defined for specific alerts within the messaging system. The Alert Category nformation
is set, for example, in each event for Unite Connect-based products or in the element Tag in the Message
block.

The following category labels are available:

Icon Description Tag

Anesthesia delivery unit Anesthesia deliver unit

Assistance call AssistanceCall

Blood filter Blood filtration

Blood-gas analyzer Blood gas analyzer

103 TD 93072EN / 08 October 2020 / Ver. R


CONFIGURATION MANUAL
Ascom Myco Easy Deployment

Category A Category A

Category B Category B

Category C Category C

Category D Category D

Category E Category E

Code A Code A

Code B Code B/Code Blue

Emergency call Emergency

Failure Failure

Fire Fire

Heart-lung machine Heart lung machine

Incubator Incubator

Infusion pump Infusion pump

Lab result Lab

Lavatory call LavatoryCall

TD 93072EN / 08 October 2020 / Ver. R 104


CONFIGURATION MANUAL
Easy Deployment Ascom Myco

Medical call MedicalCall

Monitoring Monitoring

Nurse call NurseCall

Personal Personal

Service call ServiceCall

Task Task

Technical alert PM Technical

Ventilator Ventilator

X-ray result Xray

105 TD 93072EN / 08 October 2020 / Ver. R


106 TD 93072EN / 08 October 2020 / Ver. R
TD 93072EN / 08 October 2020 / Ver. R

Manufacturer

Ascom (Sweden) AB

Grimbodalen 2

SE–417 49 Göteborg

Sweden

Phone +46 31 55 93 00

www.ascom.com

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy