Release note Ascom Myco | Version 6.4 · Ascom Myco version 6.4.0 Release note Ascom Myco™ ......

Ascom Myco version 6.4.0

Release note

Ascom Myco™ | Version 6.4.0

Gothenburg

October 25, 2016

[ ]


TABLE OF CONTENT:

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

SUMMARY CHANGES 6.4.0 ........................................................................................................................................... 5

NCR related changes................................................................................................................................................. 5

Change requests ....................................................................................................................................................... 9

New Features .......................................................................................................................................................... 12

Other changes ........................................................................................................................................................ 15

KNOWN ISSUES ........................................................................................................................................................... 20

DOCUMENT HISTORY ................................................................................................................................................. 23


GENERAL

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

HIGHLIGHT The Ascom Myco 6.4.0 contains approximately 50 improvements. Some highlights:

Ascom Myco SDK, Revision 2

APN setting in Device Manager

Easily distinguishable prio 1 alerts

SIP routing GSM emergency numbers

Local Music on Hold

PURPOSE OF THE RELEASE This version is for general availability, but combinations where 3G data is included is under Controlled Shipment. (NEW) This release is not allowed to be used in customer installations where Push button or Man-Down/No-movement alarms are sent over cellular network.

ASCOM MYCO FIRMWARE AND LAUNCHER Build date: 2016-10-14 Software name: Myco_Firmware_v6.4.0.pkg Software version: 6.4.0 OS version: 4.4.2

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

Compatibility info (NEW) Ascom Myco Firmware 6.4.0 is not fully compatible for use with MMG 4.4.2 and Cardiomax. Validation is ongoing and the plan is to be ready end of 2016. (NEW) The hotfix 5.3.4 is not included in this version. Therefor customer using hotfix 5.3.4 must not upgrade to

6.4.0. A hotfix 6.4.1 will be created with fix for the roaming issue due to small buffer in Wi-Fi firmware.

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.

Important:

(NEW) When upgrading to 6.4.0 active APN settings might be de-selected. Only affects the Cellular

version.

o Workaround is to apply a template from the Device Manager with the correct APN.

o If you are using the Cellular version with 3G data (i.e. APN) we recommend waiting for new

software with correction.

(NEW) When upgrading to 6.4.0 APN entries might be duplicated. Only affects Cellular version.

o If you are using the Cellular version with 3G data (i.e. APN) we recommend waiting for new

software with correction.


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 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.

https://confluence.ascom-ws.com/display/SD/3.1+Setup+Handsets+in+the+Device+Manager

https://confluence.ascom-ws.com/display/SD/3.2+Install+and+Configure+Handsets


SUMMARY CHANGES 6.4.0

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

NCR related changes

SUPPORT FOR ON-SITE TROUBLESHOOTING (SIP AND UNITE CONNECTIONS)

Background: Ascom technicians need a way to read logs on site. The log shall contain reasons for disconnects and audible warnings. The log shall be readable on site either from the handset or from a laptop.

Solution: Syslog content is now possible to read on a device. The shortcut to open the syslog window is: Settings->Admin settings->Ascom settings->Syslog viewer The following functionality is supported:

Displaying syslog messages in runtime, new messages appear at the bottom of the list

A coloring scheme to easily identify important messages:

Dark red for emergency, alert, critical and error messages

Dark orange for warning messages

all other messages are not colored

Auto-scrolling the list to the bottom when new message appears. This happens only when the list

exceeds the screen size and only if the previously last element is visible.

The reported Syslog messages have been improved for the Unite websocket connection and SIP

registration.

Whenever the Unite websocket is connected or disconnected, a detailed message is sent to the

Syslog which includes the RSSI of the wireless networks.

All calls to close the websocket from the handset now includes the reason for reconnecting.

If the SIP registration is down, the detailed reason message from the SIP stack is sent to the

Syslog.

THERE IS NO AUDIBLE INDICATION WHEN THE HANDSET IS UNABLE TO CONNECT TO UNITE ON START-UP

Background: There is no "beep" when starting up a phone and it cannot connect to Unite.

Solution: Added an audible indication when the handset is unable to connect Unite on startup. The audio indication is controlled by a parameter in the device manager: Sound -> Start-up connection failure sound

