Ascom Myco version 5.5.0

Release note

Ascom Myco™ | Version 5.5.0

Gothenburg

July 15, 2016

[ ]

Ascom Myco version 5.5.0

TABLE OF CONTENT:

GENERAL ....................................................................................................................................................................... 3

KNOWN ISSUES ............................................................................................................................................................. 5

SUMMARY CHANGES 5.5.0 ........................................................................................................................................... 7

NCR related changes................................................................................................................................................. 7

Change requests ..................................................................................................................................................... 10

Other changes ........................................................................................................................................................ 11

DOCUMENT HISTORY ................................................................................................................................................. 13

Ascom Myco version 5.5.0

GENERAL

This document contains release notes for the changes in Release 5.5.0 relative to version 5.3.0.

Highlights This release is a maintenance release of the 5.x-track includes the following features and improvements.

12 NCRs, 4 CRs and 7 Bugs

The release 5.5.0 releases a temporary workaround known as “Switch of suspend” solving a known issue seen when sending mission critical alerts over cellular network. This workaround is only available under Controlled Shipment.

Purpose of the release This version is available for general use but under Controlled Shipment where mission critical alerts are sent over cellular network.

ASCOM MYCO FIRMWARE AND LAUNCHER Build date: 2016-07-14 Software name: Myco_Firmware_v5.5.0.pkg Software version: 5.5.0 OS version: 4.4.2

Included Ascom Components which are version handled separately Wi-Fi Interface: Software version: 4.2.e SIP app: Software version: 1.5

Compatibility info The Ascom Myco 4.2.0 (or later) software requires Unite CM version 5.3.8 or later. For Ekahau support, Unite CM version 5.5.3 or later is required. User Authentication/User login requires Unite CS. (Server version) Active supervision for a websocket connection requires Unite CM version 5.8.x or later. (NEW) Ascom Myco Firmware 5.5.0 can be considered validated as fully compatible for use with MMG 4.4.2 and Cardiomax if the default setting for “Vibrate for incoming message during call” is set to vibrate. For more details see change request - VIBRATION DURING ONGOING CALL.

Important:

New - There is no longer any need to install the Ascom Myco Launcher separately, see instructions below

for how to enable it.

If upgrading handset with software 1.9.0 (May 2015) or older, see Release note for 3.3.0 and read the

instructions in the “Migration from Earlier Versions” section before upgrading the software in the

handsets. When upgrading handset from 2.1.0, the numbers configured for calls using alarm button will

be erased. The phone number field needs to be reconfigured after the upgrade.

Before installing this software please read this document thoroughly.

Enabling the Ascom Myco launcher From 4.x onwards, the Myco launcher is integrated in the Myco firmware. However, it has to be enabled in the Device Manager - it is not possible to enable it from the handset. After installing the firmware go to the Numbers tab in the Device Manager, chose Edit parameters for the number in question and go to Ascom Messaging. Choose Yes for “Use Ascom Myco launcher”. If you are registering a new handset on a number that already has

Ascom Myco version 5.5.0

the launcher enabled you may have to disable it (choose No for “Use Ascom Myco launcher”) and then enable it again, in order for it to take effect. The launcher can also be enabled through the use of templates if, for example, you need to handle several handsets at the same time, see the Configuration Manual. If the handset does not have a number associated, it is also possible to enable the launcher by creating a template, making a QR code and scanning that, see the Configuration Manual.

Ascom Myco version 5.5.0

KNOWN ISSUES

DEVICE MANAGEMENT, VIA ASCOM DEVICE MANAGER - When upgrading Ascom Myco from 2.1.0, the numbers configured for calls using alarm button will be

erased. The phone number field needs to be reconfigured after the upgrade.

- Wi-Fi networks cannot be synchronized via GSM/3G if Wi-Fi is turned off.

- 'Automatic time zone' setting only applicable for use with GSM/3G. For “Wi-Fi only” use “NTP server

address”.

- If device has been locked from Device Manager, status will not change back to unlocked even though

device is unlocked. Workaround – restart the handset to update status in Device Manager.

- If locking device from Device Manager with an info text specified, the text will not show in the device.

WI-FI Preferably use the Device Manager when changing Wi-Fi configurations. One important reason is: If

