JD/NC-95/4 ABS - Alcatel
Transcription
JD/NC-95/4 ABS - Alcatel
TECHNICAL COMMUNICATION No. TC1118 Ed. 12 OmniPCX Enterprise/OmniPCX Office Nb of pages : 20 Date : 5 October 2010 URGENT NOT URGENT TEMPORARY PERMANENT SUBJECT: TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS CONTENTS 1. INTRODUCTION ..........................................................................3 2. RELEASED COUNTRIES ................................................................3 3. COMPATIBILITIES.........................................................................4 3.1 With the OmniPCX Office Communication (cellular mode only) ................ 4 3.2 With the OmniPCX Enterprise Communication.......................................... 4 3.2.1 In cellular mode................................................................................................4 3.2.2 In dual-mode (cell/WiFi) (NCC only).................................................................5 4. PRODUCTS ACTIVATION AND LICENSES .....................................5 5. NOKIA NCC 2.2.26 .....................................................................6 5.1 Main features ........................................................................................... 6 5.2 Supported devices for NCC 2.2.26............................................................ 6 5.2.1 In cellular mode only ........................................................................................6 5.2.2 In dual-mode and/or cellular mode..................................................................6 5.3 5.3.1 Known restrictions in version NCC 2.2.26................................................. 7 Tips...................................................................................................................8 5.4 Delivered corrections for this version ........................................................ 9 5.5 NCC 2.2.x clients installation .................................................................... 9 5.6 Upgrade to the NCC 2.2.x clients............................................................ 10 5.6.1 Upgrade from ICC 2.1m or NCC 2.2.13 to NCC 2.2.y (with y ≥ 16) ...............10 5.6.2 Upgrade from NCC 2.2.x (with x ≥ 16) to NCC 2.2.y......................................10 5.7 Nokia PC tools ........................................................................................ 11 1 ACE 2.3.7.4 ON WINDOWS MOBILE® 6.X ..................................12 6. 6.1 Main features ......................................................................................... 12 6.2 Supported devices................................................................................... 13 6.2.1 Generic devices ..............................................................................................13 6.2.2 Orange devices...............................................................................................13 6.3 Known restrictions in version 2.3.7.4 ...................................................... 14 6.3.1 Restrictions .....................................................................................................14 6.3.2 Devices Specific Restrictions ............................................................................14 6.3.3 Tips.................................................................................................................14 6.4 ACE 2.3.7.4 signed version..................................................................... 15 6.4.1 Delivered corrections for this version ..............................................................15 6.5 ACE 2.3 client installation ....................................................................... 15 6.6 Microsoft ActiveSync ............................................................................... 16 MCE 1.1.8.0 ON WINDOWS MOBILE® 6.5 .................................17 7. 7.1 Main features ......................................................................................... 17 7.2 Supported devices................................................................................... 17 7.2.1 Generic devices ..............................................................................................17 7.2.2 T-Mobile devices .............................................................................................17 7.3 Known restrictions in version 1.1.8.0 ...................................................... 17 7.3.1 Restrictions .....................................................................................................17 7.3.2 Devices specific restrictions .............................................................................18 7.3.3 Tips.................................................................................................................18 7.4 Delivered corrections for this version ...................................................... 18 7.5 MCE 1.1 application installation ............................................................. 19 8. 8.1 SOFTWARE DEPLOYMENT USING BPWS ....................................20 Download link 'Other' ............................................................................. 20 2 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 1. INTRODUCTION This document describes the NCC 2.2.26 (Nokia Call Connect), ACE 2.3.7.4 (Advanced Cellular Extension) and MCE 1.1.8.0 (My Cellular Extension) versions available for the Alcatel-Lucent mobility solution for cell phones. It concerns all the nomadic mobile users using the Cellular Extension function of the Alcatel-Lucent OmniPCX Office / Enterprise. Nokia Call Connect is the new name of the cellular mobility application of Alcatel-Lucent for the Nokia E series mobile devices. It was developed in continuity of Intellisync Call Connect (ICC) and replaces it for new Nokia E series devices (see Supported devices for NCC 2.2). For more information on MIC (My Instant Communicator) mobility solutions for Blackberry, Windows Mobile or Nokia devices associated to Instant Communications Suite (ICS), refer to the technical communication TC1218 Technical release notes for MIC mobile client: Windows Mobile 1.1.8.0, Blackberry® MIC 3.1.0.3, iPhone MIC 3.1.2, Nokia NCC 2.2.26. Note In the version NCC 2.2.x, the Nokia license is embedded within the NCC software (a selection between single and dual mode is required). The Nokia licenses still have to be purchased as for version 2.1.8. But there is no need to wait for a license. This technical communication replaces the technical communication TC1059 Software evolutions of the ICC/ACE Mobility Solution published for Alcatel-Lucent R7.0 OmniPCX Office and Alcatel-Lucent R8.0.1 OmniPCX Enterprise. 2. RELEASED COUNTRIES Refer to the country lists documentation "Alcatel-Lucent Office Communication Solutions Country List" for OmniPCX Office environment and "MLE 2010 Offer – Regulatory status" for OmniPCX Enterprise environment available on BPWS. Note For the SMS providers list per country, refer to the "Business Partner Guide - Off-Site Mobility Advanced Cellular Extension My cellular Extension - SMS Worldwide country list Annex". Ed. 12 / 05 October 2010 3 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 3. COMPATIBILITIES The NCC/ACE/MCE mobility solution is available with the following software versions. 3.1 With the OmniPCX Office Communication (cellular mode only) Alcatel-Lucent OmniPCX Office Communication Server R7.0 (and higher) with the services installed: • • • • • Nomadic Remote customization Remote substitution Nokia Call Connect 2.2.26 software + Alcatel-Lucent off-site mobile user for Nokia License Advanced Cellular Extension 2.3.7.4 software + Alcatel-Lucent off-site mobile user for Windows Mobile license Respective Alcatel-Lucent OmniPCX Office Communication Server R7.1 with the services installed: • • • • Nomadic Remote customization Remote substitution My Cellular Extension 1.1.8.0 software + Alcatel-Lucent off-site mobile user for Windows Mobile license 3.2 With the OmniPCX Enterprise Communication 3.2.1 In cellular mode • Alcatel-Lucent OmniPCX Enterprise Communication Server R8.0.1 (or later version) • • • • Alcatel-Lucent Remote Extension license Alcatel-Lucent My Cellular Extension license Nokia Call Connect 2.2.26 software + Mobility Nokia SW ID license for Nokia sets Advanced Cellular Extension 2.3.7.4 + Mobility Windows SW ID license for Windows Mobile devices Respectively • Alcatel-Lucent OmniPCX Enterprise Communication Server R9.0 (or later version) • • • Alcatel-Lucent Remote Extension license Alcatel-Lucent My Cellular Extension license My Cellular Extension 1.1.8.0 software + Mobility Windows SW ID license for Windows Mobile devices TC1118 4 Ed. 12 / 05 October 2010 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 3.2.2 In dual-mode (cell/WiFi) (NCC only) • Alcatel-Lucent OmniPCX Enterprise Communication Server R8.0.1 (or later version) • • • • • Alcatel-Lucent Remote Extension license Alcatel-Lucent My Cellular Extension license Mobility dual mode license Nokia Call Connect 2.2.26 software + Mobility Nokia SW ID license OAW switch version 3.4.1.1 or later Mobiles running ACE or MCE operate in cellular mode only. NCC Nokia mobiles operate in cellular mode or in dual-mode (on OmniPCX Enterprise only). Refer to the white list (see below) for supported phone models. Nokia sets used in Dual mode with OmniPCX Enterprise must be created as Set Type = SIP Device. If migrating from R8 to R9, you should export the concerned users (via 4760i/4760) in order to change their set type from SIP Extension to SIP Device and to import them after removing them in OmniPCX Enterprise. 4. PRODUCTS ACTIVATION AND LICENSES ACE, MCE and Nokia NCC bundles need licenses to be activated. For details, refer to the "Business Partner Guide - Off-Site Mobility Advanced Cellular Extension My Cellular Extension Business Partner Guide" documentation. Ed. 12 / 05 October 2010 5 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 5. NOKIA NCC 2.2.26 Nokia Call Connect 2.2.26 is signed software for the Nokia E series mobile devices to access to the PBX features. It is available on BPWS. NCC 2.2.26 is a maintenance version for ICC 2.1.10 for following Nokia E series mobiles devices: E51, E63, E66 and E71. NCC 2.2.26 does support the Nokia E series mobiles devices based on the new 3.2 platform: E75 (in cell mode), E72, E55 and E52. To learn about the exact list of mobile devices supported, refer to the "ACE/MCE Applications Device white list" documentation. The license is embedded within the application NCC 2.2.x. 5.1 Main features Refer to the "Alcatel-Lucent OmniTouch 8622 My Cellular Extension" datasheet available on BPWS. 5.2 Supported devices for NCC 2.2.26 NCC 2.2.26 is only validated and supported on the following devices: 5.2.1 In cellular mode only • Nokia E51 firmware 400.34.011 or later • Nokia E63 firmware 410.21.010 or later • Nokia E66 firmware 410.21.010 or later • Nokia E71 firmware 410.21.010 or later • Nokia E75 firmware 202.12.01 or later • Nokia E52 firmware 033.002 or later • Nokia E55 firmware 033.002 or later • Nokia E72 firmware 031.023 or later 5.2.2 In dual-mode and/or cellular mode • Nokia E51 firmware 400.34.011 or later • Nokia E63 firmware 410.21.010 or later • Nokia E66 firmware 410.21.010 or later • Nokia E71 firmware 410.21.010 or later • Nokia E52 firmware 033.002 or later • Nokia E55 firmware 033.002 or later • Nokia E72 firmware 031.023 or later Find your current software version by entering *#0000# on your Nokia device's keypad. TC1118 6 Ed. 12 / 05 October 2010 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS The firmwares for the different models are available on the Nokia web site www.nokia.com. To know the latest firmware available for one Nokia device, refer to http://europe.nokia.com/Get support and Software/Download-software/Device software update/Can I update. You can easily upgrade your firmware using Nokia Software Updater. Carry out a backup before upgrading the firmware version of the device. 5.3 Known restrictions in version NCC 2.2.26 Upgrading NCC 2.2.13 and older version with NCC 2.2.16 or with newer version is not supported. Therefore the mobile device must be reset to factory settings before installing the NCC 2.2.x (x>13) version; refer to § 5.6 for details on the procedure. • Manuel handover Cell to WiFi is not implemented. Anyway, it is possible to use automatic handover Cell to WiFi. • The provisioning of the WLAN configuration is supported only with the setting text file. • Nokia Call Connect is not supported on Nokia carrier bundles. • Nokia Call Connect is only supported on the Nokia E series mentioned in the "ACE/MyCE Applications Device White List" document available on BPWS and equipped with a SIM card. • Second call, change availability, conference, pick up parked calls are features provided by the OmniPCX Enterprise only. These services may be offered by your mobile provider but their use with NCC is not advised. • G.723 is not supported. • Nokia phone does not negotiate the 40ms framing in G.729. • If a handset is already in call, there is no call waiting beep for the second incoming call. • CAC IP domain counter being wrong, IP domain configuration of "remote extensions" (e.g. Nokia mobile devices) is not recommended. • WLAN provisioning is not supported over BPWS. • SIP emergency call goes through the cell network and not through the WLAN network. So the emergency call is not available without SIM card in all countries because some carriers forbid such calls. • Impossible to put on hold/retrieve held incoming SIP call on the Nokia mobile device. • Nokia does not reconnect to the WLAN after having lost the IP link during a certain period of time (around 10 minutes). • In business WLAN mode, initiating a call using speed dial creates a cellular call. • NCC client updates the call logs by removing the IP address after the VoIP call is terminated. The client may be not able to modify the call log in some cases (e.g. if the call fails before the phone notifies the client). • The iLBC codec is not supported. It must be removed from the mobile device settings. • An extern DHCP server (not the OmniPCX Enterprise) is required. Ed. 12 / 05 October 2010 7 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS • In business WLAN mode, if you want to browse, many trials to select the access point may be required: if the device shows "search for WLAN" in select access point menu, then you have to go back and try again until the menu shows the access point you are already connected to. • In case of "essysapp error", reboot the mobile device. • It is not possible to navigate through eVA voice mail when the Nokia mobile phone uses G711. • The parameter 1068 "EAlcOmniWiFiToGsmCli" from text file must be compatible with the value sent by the OmniPCX Enterprise. If not, the mobile device may be blocked. In such case, it must be rebooted. Usually this parameter is the "remote extension" number. If not, refer to the next section for a procedure for getting the value sent by the OmniPCX Enterprise • Some internal numbers are not reachable from some Nokia mobile device (e.g. E51, E66, and E71) when the internal corporate numbering plan size is less than 3 digits. • On E63, the dual mode software must be used to have access to the business call options. The settings of the text file for provisioning the Nokia device changed between version ICC 2.1 and version NCC 2.2. The correct version of the text file must be used for provisioning the mobile device. The signed version NCC 2.2.26 is released for cellular mode and dual mode. The NCC 2.2.26 client is delivered as a Symbian Installation System (SIS) file. Two versions of the installation file are available, one for single mode, the other one for dual mode. Some devices can operate in cellular mode only (see supported device list above). 5.3.1 Tips • The operator voice mail should be defined on the website as an "Emergency number": in this case, you can directly access to it in Business mode. • As there is no signaling back from the PBX to NCC, NCC expects that all operations succeed and is only aware of events happening on the terminal’s side of the call. This can lead to "desynchronization" side effects in some cases. In the worst case, resynchronization is obtained at the end of the current call. • After the battery is full empty, you might restart the NCC after the charging. • Procedure for getting the value of the parameter 1068 "EAlcOmniWiFiToGsmCli" sent by the OmniPCX Enterprise: Make a handover WiFi to Cell and for the incoming call write down the calling number displayed on the mobile device. If it is not displayed, make a capture of the data transmitted by the OmniPCX Enterprise. • Some audio issues occurred with 30 ms framing in G.711 with OXE 9.0 version. There are no issues with OXE 9.1 version • The "Voice recorder" key on the side of the device can be used for accessing the NCC menus. Refer to the NCC 2.2 Release Note and "ACE/MCE Applications - Device white list" available on BPWS TC1118 8 Ed. 12 / 05 October 2010 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 5.4 Delivered corrections for this version • Unidirectional communication may occur with the attendant in G.729 with 20 ms framing on E52, E55 or E72 devices. • Warning tones used for getting handover tones may stop after a certain time on E52, E55 or E72. • The menu to access business call options isn’t present anymore. • The name of a known contact may not be displayed on an incoming call. • Forward may not be correctly deactivated when switching from private to business mode. 5.5 NCC 2.2.x clients installation NCC client software is available and can be sent Over The Air to the device thanks to Alcatel-Lucent Business Partner Web Site: http://www.businesspartner.alcatel-lucent.com under the link Home > Support > Technical Support IP Telephony > Software download (select: Mobility > Advanced Cellular Extension/My Cellular Extension). In order to be operational once installed, the software must be configured: • Install NCC software and restart the device. After restarting the device, the embedded license is automatically verified by Nokia license server and the mobile device registered there. • Configure the application with a SMS sending via BP Web Site (cellular mode only) or with the text file (dual mode). • Restart the mobile device. For more details, refer to the installation and provisioning procedures described in the Nokia Administration Guide "Call Connect for Alcatel-Lucent Administration Guide Version 2.2" available on BPWS. For the configuration in cellular mode, the NCC software and the telephony service must be activated at the SMS reception. For the provisioning via text file, templates of ESVoiceSettingsData.txt text file are available on BPWS with the software and documentation. The file must be adapted with the installation parameters. Notes • For the SMS providers list per country, refer to the "Business Partner Guide - Off-Site Mobility Advanced Cellular Extension My Cellular Extension- SMS Worldwide country list Annex". • Before starting the activation, it is advised to get a valid data connection or have a valid WLAN access to make the Nokia server reachable. Ed. 12 / 05 October 2010 9 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 5.6 Upgrade to the NCC 2.2.x clients 5.6.1 Upgrade from ICC 2.1m or NCC 2.2.13 to NCC 2.2.y (with y ≥ 16) No upgrade is possible. The mobile device must be reset to factory settings. Some data may be lost even if a backup/restore is done since not all user data can be restored. In such case, the procedure for installing the new NCC version is the following: • If needed, backup the mobile data on a PC • Reset the mobile to defaults by entering *#7370# (code 12345) • If needed, restore the data (restore only contacts, calendar, notes, messages, bookmarks) • Install the new NCC version as usual • Configure the application as usual 5.6.2 Upgrade from NCC 2.2.x (with x ≥ 16) to NCC 2.2.y Before upgrade: • Duplicate the WLAN access point: Go to Menu > Tools > Parameters > Connection > Access Points, select the access point (e.g. MARLIN) and go to Options > Duplicate access point. Select then the new access point MARLIN(01), select [OK][OK] and change the name to MARLIN.BAK. Go out of the menu with [Back]. • Set the device in private mode. Installation: • Do the installation as usual and reboot the device. • It is not required to reconfigure the application afterwards. After upgrade: • If the mobile device was provisioned again, replace the access point which was erased by the provisioning: Go to Menu > Tools > Parameters > Connection > Access points, select the access point (e.g. MARLIN.BAK), duplicate this access point and rename it into the name you have in the provisioning file (e.g. MARLIN). • If the mobile device was provisioned again, in business mode, select your web service access point and enter the password. • Change the SIP registration mode to "Always": Under the WLAN coverage, in the NCC application, go to Options > Parameters then General tab, select SIP parameters and your access point. Go down to register and change "if necessary" into "always". TC1118 10 Ed. 12 / 05 October 2010 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 5.7 Nokia PC tools You can find on the Nokia web site www.nokia.com all the PC tools that can help you to install, configure or update your Nokia devices (Nokia Intellisync Mobile Suite 9.1, Nokia Software Updater, and Nokia PC Suite). Ed. 12 / 05 October 2010 11 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS ACE 2.3.7.4 ON WINDOWS MOBILE® 6.X 6. The ACE 2.3.7.4 software is currently released. It is only compatible with the Touchscreen devices (previously named as PocketPC) and Non-Touchscreen devices (previously named as Smartphone platforms) on Windows Mobile 6.xTM whose exhaustive list follows: 6.1 Main features The client operates in two modes: Business mode or Private mode. In Business mode: • The PBX services are available. • All call from the device pass through the PBX. • All Business calls are presented to the device. • Callers always see one number: business number. In Private mode: • All call from the device goes directly to the operator network. • All Business calls are not presented to the device (thanks to forward setup on OmniPCX Office, and dual-ring feature on OmniPCX Enterprise). Otherwise the call is setup on the device. • Callers see private cell phone number. The users can switch between the modes via the client menus. OmniPCX services available: At any time via the configuration menus: • Making a call • Receiving a call • Consult your business voice mail • Check your availability status • Change your availability status (OmniPCX Enterprise only) • Remote Extension activation /deactivation for OmniPCX Enterprise (from Release 9.0) • Update call forwarding settings in the telephone exchange • Forward business calls to your business voice mail • Forward business calls to another phone number • Forward business calls to personal assistant (OmniPCX Office only) • Cancel forwarding • Contact the telephone exchange attendant • Switch to Private mode • Help TC1118 12 Ed. 12 / 05 October 2010 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS In active Business call: • Make consultation calls (OmniPCX Enterprise only) • Put calls on hold (OmniPCX Enterprise only) • Retrieve held calls (OmniPCX Enterprise only) • Switch between active and held calls (OmniPCX Enterprise only) • Transfer calls (OmniPCX Enterprise only) • Make a second call (OmniPCX Enterprise only) • Receive a second call (OmniPCX Enterprise only) • Make conference calls (OmniPCX Enterprise only) • Park and pick up calls (OmniPCX Enterprise only) • Reverse calls (OmniPCX Enterprise only) • Request callback (OmniPCX Enterprise only) Leave messages in business voice mail (OmniPCX Enterprise only) Send manually entered service codes to invoke functions which are not directly available via the client menu (OmniPCX Enterprise only) Contact the attendant (OmniPCX Enterprise only) • • • Note Depending on your system, some services are not available. 6.2 Supported devices 6.2.1 Generic devices ACE is only validated and supported on the following devices: • HTC S740 Windows Mobile 6.1 • Samsung i200 Windows Mobile 6.1 • Samsung C6625 Windows Mobile 6.1 • Samsung OmniaPro 7330 Windows Mobile 6.5 6.2.2 Orange devices ACE is only validated and supported on the following devices on OmniPCX Enterprise. • Samsung i200 Windows Mobile 6.1 • Samsung i900 Windows Mobile 6.1 (with ACE 2.3.4.6 OBS version) • HTC S740 Windows Mobile 6.1 • Samsung C6625 Windows Mobile 6.1 • Samsung OmniaPro 7330 Windows Mobile 6.5 Ed. 12 / 05 October 2010 13 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 6.3 Known restrictions in version 2.3.7.4 6.3.1 Restrictions • The software must not be installed on the Flash card. • Double call ACE / cellular is not possible: ACE does not support the second cellular call in Business Mode. This is a feature that enables a mobile device to establish two calls and to swap from one call to the other (not to be confused with the ACE second call which is performed by the OmniPCX Enterprise on the same cellular communication). The ACE software prevents the second call to be accepted by the terminal. • ACE cannot work in parallel with My Pocket Communicator. • In Business mode, it’s not possible to make a private call from the contact: need to switch to Private mode or prefix the number by * in Business mode. • The ACE does not handle SIM contacts (if a contact of the SIM card calls or is called, the name does not appear). Only Outlook contacts are handled. • In the ACE menu, the forward to an external number does not work. • In tandem mode, if the device is switched off, the incoming calls are directly forwarded on the cell phone mailbox. • On conference mode, the display is not refreshed when a participant hook on (there are no information coming from the PBX to manage that). 6.3.2 Devices Specific Restrictions • On HTC S740 the ACE plug-in is not installed. • On Samsung i900, when changing mode, the contextual menu may not be updated. This is fixed by Windows Mobile update from Windows CE 5.2.20757. • On Samsung C6625, Samsung OmniaPro 7330 and Samsung Omnia2, the homescreen "Samsung WizPro" must be deactivated before installing the ACE 2.3 application. It can be reactivated after the installation is complete. 6.3.3 Tips • The reverse call feature can be used only when the communication is established. • The operator voice mail should be defined on the website as an "Emergency number": in this case, you can directly access to it in Business mode. • As there is no signaling back from the PBX to the ACE, ACE expects that all operations succeed and is only aware of events happening on the terminal’s side of the call. This can lead to "de-synchronization" side effects in some cases. In the worst case, resynchronization is obtained at the end of the current call. • After the battery is full empty, you might restart the ACE after the charging. • We have seen that some sets can get block randomly even without the ACE application installed. In this case, resetting the device resolves the problem. TC1118 14 Ed. 12 / 05 October 2010 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS On Smartphones, we advice to stop the HTC plug-in to see ACE icon and check the ACE current mode (Business / Private). To remove the ACE banner from the desktop screen: "Start" > "Settings" > "Home Screen" > "Home screen layout": "HTC… + ACE" replaced by "HTC…" (or other choice). If the plug-in is stopped, you can push the "Unhook" key to see if the ACE icon is displayed in the top left corner. This icon permits to rapidly check the ACE current mode (Business / Private). 6.4 ACE 2.3.7.4 signed version This ACE 2.3 version is a Microsoft signed version for OmniPCX Enterprise and OmniPCX Office. It is only validated and supported on the following devices: • For Non-Touchscreen devices: o Version: ACE_SMP_WM6_2.3.7.4_WM_VerisignSigned.cab (SMP WM6 generic) o Devices: HTC S740, Samsung i200, Samsung C6625, Samsung OmniaPro 7330 • For Touchscreen devices: o Version: ACE_PPC_WM6_2.3.7.4_WM_VerisignSigned.cab (PPC WM6 generic) o Devices: Samsung Omnia2 • For Orange (Dedicated release): o Version: ACE_PPC_2.3.4.6_WM_Signed.cab (PPC WM6 Orange) o Devices: Samsung i900 o Version: ACE_SMP_WM6_2.3.7.4_OBS_Signed.CAB (SMP WM6 Orange) o Devices: HTC S740, Samsung C6625, Samsung i200, Samsung OmniaPro 7330 o Version: ACE_PPC_WM6_2.3.7.4_OBS_Signed.CAB (PPC WM6 Orange) o Devices: Samsung Omnia2 6.4.1 • 6.5 Delivered corrections for this version Remove Samsung Omnia2 in generic and Orange version from list of supported devices (introduced in MCE 1.1 version). ACE 2.3 client installation ACE client software is available on Alcatel-Lucent Business Partner Web Site: http://www.businesspartner.alcatel-lucent.com. ACE_PPC and ACE_SMP softwares are available for download in the “Software download” section on the BPWS. ACE_SMP can also be sent Over The Air to the device. Refer to the "Business Partner Guide - Off-Site Mobility ACE 2.3 / ICC 2.1" documentation. In order to be operational once installed, the software has to be activated a first time via BPWS (SMS sending via Pricing and Ordering > eLicensing Management). This client activation also configures it. The process is available in the ACE User Guide. Ed. 12 / 05 October 2010 15 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS Note Language will automatically fit with the device’s regional settings (Locale field). It must be chosen before the ACE installation. It is not possible to change the language for a carrier bundle. The first installation shall be done on a "clean" device by: • Install the ACE 2.3 software corresponding to the device (ACE_PPC_xxx for Touchscreen devices and ACE_SMP_xxx for Non-Touchscreen devices). • Choose the mobile as recipient of installation. The application will ask you to reboot (mandatory). • Start and activate the application by sending SMS through the website. The ACE application and the telephony service must be active when receiving the SMS. The next time you will install an ACE, it will not be necessary to reactivate it with the SMS. Note If the MCE or MIC 1.1 application is installed on the device, it is required to: • first uninstall the MCE resp. MIC 1.1 application • delete HKLM/Software/Alcatel/MyTeamWork & HKLM/Software/Alcatel before starting installing the ACE 2.3 application. Note For the SMS providers list per country, refer to the "Business Partner Guide - Off-Site Mobility Advanced Cellular Extension My Cellular Extension- SMS Worldwide country list Annex". Upgrading ACE 2.3 shall be done as follows: • Install the new ACE 2.3.7.4 version as for a first installation. • Accept to keep old configuration, it is not necessary to reactivate the device with SMS. • Confirm the device’s restart. 6.6 Microsoft ActiveSync You will find on the Microsoft Mobile 6 website the ActiveSync software to synchronize your NonTouchscreen devices and Touchscreen devices running Windows Mobile 6TM. TC1118 16 Ed. 12 / 05 October 2010 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS MCE 1.1.8.0 ON WINDOWS MOBILE® 6.5 7. The My Instant Communicator 1.1.8.0 software can be used: • in full mode (requiring an ICS - see MIC documentation) • in MCE mode It is a signed software for Windows Mobile devices to access to the PBX features. It is available on BPWS. 7.1 Main features Refer to the "Alcatel-Lucent OmniTouch 8622 My Cellular Extension” datasheet available on BPWS. 7.2 Supported devices MCE 1.1.8.0 is validated and supported on the mobiles devices running Windows Mobile 6.5 whose exhaustive list follows: 7.2.1 Generic devices • HTC Diamond2 Windows Mobile 6.5 • HTC Pro2 Windows Mobile 6.5 • HTC HD2 Windows Mobile 6.5 • HTC Touch2 Windows Mobile 6.5 • Samsung Omnia2 Windows Mobile 6.5 7.2.2 T-Mobile devices • MDA Compact V Windows Mobile 6.5 • MDA Vario V Windows Mobile 6.5 7.3 Known restrictions in version 1.1.8.0 7.3.1 Restrictions • Double call MCE / Cellular is not possible: MCE does not support the second cellular call in Business Mode. This is a feature that enables a mobile device to establish two calls and to swap from one call to the other (not to be confused with the MCE second call which is performed by the OmniPCX Enterprise on the same cellular communication). The MCE software prevents the second call to be accepted by the terminal. • In tandem mode, if the mobile device is switched off, the incoming calls may be directly forwarded to the cell phone mailbox. • Some specific error messages are always displayed in English even if the localization setting is different. Ed. 12 / 05 October 2010 17 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS • In private mode, it is not possible to take a DISA second call, even if the user can hear the beep generated by the PBX. • The Asian languages (Chinese and Korean) are correctly handled only on mobiles that natively support these languages, i.e. on mobiles that have Asian versions of Windows Mobile operating system. • The interface for setting the MCE application parameters remain in English even if the language of the application is in another language. 7.3.2 • 7.3.3 Devices specific restrictions On HTC HD2, the default screen lock should be changed to Windows Classic for being able to divert an incoming call to the voicemail. Tips • The reverse call feature can be used only for an outgoing call when the communication is established. • In business mode, it is possible to make a private call by entering * as a prefix before the number to dial or after searching for a contact in the local phonebook through MCE by using the menu more > make a private call. • The operator voice mail should be defined on the website as an "Emergency number": in this case, you can directly access to it in Business mode. • As there is no signaling back from the PBX to the ACE, ACE expects that all operations succeed and is only aware of events happening on the terminal’s side of the call. This can lead to "de-synchronization" side effects in some cases. In the worst case, resynchronization is obtained at the end of the current call. • On HTC devices, the native dialer may be displayed at end of communications. To solve the problem, go to "Settings> Personal>Telephony /Advanced (Tab)" and disable the feature "Add new phone number to contacts at the end of the call". • The virtual keypad icon is sometimes missing in the bottom bar of the screen. A click at this location shows the virtual keypad even if the icon is not displayed. • For a contact detail, using the “make call” menu (at bottom link on the screen) makes always a call to the first phone number even if another number is selected. To avoid this, use the "make call" menu accessible through the More menu (at bottom right on the screen). 7.4 Delivered corrections for this version • Adding generic device Samsung Omnia2 to the list of supported devices. • The application dialer does not accept pause or wait (pw,.) in the called number. • The first launch of the application may stops at 100%. In such case, close the application and start it again. • In case of a second call, all DTMF tones dialled to call the second person are heard by the first person. • On HTC Diamond2, the reverse call icon and menu may be missing (HTC ROM issue). TC1118 18 Ed. 12 / 05 October 2010 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 7.5 MCE 1.1 application installation MCE client software is available for download on the Alcatel-Lucent Business Partner Web Site: http://www.businesspartner.alcatel-lucent.com. It can also be sent Over The Air to the device thanks to Alcatel-Lucent Business Partner Web Site. In order to be operational once installed, the software has to be activated a first time via BPWS (SMS sending via Pricing and Ordering > eLicensing Management). This client activation also configures it. Refer to the "My Cellular Extension Windows Mobile User guide Alcatel-Lucent OmniPCX Entreprise", "My Cellular Extension Windows Mobile User guide Alcatel-Lucent OmniPCXOffice” and "Business Partner Guide - Off-Site Mobility ACE 2.3 / ICC 2.1" documentation. Note The interface language of the application can be defined as a general parameter of the application. The MCE application settings are available under the personal settings of the device. If the ACE 2.3 application is already installed on the device, it is required to first uninstall the ACE 2.3 application before starting installing the MCE 1.1 application. The MCE 1.1 installation is done using the same software for MCE and MIC application by: • Selecting "MCE" mode during the installation process • Rebooting the device at the end of the installation process • Sending SMS for provisioning the MCE application. The device must be switched on when receiving the SMS. When upgrading to another MCE version, it will not be necessary to again do provisioning the application with the SMS. Refer to both documentation "My Cellular Extension Windows Mobile User guide" for OmniPCX Entreprise resp. OmniPCXOffice for a detailed description of the installation procedure. Note For the SMS providers list per country, refer to the "Business Partner Guide - Off-Site Mobility Advanced Cellular Extension My Cellular Extension- SMS Worldwide country list Annex". Ed. 12 / 05 October 2010 19 TC1118 OmniPCX Enterprise / OmniPCX Office TECHNICAL RELEASE NOTE FOR NCC 2.2.26, ACE 2.3.7.4 AND MCE 1.1.8.0 VERSIONS 8. SOFTWARE DEPLOYMENT USING BPWS The BPWS offers the possibility to send and SMS containing an URL to the software to download to a device. By clicking on the link into the SMS, the NCC, ACE_SMP or MCE software is downloaded into the device and then installed. To do that, in the configuration file you have to select which software to download. By default you can choose URL of the software that are stored in Transatel server, nevertheless you are able to use your own server. For ACE_SMP software, the user can find the software on the BPWS in the Software Download section. 8.1 Download link 'Other' When defining your configuration, you have to select which software to upload into the device. A Business Partner that wants to use its own web portal as software server can do it simply. So they have to select "Other" and give a link to the software on their server. To be able to download ACE Software on Windows Mobile when using "Other" choice in the profile. The customer must be aware that some parameters have to be setup in his server to be sure the software will be download and run, and not displayed in a browser page as text. Here are the parameters related to an Apache server: • AddType application/x-cab-compressed cab • AddType application/octet-stream .cab • AddType application/cab .cab • AddType application/x-compress .cab • AddType application/x-compressed .cab • AddType zz-application/zz-winassoc-cab .cab • AddType application/vnd.ms-cab-compressed .cab TC1118 20 Ed. 12 / 05 October 2010