DELAY BEFORE THE VOICE STREAM STARTS

Background: When A calls B, B hears the voice stream first after 3 seconds. A hear the voice stream after 2 seconds.

Solution: The receiver de-pop function was activated in the hardware codec. This function removed the first second of audio played on the receiver to prevent sound pops during initialization. The function has removed because it is no longer needed.


CAPITALIZED BUTTON TEXT ARE TRUNCATED IN THE "IN CALL" VIEW IN SOME LANGUAGES

Background: Capitalized text in some languages below the buttons in the "in call" view are truncated, depending on which letters that are part of the word.

Solution: The spacing between buttons in the "In call" view is now increased which enables the use of capitalized translations for more languages, Dutch in particular.

SOME DUTCH TRANSLATIONS ARE TOO LONG AND NOT CORRECTLY CAPITALIZED

Background: Translations in Dutch for "toetsenblok" and "luidspreker" are too long and shall be capitalized.

Solution:

“Toetsenblok” has been changed to "TOETSENB."

“LUIDSPREKER” has been changed to "LUIDSPR."

HANDSET DOES NOT SEND DEAUTH REQUEST EVEN THOUGH IT IS ENABLED

Background: Even if the "Deauth on roam" parameter is enabled, the handset will not send a deauth request when roaming on WiFi.

Solution: Deauth request is now sent at roam if the "Deauth on roam" parameter is enabled.

THE HANDSET SHOWS "VOLUME RESET TO LOWEST LEVEL ALLOWED" AT EVERY MESSAGE THE HANDSET

RECEIVES

Background: The handset shows "Volume reset to lowest level allowed" at every message the handset receives when sending "urgent" Unite messages from the Ascom Ward Agent to a Myco with "Minimum volume" setting active.

Solution: Added a check to see if the Ring stream is muted before showing the toast. If the stream is muted, we vill optimistically assume that it's a transient state because of the notification taking control over the audio streams.

NEW SETTINGS FOR RIL NOT APPLIED ON UPDATE

Background: Changes to RIL configuration (ril.conf) are not applied correctly when upgrading a handset since the old configuration is not properly removed. The handset needs to be factory reset for the settings to be applied.

Solution: A delay has been added to the system update so that the old configuration is removed before we try to add the new configuration.

ACCIDENTAL HOLD/HANG UP A SIP CALL

Background: It is possible to hang up/hold a SIP call by accident when holding the phone to the ear. The proximity sensor does not disable the screen in time.

Solution: The proximity LED current has been increased and the proximity threshold (the distance where the screen is


turned off) has been increased from 5cm to 9.5 cm to avoid having the screen enabled while in a call and holding the phone to the ear.

THE ALERT BADGE COUNTER IS DISPLAYED INCORRECTLY WHEN THE ALERT SUBJECT IS LONG

Background: The highest prioritized and oldest alert that has not been handled is indicated in the top priority bar. A counter indicating the number of unhanded alerts is also shown here, but the counter is truncated when the alert subject is long. For example, display 10 unhandled alerts instead of 100.

Solution: The alerts badge counter now shows the correct value when there are 100 unhandled alerts and the alert subject is longer than 12 characters

UNEXPECTED RESTART OF APP (COM.ASCOM.UNITESERVICE)

Background: Unexpected restart in app (com.ascom.uniteservice) caused by a failing websocket.

Solution: Corrected a race condition bug which caused dereference of null members.

SHORTER BATTERY LIFETIME WHEN SIP HAS BEEN CONFIGURED BUT WIFI IS NOT AVAILABLE ON A

3G/WIFI HANDSET

Background: When the SIP service is configured and WiFi has been turned off, the SIP service tries incorrectly to reach the SIP proxy over the 3G data link. This causes the 3G modem to be powered up for approximately 12 seconds which causes an additional power consumption approximately 100 - 150 mA during this time. The problem only occurs if the WiFi has been turned on at some point after power up.

Solution: When WiFi is disconnected, the SIP client will no longer send out registration retries on the 3G network interface. As soon as WiFi is reconnected, the SIP client will try to register again.