having multiple networks configured any Wi-Fi configuration change via the Myco Settings app will reset the parameter "Active Wi-Fi network" to "Automatic Wi-Fi network selection".

There are two limitations to the “Auto band” functionality.

1. Disabling 802.11n is not possible when using “Auto band”

2. Initial scanning is done on both 2.4 and 5 GHz, but after association scanning is only

done on associated band.

Precaution should be taken when configuring multiple SSID’s in the Myco. Specifically if the SSID’s are not physically separated and can be heard at the same time, the Myco might switch network if the currently connected is lost. Preferably only use one SSID.

Adding network(s) in the DM:

When selecting one network in the DM this network will be scanned using unicast probe request and all

other configured networks will be disabled, i.e. the Myco will not try to associate to them even if the

selected network is unreachable and the other networks are reachable.

When selecting “Automatic Wi-Fi network selection” none of the configured will be scanned with unicast

probe requests, only broadcast probe requests will be sent out, i.e. all networks will have the same

possibility to be connected to.

When connected the network connected to will be scanned using unicast probe requests.

Limitation scanning channels:

Not possible to scan all 38 channels on 2.4 and 5 GHz without reconfiguring the handset. Current limit is

32 channels. Maximum 29 can be used by one system.

Default channels that are scanned. 1,6,11,36,40,44,48,149,153,157,161,165.

If an all channels site survey is to be done on both 2.4 and 5 GHz it must be done doing two separate site

surveys, one for each band. Hidden SSID:

Only one hidden SSID can be used at a time. The hidden SSID must be selected as “Active Network” using the Device Manager, or added using the “+” button via the handset GUI (only one SSID must be added using the “+” button). “Auto Network” option will not work with hidden SSID.

Myco may roam to AP during call even when CAC is refusing traffic. Only handsets using TSPEC. High power consumption when 11n is enabled. In a Cisco system with a certain SW version it was noticed

that standby with 11n enabled was only 14h and with 11n disabled it was 48h. (New) Server validation when using 802.1X autentisering is default not activated. Be aware of the security

risk.

SIP - Individual ring signals set for contacts in the local phonebook on the device do not work in case of SIP

(Wi-Fi) call. (Works OK for GSM calls).

- Myco does not show that SIP registration is down on startup. When starting up Myco with SIP configured,

and the handset does not succeed to register to SIP Proxy, no indication is made for the user.

Ascom Myco version 5.5.0

CELLULAR - Myco doesn´t allow international calls from behind a PBX that requires a 0 to get an external connection

- Signal strength indicator sometimes shows no signal even when possible to call.

- Sometimes Unite message is lost due to 3G network connection down.

SECURITY - Only manage security password policies at one place (in either Device Manager, Myco Settings in the

handset, and Android Settings in the handset or MDM). The strongest security password policies will win but Device Manager and Myco Settings in the handset are not able to reflect the setting and are not able to feedback that a security setting might not take effect (if trying to set a weaker policy than MDM).

CAMERA - Digital zoom not implemented.

AUDIO - After a substantial uptime, audio playback may fail resulting in one sound not being played. Only seen in

internal automated tests.

Charge Ascom Myco using the USB connector - Power adapter

o Ascom Myco requires that the data signals in the USB adapter are shorted to charge the battery

with 500mA (or if it´s an active host like a PC and the USB port supports 500mA). If this is not the

case Myco will only charge with 100mA and that is not enough to really charge the battery. This is

according to the USB standard.

o Ascom Myco needs to be powered up to charge with 500mA otherwise the Myco will charge with

only 100mA and the charging cycle will be ended before the battery is full charge.

- When the battery is empty and the USB cable is connected it could take up to one hour before the Myco

could be powered up. A workaround for this issue is to disconnect the battery for a few seconds before

connecting the USB charger, then Myco will automatically power up when the voltage is enough.

OTHER - Not possible to downgrade the firmware (Android limitation). - The app Axess for smart devices cannot be installed on a Myco. No change planned. - Myco in rack charger occasionally stuck showing "Myco at the heart of care" – factory reset needed. - Ascom Myco cannot connect via IPsec VPN. This is a known Android issue. Workaround is to use the

application VpnCilla. - Settings crashes when trying to enable "Bluetooth HCI snoop log" - Since the handset does not have

Bluetooth, it’s not a normal use case to use the Bluetooth snoop log - Wi-Fi network is removed after it is deleted and added again - If the Wi-Fi is configured from the device

