Technical Information

List of AMC+ Supported Mobile Operating Systems and Tested Phone models

Aastra Deutschland GmbH Date: 2011-12-20 Zeughofstraße 1 Doc no: ASE/FMC/PLM/ 0001 10997 Berlin • Germany Version : RH www.aastra.com

Contents

1 Introduction ...... 3 2 Supported Communications Systems ...... 3 3 Supported phone OS ...... 3 3.1 Android phone OS ...... 3 3.2 BlackBerry RIM OS ...... 3 3.3 3rd edition...... 4 3.4 Symbian S60 5th edition, Symbian ^3 & Symbian Anna ...... 4 3.5 iPhone OS phones ...... 5 4 AMC+ Test Results with Different Mobile Phones Models ...... 6

2 (8)

1 Introduction Aastra Mobile Client plus (AMC+) 2.0 has been tested on different types of mobile phones and their Operating Systems (OS) in order to secure good product quality and interoperability. From that reason Aastra cannot guarantee that other mobile phone releases or OS can work with AMC+ software in the same way, unless they have been properly validated by Aastra or Aastra’s assigned partners. Aastra cannot either accept any liability for faults discovered in 3rd party software or hardware products (e.g. mobile phones and OS), which are not under Aastra’s control. However, should there be any compatibility issues or faults discovered with any new mobile phone and/or OS release, Aastra will work with mobile phone vendors/partners to find a suitable resolution in a timely manner to minimize the inconvenience to customers. 2 Supported Communications Systems AMC+ 2.0 supports following Aastra call managers: Aastra MX-ONE V.4.1, Aastra 700, Aastra 5000, IntelliGate / Aastra 400 and OpenCom.

For more details, please, see AMC information for the respective platform release. 3 Supported phone OS

3.1 Android phone OS AMC+ 2.0 supports Android 2.1 – 2.3. AMC+ 2.0 software for Android based OS phones can be downloaded from the AMC portal or the market place. It is recommended to use the Android market place for installation as it will give the user notifications of available software updates. Current release of AMC+ for Android does not yet support instant messaging and presence.

Android phone known problems: • SonyEricsson X10 - Consumes a lot of battery if Wi-Fi is turned on - The audio quality on this device in VoIP is affected by very sensitive microphones • Motorola Defy is currently not supported due to proximity sensor problem where the feature screen turns black at feature requests • Samsung Nexus S is not currently supporter due to automatic Wi-Fi/GSM handover instability issues • Samsung Galaxy SII is not currently supported due to issues with call log • headsets are not guaranteed to work with Wi-Fi / VoIP calls • Huawei U8100 has memory problem that affects AMC+ stability • Some phones have problems with Wi-Fi power saving, meaning that despite setting the device to the contrary, Wi-Fi is turned off in standby mode. This, of course, affects clients using Wi-Fi. Therefore a setting in the client has been provided to override this system power management issue. Note that you should only disable the power saving in the client if you have a problem regarding this.

3.2 BlackBerry RIM OS AMC 2.0+ supports RIM OS versions 5.0, 6.0 & 7.0 The AMC 2.0+ software for the correct OS version can be downloaded from the AMC portal. To know which OS version is installed on the phone do following: On the phone go to option menu Æ About or, if the user is connected to a BlackBerry Enterprise Server (BES), you can check which OS the user has installed on the device.

BlackBerry RIM OS known issue: • Bluetooth headsets are not guaranteed to work with Wi-Fi / VoIP calls

3 (8)

• In VoIP / Wi-Fi call cannot disable RIM security timer. If used, users might have to type in password for answering and hanging up VoIP calls if device locking is enabled. Here is a list of known issues: • When pressing "Euro" or $ key in GSM calls while the client is in foreground, the speaker will not be activated or deactivated. Please, use either the menu or put the client to background, then press it. This issue is a known and acknowledged bug on Blackberry firmware • There are problems with the 303 and 297 firmware of the Bold device that can lead to device crashing during the activation of the loudspeaker in a VoIP call, or during handover of a VoIP call. We recommend upgrading to 5.0.x firmware version • In Bold 2 with firmware versions below 593, there are problems with call log entries. (This is fixed in later versions.) • In Bold 2 firmware version 351, the ringtone for VoIP call is not sometimes permanently stored. Usually this can be fixed by reinstalling the client for resetting the configuration for the device. Also you can create a custom profile (other than the Standard) where you will also not have the problem • It is not recommended to turn on file logging on the Bold 2 device, since it can become very slow, especially in VoIP mode • VoIP calls cannot be accepted if the Blackberry is in password lock mode. The user must first unlock it • The client has no way to know the utilized audio path in GSM calls (speaker, earpiece). This also means that the client can only display all choices at all times and let the user choose. Furthermore, since the current status is not known, it cannot be preserved through a GSM to Wi-Fi handover • When muting a GSM call on the native GUI, no icon will be displayed inside the client for this. The same applies for loudspeaker • During a handover the currently set audio path (speaker / mute) gets lost and must be manually reestablished. Unfortunately there is no way to set the GSM audio path from the client