SIP CALL FAILED WITH MESSAGE "END THE ONGOING CALL SESSION BEFORE STARTING A NEW CALL"

Background: In rare cases, it is not possible to place a SIP call and it fails with the error message "End the ongoing call session before starting a new call".

Solution: Make sure that all internal processes are ready to place a call before trying.

CALL-WAITING BEEP IS UNUSUALLY LOUD

Background: The call waiting indicator beep is unusually loud compared to the speech volume.

Solution: The call waiting tone volume has been decreased to more humane levels.


ACCELEROMETER KEEPS HANDSET FROM GOING INTO SUSPEND

Background: When the handset is moved it will stay awake for the next 100 seconds. The effect will be that the device never goes to sleep when it is being walked around decreasing the battery lifetime.

Solution: A device with man-down/no-movement enabled will now go to sleep if no motion is detected for 1 second since the last detection.

BUSY TONE IS PLAYED WHEN SECOND INCOMING CALL IS ENDED DURING CALL

Background: When someone calls in while the Myco is engaged a call waiting tone will sound, but when the incoming call is directed to voicemail or the caller hangs up the Myco plays a loud busy tone.

Solution: "Call ended by remote party" is not played if the call is in ringing state.

(UNATTENDED) TRANSFER REJECTED MESSAGE

Background: Calls transferred from an Ascom Myco to another phone give a rejected message but the transfer actually completes.

Solution: SIP INVITE after REFER when doing a unattended transfer is no longer treated as a failure. This behavior was introduced to resolve a PBX vendor specific bug, but can now be removed as the affected PBX version no longer is in use.

CALL-WAITING BEEP IS UNUSUALLY LOUD

Background: The call waiting indicator beep is unusually loud compared to the speech volume.

Solution: The call waiting tone volume has been decreased to more humane levels.


Change requests

MAKE PRIO 1 ALERTS EASILY DISTINGUISHABLE FROM OTHER ALERTS NCR/CR: CR-219

Background:

Prio 1 alerts shall be easily distinguishable according to standards for medical devices. The visual indication

of prio 1 alerts needs to be improved.

Solution: Prio 1 alerts are now additionally distinguished by adding a red border in both notifications and the alarm list.

CALL A SIP NUMBER STARTING WITH A GSM EMERGENCY CALL SEQUENCE NCR/CR: CR-206

Background: International handset standards specify which emergency call numbers that needs to be available in which situation. “ETSI 3GPP TS 22.101 version 14.3.0 (2016-06) Identification of emergency numbers a) 112 and 911 shall always be available. These numbers shall be stored on the ME. b) Any emergency call number stored on a SIM/USIM when the SIM/USIM is present. c) 000, 08, 110, 999, 118 and 119 when a SIM/USIM is not present. These numbers shall be stored on the ME. d) Additional emergency call numbers that may have been downloaded by the serving network when the SIM/USIM is present. “ Many installations of Myco use WiFi-only or WiFi/GSM handsets without the SIM. This creates a conflict between international GSM standards and the internal (SIP) number schemes. It must be possible for an administrator to manually set the valid emergency numbers when a SIM card or GSM network is not present.

Solution: It is now possible to configure the number(s) that shall be treated as emergency numbers when no SIM is present from the device manager (Telephony -> Emergency numbers for device without SIM). On a Cellular device, the value configured in this parameter will override the value specified by 3GPP TS 22.101 when no SIM/USIM is present (i.e. 000, 08, 110, 999, 118 and 119). 112 and 911 will still be treated as emergency number regardless of the configured value. On a Wi-Fi device, this value will override Androids default emergency number look up based on locale.

LOCAL MUSIC ON HOLD (MOH)

Background: Play local Music on Hold if the remote part does not provide it.

Solution: Music on hold can now be played if the remote party does not provide it. The feature can be activated from the device manager via the parameter "Telephony -> Ascom VoIP -> MoH locally".

APN SETTING IN DEVICE MANAGER NCR/CR: CR-69

Background:


APN settings shall be configurable from the Device Manager to simplify the deployment of multiple handsets

on a site.

Solution: The APN list and the Preferred APN parameter can now be configured from the device manager (Network -> Mobile networks). APNs have 20 attributes, including name, all of which can be modified via both the device manager and the Android Settings application.