manager this will not happen. - Only one way encrypted RTP payload. Customer is encouraged to NOT use the option “retry with RTP” for

the parameter “Secure RTP negotiation”. - Mitel MCD3300: RTP half-way encrypted when both parties use SRTP. Customer is encouraged to NOT

use the option “retry with RTP” for the parameter “Secure RTP negotiation”.

Ascom Myco version 5.5.0

SUMMARY CHANGES 5.5.0

Below is a summary of the changes in version 5.5.0 compared to version 5.3.0.

NCR related changes

MYCO CANNOT CONNECT TO UNITE IF THE HOST ADDRESS CONTAINS AN UNDERSCORE NCR/CR: ASCOM-506

Background:

When adding a host name in the Myco settings "Unite Interface Address" field that contains an underscore,

the DNS query will fail due to a faulty sign and Myco will not be able to connect to Unite.

Solution:

It is no longer possible to enter underscores in the host name part of the Unite Interface Address field.

CANNOT SET UP CALL ON A RAEMIS-BASED GSM PICOCELL NETWORK Components: 3G/GSM

NCR/CR: INTOP-19, POC-6

Affects system/s: Raemis by Druid software (Mitel LMN)

Background:

Calls get disconnected immediately when using UICC (SIM) from Druid Software, but works when using SIM

from for example Telia or Tele2.

Solution:

Added workaround for missing terminal profile information in the Druid Software UICC. The handset needs to

be factory reset after applying the fix.

AN EAP WIFI NETWORK PROFILE PUSHED FROM A THIRD-PARTY APPLICATION IS SILENTLY REJECTED BY

THE HANDSET NCR/CR: ASCOM-583

Affects system/s: AirWatch Agent v5.3.2.790

Background:

The Ascom Myco requires that an EAP network negotiates for CCKM key management. If CCKM is not

included in a network profile pushed from a third-party application, the profile will be silently rejected.

Solution:

EAP Wi-Fi network profiles added from a third-party application will now automatically add CCKM to the

network profile if it is missing.

RESTART OF COM.ASCOM.LOCATIONMGR NCR/CR: Part of CBNX-1878

Background:

Currently the LocationManager relies on getting either boot completed or a change of wifi state in order to set

the initial configuration. But if the service is restarted, the device has already booted, and is in a stable Wi-Fi

state, no configuration will be set which will cause a NullPointerException when an alarm is triggered.

Ascom Myco version 5.5.0

Solution:

The service will now always configure the scanner at startup. This means that no matter if it is started on boot

or by an alarm, the scanner will always have a configuration to fall back on.

THE HANDSET CAN SOMETIMES NOT RECEIVE SIP CALLS NCR/CR: CBNX-1875

External Issue ID: Innovaphone Mantis: 175065

Background:

When going in and out of Wi-Fi coverage, the handset can sometimes end up in a state where it is no longer

possible to receive SIP calls.

Solution:

When going in/out of Wi-Fi coverage the SIP registration is now updated properly.

CANNOT QUICK DIAL TO RETRIEVE VOICE MAILS NCR/CR: CUS-6592

Background:

Some PBXs use different numbers to register for message waiting indications (MWI) and for retrieving the

actual voice mails. Currently, there is only one number available for configuration. If we use the message

center number, the handset will receive MWI, but it is not possible to quick dial to retrieve the voice mail. If we

use the voice mail number, the handset will not register for MWI.

Solution:

Added a new parameter to set the message center number. When registering with the PBX we will now try to

use the message center number first and fallback to voice mail number in case the message center number is

missing (i.e. the PBX use the same number for registering and for retrieving voice mails). The voice mail

number will be used when quick dialing.

THE HANDSET TIME WILL NOT BE SAVED IN PERSISTENT STORAGE IF NTP TIME DIFFERS BY LESS THAN 5

SECONDS NCR/CR: Part of CNO-44882

Background:

We backup the time in the Ascom Myco when you receive the NTP time and the new time differs by more

than 5 seconds compared to the current time in Myco. When the Myco is restarted, we fall back to the saved

time before a new time is received. If you don't reset the Ascom Myco regularly, the saved time can be quite

old and cause issues with certificates when the handset is restarted.

Solution:

The Myco now stores the time persistently each time a NTP update is received. After reboot, the time will be