3.3 Symbian S60 3rd edition AMC+ 2.0 supports most of the Symbian S60 3rd edition FP2 phones. Please search on Internet to find out what OS type the phone has (manufacture web page, manufacture forums or Wikipedia). Typical manufactures of Symbian S60 3rd based phones are: , LG and Samsung.

Symbian S60 3rd edition phone known issues: • Bluetooth headsets are not guaranteed to work with Wi-Fi / VoIP calls • In some markets customers has reordered that Nokia E52, E72 & C5 phones in specific networks have sporadic problems with no audio on outgoing GSM calls. The current client provides some detection for this phone behavior and will abort any such call and display a warning message. Should such state persist over multiple calls, the phone needs to be rebooted.

3.4 Symbian S60 5th edition, Symbian ^3 & Symbian Anna AMC+ 2.0 supports most of the Symbian S60 5th edition & Symbian ^3 & Anna phones. Please, search on Internet to find out what OS type the phone has (manufacture web page, manufacture forums or Wikipedia). Typical manufactures of Symbian S60 5th based phones are: SonyEricsson, Nokia, LG and Samsung.

Symbian S60 5th edition phone known issue: • Samsung and SonyEricsson phones do not provide good VoIP speech quality without headset attached to the phone • SonyEricsson Satio and Vivas are not recommend due to processor capacity (AMC+ becomes very slow on theses phones). • Bluetooth headsets are not guaranteed to work with Wi-Fi / VoIP calls

4 (8)

Here is the list of Symbian hints: • Since Symbian 3 is taking the complete control of access point handling, so the AP configuration in the client can be problematic. Depending on what you set there, this can have grave consequences for the client behavior. The native priorities are the ones that are important to configure, since the system has the last say in AP connection. This means that for your Internet connection in the system, all Wi-Fi access points must be before the first GPRS access point to make sure the client connects over Wi-Fi. Furthermore, the GPRS access point providing Internet access (as compared to MMS or WAP) must be above any of those. Since the application has no influence on AP selection anymore, we can only make things in the client more intuitive and alert for the user in order to avoid wrong configuration, but we cannot actually override the system behavior • Sometimes the first configurations download after application installation fails on an E52. This can happen in the case application was not able to establish a data connection quickly enough. Simply retry this again. • If you see the message "Maximum Number of connections reached. Please close an active connection first. (-6000)" error message or similar when trying to use features in GPRS, please make sure to check your APN settings. It is a known Symbian issue to react this way on a failed connection attempt • When typing a number with a + or a * as the first character inside the client, this character can only be seen when typing the next digit or other character. This happens on E52 and is a firmware issue • Activating the loudspeaker in VoIP calls on Symbian ^3 phones is currently disabled as several firmware versions across different phones have broken firmware support for this

3.5 iPhone OS phones AMC+ 2.0 supports iPhone iOS v4 & 5 phones. AMC+ 2.0 software can be downloaded from the Apple iStore. iPhone OS phone known issues: • iPhone requires data access during the cellular call to handle mid call services (e.g. 3G or Wi-Fi) • No seamless hand over from Wi-Fi to GSM (only from GSM to Wi-Fi). The handover from Wi- Fi to GSM must be manually triggered • When traveling aboard, users have to set manually AMC+ to roaming

Here is what we provide in addition: • Silencing ringing with power button in Wi-Fi only works if the phone is not in the lock screen. This currently seems a system restrictions, but question have been posted to Apple to clarify the behavior • Not all settings can be applied on the fly if an OTA download happened or if these are changed on a multitasking phone. To make sure that all settings have been applied, please restart the application • AMC+ can not reset the phone lock password. • When iPhone is in GSM communication not managed by AMC, AMC Wi-Fi call can be answered but no voice establish for this Wi-Fi call.

5 (8)

4 AMC+ Test Results with Different Mobile Phones Models Phones listed below have been tested with good results in Germany, Switzerland and Sweden. It should however be noted that other solutions or network scenarios can show different test results.