USABILITY IMPROVEMENTS FOR ALERT HANDLING NCR/CR: CR-219

Background:

Improve the usability of alert handling

Solution:

Added new colors for nurse call messages indicated in GUI and by LED (burgundy, pink, grey, black, white, and magenta)

Improved indication of handled/accepted alerts (read status of alert in alert list, number of unread events below availability status and highlight of button press for accept)

The color of the badge indication has been changed from laguna to red The frequency of the LED indication for "Crisis" priority alerts has been changed from 2Hz to 3Hz to resolve a

conflict with IEC 60601-1-8 The correct user dialog is now shown when calling from an IM Support for showing confirmation text on option selection (DispText Unite tag) Updated event type icons for nurse call and call in top display

CALL A SIP NUMBER STARTING WITH A GSM EMERGENCY CALL SEQUENCE

NCR/CR: CR-206

Background:

International handset standards specify which emergency call numbers that needs to be available in which

situation. ETSI

3GPP TS 22.101 version 14.3.0 (2016-06)

Identification of emergency numbers

a) 112 and 911 shall always be available.

These numbers shall be stored on the ME.

b) Any emergency call number stored on a SIM/USIM when the SIM/USIM is

present.

c) 000, 08, 110, 999, 118 and 119 when a SIM/USIM is not present.

These numbers shall be stored on the ME.

d) Additional emergency call numbers that may have been downloaded by the

serving network when the SIM/USIM is present.

Many installations of Myco use Wi-Fi-only or Wi-Fi/GSM handsets without the SIM. This creates a conflict

between international GSM standards and the internal (SIP) number schemes. It must be possible for an

administrator to manually set the valid emergency numbers when a SIM card or GSM network is not present.

Solution: It is now possible to configure the number(s) that shall be treated as emergency numbers when no SIM is present from the device manager (Telephony -> Emergency numbers for device without SIM). On a Cellular device, the value configured in this parameter will override the value specified by 3GPP TS 22.101 when no SIM/USIM is present (i.e. 000, 08, 110, 999, 118 and 119). 112 and 911 will still be treated


as emergency number regardless of the configured value. On a Wi-Fi device, this value will override Androids default emergency number look up based on locale.

SUPPORT FOR INTERNATIONAL RING TONES (US/UK/JAPAN) IN SIP CALLS

NCR/CR: CR-39

Background:

The ringtone shall be configurable by country (UK/US/Japan) for SIP calls.

Solution: The ringtone for SIP calls is now configurable from the device manager (Sound -> Dialing tone patterns). Available options for ringtones are US, UK, Japan and other countries. When configured, the ringtone when establishing a SIP call is equal to what would be the ringtone when dialing with a SIM card from that specific region / country.

CLEAR MESSAGE WAITING INDICATION (MWI) ON CALL TO VOICEMAIL

Background: Since some PBXs do not notify the handset on remaining unlistened voice mail messages, the handset needs another way to clear the message waiting indication (and badge). Add the same possibility as in i62 to clear the MWI notification (and badge) upon a call to voicemail.

Solution: A parameter in the device manager has been added to control this functionality (Telephony -> Voicemail -> Voicemail call clears MWI). When this is set to "Yes", the handset will clear the pending MWI notification and badge upon a successful connected (VoIP) call to the number specified by the "Voicemail number" parameter.

DISPLAY NAME AND NUMBER FROM PBX IN SIP CALL

NCR/CR: Part of CR-115

Background:

Display the name and number received from the PBX in a SIP call.

Solution: Both name and number from PBX are now shown during the connecting phase on incoming and outgoing SIP calls. Known limitations

Phone bar: The number is shown instead of the name before the call is connected when doing an outgoing SIP call.

Call forwarding: If you make a SIP call to a phone with call forwarding, the number of the called phone will be shown. This differs from the i62 handset.


New Features

DEMO APPLICATION FOR THE BARCODE SCANNER Affects system/s: Requires Ascom Myco 6.4.0 or later

Background:

Create an application which can demonstrate the Ascom Myco barcode capabilities while not needing a

barcode license to work.