initialized to the previously stored time.

ONE-WAY VOICE AFTER ROAM FROM LOST AP IN A TSPEC-ENABLED SYSTEM NCR/CR: CAUS-2480

Affects system/s: Cisco AP 3700 (v8.1.131)

Background:

When roaming from a failing AP (for example in bad coverage), the handset can end up with one-way voice in

SIP calls.

Ascom Myco version 5.5.0

Solution:

When adding TSPEC info to (re-)assoc request the driver used the connected AP's information, but the

correct way is to use the info for the new, not yet connected, AP.

"NO RESPONSE" IS NOT TRANSLATED CORRECTLY IN FINNISH NCR/CR: CFI-17090

Background:

Translated “No Reponse” text is missing one letter "i". “E vastaa” Should be “Ei vastaa”.

Solution:

"No response" is now translated to "Ei vastaa" in Finnish.

INTERACTIVE MESSAGE ID (HEX) IS IN LOWERCASE IN RESPONSE MESSAGE NCR/CR: CUS-3660, CUS-5138

Background:

The Interactive Message ID (hexadecimal value) is represented internally in Myco as a value and then

generated back into a string when the message is returned. When the ID is transformed back into a string, the

hexadecimal value is in lowercase. Some external applications use the Interactive Message ID as a string and

expects it to keep the case when returned. If it is sent to the Myco in uppercase and then returned in

lowercase, external applications which treats the hexadecimal ID as a case-sensitive string will then not be

able to successfully identify the incoming response.

Solution:

The Interactive Message ID will now always be uppercase hexadecimal encoded instead of lowercase

hexadecimal encoded when returned from Myco.

NOTE!

This fix is only a workaround for applications that do not use the protocol in the intended way. The proper fix

is to change the applications to use the Interactive Message ID as a hexadecimal value.

HANDSET TRIES TO USE REMOTE PCAP EVEN THOUGH "NETWORK PACKET LOGGING" IS SET TO LOCAL NCR/CR: ASCOM-696, ASCOM-700

Background:

If I have made a remote PCAP trace and then switch over to local logging without removing the IP address to

the remote PC, the Myco will still try to connect to the remote PC.

Solution:

Network logging is no longer sometimes started/stopped when the "Network packet logging" is set to local,

but the ”Network logging hostname” is set (and is hidden).

PARAMETERS FAIL TO SYNC WITH DEVICE MANAGEMENT ON A WIFI-ONLY HANDSET

Background:

Sometimes Wi-Fi-only handsets does not use parameters (for example language parameters, NTP, ...)

synced from the device manager. This happens for both new and exchanged Ascom Mycos.

Solution:

Parameter synchronization will no longer stop on a Wi-Fi-only handset if the device manager sends a GSM

voice mail number during parameter synchronization.

Ascom Myco version 5.5.0

Change requests

VIBRATION DURING ONGOING CALL NCR/CR: CFI-12720, CUS-6445, Part of CR-226

Background:

Add a possibility to set when/if the handset shall vibrate to indicate an incoming messages during call.

Solution:

A new parameter has been added that makes it possible to configure if incoming messages shall be indicated

with vibration while in a call. High priority messages can be configured to vibrate, while messages of lower

priorities are indicated by (in-band) sound only.

The new parameter can be found at {{Sound > Vibrate for incoming message during call}}.

NOTE! The default setting in the handset is changed from “Vibrate” to “Not vibrate”. This is the same behavior

as the i62. The firmware 5.5.0 can be considered validated as fully compatible for use with MMG 4.4.2 and

Cardiomax if the parameter is set to “Vibrate” as it was in previous firmware release.

SWITCH OFF SUSPEND

NCR/CR: CR-250 Background:

Added an admin parameter to be able to force the handset to remain awake. This gives the possibility to

make the Myco more reliable for customers who experience a lot of GSM issues. Battery life time will be

decreased significantly but temporarily reduces GSM issues until a more appropriate solution has been

found.

Solution:

Added a parameter for preventing the handset from going into suspend. Note that by setting this you will

significantly increase the battery consumption of the handset.

The parameter can be found at {{Performance > Allow suspend mode}}

NOTE! This feature is only to be used under Controlled Shipment.

SET VOLUME FOR INCOMING MESSAGES NCR/CR: Part of CR-226