Basic Extended tests function AMC Operator passed tests AMC version Controller OS Version Mobile Phone PBX Platform subscription (~60 passed Version test (~150 test cases) cases) MX-ONE V.4.1, Telia (Swe) AMCC125 OpenCom 1000, Telekom.de AMC+ 2.0.4.1088 AMCC30 Symbian 3rd Nokia E72 Yes Aastra 400, SwissCom v.10684.x Aastra 5000 Orange AMCC125 Telekom.de OpenCom 1000, AMC+ 2.0.4.1088 AMCC30 Symbian 3rd Nokia E75 SwissCom Yes Aastra 400 v.10684.x AMCC125 MX-ONE V.4.1, Telia (Swe) AMC+ 2.0.3.1058 AMCC30 Symbian ^3 Nokia C7-00 OpenCom 1000, Telekom.de Yes Yes v.10684.x Aastra 400 SwissCom AMCC125 OpenCom 1000, Telekom.de AMC+ 2.0.3.1058 AMCC30 Symbian ^3 Nokia N8 Yes Aastra 400 SwissCom v.10684.x MX-ONE V.4.1, Telia (Swe) AMCC125 OpenCom 1000, Telekom.de AMC+ 2.0.2.1058 AMCC30 Symbian 5th Nokia N97 Yes Aastra 400, SwissCom v.10684.x Aastra 5000 Orange AMCC125 MX-ONE V.4.1, Telia (Swe) Samsung AMC+ 2.0.11.1879 AMCC30 Android 2.3.3 OpenCom 1000, Telekom.de Yes Yes Galaxy S I v.10684.x Aastra 400 SwissCom Telia (Swe) AMCC125 OpenCom 1000, Samsung Telekom.de AMC+ 2.0.11.1879 AMCC30 Android 2.3.3 Aastra 400 Yes Galaxy S II SwissCom v.10684.x Aastra 5000 Orange MX-ONE V.4.1, Telia (Swe) AMCC125 AMC+ 2.0.10.1822 Android 2.2 Desire Z OpenCom 1000, Telekom.de Yes v.10684.x Aastra 400 SwissCom MX-ONE V.4.1, Telia (Swe) AMCC125 AMC+ 2.0.5.1436, BlackBerry OpenCom 1000, Telekom.de Yes (none AMCC30 BB bold 9700 Yes AMC+ 2.0.9.1685 RIM 5.0 Aastra 400 SwissCom for 2.0.5) v.10684.x Aastra 5000 Orange, SFR MX-ONE V.4.1, Telia (Swe) AMCC125 IPhone iPhone 3GS OpenCom 1000, Telekom.de AMC+ 2.0.10.1311 AMCC30 Yes Yes iOS4.3.1 32GB Aastra 400 SwissCom v.10684.x Aastra 5000 Orange, SFR AMCC125 OpenCom 1000, Telekom.de IPhone AMC+ 2.0.10.1311 AMCC30 iPhone 4 Aastra400 SwissCom Yes iOS4.3.5 v.10684.x Aastra5000 Orange, SFR IPhone iPhone 4, Orange AMC+ 2.0.12.1451 V.10684.x Aastra5000 Yes iOS5.0.1 iPhone 4S AMCC125 HTC Desire Z AMC+ 2.0.11.1879 Android 2.3.3 MX-ONE V.4.1 Telia (Swe) Yes v.10684.x A7272 Telia (Swe) AMCC125 Samsung AMC+ 2.0.11.1879 Android 2.3.4 MX-ONE V.4.1 Telekom.de Yes v.10684.13 Nexus S SwissCom AMCC125 MX-ONE V.4.1, Telia (Swe) AMC+ 2.0.11.1879 AMCC30 Android 2.3.3 HTC Wildfire S OpenCom 1000, Telekom.de Yes v.10684.x Aastra 400 SwissCom AMCC125 Telia (Swe) OpenCom 1000, AMC+ 2.0.11.1879 AMCC30 Android 2.3.3 HTC Wildfire Telekom.de Yes Aastra 400 v.10684.x SwissCom AMCC125 MX-ONE V.4.1, Telia (Swe) AMC+ 2.0.11.1879 AMCC30 Android 2.3.3 HTC Desire HD OpenCom 1000, Telekom.de Yes v.10684.x Aastra 400 SwissCom AMC+ 2.0.11.1879 AMCC125 Android 2.3.3 Ericsson Xperia MX-ONE V.4.1, Telia (Swe) Yes

6 (8)

v.10684.x ARC OpenCom 1000, OSD Aastra 400 Telekom.de SwissCom MX-ONE V.4.1, Telia (Swe) AMCC125 AMC+ 2.0.8.1618, Blackberry OpenCom 1000, Telekom.de AMCC30 BB bold 9780 Yes AMC+ 2.0.9.1685 RIM 6.0 Aastra 400 SwissCom v.10684.x Aastra 5000 Orange, SFR AMCC125 Blackberry AMC+ 2.0.10.1688 BB Torch 9810 MX-ONE V.4.1 Telia (Swe) Yes v.10684.x RIM 7.0 AMCC125 MX-ONE V.4.1 Telia (Swe) AMC+ 2.0.5.1201 Symbian 3rd Nokia C5-00 Yes No Wi-Fi v.10684.x Aastra5000 SFR

7 (8)

------© 2011 Aastra Technologies Limited. All rights reserved. This document contains proprietary information, which is protected by copyright. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, or translated into another language, without the prior written consent of Aastra Technologies Limited, Concord, Ontario, Canada.

NOTICE The information in this document is subject to change without notice. AASTRA MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. AASTRA shall not be liable for errors contained herein, neither for incidental nor for consequential damages in connection with the furnishing, performance, or use of these materials.

Aastra Technologies Limited Concord, Ontario, Canada

8 (8)