Solution: The barcode scanner demo application (DemoBarcodeScanner) now starts in unlicensed mode when no valid license is available instead of closing with an error. The old barcode scanner demonstration application (MyBarcodeScanner) is still valid, but now serves as an tutorial/test application for developers.

TESTFUNCTION: NUMBER OF ALERTS

Background: There is a need for a test function the returns number of alerts. To read the number of unhandled (unread) alerts would also be useful. This test function is probably similar to getReceivedPagingCount()

Solution: The following methods were added to the test interface:

{{getAlertsFromDb}} {{getUnreadAlertsFromDb}} {{getNumberOfAlerts}} {{getNumberOfUnreadAlerts}}

See the generated Javadoc for more details.

ADD TEST FUNCTION TO GET AND SET SYSTEM PROPERTIES

Background: To allow automated testing on release builds, we need to add a test interface function for setting system properties since the shell user (the one used when running "adb shell setprop") does not have permission to alter all properties needed. We want to do this so we can run product tests on the actual release candidate without having to build a "rooted" engineering build to run the tests.

Solution: Two new test functions have been added to the test interface. It is now possible to get and set system properties that are owned by the system user through the test interface.

INFORM THE USER WHEN 3G/GSM IS NOT AVAILABLE

Background: Create a notification similar to when SIP/Unite is unavailable.

Solution: New problem type "No telephony" has been added. The warning can be shown from 5 minutes after startup if there is a problem making phone calls via 3G. The "No telephony" warning will be shown even if user can make SIP calls (compare with if SIP registration goes down and user can still make 3G calls, the "No phonecalls" warning will be suppressed). Limitations:


The warning message is only available in English and Swedish for this release. There is no parameter for controlling this warning.

CONFIGURE MOBILE DATA THROUGH DEVICE MANAGEMENT

Background: Create a parameter to enable/disable mobile data from the device manager.

Solution: Added a device manager parameter (Network > Mobile networks > Enable cellular data (caution)) to configure the mobile data. Important note: If there is no Wi-Fi configured on the device, disabling cellular data will result in the device being unable connect to Unite. As a consequence the device will not be able to send or receive alerts or messages and will not be visible in the Device Manager. Disabling or enabling cellular data does not have any effect on GSM-calls.

IMPROVED DEVICE DIAGNOSTICS SUPPORT

Background: The diagnostic application needs to be able to verify important functionality so that it can be used to screen units that comes back from the field. The current application includes some of the necessary tests, but most needs to be improved and it should be possible to step to the next ‘test step’ if the test is ‘Pass’ or cancel the test procedure if it is ‘Fail’.

Solution: New features:

Added a restart button to the action bar so that the user can restart a test easily if needed. Added a test for checking if the accelerometer works as intended. Added a test to check if the device's NFC module is working. Added a test to check if the WiFi adapter can find nearby networks. Added a test to check if the GSM adapter can read current SIM-card and if it finds any GSM network. Added a LED test that flashes the LED in white color for 5 seconds. Added version control so that tests that should not work on the device are not included in the test suite. Added a notification to the user when the test suite is completed.

Improved features:

Updated how the user navigates between tests by moving both the "Select all tests" and "next test" 'action buttons' out from 'OptionsItem' so that they are directly visible to the user. Navigation have further improved by adding a button to navigate to the next test in most tests.

Updated the display test to show the name of the currently displayed color and included a grayscale. Updated the touch test to not only show strokes but also the actual touches on the screen. Updated the microphone test to automatically stop the recording and playback after 3 seconds respectively. Improved the interface by having a coherent design throughout the application. Updated the button tests (volume and alarm) by combining them in one test.

Known issues:

The LED test does not work when the Myco launcher is activated

ASCOM MYCO SDK, REVISION 2 NCR/CR: CR-27

Background:

The Ascom Myco SDK shall be updated to support integration into the Ascom Myco launcher.


Solution: This revision introduces the following APIs:

Single sign-on support Generic user authentication handling Generic user availability handling Show custom contacts activity and lookup contact info A collaboration application can inform the platform its number of unread events Modify the visibility of Android's navigation bar when using virtual navigation keys Possibility for third party applications to get the Unite Messaging Call ID (CR-27) Support for starting barcode scanning via Ascom Myco's built in scanner application