Background:

Add a possibility to set the volume for the indication of incoming messages.

Solution:

Added a new parameter which allows the administrator to set the indication volume for incoming messages to

be different than the ring volume (unless the message itself specifies the indication volume). While in a call,

the (in-band) message indication volume follows the volume of the voice stream.

The new parameter can be found at {{Sound > Volumes > Message volume}}.

Ascom Myco version 5.5.0

Other changes

WIFI VERSION 4.2.E

Background:

Update Wi-Fi version to 4.2.e.

Solution:

Version 4.2.e includes:

- An EAP Wi-Fi network profile pushed from a third-party application is silently rejected by the handset

HANDSET LOST CONNECTION TO UNITE AND DOES NOT TRY TO RECONNECT

Background:

The handset sometimes does not try to reconnect to Unite after a disconnect.

Solution:

The handset makes sure that only one request to reconnect the Unite connection is active simultaneously

(otherwise a second reconnect attempt would close the one already scheduled - making the Unite connection

go up and down). If Unite is connected, requests to close, and the reconnect alarm triggers immediately, the

reconnect attempt will be ignored (since the previous connection is in the state of being disconnected - this is

correct). The problem is that when the connection is reported to be disconnected and a new reconnect

attempt shall be scheduled, the handset sometimes believed (incorrectly) that the alarm had already triggered

and stopped trying to reconnect.

DISCONNECTED FROM WIFI FOR A LONG TIME

Background:

Sometimes the handset does not reconnect a lost WiFi connection. Disabling/enabling the WiFi adapter

resolves the problem.

Solution:

The key exchange phase of a roam can no longer end up in a blocked state.

IDLE HANDSET SOMETIMES CANNOT ROAM TO FULL AP IN A TSPEC ENABLED SYSTEM

Background:

Sometimes, the handset cannot roam to a full AP in a TSPEC enabled system.

Solution:

Wrong TID was disabled and/or TSPEC was disabled for wpa_supplicant even if it was enabled in the driver.

NOT POSSIBLE TO CONNECT VIA VPN

Background:

It is not possible to establish VPN connections.

Ascom Myco version 5.5.0

Solution:

VPN functionality had been corrupted, but is now cleansed and working again.

UNABLE TO MAKE/RECEIVE SIP CALLS FOR 2 MINUTES AFTER REBOOT IF VOICEMAIL NUMBER IS

CONFIGURED

Background:

When VoIP voicemail number is configured and handset is restarted it is not possible to make or receive calls

for the period of about 2 minutes.

When trying to make call from that handset GUI says 'Call failed'.

When trying to call that handset you get 'No response'

NOTE: This was seen when testing towards IP6000. Have no complete setup to try with other PBXes.

Not reproducible on 5.3.0

Solution:

Internal startup sequence cleaned up.

MWI STOPS WORKING AFTER REBOOT.

Background:

If VoIP voicemail number is configured on a handset and handset is rebooted, it stops receiving voicemail

indication.

Upgrade from 5.3.0 to 5.4.0 does the same scenario.

Solution:

This fix only affects the startup sequence of the phone when registering towards SIP proxy.

Startup sequence is now cleaned up. Before the correction, in some scenarios, several REGISTER requests

was sent to SIP stack resulting in undefined behavior - such as incorrect MWI subscription.

MWI STOPS WORKING AFTER A SHORT WIFI DISCONNECTION

Background:

If handset is configured to received voicemail indications (VoIP voicemail number) and that handset loses a

Wi-Fi connection for a short while (about 10-20 seconds out of Wi-Fi coverage) it then stops receiving MWI

and it fails to make/receive SIP calls for about 2 minutes.

If handset stays out of Wi-Fi coverage for a longer period (~1 minute maybe) so that it reports 'System failure'

('No phone calls or messages' popup on screen) - the problem is NOT reproducible.

Solution:

If MWI is configured and the device is registered with the PBX when a new PBX registration is requested, the

existing PBX registration (and MWI update subscription) is canceled. The new PBX registration is not started

until the unregistration has completed.

Ascom Myco version 5.5.0

DOCUMENT HISTORY

Rev Date Author Description

PA1 2016-07-15 SEJOAN This document is based on Software Declaration Myco

5.5.0_PA1.docx

A 2016-08-15 SEJOAN Approved version