Ascom Myco Smartphone CM 93072EN R
Ascom Myco Smartphone CM 93072EN R
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.
1G, 2G, 3G, 4G Common naming of the generations of mobile communication evolution.
802.11b Standard for transmission rates up to 11 Mbps, operates in the 2.4 GHz
spectrum.
802.11g Standard for transmission rates up to 54 Mbps, operates in the 2.4 GHz
spectrum.
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).
Ad-hoc WLAN A WLAN between two wireless capable devices (normally PCs), where no
Access Point (AP) is involved.
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
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.
QoS on the Internet Layer used both for WLANs and LANs.
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
IM Interactive Messaging
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
PARK Portable Access Rights Key. Used for DECT system identification.
PTT Push-To-Talk
PUN Physical Unit Number.
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.
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).
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.
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.
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
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.
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.
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.
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.
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.
IP-PBX If used
Subnet Mask 2 If used
Unite CM/Unite CS (incl. Number Yes
plan)
DHCP range
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.
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:
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.
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.
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.
If the handset is used without a Unite CM/Unite CS, follow the applicable steps in 3.2.3 Manual
Installation, page 13 instead.
Figure 3. Handset configuration using the Device Manager in Unite CM/Unite CS.
IP AP W i-FiAccess Point
− The network address (IP address or host name) of the Unite CM/Unite CS.
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
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.
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.
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).
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.
Unite CM/Unite CS is required for handset features such as alert and message handling, and
the Ascom Myco Launcher interface.
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
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.
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.
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.
3. If the scan is successful the Setup app closes automatically and the text Deployment data applied
successfully appears on screen.
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.
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.
The Ascom Myco Launcher user interface cannot be enabled without a Unite CM/Unite CS.
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.
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.
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
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
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.
13. The SIP Endpoint ID and SIP password are limited to a total length each of fifty unicode characters.
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.
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.
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.
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.
If a hunt call is transferred, the number of the call originator is shown instead of the hunt group
name.
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.
The number of parameters the template contains affects the time it takes to apply it to the
handsets.
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.
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.
Transfer with a USB cable is only recommended for handsets that hasn't yet been connected to a
Unite CM/Unite CS.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
Only select the parameters that are changed, if all parameters are selected, the system
performance decreases.
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.
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.
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.
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.
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).
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.
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.
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.
− 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:
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.
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:
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.
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).
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.
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
− 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.
UNII-2 Extended 5.470 - 5.725 MHz 100, 104, 108, 112,116, 120, 124,
128, 132, 126, 140
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).
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
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 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)
− System-aided roaming
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.
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.
Only Access Point Names applicable for the cellular handset version.
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.
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.
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).
Device Manager:
1. Select Network → Mobile networks.
2. In the Enabled cellular data (caution) drop-down list, select No.
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.
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.
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.
The IPEI number is also displayed on the Add new Subscription screen. Refer to the 5.3.3 Add a
New Subscription, page 41.
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.
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.
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.
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.
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
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.
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.
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.
TIP: The Ascom Myco Launcher replaces the default Android launcher and adds customized functionality
such as alert and conversation handling to the handset.
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.
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.
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:
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.
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.
The handset can be configured to automatically call a predefined number after an alarm has been sent.
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.
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.
• 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 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.
The basic location settings does not affect the performance of an RTLS service.
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.
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.
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.
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.
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)
− Hidden
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.
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 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.
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”).
The maximum number that can be set is 4 and the minimum number that can be set is 1.
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.
If no other value is set, the default value is the Call ID/number of the handset.
− 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.
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.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).
1. Select Sound.
2. In the Dial tone patterns drop-down list, select a country to use the dial tone pattern from that country.
1. Select Sound.
2. In the Notification sound drop-down list, select the sound to use for notifications (default Tethys).
1. Select Sound.
2. In the Screen lock sound drop-down list, select Yes (default) or No.
Do the following to change what type of messages the handset vibrates for during an call:
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
19. Only the default value if the Ascom Myco launcher is enabled.
Breakthrough messages and the Minimum volume parameter will override this parameter value.
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.
− 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).
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.
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.
Important
The Unspecified or Numeric option must be selected for shared phones if the badge login
feature is enabled.
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.
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.
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.
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.
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.
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.
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).
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)
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.
Select Telephony. In the Call setup notification type drop-down list, choose between:
• As call (default)
• As alert
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.
If the handset fails to register with the primary SIP proxy, it can register with the optional secondary SIP
proxy.
When the handset has connected to the Secondary SIP proxy, it continuously tries to reconnect to the
Primary SIP proxy.
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.
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).
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)
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
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).
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.
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 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.
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.
− 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.
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:
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.
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).
1. Select In charger.
2. In the Clear images when docked drop-down list, select:
− Yes.
− No (default).
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.
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.
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”).
− 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”.
6 Related Documents
Data Sheet, Ascom Myco 2 Wi-Fi and DECT Smartphone, TD 93220EN
Installation and Operation Manual, IPBS, IPBL and IPVM (10.1.X), TD92579EN
7 Document History
Version Date Description
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.
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.
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
• In the handset, all other network parameters must be at their default settings, which means for instance:
Unite CM
Device Manager
Secured port.
Local Area Network Only traffic to/from
Device Manager allowed
+ DHCP, NTP, ASDP
AP AP
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.
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.
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 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.
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.
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
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.
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.
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:
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.
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.
Option 43:
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
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:
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:
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
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/OEM Value
Ascom 1.3.6.1.4.1.27614.2.3
class "vendors" {
vendor-option-space easy;
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.
The standard options are used by all clients, while the Vendor class option adds/overrides options for
specific clients.
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
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.
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:
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.
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.
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.
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.
A length value (in Data: field) isn't needed to be entered here (as normally done, when
entering a TLV record).
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>
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 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.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:
incoming 5060
incoming 5060
incoming 5060
Category A Category A
Category B Category B
Category C Category C
Category D Category D
Category E Category E
Code A Code A
Failure Failure
Fire Fire
Incubator Incubator
Monitoring Monitoring
Personal Personal
Task Task
Ventilator Ventilator
Manufacturer
Ascom (Sweden) AB
Grimbodalen 2
SE–417 49 Göteborg
Sweden
Phone +46 31 55 93 00
www.ascom.com