Additional fixes:

Support for Android Studio 2.0 (and later) on Linux

Deprecations:

The standalone barcode scanning APIs are still supported, but will be deprecated with the release of the API level 22 (Lollipop) SDK. Please migrate your applications to the barcode scanning functionality of the Ascom Myco SDK. It is the same API, but a different namespace.


Other changes

ADD SUPPORT FOR TOUCH IC GT5688 (FIRMWARE VERSION 5.6.0)

Background: We need to support both touch IC GT915 and touch IC GT5688 due to end-of-life support for GT915.

Solution: Both touch ICs GT915 and GT5688 are now supported for Ascom Myco hardware configurations (i.e. supporting Ascom Myco handsets produced after October 2016).

HANDSET DOES NOT INDICATE WHEN NUMBER LOGIN TO UNITE CM FAILS

Background: The handset has two login states:

1. Logged in as device

2. Logged in as number

If both device and number login fails, a problem notification is shown that informs the user that the handset will NOT receive alerts and messages. If device login is successful but the number login fails, the handset will not be able to receive alerts and messages. The user is not informed about this. The alerts list will show as normal, and no problem notification is shown. If User login is enabled, the User login panel is shown after the failed number login. When the user tries to perform a user login, it will fail.

Solution: Added a connection loop sequence that is shown in the start-up phase. If a problem exist, the user will be informed about the nature of the problem and what he/she needs to do to solve it.

HANDSET RESTARTS WHEN PRESSING SOFT HOME BUTTON INSIDE LAUNCHER WHILE IN A CONNECTING

STATE

Background: Pressing soft HOME button when launcher is open can cause an unexpected restart with the reason: MycoLauncher restart: java.lang.IllegalStateException: Recursive entry to executePendingTransactions

Solution: Changed the architecture to avoid a state that caused recursive fragment transactions.

AVAILABILITY PANEL BEHAVES INCONSISTENTLY WHEN UNITE CONNECTION IS LOST

Background: When the Unite connection is lost, a warning notification will indicate the connection loss. After connection loss, it is still possible to change availability for a few minutes before the Availability panel also shows the connection loss.

Solution: The Availability activity is now listening for connectivity changes broadcasted by the Supervisor Service and will now directly indicate connectivity warnings instead of after a few minutes.


ALERT IS ACCESSIBLE VIA TOP PRIO BAR EVEN THOUGH USER IS LOGGED OUT

Background: The first unhandled alert is accessible via the Top Prio bar even though a user is logged out. If the first unhandled alert is closed, the second is accessible etc. Unhandled alerts shall not show up unless the user is authorized.

Solution: Added a check to make sure unhandled alerts show up in Top Prio bar only when the user is authorized.

"SEND" ICON DISAPPEARS AFTER A CONVERSATION MESSAGE IS SENT

Background: The "Send" (green arrow) icon disappears after the conversation message has been sent. The icon shall be displayed as inactive (with grey color) when the message is empty and shall be green when the user has typed any character in the message.

Solution: The button background is now updated instead of setting the send button visibility to "GONE" after sending a conversation message.

IM OF TYPE "CONFIRMATION" IS NOT UPDATED PROPERLY IF IT IS OPEN WHEN AN UPDATE ARRIVES Background:

IM of type "Confirmation" (e.g Accept/Reject) is not updated properly if it is open in full screen when an

update arrives. Buttons are updated but neither text nor icons are. As soon as the IM is closed, everything is

updated. This only affects IM of type "Confirmation", other types of IM are updated properly in full screen.

Solution: The callback code for updating the user interface is now run for all types of IMs, including Confirmations.

THE VOICE QUALITY IN LOUDSPEAKER MODE IS AFFECTED BY NOISE REDUCTION FUNCTIONALITY

Background: Noise reduction shall not be enabled during loudspeaker mode, currently it is always on.

Solution: The codec driver was writing to the wrong coefficient for turning on/off noise reduction which caused the noise reduction to be enabled in some cases for the loudspeaker mode. The noise reduction shall only be used in receiver mode.

THE CELLULAR VOICEMAIL NUMBER DOES NOT ACCEPT THE '+' SIGN

Background: It shall be possible to enter a number starting with '+' or '*' when configuring the "Telephony -> Voicemail -> Cellular voicemail number" parameter in the device manager.

Solution: The input check now correctly allows '+' and '*' at the start of a cellular voicemail number.

NOT ABLE TO PASTE IN THE MESSAGE VIEW AFTER SENDING A MESSAGE

Background: It is not possible to paste text in the text field after the user sends a conversation message.

Solution: The cursor in the text field has been activated to allow input.


AUTOMATIC CALL AFTER ALARM IS NEVER ACTIVATED IF FIRST ACTIVATION ATTEMPT WAS MADE WHILE

NO NETWORK CONNECTION

Background: If automatic call after alarm was first activated while no network connection, it will not be activated even if network connection is restored. It is activated again only after an outgoing call is made.

Solution: Added check to see if there is GSM network before attempting to make call. It prevents Myco from setting flag that call is in progress when it is not possible to make calls.

UPDATING WIFI NETWORK CONFIGURATION FAILS IF PASSWORD IS SET TO '*'

Background: When updating a network from framework, the update will fail if the password is a *, leading to a partial saved network.

Solution: Invalid password (only a '*') is ignored when updating an existing network, i.e. the update will not be failed and the invalid password will not be saved. For a new network the network will not be saved.

SPECIAL CHARS LIKE \+'[+#]/*; CAN BE ENTERED TO HOSTNAME INPUT FIELD

Background: Special characters, such as \+'[+#]/*; can be entered in hostname input field even though they are not allowed, resulting in invalid hostname.

Solution: Implemented template to prevent entering special symbols like \+'[]#/*.

3G MODEM AUTOMATIC RESTARTS TRIGGER USER PIN INPUT

Background: In case of a data stall, the modem will be automatically restarted (DCT recovery action 3 and 4) and the cached pin will be reset in rild resulting in user PIN input.

Solution: Configure rild to not reset the stored PIN so it can be used after modem power down (restart, flight mode).

BUGREPORT APP CRASHES WHEN TRIGGERED ON OLD SOFTWARE

Background: When version 1.4 of the app is triggered by for example, a lost WiFi connection, it crashes due to "method not existing".

Solution: If the functionality for starting 10 minutes of logging is not present in the Myco software, the current logs will be dumped instead of crashing.

ACCELEROMETER TRANSIENT IRQ IS ALWAYS ON EVEN IF MAN-DOWN/NO-MOVEMENT FUNCTIONALITY

IS NOT ACTIVATED

Background: Accelerometer transient irq is always on by default in boot even if man-down/no-movement functionality is not


activated. This causes the device to wake up from suspend when it is moved. Enabling and then disabling man-down/no movement functionality resolves the issue.

Solution: Interrupts from the accelerometer will now be turned off at boot. The device will no longer wake up from suspend when moved unless Man-Down/No-Movement has been turned on.

AVAILABILITY STATUS INDICATION COLOR IS ALWAYS GREY

Background: The availability status icon is always grey regardless of the Unite login status. It shall be green when the device is logged in to Unite. The behavior is the same no matter if 'Require user login' is set to "On" or "Off" in the device manager.

Solution: Changed the logic so that we show a green ball in the notification if we are online. Before, we would show a grey ball when we were connected but now we check the connectivity before we look at availability.

SUPERVISION FOR ENUMERATION OF USB BUS TO GSM MODULE

Background: While implementing fixes for updating the GSM module firmware we found that the enumeration problems we have seen on the USB bus to the GSM module can be solved by reloading the USB driver. Add supervision of the /dev/ttyUSBx interface which can reload the USB driver if we see an incorrect enumeration.

Solution: A modem supervision daemon was added that monitors USB re-enumerations and fixes any mismatching enumerations. It also stores the number of times the mismatch happens and latest time it happened in 2 system properties (persist.ascom.gsm.usbenmfixcnt, persist.ascom.gsm.usbenmfixlast).

INCORRECT USB VENDOR ID

Background: The Ascom Myco identifies itself as a "Google Inc." device when developer options (USB debugging) is turned off.

Solution: The USB vendor ID has been corrected and the device now identifies itself as an Ascom Myco.

UPDATE TO GEMALTO RIL 1500

Background: N/A

Solution: Gemalto RIL updated: June 2015: Version 1.5.0.0:

Support of Android 5/5.1 Add missing DCS codes for SAT with EHSx Rel2 Workaround for blocking AT interface after AT+CSCB in PHS8 New setting "IncludeARevision" Correction on SAT Icons Solve problem with too many polling requests on network loss


APPLY FIXES FOR SECURITY ISSUES REPORTED IN NEXUS SECURITY BULLETIN FOR MAY 2016

Background: Apply fixes for security issues reported in Nexus Security Bulletin for May 2016, which are applicable for the platform and not causing conflicts.

Solution: Applied the following security patches:

Remote Code Execution Vulnerability in Mediaserver (CVE-2016-2428,CVE-2016-2429) Remote Code Execution Vulnerability in Bluetooth (CVE-2016-2439) Elevation of Privilege Vulnerability in Binder (CVE-2016-2440) Elevation of Privilege Vulnerability in Wi-Fi (CVE-2016-4477) Elevation of Privilege Vulnerability in Mediaserver (CVE-2016-2448,CVE-2016-2449,CVE-2016-2450,CVE-2016-

2451,CVE-2016-2452) Information Disclosure Vulnerability in Mediaserver (CVE-2016-2459,CVE-2016-2460)

APPLY FIXES FOR SECURITY ISSUES REPORTED IN NEXUS SECURITY BULLETIN FOR JUNE 2016

Background: Apply fixes for security issues reported in Nexus Security Bulletin for June 2016, which are applicable and not causing conflicts.

Solution: Applied the following security patches:

Remote Code Execution Vulnerability in Mediaserver (CVE-2016-2463) Remote Code Execution Vulnerabilities in libwebm (CVE-2016-2464) Elevation of Privilege Vulnerability in Mediaserver (CVE-2016-2484,CVE-2016-2485,CVE-2016-2486,CVE-2016-

2487) Elevation of Privilege Vulnerability in SD Card Emulation Layer (CVE-2016-2494) Remote Denial of Service Vulnerability in Mediaserver (CVE-2016-2495) Information Disclosure Vulnerability in Mediaserver (CVE-2016-2499)

WIFI VERSION 4.3.B

Background: N/A

Solution: WiFi version 4.3.b contains and update to Redpine firmware 4.2.12.3:

1. Fixed an issue where the module tries to connect to an AP in wrong channel.

2. Enhancements to the EAPOL packet handling.


KNOWN ISSUES

NEW - When upgrading to 6.4.0 active APN settings might be de-selected.

o Workaround is to apply a template from the Device Manager with the correct APN.

- VPN does not connect over 3G

- Big delay in (re-)connecting to Aruba WLAN system with hidden SSID

- Alcatel OXE: SRTP mode above 128 bit encryption fails

- Not possible to cancel ongoing GSM call when GPS is active

o Workaround is to keep the parameter ‘location settings’ to ‘off’

- Handset has Unite connection but indicates lost connection with Led and vib

o Only affects handset with SIM card and the parameter 'startup connection failure sound' changed

from default value.

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.

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

- 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:

o 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.

o 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.

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

- Limitation scanning channels:

o 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.

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

o 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. - Server validation when using 802.1X authentication 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.

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”.


DOCUMENT HISTORY

Rev Date Author Description

PA1 2016-10-18 SEJOAN This document is based on Software Declaration Myco

6.4.0_PA1.docx

PA2 2016-10-19 SEJOAN Added issues from release 5.6.0 and 5.6.1

PA3 2016-10-21 SEJOAN Added known issues

A 2016-10-21 SEJOAN Approved

PB1 2016-10-25 SEJOAN Updated information (NEW) in section “Important”

Updated statement in section “Purpose of the release”

B 2016-10-25 SEJOAN Approved

Release note Ascom Myco | Version 6.4 · Ascom Myco version 6.4.0 Release note Ascom Myco™ ......

Documents

Transcript of Release note Ascom Myco | Version 6.4 · Ascom Myco version 6.4.0 Release note Ascom Myco™ ......