Preview only show first 10 pages with watermark. For full document please download

Technical Release Note Release 1.3.000.043

Rating
Date

October 2018
Size

5.1MB
Views

6,845
Categories

Computers & electronics Networking Telephone switching equipment

Transcript

Release Note Alcatel-Lucent OpenTouch R. 1.3.000.043 TC1798 Ed05 TECHNICAL RELEASE NOTE RELEASE 1.3.000.043 This Release Note provides technical information about OpenTouch Release R1.3.000.043 Such document includes installation and operating notes, as well as restrictions and limitations. Revision History Edition 1: April 25, 2013 creation of the document for OpenTouch R.1.3.000.042 Technical Release Edition 2: May 16, 2013 OXE update: OXE J2.603.20i (DTMF correction) integrated in OTBE R1.3.000.043 Flex update: new Flex server R1.3.000.051 (script to recover dongle visibility if lost) Document comments for better explanation taken into account Edition 3: May 24, 2013 8082 Version R260 1.12.1 and FLEX R1.3.000.051 Edition 4: May 31, 2013 8002/8012 Version R100 2.32.1 and ALEDS 2.2.2 “Restricitons” chapter checked, fixed issue move to “Removed restrictions” chapter Edition 5: June 24, 2013 8082 Version R260 1.12.2 Reminder on new OXE OT profile, Certificate expiration Legal notice: Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners. The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein. Copyright © 2013 Alcatel-Lucent. All rights reserved. Release Notes sections New features and enhancements section provides a basic description of Alcatel-Lucent OpenTouch functionalities. Requirement section provides technical information required to setup the solution: supported hardware, software environment…. List of Major issues, Restrictions section describes features limitations and restrictions associated with this release R1.3 of Alcatel-Lucent OpenTouch. Corrections section present correction of customer issue Focus on section is dedicated for end to end aspect of the solution: licensing, routing, video… Recommendation on using this Release Note document The release note does not replace the installation guide, administration manual or user guides but provide basic hints on new features description and setup. Please follow these manual documents for a complete feature setup. Take care that some feature setup requires managing several component, read carefully the documentation to avoid missing setup. Although some features are similar to ICS, take care that the unified user management and the 8770 graphical interface require some adaptation in term of feature activation. This release note has collected various information from other official documents (see list of references) to get a single document. Any recent update / correction on this source documents may not be available in this release note. This document is very large; you may not have time to read it completely. Focus on green light, installation procedure, and use as reference when needed the other section of this document For instance, in case of issue with OpenTouch solution, check the restriction section: it has been organized per sub component of OpenTouch solution use CTL F to search for keyword. Example of issue search, you encounter this issue on 8770 update: error insert disk 1, search “insert disk 1” in this document and you will reach the paragraph which describes the issue and its root cause. Disclaimer This documentation is provided for reference purposes only. While efforts were made to verify the completeness and accuracy of the information contained in this documentation, this documentation is provided “as is” without any warranty whatsoever and to the maximum extent permitted. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 2/193 In the interest of continued product development, Alcatel-Lucent reserves the right to make improvements to this manual and the products it describes at any time without notice or obligation. List of Trademarks Microsoft™ and Windows™ are registered trademarks of Microsoft ™ Corporation in the United States and other countries. Linux™ is a registered trademark of Linus Torvalds. Red Hat™ is a registered trademark of Red Hat™, Inc. in the United States and other countries. Lotus™ and Lotus Notes are registered trademarks of Lotus Development Corporation. FlexLM™ is a registered trademark of Macrovision Corporation. IPhone™ is a registered trademark of Apple Inc. ©LifeSize is a division of Logitech. All other trademarks and copyrights referred to are the property of their respective owners. Glossary   ACS BTCO                          CaaS, UCaaS, CAC CPE CPE CTL DCS DM DVA ESS GUI GVP ICE / OT Core ICM ICS LSVM MOC MOH MCU MCU MMI OAMP OT OTBE OTBE-H OTBE-V  OTC Advanced Communication Server Built To Customer Order (no preinstalled appliance server stored in HUB but install when requested) conference as a service Unified Communication as a Service Call Adminssion Control (to limit used bandwidth by VoIP calls) Customer Premise Environment Customer Premises Equipment Certificate Trust List Document Conversion Server Device Management Dynamic Virtual Assistant Enterprise SIP Server, SIP core of ICM acting as SIP B2B UA Graphical User Interface Genesys Voice Platform (Media server of OpenTouch) Sub part of OpenTouch containing mainly ICM and ICS sub-systems Instant Communication Manager (based on SIP server of OpenTouch) Instant Communications Suite Local Storage Voice Mail : internal Voice mail of OpenTouch Microsoft Office Communicator Music on Hold Multipoint Control Unit Vide Multimedia control Unit Man Machine Interface (like the setup Menu on 4008 / 8002…) Operation Administration Maintenance Provisioning OpenTouch OpenTouch Business Edition OpenTouch Business Edition Hosted OpenTouch Business Edition virtualized (Commercial sell of the 3 Virtual Machines OTMS-V, OXE-V, 8770-V) OpenTouch conversation Client (unified client for conference and voice control) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 3/193                OTMS OTMS-V OXE PCS, SBC, TKB TTS TUI User User UUM VHE VLE VM WBM OpenTouch Multimedia Services OpenTouch Multimedia Services virtualized on top of Vmware ESXi OmniPCX Enterprise Passive communication Server of OXE Session border controller Technical Knowledge Base (documentation for Business Partner) Text to Speech Telephony User interface (using DTMF in Voice application like Voice Mail..) OpenTouch Multimedia user OpenTouch user declared in ICM OpenTouch Standard user Omni PCX Enterprise user User unified Management Very High End (8082 for 8xxx line of device) Very Low End (8002-8012 for 8xxx line of device) Virtual Machine Web Based Management Video glossary Another glossary for video is available in chapter 8 dedicated to video. Release policy Alcatel-Lucent OpenTouch R1.3 is a minor release of OpenTouch R1.x  Existing OT R1.x Hardware still supported, but HP G8 server are now delivered by default  No new ACSE certification required o OT 1.x certification is enough + Valid support contract However  You need a Specific license for OpenTouch R1.3 (Release ID=5) ,OXE 10.1.x, 8770 R1.3  If old OT license is used with its Release ID=3, all user right are disabled hence no OT application  Training is updated to include OT R1.3 new feature and a delta OT R1.x to OT R1.3 is available Related documents: Feature list / Cross compatibility / Release Policy Ref 8AL020040085 FLARA 8AL020033230 TCASA 8AL020033609 DRASA ED Comment Feature List and Product Limit: updated for OT R1.3 26b Release Policy Information: updated for OT R1.3 18 Large Medium Enterprise Product Cross compatibility: updated for OT R1.3 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 4/193 Related documents: OpenTouch release note, migration, data collection TC TC1758 ED 2 Comment OpenTouch R1.2-R1.3 Prerequisites and Data Collect Guide TC1782 4 OTMS OTBE OXE compatibility matrix TC1755 3 OpenTouch – Technical Release Note R1.2.000.055 and Hotfix TC1762 OpenTouch – Technical Release Note R1.1.000.091 and Hotfix TC1701 OpenTouch – Technical Release Note R1.1.000.080 and Hotfix TC1799 1 TC1704 TC1635 OpenTouch – Upgrade procedure from R1.x to R1.3 with server reinstallation OpenTouch OT_SW Version upgrade on inactive-partition and maintenance 4 TC1807 OpenTouch – Migration BiCS R2.x to OpenTouch R1.1, obsolete replaced by official install manual Instant Communications Web Services 6.x Available on Open Touch 1.2 Related documents: OpenTouch components release note (server part) TC TC1803 ED 3 Comment Technical Release Note for OXE Release 10.1.1 - Version J2.603.20i TC1801 1 Installation procedure for 8770 Release 1.3 - Version 1.3.05.00a (patch I) TC1689 4 TC1327 13 Technical Release Notes for OmniTouch 8400 Instant Communications Suite Release R6.7.200.000d Technical Release Notes ICS R6.7.100.000.f (ACS 8.5.0b6312)) TC1575 2 Technical Release Note for OmniTouch 8450 Fax Software OFS Software Version R6.6.0.16 Related documents: OpenTouch components release note (client part) TC TC1781 TC1819 TC1616 ED 2 1 2 Comment Technical Release Note for MyIC Phone release R260 in Business environment – Version TC 1781 for 1.11.x / TC 1819 for 1.12.x Technical Release Note for MyIC Phone Synchronizer – Version 1.1.12.0 TC1651 1 TC1786 3 Alcatel-Lucent My IC Customizer - Technical Release Notes R2.1.x =>Product Not available by default but can be requested via eSR, Technical Release Notes of 8002/8012 Deskphone R100/2.032.1 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 5/193 TC TC1677 ED 7 Comment Technical Release Note for MyIC Mobile 4.3 on OT (BB/Android) TC1218 14 Technical Release Notes for MIC Mobile clients (OXE/ICS) TC1791 1 Technical Release Notes for OpenTouch Conversation for iPad 1.2 TC1815 1 Alcatel-Lucent 4059 EE - Installation procedure for Release 1.3 TC1468 5 4008/4018 EE SIP 2.11.91 (not yet updated to show compliancy with OpenTouch R1.1) Related documents: Configuration guidelines on Mobility TC TC1559 ED 2 Comment BES Management for MCE MIC BlackBerry TG0056 4 MyIC BlackBerry R4 configuration guideline (for OT user, not updated for R4.1, the guideline is now in official OT admin manual ) Mobility Troubleshooting Guide for OmniPCX Enterprise / ICS / OpenTouch TC1323 5 TC1503 TC1433 TC1287 MIC iPhone solution configuration guideline (only for OXE user, and only external gateway supported in OpenTouch) MIC Android Solution Configuration Guideline (for OXE user, not updated when OT used instead of ICS : see OT admin manual for the server part configuration) MIC BB 3.x Solution Configuration Guideline (for OXE user, not updated when OT used instead of ICS: see OT admin manual for the server part configuration) Related documents: Configuration guide line on other subject TC TC1528 ED 5 TC1521 3 Comment Software Deployment Solution - Version 2.0.x TC replaced by install manual and Release note of OT OpenTouch mass users and devices import with UUM and DM TC1520 2 User management with the Unified User Management application TC1519 1 SNMP management for alarms and performance TC1652 2 OpenTouch connected to OXE in spatial redundancy TC1629 2 OmniTouch 8400 ICS and OpenTouch on same OXE TC1623 4 OpenTouch Single Sign-On Kerberos in-deep TC1614 2 IBM Unify Messaging Lotus Domino Configuration TC1711 6 OpenTouch – Deployment example for MyIC Desktop using Microsoft Group Policy TC1763 1 OpenTouch interworking with OXE connected to public SIP BTIP trunk group Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 6/193 TC TC1790 ED 2 Comment OpenTouch 1.2 8002/8012 Deskphone installation guide Related documents: Maintenance and Troubleshooting TC TC1598 ED Comment OpenTouch R1.0 Preventive Maintenance TG0064 14 Alcatel-Lucent OpenTouch R1.x Troubleshooting guide TC1494 5 OpenTouch product Siebel solutions TG0065 My IC Phone OT 8082 Troubleshooting Guide TG0071 2 4059 EE R1.2 Troubleshooting guide TC1643 4 TC1636 OpenTouch Backup Restore procedure for R1.0 / R1.1 / R1.2 TC replaced by Administrator manual Commands BiCS R2 vs OpenTouch Business Edition R1.0 TC1625 OpenTouch server cold hard disk image cloning with CloneZilla TC1708 OmniPCX Enterprise PC installer V3.4 TC1701 OmniPCX Enterprise OPS installation TC1748 Certificate trust list overview on My IC Phone range TC1785 OpenTouch R1.1 : Loss of Customer ACS data in backups (concern R1.1 and R1.1 updated to R1.2, not fresh R1.2 installation) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 7/193 Table of contents 1 Welcome .............................................................................................................................................. 14 1.1 Introduction to OpenTouch R1.3 ...................................................................................................... 14 1.2 Software identification ..................................................................................................................... 15 1.3 Software files: DVD, ISO and ZIP ..................................................................................................... 16 1.4 Software documentation .................................................................................................................. 18 1.5 Feature List / Compatibility related information ................................................................................. 22 1.6 OpenTouch topology with OmniPCX Enterprise ................................................................................. 22 1.7 Software Maintenance and Support .................................................................................................. 24 1.8 Solution and Licensing model ........................................................................................................... 25 1.8.1 Solution description................................................................................................................... 25 1.8.2 Licensing model ........................................................................................................................ 28 1.8.3 Licensing guides ....................................................................................................................... 28 1.9 Training and certification ................................................................................................................. 29 2 New features and enhancements ........................................................................................................... 30 2.1 OpenTouch Release R1.3 new features: R1.3.000.043 status ............................................................. 30 2.2 OpenTouch Release R1.3 feature postponed to next OT 1.3 version ................................................... 32 2.3 OT R1.3.000.043 Installation / Update / Upgrade / Migration............................................................. 32 2.4 What’s new in OpenTouch Release R1.3.000.043 .............................................................................. 35 2.4.1 OT R1.3.000.043: Features on server side .................................................................................. 35 2.4.2 OT R1.3.000.043: Voice application ........................................................................................... 35 2.4.3 OT R1.3.000.043: Application .................................................................................................... 36 2.4.4 OT R1.3.000.043: Conference and video .................................................................................... 37 2.4.5 OT R1.3.000.043: Management ................................................................................................. 37 2.5 Reminder: What’s new in OpenTouch Release R1.2.000.055 .............................................................. 38 2.5.1 OT R1.2 new features: R1.2.000.055 status ............................................................................... 38 2.5.2 OT R1.2.000.055: Installation / Update / Upgrade / Migration ..................................................... 40 2.5.3 OT R1.2.000.055: New Features introduced ............................................................................... 43 2.6 Reminder What’s new in OpenTouch Release R1.2.000.054 ............................................................... 43 2.6.1 OT R1.2.000.054: Features on server side .................................................................................. 43 2.6.2 OT R1.2.000.054: Device and Routing ........................................................................................ 44 2.6.3 OT R1.2.000.054: PC Application, MyIC Desktop features and integration .................................... 46 2.6.4 OT R1.2.000.054: Voice Mail / Telephony ................................................................................... 46 2.6.5 OT R1.2.000.054: Conferencing and Video ................................................................................. 46 2.6.6 OT R1.2.000.054: Administration / Internal feature ..................................................................... 47 2.6.7 Features not yet available in R1.2.000.054 ................................................................................. 47 2.6.8 Features Removed from OpenTouch R1.2 .................................................................................. 48 2.6.9 Features postponed to OpenTouch R1.3 ..................................................................................... 48 2.7 Reminder: What’s new in OpenTouch Release R1.1.000.091 .............................................................. 48 2.7.1 OT R1.1.000.091: New feature provided .................................................................................... 48 2.7.2 TC for R1.1.000.091 .................................................................................................................. 48 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 8/193 2.8 Reminder: What’s new in OpenTouch Release R1.1.000.080 .............................................................. 48 2.8.1 OT R1.1.000.080 major restriction and feature not yet released .................................................. 48 2.8.2 OT R1.1.000.080 Installation / Update / Upgrade / Migration ...................................................... 49 2.8.3 OT R1.1.000.080 : New feature ................................................................................................. 50 2.8.4 OT R1.1 Feature not released .................................................................................................... 51 2.9 Reminder: What’s new in OpenTouch Release R1.1.000.060 .............................................................. 51 2.9.1 OT R1.1.000.060: Installation / Upgrade / Migration ................................................................... 51 2.9.2 OT R1.1.000.060: Features on server side .................................................................................. 52 2.9.3 OT R1.1.000.060: Device and Routing ........................................................................................ 54 2.9.4 OT R1.1.000.060: PC Application, MyIC Desktop features and PC integration ............................... 55 2.9.5 4059EE R1.2: OpenTouch user telephonic presence .................................................................... 57 2.9.6 OT R1.1.000.060: Voice Mail ..................................................................................................... 57 2.9.7 OT R1.1.000.060: Conferencing and Video ................................................................................. 58 2.9.8 OT R1.1.000.060: Administration ............................................................................................... 60 2.9.9 Features Postponed to OpenTouch R1.1.000.080 ........................................................................ 60 2.10 Reminder: What’s new in OpenTouch Release R1.0.100.060 ............................................................ 60 2.11 Reminder: What’s new in OpenTouch Release R1.0.100.050 ............................................................ 61 2.11.1 OT R1.1.000.050: Update / Migration ....................................................................................... 61 2.11.2 OT R1.1.000.050: Features on server side ................................................................................ 61 2.11.3 OT R1.1.000.050: OpenTouch User Experience ......................................................................... 61 2.11.4 OT R1.1.000.050: MyIC Desktop features and integration ......................................................... 62 2.11.5 OT R1.1.000.060: Voice Mail / Prompt / Automated attendant ................................................... 63 2.11.6 OT R1.1.000.050: Localization ................................................................................................. 64 2.11.7 OT R1.1.000.050: Feature not released .................................................................................... 65 2.12 Reminder: What’s new in OpenTouch Release R1.0.007.010 ............................................................ 65 2.12.1 OT R1.0.007.010: Features on server side ................................................................................ 65 2.12.2 OT R1.0.007.010: Features on user / device side ...................................................................... 66 2.12.3 OT R1.0.007.010: Ecosystem ................................................................................................... 67 2.12.4 Features Postponed to OpenTouch R1.0.1 ................................................................................ 68 2.12.5 Features Removed from OT R1.0 ............................................................................................. 68 2.13 Features under PCS process ........................................................................................................... 68 3 Requirement and compatibility ............................................................................................................... 69 3.1 Data collection ................................................................................................................................ 69 3.2 Hardware and software requirements ............................................................................................... 69 3.2.1 General .................................................................................................................................... 69 3.2.2 Hardware platfrom not tested by ALU ........................................................................................ 69 3.2.3 OTMS R1.3 / OTBE R1.3: Hardware platforms tested and supported ............................................ 70 3.2.4 Virtualized requirement ............................................................................................................. 70 3.2.4.1 OXE-V 10.1.1 requirement ..................................................................................................................71 3.2.4.2 OTMS-V 1.3 requirement ....................................................................................................................71 3.2.4.3 8770-V 1.3 requirement .....................................................................................................................71 3.2.4.4 OTMS-V 1.3 Flexera Hardware platforms tested and supported ..............................................................71 3.2.4.5 Document Conversion Server VM requirement ......................................................................................71 3.2.5 OTMS/OTBE: Hardware platforms supported with capacity restriction .......................................... 72 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 9/193 3.2.6 OTMS/OTBE: Hardware platforms not supported ........................................................................ 72 3.2.7 OpenTouch SBC Hardware tested .............................................................................................. 73 3.2.8 Hardware support ..................................................................................................................... 73 3.2.9 Delivered Software ISO and file ................................................................................................. 73 3.2.10 Recommended versions for OpenTouch sub-systems ................................................................ 74 3.3 Supported languages ...................................................................................................................... 75 3.4 Software locks OmniPCX side ........................................................................................................... 77 3.5 Application compatibility (test done in validation) .............................................................................. 78 3.6 Application Programming Interface (API) .......................................................................................... 79 4 Installation procedures .......................................................................................................................... 80 4.1 General information ........................................................................................................................ 80 4.2 DNS ............................................................................................................................................... 81 4.3 ALEDS: Alcatel-Lucent Enterprise Deployment solution ...................................................................... 82 4.3.1 ALEDS: description.................................................................................................................... 82 4.3.2 ALEDS 2.2.2: compatibility for VM deployment ............................................................................ 83 4.3.3 ALEDS 2.2.2: additional feature for 8082 device update in lab ..................................................... 83 4.4 Omnivista 8770 update methodology ............................................................................................... 84 4.5 Installation (readme)....................................................................................................................... 84 4.6 New installation .............................................................................................................................. 85 4.6.1 Main steps of OT R1.3.000.043 installation from scratch: ............................................................ 85 4.6.2 Post installation (no factory server) ............................................................................................ 85 4.6.3 Post installation (factory server) ................................................................................................ 86 4.7 New installation on virtual machine .................................................................................................. 86 4.7.1 Documentation ......................................................................................................................... 86 4.7.2 Deployment topology ................................................................................................................ 87 4.7.3 Licensing .................................................................................................................................. 87 4.7.4 Deployment Steps ..................................................................................................................... 88 4.7.5 Advance management : SAN ..................................................................................................... 88 4.7.6 Advanced management: High Availability ................................................................................... 89 4.8 BEFORE Update OTMS/OTBE R1.1/R1.2 to OTMS/OTBE R1.3 ............................................................ 91 4.9 BEFORE Update OTBE R1.1/R1.2 to OTMS/OTBE R1.3: 8770 update.................................................. 91 4.10 Update from OTMS R1.1/R1.2 to OTMS R1.3.000.043 ..................................................................... 92 4.11 Update from OTBE R1.1/R1.2 to OTBE R1.3.000.043....................................................................... 94 4.12 Upgrade from OpenTouch R1.x to R1.3 with server reinstallation ..................................................... 96 4.12.1 ACS Patches ........................................................................................................................... 97 4.13 Migration ...................................................................................................................................... 97 4.14 OpenTouch R1.3.000.042 Critic restriction and Hotfix installation ..................................................... 98 4.15 OpenTouch R1.3.000.043 Hotfix installation and manual correction .................................................. 98 5 Server post installation check and operation ........................................................................................... 99 5.1 Global overview of post installation action ........................................................................................ 99 5.2 OpenTouch settings ...................................................................................................................... 100 5.2.1 TTS / TUI language ................................................................................................................ 100 5.2.2 Single Sign on authentication through Kerberos ........................................................................ 100 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 10/193 5.3 OmniPCX Enterprise settings .......................................................................................................... 101 5.3.1 OXE External voicemail............................................................................................................ 101 5.3.2 PRACK configuration ............................................................................................................... 101 5.3.3 CCBS timer for CCBS ............................................................................................................... 101 5.4 OpenTouch user and device creation .............................................................................................. 102 5.5 MyIC Phone setup ......................................................................................................................... 102 5.5.1 MyIC Phone hardware and compatibility matrix......................................................................... 102 5.5.2 MyIC Phone Deployment ......................................................................................................... 103 5.5.3 MyIC Phone 8082 Deployment without MAC address ................................................................. 105 5.5.4 MyIC Phones 8082 deployment using OXE DHCP ...................................................................... 106 5.5.5 MyIC Phones 8082 mass upgrade: 100 max ............................................................................. 107 5.5.6 Survivability on PCS ................................................................................................................ 107 5.5.7 MyIC Phone / 8002-8012 Survivability set-up rule ..................................................................... 108 5.5.8 Memory consumption check .................................................................................................... 109 5.5.9 MyIC Phone applications ......................................................................................................... 109 5.6 8002 - 8012 .................................................................................................................................. 111 5.6.1 8002 - 8012 Deployment as OpenTouch device ........................................................................ 111 5.7 4008-4018 EE ............................................................................................................................... 112 5.7.1 4008-4018 EE Deployment as OpenTouch device ...................................................................... 112 5.8 MyIC Desktop setup ...................................................................................................................... 114 5.9 My IC Mobile setup (for Opentouch user) ....................................................................................... 118 5.10 LifeSize setup ............................................................................................................................. 120 5.11 OpenTouch maintenance and back-up & restore ........................................................................... 122 5.12 OpenTouch Edge server .............................................................................................................. 123 5.13 Voice mail notification through mail / SMS .................................................................................... 124 6 List of Major issues, Restrictions and workaround ................................................................................. 125 6.1 Remaining major issue detected in OT R1.3.000.043 ....................................................................... 125 6.2 OpenTouch server ......................................................................................................................... 132 6.2.1 Fresh Installation .................................................................................................................... 132 6.2.2 Fresh Installation (on VMWARE) .............................................................................................. 134 6.2.3 ALEDS deployment restriction .................................................................................................. 134 6.2.4 Active partition Update ............................................................................................................ 135 6.2.5 Inactive partition + clean install: Update from OT R1.1/R1.2 to OT R1.3 .................................... 135 6.2.6 Upgrade from from OTBE R1.1,R1.2 to OTBE R1.3 with CCxx activated ..................................... 137 6.2.7 Upgrade from OpenTouch R1.x to R1.3 with server reinstallation ............................................... 137 6.2.8 Migration from BiCS to OTBE R1.3 ........................................................................................... 138 6.2.9 Migration from ICS to OTMS R1.3 ............................................................................................ 138 6.2.10 High availability .................................................................................................................... 139 6.2.11 Security ................................................................................................................................ 139 6.2.12 OpenTouch server ................................................................................................................. 140 6.3 MyIC Phone .................................................................................................................................. 141 6.3.1 MyIC Phone setup ................................................................................................................... 141 6.3.2 MyIC Phone debug .................................................................................................................. 143 6.3.3 MyIC Phone application ........................................................................................................... 143 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 11/193 6.4 4008-4018 EE ............................................................................................................................... 145 6.5 8002-8012 MyIC Phone (VLE – VLE+) RELEASED since OT 1.2.55 ............................................... 146 6.6 OTC iPAD ..................................................................................................................................... 146 6.7 MyIC Mobile ................................................................................................................................. 147 6.8 PC Application / MyIC Desktop ....................................................................................................... 148 6.8.1 Application / Browser .............................................................................................................. 148 6.8.2 MyIC Desktop Installation / Deployment / Start-up ................................................................... 148 6.8.3 MyIC Desktop common feature for OXE and ICM user ............................................................... 148 6.8.4 MyIC Desktop specific feature for ICM user .............................................................................. 150 6.8.5 MyIC Desktop specific feature for OXE user .............................................................................. 151 6.9 Directory, Telephony and Multidevice ............................................................................................. 151 6.10 Voice Mail / TUI / Prompt / Automated Attendant ......................................................................... 152 6.11 Conferencing and ACS ................................................................................................................. 153 6.12 Video.......................................................................................................................................... 154 6.13 Interoperability with OXE ............................................................................................................. 155 6.14 Management, Tools and backup ................................................................................................... 156 6.14.1 8770 Administration .............................................................................................................. 156 6.14.2 8770 core ............................................................................................................................. 156 6.14.3 Wireshark – how to limit disk usage ....................................................................................... 157 6.14.4 VNC ..................................................................................................................................... 157 6.14.5 Dynamic Log Activation ......................................................................................................... 158 6.14.6 Backup - Restore .................................................................................................................. 158 6.14.7 FAX server ............................................................................................................................ 158 7 List of Corrections ............................................................................................................................... 159 7.1 7.2 7.3 7.4 7.5 7.6 7.7 7.8 7.9 Closed OT 1.3.42 intial deilvery restriction with componant update .................................................. 159 Closed OT 1.2 restrictions in OT 1.3 ............................................................................................... 159 Closed OT 1.1 restrictions in OT 1.2 (info updated) ......................................................................... 160 Closed OT R1.1.60 restrictions in OT R1.1.80 (info updated) ........................................................... 161 Issues solved by VHE R260 1.11.0 and 1.12.2 ................................................................................ 161 Changes in OT R1.3.000.043 ......................................................................................................... 164 Customer issues solved in OT R1.3.000.042.................................................................................... 164 Customer issues solved in OT R1.2.000.055.................................................................................... 165 Customer issues solved in OT R1.2.000.054.................................................................................... 166 8 Focus on............................................................................................................................................. 167 8.1 Licenses ....................................................................................................................................... 167 8.1.1 Overview (updated with OT R1.3 news) ................................................................................... 167 8.1.2 License control : by FLEX ........................................................................................................ 168 8.1.3 Flex Deployment ..................................................................................................................... 168 8.1.4 ICE Core licence file description (with OT R1.3 update) ............................................................. 170 8.2 Contact and directories .................................................................................................................. 172 8.3 Telephony and routing .................................................................................................................. 173 8.4 Video - Visual collaboration ............................................................................................................ 178 8.4.1 Video Acronym ....................................................................................................................... 178 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 12/193 8.4.2 Visual equipments and version supported ................................................................................. 179 8.4.3 Video equipment interface details ............................................................................................ 180 8.4.4 Video Matrix ........................................................................................................................... 181 8.4.5 Ad hoc video conference ......................................................................................................... 181 8.4.6 Schedule video conference ...................................................................................................... 181 8.4.7 Video usages .......................................................................................................................... 181 8.4.7.1 LifeSize usage ................................................................................................................................. 181 8.4.7.2 MyIC Desktop calling OT user with a LifeSize ..................................................................................... 182 8.4.7.3 Initiate a video call from MyIC Desktop .............................................................................................. 182 8.4.7.4 Initiate a video call from LifeSize equipment ...................................................................................... 184 8.4.7.5 Initiate an ad hoc video conference from MyIC Desktop ...................................................................... 184 8.4.7.6 Join a scheduled conference – Dial out from the bridge ....................................................................... 186 8.4.8 ACS Administration ................................................................................................................. 187 8.4.8.1 An internal MCU is configured in ACS. ............................................................................................... 187 8.4.8.2 An external MCU is configured in ACS. ............................................................................................... 187 8.4.9 Video engineering rules ........................................................................................................... 189 8.4.9.1 ITU-T G.1050 – Profile A, B & C IP network ....................................................................................... 189 8.4.9.2 Multimedia communications with MyIC Desktop ................................................................................. 189 8.4.9.3 Multimedia conference with MyIC Desktop ......................................................................................... 190 8.4.9.4 MyIC Desktop / GVP video engineering rules / restrictions .................................................................. 190 8.4.9.5 Bandwidth requirement .................................................................................................................... 190 8.4.9.6 MyTeamwork IVC / ACS+MCU Radvision – video engineering rules .................................................... 191 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 13/193 1 Welcome 1.1 Introduction to OpenTouch R1.3  Alcatel-Lucent OpenTouch R1.3 is a minor release of OpenTouch R1.x line. It needs a specific OpenTouch R1.3 license with o OpenTouch Release R1.3 (release ID = 5) o MAX Device per platform + user and device quantity allowed for your deployment o OmniPCX Enterprise R10.1.1, o 8770 R1.3. It needs Actis 17.3.1 for generating OpenTouch R1.3 order It supports same hardware as OpenTouch R1.0/R1.1/R1.2 (see limitation on 300 users max for old HP server G6 and IBM Maokonk platforms and the new introduced HP server G8)  Installation, update and migration (using a data reload) OpenTouch R1.3 can be installed from scratch or in update of OpenTouch R1.1 / R1.2.000.05x After an installation from scratch, reload of data from OT R1.x, ICS 6.7, BiCS R2.1/R2.2, and OXE are possible. Note that CCS / CCA / ACR activation requireto install from scratch OT 1.3. To upgrade from OT R1.0.1 to OT R1.3, apply upgrade operation detailed in TC1760 To migrate from BiCS to OTBE R1.3, apply migration operation detailed in install Manual To migrate from OXE to OTBE R1.3, restore OXE DB in OTBE and update OXE setting required for OT interworking (SIP gateway, External voice Mail …)  The purpose of OpenTouch R1.3 release is to provide ICS R6.7.1 evolution inside OpenTouch to improve serviceability aspect : 8770 Meta-Profile with 1 device creation for OT users to simplify log activation / retrieval, certificate deployment …  This OpenTouch R1.3.000.043 is based in term of feature level and bug fixes on ICS R6.7 (some feature may not be available or reported within OT, check the feature list) ACS R9.2 (note that there is not ACS 9.2 standalone deployment) OmniPCX Enterprise GA version J2.603.20i A dedicated documentation for OpenTouch R1.3 has been produced and is available under the Technical Knowledge Base (TKB) of Alcatel-Lucent Business Portal Enterprise Activities Technical Documentation System Documentation Installation Manuals Installation on a physical machine Alcatel-Lucent Enterprise Deployment Solution Remote Worker with SBC Installation Administrator Manual Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 14/193 1.2 Software identification OpenTouch Release 1.3.000.043 is provided has a full version. The table below summarizes the main component / server / device and client version of the OpenTouch solution. To prevent installation issue due to a corrupted ISO / ZIP file, it is mandatory to check the MD5 checksum of each file after download (see Chapter 1.3 and see TC 1271) 1.3.000.043 Comment VM Ware compatibility 5.0 and 5.1 For OTBE-V or OTMS-V ALEDS 2.2.2 Boot DVD 5.8.100.012x86_64 VM Flex 1.3.000.051 Solve OXE deployment by ALEDS Boot DVD is not only a Linux version but also defines partitioning setup, account right, Only needed for OTMS-V and OTBE-V using a flex server deployed out of OTMS component ICE Core DVD 1.3.000.043 --ICS 7.3.000.043 --ACS 9.2.0.6509 --DCS 9.2.0.6509 --SIP server 1.3.003.03 --GVP MCP 8.1.704.00 --GVP RM: 8.1.601.00 DCS delivered in ICE DVD Fax server 6.6.0.16 Binaries for 4008-18, 8002-8012 and 8082 are in \devices folder of OT ICE core DVD Same FAX version as for OT R1.1 License is the same as FAX 6.5 OmniVista 8770 8770 1.3.05.00a Up to Patch --CCS 10.1.8.3 --CCA 10.1.8.4 --ACR 10.2 OmniPCX Enterprise J2.603.20i MyIC Phone R260 01.012.2 VLE 8002/8012 R100.2.32.1 IP Touch 4008 /4018 EE SIP 2.11.92 MyIC Phone customizer 2.1.4 (for R260) Not released MyIC Phone PC synchronizer 1.1.12.0 Do not use MY IC synchronizer 1.2.4 it is not compliant with R260 MyIC Desktop 5.2.007.24 --Devices Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved G (+ patch H and I) inside OT core DVD , R260 01.011.0 is supplied R260 01.012.2 is only on business Portal inside OT core DVD , R100 2.31.2 is supplied R100 2.32.1 is only on business Portal inside OT core DVD , old 2.11.92 is supplied Requirement : .NET Framework 3.5 Microsoft™ VSTO TC1798 Ed05 page 15/193 1.3.000.043 MyIC Mobile Blackberry 4.3.0.4 MyIC Mobile Android 4.1-2.0.31.4 OpenTouch Conversation Client for iPad Middleware server: 1.2.005.012 LifeSize 4.11.8 (4.11.12 also ok) TTS 1 1.0.000.003 TTS 2 1.0.000.003 TTS 3 1.0.000.002 TTS 4 1.0.000.004 Comment For OT user only, Also valid for use with OT R1.0 / 1.0.1 and 1.1 For OT user only, Also valid for use with OT R1.1 Take last iPad client on apple store Download this version from LifeSize support web page (need a valid LifeSize license) de-DE, en-GB, en-US, fr-FR, nl-BE, nl-NL ca-ES, da-DK, es-ES, es-MX, it-IT, no-NO, pt-BR, pt-PT cs-CZ, fi-FI, kr-KR, ru-RU, sv-SE, tr-TR, zh-CN, zh-HK ja-JP, pl-PL, fr-CA 1.3 Software files: DVD, ISO and ZIP The software of the various OpenTouch sub-systems can be downloaded from Business Portal as ISO files at: Customer Support / Software download / OpenTouch Business Edition or OpenTouch Multimedia Services / Release 1.3 Select Full release 1.3.000.043 Important Note: It is mandatory to check the MD5 checksum after Business Portal download to prevent installation issue due to corrupted ISO / ZIP files. (see TC 1271) 1.3.000.043 Label File Name 01-OTBE - OTMS Common Installation Files Boot DVD ICE Core 1.3.000.043 OPENTOUCH R1.3 Boot RHEL 5 64 bits DVD bootdvd.5.8.100.012x86_64.iso ot1.3.000.043.iso Text To speech 4 OPENTOUCH R1.3 Core Setup DVD-R OPENTOUCH TTS-1 DVD-R TTS_11.0.000.003 OPENTOUCH TTS-2 DVD-R TTS_21.0.000.003 OPENTOUCH TTS-3 DVD-R TTS_31.0.000.002 OPENTOUCH TTS-4 DVD-R TTS_41.0.000.004 Fax server OT 8450 FAX software installation DVD-R 6.6 OmniTouchFaxServer-6.6.0.16.iso Text To speech 1 Text To speech 2 Text To speech 3 TTS_1-1.0.000.003.iso TTS_2-1.0.000.003.iso TTS_3-1.0.000.002.iso TTS_4-1.0.000.004.iso 02a-OTMS-V Additional Virtual Machine FlexLM FlexLM 1.3.000.051 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved FlexLM 1.3.000.051 TC1798 Ed05 page 16/193 1.3.000.043 DCS 9.2.6509 Label Doc Converter deployment package to place on separate VM File Name dcs-9.2.0.6509-IP0001 (not supplied as DVD but inside ICE core DVD) 02b-OTBE Virtual Machine 8770 VM R1.3.05.00a 8770 VM R1.3.05.00a 8770 ISO R1.3.05.00a OXE VM J2.603.20i OPENTOUCH R1.3 8770 VM-1 DVD-R bics_vmManagement-1.3.000.041-1.iso OPENTOUCH R1.3 8770 VM-2 DVD-R OPENTOUCH R1.3 8770 ISO reserved to update VM 8770 of an installed OTBE 1.1 bics_vmManagement-1.3.000.041-2.iso OPENTOUCH R1.3 OXE VM DVD-R bics_vmOXE-1.3.000.043.iso 8770-1.3.05.00.a-b0003.iso 03-OmniPCX Enterprise Version dedicated to OpenTouch OXE R10.1.1 J2.603.20i OPENTOUCH R1.3 TELEPHONY DVD-R bics_OXE-j2.603.20.i Request document for security patch access (OXE Version, OT SBC) 04-OmniVista 8770 dedicated server 8770 R1.3.05.020a 8770 R1.3 Master Software DVD-R 8770. 1.3.05.00.a-b0003.zip MyIC BlackBerry 4.3 myicm(R4.1-4.3.4).zip ; canot be deployed by 8770, each user has to use his BB manager or BES admin has to deploy it Not given, end user has to use google play to get the application 05-Mobile Client MyIC BlackBerry ICM user MyIC Android ICM user MyIC Android 4.3 (version 4.3-2.0.31.4) 06-Software MyIC Phone MyIC Phone R260_01_12.2 MyIC Phone customizer PC synch 1.1.12.0 Software My IC Phone R260.01.12.2 ICTouch_VHE_R260_01_012_2.zip Software My IC Customizer Software My IC Phone PC Synchronizer 1.1.12.0 NOT released yet for MyIC Phone R260 MyIC_Synchronizer_1.1.12.0.zip 07-SIP Binaries for 4008-4018 EE and 8002-8012 4008-4018 SIP Binary for 4008-4018 EE 2.11.92 2.11. 92_SIP_Version.zip 8002-8012 SIP Binary for 8002-8012 2.32.1 MyICPhone_8002_8012_R100_02_032_1.zip 08-Software Deployment Tool Deployment tool Release 2.2.2 ale-deployment-solution-2.2.2.exe 09-HotFix OT Hotfix OXE Patches 8770 Patches No OT HotFix OXE dynamic patch, Pathc H and I for 1.3.05.00a Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved J2.603.20i in case of OT 1.3.000.042 installed Patch_130500I_CLIENT_JAR.ace Patch_130500H_JAR_AAR_DICT_COMMON.ace TC1798 Ed05 page 17/193 1.3.000.043 Label File Name 10-OpenTouch Edge server OTES 9.2.6509 OTES DOC OPENTOUCH R1.3 EDGE SERVER APPLICATION DVD-R OPENTOUCH R1.3 EDGE SERVER DOCUMENTATION CD-ROM Secured Patch (visible only after a request to access security patch for OXE or get SBC) OXE R10.1.1 sJ2.603.20i OPENTOUCH R1.3 TEL. SECURED DVD-R sj2.603.20.i.zip OpenTouch SBC OPENTOUCH SBC ssbc_F60.40AZ.033.005.iso 1.4 Software documentation Access to Alcatel-Lucent Enterprise Technical Knowledge Base Launch https://www.technical-knowledge-base.com/km  For Installation, Administration manuals Select these products and version then use menu Download to get the OpenTouch Documentation DVD or PDF files use menu Browse / Reference Book to view the OpenTouch Documentation online and associated documentation like user manual, technical communication … OpenTouch Business Edition Documentation DVD : 8AL 90506 USAD Product OpenTouch Business Edition Release 1.3 System Documentation Administrator Manual Installation Manual 8AL 90504 USAD Ed.01 APRIL 2013 8AL 90505 USAD Ed.01 APRIL 2013 User Manuals / User Guides Release Notes / Technical bulletins OpenTouch Multimedia Services Documentation DVD : 8AL 90506 USBD Product OpenTouch Multimedia services Release 1.3 System Documentation Installation Manual Administrator Manual 8AL 90504 USBD Ed.01 April 2013 8AL 90505 USBD Ed.01 April 2013 User Manuals / User Guides Technical bulletins OmniPCX Enterprise Documentation DVD : 3EU 19918 ENAQ Standard offer Product System Documentation OmniPCX Enterprise Administrator Manuals Installation Manuals Release 10.1 User Manuals … Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 18/193 OmniVista 8770 Installation Manual 8AL 90704USAC Ed.01 November 2012 Product 8770 1.3 Release 1.2 (no 1.3 doc) Security Guide 8AL 90705USAC Ed.01 April 2013 Administrator Manual SNMP Proxy 8AL 90703USAC Ed.01 November 2012 8AL 90708USAA Ed.01 November 2012 Ticket collector 8AL 90709USAA Ed.01 November 2012  Documentation DVD To obtain a master copy of the interactive OTBE R1.3 CD-ROM (8AL 90506 USAD Ed.01 ) for consulting documentation on your workstation, follow the procedure below: 1 - Download the files below into the same directory: xx.part1.exe (yy Mb) checksum xx.rar xx.rar (yy Mb) checksum checksum (yy Mb) Global file containing all checksum checksum file 2- Use right click on each link and save all files in same direcotry of PC. 3- run the exe file which uncompres the documentation Once decompression has finished, the interactive documentation consultation is available in the target directory. You can then burn it onto a CD-ROM or start consulting it. 4- To read the documentation, start the "load_doc.jar" application. You need ot have JRE 1.6 on your PC. 5- to run the doc from a .exe and use JRE in doc folder, copy /arch/load_doc.exe to / of doc folder Here the doc stucture for OTBE Enterprise Activities Technical Documentation System Documentation General Architecture Telephony Services Universal Directory Access Telephony Services for OpenTouch Users Automatic Callback on Busy Set or No Reply Supervision and Call Pickup Three-Party Conference Transfer Messaging Services Visual Voice Mail Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 19/193 Applications Manager/Assistant IM/Presence Dynamic Virtual Assistant One Number Services One Number Service for standard users Multi-devices for OpenTouch users Maintenance and Supervision Security Configuring 802.1x External Authentication Single Sign On Authentication through NTLM Single Sign On Authentication through Kerberos Certificate Management Description of IP Flow Installation Manuals Installation on a physical machine Alcatel-Lucent Enterprise Deployment Solution Remote Worker with SBC Installation Administrator Manual Before you start administration Quick Start User creation and administration Configuring voice mail services Configuring advanced applications Implementing OmniTouch 8600 MIC Mobile Implementing OmniTouch 8600 MIC Desktop Implementing OpenTouch Conversation (OTC) Implementing 8082 My IC Phone sets Implementing 8002/8012 DeskPhone sets Implementing IP Touch 4008/4018 sets Implementing OmniTouch 8450 Fax Software Configuring video devices Configuring OpenTouch multimedia conferencing and collaboration Configuring an automated attendant CAC management Backup and restore Appendix - User parameter list TUI .wav file list Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 20/193  For Release Note of the solution and associated component Select Product OpenTouch Business Edition or OpenTouch Multimedia Services Menu Browse / Reference Book / Release Notes  For Technical communication Select Product OpenTouch Business Edition or OpenTouch Multimedia Services Menu Browse / Reference Book / Technical Bulletins  For MyIC Phone , MyIC Mobile and MyIC Desktop User Guides Select Product OpenTouch Business Edition or OpenTouch Multimedia Services Menu Browse / Reference Book / User Manuals or User Guides User Manuals / User Guides Product OTBE or OTMS Release 1.3 Operation - OmniTouch™ 8082 My IC Phone (R260) 8AL90835xxCE OmniTouch 8002/8012 Deskphone Quick User Guide 8AL 90878 xxAA Operation - User Manual for OpenTouch : 8AL 90879 xxCA Operation - My Instant Communicator BlackBerry® R4.1 My Instant Communicator Desktop R3.2 (R5.1 in the menu help) My Instant Communicator Mobile Android R4.1 8AL90865xxBA  MyIC Phone 8082 Customizer tool and external Web App A presentation of MyIC Customizer tool and its main features is included in the MyIC Phone section of the technical documentation. A more extensive documentation is embedded in the tool. For R260 such tool is not ready. External Web App for MyIC Phone should be signed to allow the deployment in secured mode (otherwise administrator needs to put deployment mode=OPEN for testing an unsigned WebApp) End user equipment description and for some end user equipment documentation can be found on a public Web server: Ressource libray section > User guides http://enterprise.alcatel-lucent.com/?content=ResourceLibrary&page=overview here the list of usefull doc and links OTC iPAD http://enterprise.alcatel-lucent.com/includes/userguides/OTC/ updated for last OTC iPAD 1.2 feature, now several languages available Outlook integration Outlook integration OmniTouch 8400 Instant Communications Suite Microsoft Outlook Integration User Guide | English | 03/15/2009 Done for ICS , Similar to OpenTouch Link integration My Instant Communicator for Microsoft© Lync© User Guide OmniTouch™ 8400 Instant Communications Suite My Version 6.7 User Manual | English | 10/12/2012 Done for ICS , Similar to OpenTouch Voice Mail TUI Voice Messaging Service User Interface - Quick Reference Guide OmniTouch 8440 Messaging Software Quick Reference Guide Quick Start Guide | English | 03/15/2009 Donce for ICS , Similar to OpenTouch Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 21/193 Conference bridge quick guide OmniTouch 8660 My Teamwork 6.1 Quick Start Guide Conference bridge tone guide OMNITOUCH 8660 MY TEAMWORK 6.1 TOUCHTONE GUIDE Highlights product features and instructions on how to use them Quick Start Guide | English | 02/21/2006 Done for ACs simiar to Opentouch except for Webinar: use share document with OT OMNITOUCH 8660 MY TEAMWORK 6.1 TOUCHTONE GUIDE Quick Start Guide | English | 12/18/2009 Done for ACS similar for OpenTouch  OpenTouch Conversion for iPad User Guide The OTC includes a short series of screenshot in its application, (see help menu …) The user guide is available on a public web server: http://enterprise.alcatel-lucent.com/includes/userguides/OTC/ 1.5 Feature List / Compatibility related information  The Feature List / Cross compatibility and Release policy is available on business Portal in the section. Tools and Resources > Pre Sales Corner > In-depth Product Insight View product documents Alcatel-Lucent OpenTouch - R. 1.3 - Product Limits and Feature List 8AL020040085FLARA May 2013 OpenTouch Suite for MLE - Release Presentation - Virtualized offers 8AL020033239TCASA_6 January 2013 Mid and large Enterprises - December 2012 Offer - Release policy 8AL020033230TCASA_26b May 2013 MLE May 2013 offer - cross compatibility MLE May 2013 Offer: Cross compatibility 8AL020033609DRASA_18  OpenTouch solution can be placed in a federation with other standalone ACS server. The ACS version must be in R8.5 minimum versions (note that ACS R9.2 will not be released). This federation only allows: Instant Messaging and presence information: no call, no video. 1.6 OpenTouch topology with OmniPCX Enterprise  OpenTouch solution can be integrated in an OmniPCX Enterprise network The rules are In case of OTBE, the OXE node integrated in OTBE has to use the OXE version dedicated to OpenTouch : J2.603.20i for OT R1.3.000.043 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 22/193 For both OTBE, OTMS deployment, the OXE node defined as a SITE in OpenTouch (or called associated node by pre-sales) must use today the OXE J2.501.20g/h. These OXE associated nodes have local SIP Device user that matches the OpenTouch user company phone number. The OXE “SITE” is involved in all of the OpenTouch user voice communication except o Call from OpenTouch user to another OpenTouch user o Call from OpenTouch user to OpenTouch Telephonic services: voice mail, conference, routing For any other node in the OmniPCX Enterprise network, they have to be in OXE R9.0 minimum version to operate with OXE R10.1.1 (since OXE R10.1 is mandatory as explained above for OXE defined as a site in OpenTouch). These OXE nodes do not have any OpenTouch user declared.  OTMS topology  OTBE topology Note OXE compatibility with OT is announnced in TC1782. The main rule are OTMS is always tested with new Limited Availability/General Availability patch of OXE. But for OTBE, only dynamic patch are allowed. To install a new static patch of OXE in OTBE wait for next OTBE delivery Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 23/193 1.7 Software Maintenance and Support  Refer to Installation Manual, Release Note and troubleshooting guide first before submitted an issue  Use the trouble shoouting guide TG1464 to collect information and logs  Problem report submitted to Alcatel–Lucent must specify the OpenTouch release Other components release of the solution (OXE, 8770…) as well as client version List of Patch or Hotfix applied Clear description of issue with impacted device application and user type (OXE or ICM)  Release policy Life cycle process OpenTouch Business Edition OT 1.0 / 1.0.1 OT 1.1 OT 1.2 OT 1.3 DR5 General Availability End of "Active Commercial delivery" Nov 11 Jul 12 Jan 13 May 13 May 12 Nov 12 May 13 Dec 14 End of "Pre phaseout" Oct 12 May 13 May 13 May 14 End of "Phaseout" End of "Technical Support" ALTERNATIVE SOLUTIONS Jan 13 Oct 14 Oct 14 Oct 15 Jan 13 Oct 14 Oct 14 Oct 15 OT 1.3 OT 1.3 OT 1.3 active release Note: OT 1.1 support date has been aligned with OT 1.2, since both releases was available in old ACTIS 17.2. Anyway OT 1.3 is the maintenance release of OT 1.x. Hotfix will be produced on OT 1.3 only.  Patch production Policy All the details are available on the Business Portal at: Services / Software Support Services OpenTouch patch policy includes various kinds of deliveries: Full releases (Fx) for installation from scratch Update kits (ΔFx-1) never been provided Patches (Px,y): cumulative fixes and enhancements since the last full release HotFixes urgent generic fix to provide or fix delivered only to one customer To ensure a proper interoperability of the various elements, Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 24/193 Do not install a patch supplied in the green light of one of the element, but look at OpenTouch release note if such patch is compliant with OpenTouch solution. 1.8 Solution and Licensing model 1.8.1 Solution description The OmniPCX Enterprise offer has been renamed OpenTouch Suite for Large and Medium Enterprise. It means only that an OTMS can be included in the OXE offer The Alcatel-Lucent OpenTouch offer is available in several commercial packages or delivery:  OpenTouch Business Edition 1.3 for mid market in Customer Premise Environment All-in-one package including OmniPCX Enterprise with CCD/CCS, Unified Communication & Collaboration Suite, SIP Session Manager / Media Server, OmniVista 8770 (limited to 2000 users and 5 OXE nodes managed) and OmniTouch Fax Software As from OpenTouch 1.3 (Fresh installation), server for CCS, CCA and ACR are preinstalled in 8770 VM. During wizzard or via a script, these servers can be activated otherwise the software is presnet but not running. If more than 2000 users or 5 OXE nodes, an additional 8770 on a dedicated server can be used to manage the whole network of OXE and the OpenTouch server Genesys Compact Edition is on a dedicated appliance Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 25/193  OpenTouch Business Edition Virtualized 1.3: called OTBE-V Same feature as OTBE, but Deployment on top of Vmware ESXi (5.0 and 5.1) Composed by 3 Virtual Machines OTMS-V, 8770-V and OXE-V. No unified deployment like OTBE, each VM has to be deployed separately, and OXE is not pre-configured for OT interworking The licensing use a dongle. The flex server can be inside OTMS-V or in a separated Virtual Machine  OpenTouch Multimedia Services 1.3 for Large market in CPE Applicative add-on part of OmniPCX Enterprise offer, including Unified Communication & Collaboration Suite, SIP Session Manager / Media Server and OmniTouch Fax Software OmniPCX Enterprise and OmniVista 8770 are on dedicated servers.  OpenTouch Multimedia Services Virtualized 1.3: called OTMS-V Same as OTMS, but Deployment on top of VMware ESXi (version 5.0 and 5.1) The licensing use a dongle. The flex server can be inside OTMS-V or in a separated Virtual Machine Additional servers can be part of OpenTouch solution  External Flex server: The OTMS-V deployment has an embedded flex server, but for new OTMS-V R1.3 installation you can specify a unique external Flex server. Such Flex server is delivered as a VM image ready to copy inside VMware. It cannot be duplicated, but using VMotion it can be hosted on two appliance one active at a time. VMotion allow switching from one to another one. Take care that each ESXi appliance needs to have a dongle plugged and each flex server will use a specific license based on its attached dongle.  Webinar: Data conversion DCS tools (for an external VM dedicated to webinar) OTMS/OTBE has the capacity to prepare a INTERNAL virtual machine on top of KVM. No tools needed, only Windows OS DVD and Windows office DVD to supply. As from OT R1.3, the webinar virtual machine can also be deployed on top of VMware ESXi 5.x. For this after installing the Windows OS DVD and Windows office DVD you have to deploy the DCS tool. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 26/193  OpenTouch Edge server: This server is a MyTeamwork ACS server which act as an application proxy. Placed in the DMZ it receive request to join OpenTouch conference (URL available from the extranet) and relay data sharing exchange to opentouch server. It does not porcess voice or video flow, this communication flow is done via PSTN. Compared to a reverse Proxy (http proxy), it supports the Webinar feature which is not supported by reverse proxy. Conclusion o OTES product is required for providing conference access to external participant. o Reverse Proxy + SBC is required for Mobility (android, iphone, iPad) and can be used for conference (but no webinar) for internal employee having RP access credential To get the license follow the OTES licensing guide on the Business Portal  Reverse Proxy Reverse Proxy + SBC is required for Mobility (android, iphone, iPad) and can be used for conference (but no webinar) for internal employee having RP access credential This server is not supplied by Alcatel-Lucent. We recommend using Bluecoat product. The use of another reverse proxy is possible, but Alcatel Lucnet does not provide direct support to another RP product. We will only check if with you opentouch nd application version the same issue exist woth BlueCoat.  OpenTouch Session Border Controller Although the Alcatel-Lucent SBC offer is named OpenTouch SBC, it does not means that such SBC is a dedicated OpenTouch component. It can be included in any secured topology where such SBC has been validated, hence with or without an OpenTouch. Example: OXE SIP Trunking and OpenTouch SBC. This SBC runs on CentOS and cannot be installed inside OpenTouch server This SBC is delivered as software only on the secured patch section of OmniPCX Enterprise and of OpenTouch. To download the software, you need to fill first the “Request document to access secured patch” The hardware tested are HP ProLiant DL320e G8 (4GB RAM) Commercial Ref: 3BA27792AA (Harware only not soft installed) CPU: 1 x Intel Xeon E3-1220v2 3.1 GHz quad core, 8MB Cache, RAM 4GB NICs: 4 x1GbE Ethernet ports HDD: 1x500GB SATA disk 7,2KRPM, 1 x 350W non-redundant AC power HP ProLiant DL120 G7 (4GB RAM) Commercial Ref: not in Alcatel-Lucent catalogue, contact HP reseller CPU: Intel Xeon E3-1220 (Sandy Bridge) 3.1 GHz quad core, 8MB Cache, RAM 4GB NICs: 2x 1Gb Ethernet (+ 2 ports spare) HDD: 250 GB Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 27/193 1.8.2 Licensing model  OpenTouch commercial licenses are bases on a simplified generic model: Server / System licenses (base & options) User licenses (base & options) Device options Appliance Server OXE generic license Software Server options Pack SERVER OR High Availability – Management + Media ports Resources User options Messaging USERS Desktop Mobile OTC Tablet Conferencing + 80xx series 40x8 series 40x9 series DECT/WLAN Video DEVICES LEGACY Items (chassis, boards)  Refer to chapter 9.1 Licenses for more information on OpenTouch licenses. 1.8.3 Licensing guides  Licensing guides are available on the Business Portal https://businessportal.alcatel-lucent.com Customer Support > eLicensing Support Rehosting procedure (for license) Order & Logistics > supply chain > order entry rules OpenTouch Edge server Order entry Guide OmniPCX enterprise Release 10.1 Order entry Guide Direct Business Portal link https://businessportal.alcatellucent.com/alugesdp/faces/gesdp/products/Listing.jspx?PRODUCT=All&DOCTYPE=Operational_Guidelines/Ord er_Entry_Guide&RESULTSBYPAGE=25&BOXES=product,doctype OpenTouch for MLE - Order Entry Guide May 31, 2012 Operational Guidelines Order Entry Rules Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 28/193 FAX 1.9 Training and certification Alcatel-Lucent Enterprise Education has designed and updated OpenTouch™ training tracks dedicated for all audiences: Sales, Pre-sales, Post-sales and Administrators. Newcomers: new curriculum for Post-sales Training for Business Partners has been simplified with progressive training for newcomers organized by level (Advanced and Expert), certified by Alcatel-Lucent. Experienced: update your skills! Alcatel-Lucent Enterprise Education provides Post-sales delta training courses and associated certifications dedicated for Partners experienced and certified on OmniPCX Enterprise R10, OmniTouch 8400 ICS R6 and OmniVista 4760 R5 to give them the opportunity to upgrade their skills. A new evolution course (OPENWTE162) is available for partners experienced on OpenTouch R1.2 & 8770 R1.2 Learn how to manage your OpenTouch solution with OmniVista 8770 R1.3 training curriculum  Get full information on the dedicated website: https://businessportal.alcatel-lucent.com (Training & Certification section) or contact us: [email protected]  Screenshot: OpenTouch courses  Screenshot: 8770 courses Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 29/193 2 New features and enhancements  For a complete description of OpenTouch Release 1.3 contents, please refer to documents on Business Portal: Tools and Resources / Pre Sales Corner / In-depth Product Insight / OpenTouch You can find there information like feature lists, product limits, release documentation and notes, product and feature descriptions, provisioning level. 2.1 OpenTouch Release R1.3 new features: R1.3.000.043 status  Installation / upgrade / migration / license Description Green light HP DL380 G8p support  DL320 G8e support  CCA Server Integration on OTBE platform     ACR Integration on OTBE platform CCS Server integration on OTBE platform 8770 server and Contact Center on the same server Mono-instance deployment : network deployment tool improvements Deploying OTBE services without existing enterprise DNS server Upgrade-Update from previous release to OT 1.3 Migration from BICS/OTCC-SE towards OTBE 1.3 /OTCC-SE Migration from OXE , ICS , BiCS to OT 1.3      Set OXE in secured mode after OpenTouch post install  Copyright © 2013 Alcatel-Lucent. All rights reserved Hardware Server Obsolescence for DL380 G6 and G7 Hardware Server Obsolescence for DL120 G7 Only for fresh OTBE 1.3 install Only for fresh OTBE 1.3 install Only for fresh OTBE 1.3 install Only for fresh OTBE 1.3 install ALEDS 2.2 evolution OXE-V working ok since ALEDS 2.2.2 OK but see restriction on usage (qty client)  License Manager - Hosted - leftover R1.2 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Comments 4760 data export = OK Migration of ICS / OXE / 4760 from separate server Ok When virtualized , you need a external flex server, since only external flex can get OTID info concern change in setup : no SSH to SSH TC1798 Ed05 page 30/193  Voice Mail / Prompt / Telephony Replace TTS system prompts by wav-prompts for US-UK-FR-DE ICE email reading, option to use TTS for listening mail General Announcement message in Voicemail/Automated Attendant New default music on hold     TTS for such language are now used only by Automated Attendant and eMail reading since wav file has replaced TTS in EN / FR / GE) [Report ICS 6.7.1] Right to give for recording ok  Application / MyIC Desktop ICS - Support of CAS SSO authentication Support of IBM Lotus Domino 8.5.x 64-bit edition Outlook extension shall run in Citrix XenApp 6.5 environment  Conference / Video Integrated webinar doc conversion (jpg/ pdf) Internal and Management Support of ICS6.x Web Services on OT 1.3 UUM - NEW separate User template definition : OXE or ICM user (so for OXE+OT app, OT template must be with OXE ACUUSER Mobile HW must be agnostic when provisioning MIC mobile Help on line available for attribute values 8770 manage ICS user and VM MyIC Phone R260 Change of password Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved   [Report ICS 6.7.x] [Report ICS 6.7.1]         without need of extra VM DCS Take care for update to create a new porfile OT with user type ACU_OXE Require MYIC mobile 4.3 and device created as OTC mobile + option BB/android.. No possibility to deploy MyiC 4.3 on existing MYIC Android via DM OK, just the warning on format accepted Last ICS 6.7 needed, see 8770 GL , but in under control Optional file to update Apply only ofr OT user password stored in OT and used for local authentication TC1798 Ed05 page 31/193 2.2 OpenTouch Release R1.3 feature postponed to next OT 1.3 version Re-Hosting  Re-hosting of Contact Center  Pb on next upgrade OXE, inactive partition not rehosted 2.3 OT R1.3.000.043 Installation / Update / Upgrade / Migration Installation from scratch of OpenTouch release R1.3.000.043  It concerns following deployment OTBE R1.3 OTMS R1.3 on an existing OXE deployment OTMS-V R1.3 on top of VMware ESXi 5.0 / 5.1 Only one OTMS-V per Vmware appliance (mono-instance deployment) Update - Upgrade from previous OpenTouch release  Case of updates from R1.2.000.05x Update mode: installation using inactive partition option clean install, switch partition Update from OTBE R1.2.000.05x towards OTBE R1.3.000.043 (no CCx activation) Update from OTMS R1.2.000.05x towards OTMS R1.3.000.043  Case of updates from R1.1.000.xxx Updade mode: installation using inactive partition option clean install, switch partition Update from OTBE R1.1.000.0xx towards OTBE R1.3.000.043 (no CCx activation) Update from OTMS R1.1.000.0xx towards OTMS R1.3.000.043  Case of updates from R1.0.100.0x0 Update mode: 8770 update 1.3 then backup, fresh OT R1.3 install, restore Update from OTBE R1.0.100.0x0 towards OTBE R1.3.000.043 Update from OTMS R1.0.100.0x0 towards OTMS R1.3.000.043  Case of updates from OTBE R1.x with CCx activation Update mode: 8770 1.x update to 1.3 then backup, fresh OT R1.3 install with CCx activation, OT restore Concerns Update from OTBE R1.x towards OTBE R1.3.000.043 Migration from OXE to OTBE R1.3 Migration mode: save OXE, restore OXE in OTBE Any OXE version can be restored in OTBE The restoration delete the initial OXE configuration done by wizard , all OXE-OT interworking setup must be done again like for OXE with OTMS Migration from BiCS to OTBE R1.3  Migration mode: use OT tools on BiCS to save BiCS data, then fresh OT R1.2 install, restore BiCS data only BiCS R2.2/R2.3 can be migrated to OTBE R1.3.000.043 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 32/193  Note: Earlier version BiCS R1.0 / R2.0 / R2.1 cannot be migrated to OTBE But you can save OXE data of BiCS and migrate the OXE part to OTBE Migration from ICS to OTBE R1.3 or OTMS R1.3  Migration mode: use OT tools on ICS to save ICS data, then fresh OT R1.2 install, restore ICS data only ICS 6.7 can be migrated to OT R1.3.000.043  Note: Earlier version of ICS 6.x cannot be updated to OTBE R1.3 But you can update ICS 6.1, 6.2, 6.5, 6.6 versions to ICS 6.7  Fresh installation : option to select internal DNS server Internal DNS is based on local DNS entry OT element : 8770 / OT / OXE Can be consulted by any machine on the network Forwarder to an external DNS if not in the DNS domain Local DNS will be used by all the OT clients. Its address (OT address) must be configured in phone sets (8082, 8012/8002, …), tablets, in the network configuration (TCP/IP) of the PC client for MyIC PC. It is declared in 8770 : OT Config. -> Eco system -> IT Server -> DNS Server (= OT address). Wizzard to activated internal DNS Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 33/193  Fresh installation : option to access to OXE in SSH and use password aging Option O = No security No SSH Default password on OXE No password ageing Option 2 = Ageing / SSH SSH on OXE Custom password on OXE Password ageing days… Ned then to regularly change password on OXE in OT configuration (OXE declared)  OTBE 1.3 Fresh installation : option to select CCx service activation After instalaltion of OTBE 1.3 (fresh install only) It is possible ot acitvate the CCx by this command ot-config.sh  ALEDS tool to prepare OVF and the Deployment Machine OVF is a file descriptor of the VM With OVF created and deployed inside VMWare Each VM of the solution start by a BootPXE and perform an autoinstallation Using a dedicated Deployment Machine (Virtualized Machine Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 34/193 2.4 What’s new in OpenTouch Release R1.3.000.043 2.4.1 OT R1.3.000.043: Features on server side  CCx server inside OTBE platform 8770 server and Contact Center on the same server CCA Server Integration on OTBE platform, CCagent runngin on client PC ACR Integration on OTBE platformn CCS Server integration on OTBE platform, CCS clinet running on client PC  Support of ICS6.x Web Services on OT 1.3  License Manager - Hosted - leftover R1.2 2.4.2 OT R1.3.000.043: Voice application  Replace TTS system prompts by wav-prompts for English (US and UK), German and French In OT 1.2 only voiceMail TUI wasconcenred, here we add sytem prompt List of prompt concerned - My Assistant - MyPhone - Home Page - Routing management - Supervision - DVA - Forwarding - ACE Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 35/193 Management: Nothing to do this wav file is automatically used once OT 1.3 is installed Note : TTS remains in case of need of dynamic voice guide needed  ICE email reading, option to use TTS license for listening mail ACTIS impact New way to quote TTS ports with OT R1.3 (ACTIS v17.3.1): - TTS ports are new configurable in ACTIS for Automated Attendant usage and Email Reading usage  [Report ICS 6.7.1] General Announcement (only for langague suppllied as WAV instead of TTS) Define the TUI confiugration for this feature And give one user the right to record announcement  New default music on hold A new music on hold is loaded in OT, but still it can be customized 2.4.3 OT R1.3.000.043: Application ICS 6.7.1 Report  Support of IBM Lotus Domino 8.5.x 64-bit edition  Outlook extension shall run in Citrix XenApp 6.5 environment  Support of CAS SSO authentication Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 36/193 2.4.4 OT R1.3.000.043: Conference and video  Integrated webinar doc conversion (jpg/ pdf) Without any specific managemnt and NO VM creation, You have the Webinar option to share PDF or Picture (.bmp , .jpg) and add annotation 2.4.5 OT R1.3.000.043: Management 8770  UUM - NEW separate User template definition : OXE or ICM user To create an OXE user with OT app, An newOT template for user must be created in OT and snchorzed in 8770 This template should specify user TYPE= OXE ACUUSER  Mobile HW must be agnostic when provisioning MIC mobile Instead of filling IMEI, do not provide any value for Mobile identify The opration require user to have MyIC Mobile 4.3 Administrator to delete existin Mobile and create OTC smartphone (for 4.3 new creation moide) After OTC mobilke creation take care ot remove DUAL MODE option since MyIC Mobile does not support it Using IME is still possible , fill the Mibile identity  Help on line available for attribute values Example helpValue=“Allowed characters: ‘A’:’Z’, ‘a’:’z’, ‘[‘, ’\\’, ’]’, ’^’, ’_’, and ‘`’. E.g.: \“[VaN[gogH\””  8770 manage ICS 6.7 user + VM BOX from User application The sections bellow summarize OpenTouch R1.2 / R1.1 / R1.0.x major features Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 37/193 2.5 Reminder: What’s new in OpenTouch Release R1.2.000.055 2.5.1 OT R1.2 new features: R1.2.000.055 status GL with OT1.2.000.055 compared with OT 1.2.000.054 are marked in BLUE In fact 8002-8012 and 8770 OT Backup/Restore is added to the previous Green light And MyTeamwork video use is supported on Internet Explorer 9  Installation / upgrade / migration / license Name OpenTouch network deployment tool Support Red Hat 5.8 Post installation wizard security option can be removed Upgrade from previous OT releases Migration from BiCS to OT R1.2 Migration from ICS to OT R1.2 Mono-instance deployment in an existing virtualized customer environment Offers without physical dongle connected to server Licensing mechanisms for CaaS/Hosted model Windows 7 for 8770 server in OTBE  Device MyIC Phone 8082 R260 support MyIC Phone 8082 Disable Bluetooth MyIC Phone: Prog key MyIC Phone 8082 Supervision of ICM users Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved Status        Comment of Green Light ALEDS Tool is built by RD, deployment improvement for virtualization expected in OT R1.3 Allow support of next HP G8 server Without security : pre-signed certificate is deployed on VHE From OT R1.0.1 (data reload) From OT R1.1 (second partition update) Data reload (except ACS) Data reload   N/A The license server cannot serve several OpenTouch servers Feature is removed     Only direct call to one supervised user can be picked up, The call that follow a forward then ring a supervised user are not visible as TC1798 Ed05 page 38/193 supervised call TUI : Activation-de-activation of supervision  Video interoperability matrix  OK for most of peer to peer use case but restriction for conference use case  Restriction when option remote DNS is activated Survivability improvements for PCS survivability and support of OXE spatial redundancy 8002-8012 Support as OpenTouch SIP devices 8002-8012 Directory DialByName 8002/8012 Voice Survivability on OXE/PCS  Conference / Video Multipoint video Configuration settings Multipoint video User scheduling parameter      Pre configuration of default settings not working OK, but default value cannot be modified by administrator (it is all the time internal MCU by default) Video during scheduled conference Can be done without Video MCU  Compatibility with ACS Front-End    Pure ACS doc  Do not forget to apply R260 SIP profile on VHE configuration Update documentation for R9.2 additions Share webinar vm for several OpenTouch (hosted carrier deployment)  Application / MyIC Desktop Take call on Business Phone (VHE or VLE) from PC (“Broadsoft SIP extension”) Microsoft Lync for OT user Avatar consistency load and view Support of latest browsers releases Re brand Outlook calendar scheduling add-in Application Sharing System Tray Icon About Branding Automated Attendant: Dial-By_Name should wait more time to enter letters Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved     Avatar can be loaded from OTC iPAd saved in ACS and shared by other client See browser compatibility chapter   Report ICS 6.7 feature TC1798 Ed05 page 39/193 OT User presence  Voice Mail Prompt telephony Do not announce seconds for message receiving date-time Replace TTS based TUI by a wav-file based TUI Support of Exchange 2010 SP2 ICS Call-back sender confirmation prompt Email notification string improvement when mailbox is full ICS: Answer Only mode must not play system prompts but only greeting LSVM should propose to hang-up after leaving a voice message French Canadian is not available  Add of ringing state in supervision  Report ICS 6.7 feature  with restriction(greeting management)    Report ICS 6.7 feature  Report ICS 6.7: PER 2114   Report ICS 6.7 PER 1916 in OT Report ICS 6.7: PER 2080 LSVM=Local Storage of voice Message Report ICS 6.7: PER 2110 there is restriction male TTS voice Internal and Management List of OT available phone numbers  NSA security compliancy (Wizard management for admin accounts)    DM optimization Backup/Restore new API with file parameter for 8770 Automatic activation – deactivation of traces Need to rename logs file to ease component identification Information tracking: Manual audit documentation ICS - Software Architecture – Simplification    8770 Meta-Profile to create OT user and one single device (VHE or VLE) . Command dla.sh for activation, deactivation and save of traces Instead of traces.log you will get servicename.log like chameleon.log Preparation to have a license auditor tool in further release  2.5.2 OT R1.2.000.055: Installation / Update / Upgrade / Migration Installation from scratch of OpenTouch release R1.2.000.055 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 40/193 It concerns following deployment OTBE R1.2 OTMS R1.2 on an existing OXE deployment OTMS-V R1.2 on top of VMware ESXi 5.0 Only one OTMS-V per Vmware appliance (mono-instance deployment) Update - Upgrade from previous OpenTouch release Case of updates from R1.2.000.05x Upgrade mode: installation using inactive partition option clean install, switch partition Update from OTBE R1.2.000.05x towards OTBE R1.2.000.055 Update from OTMS R1.2.000.05x towards OTMS R1.2.000.055 Case of updates from R1.1.000.xxx Upgrade mode: installation using inactive partition option clean install, switch partition Update from OTBE R1.1.000.0xx towards OTBE R1.2.000.055 Update from OTMS R1.1.000.0xx towards OTMS R1.2.000.055 Case of updates from R1.0.100.0x0 Upgrade mode: backup, fresh OT R1.2 install, restore Update from OTBE R1.0.100.0x0 towards OTBE R1.2.000.055 Update from OTMS R1.0.100.0x0 towards OTMS R1.2.000.055 Migration from OXE to OTBE R1.2 Migration mode: save OXE, restore OXE in OTBE Any OXE version can be restored in OTBE The restoration delete the initial OXE configuration done by wizard , all OXE-OT interworking setup must be done again like for OXE with OTMS Migration from BiCS to OTBE R1.2  Migration mode: use OT tools on BiCS to save BiCS data, then fresh OT R1.2 install, restore BiCS data only BiCS R2.2/R2.3 can be migrated to OTBE R1.2.000.055  Note: Earlier version BiCS R1.0 / R2.0 / R2.1 cannot be migrated to OTBE But you can save OXE data of BiCS and migrate the OXE part to OTBE Migration from ICS to OTBE R1.2 or OTMS R1.2  Migration mode: use OT tools on ICS to save ICS data, then fresh OT R1.2 install, restore ICS data only ICS 6.7 can be migrated to OT R1.2.000.055  Note: Earlier version of ICS 6.x cannot be updated to OTBE R1.2 But you can update ICS 6.1, 6.2, 6.5, 6.6 versions to ICS 6.7 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 41/193 Post installation wizard: Security option to use a pre-signed certificate  During OTMS/OTBE installation you can specify the deactivation of security We have the possibility to select if we want security or not. If we select “deactivated”, the system will use a generic certificate. A pre-signed certificate will be deployed for the devices as the VHE phone. In this case, we don’t need to sign the certificate on the VHE phone. o We just have to plug the phone after having declared it on the system. o The administrator has the possibility to activate the security later. If we select “activated”, we have to specify the type of the certificate that we will import and the place where it is. If we import a PKCS12 certificate, we need to specify the passphrase. We will have the same behaviour than in the OT R1.1. Offers without physical dongle connected to server  During OTMS installation you can specify the use of an external FLEX server (type the IP address) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 42/193 2.5.3 OT R1.2.000.055: New Features introduced Configuration setting for default multipoint video 8002/8012 as OpenTouch user deskphone device  or   Support Only one deskphone per OpenTouch user: MyIC Phone 8082 4008/4018EE 802/8012 Directory DialByName from 8002-8012 Survivability for 8002/8012 8002/8012 feature to be supported CLIR (caller id hidden): The CLIR is a service offered to the caller user to prevent presentation of his/her caller number to the callee user. The identity secrecy is activated by the Man Machine Interface (MMi). Receive call: Incoming call is accepted by unhooking (handset / handfree / headset only VLE+). Receive call (auto answer): By Call-Info/Answer-after SIP Header. Local auto-answer (interphony): The VLE/VLE+ device can answer the incoming call automatically; it can be activated by MMI. Receive call (auto answer – Notify): 3PCC auto answer by SIP Notify/Talk event. Reject call: The VLE/VLE+ device can stop the incoming call ringing by pressing the release key once, reject the call by pressing the release key twice. When the disconnect (rule #3) is applied, there will be the SIP error code 486 busy in case of reject call. Call Forward – Local: It’s a local forward function of VLE. COLR (callee id hidden): The COLR is a service offered to the callee user to prevent presentation of his/her callee number to the caller user. The identity secrecy is activated by the MMI. Message waiting indication Voice mail access: The user can deposit voice messages to the callee and the callee can access the voicemail server to consult the voice messages. Busy call: When the max numbers of lines is reached, the VLE/VLE+ will prompt the caller is busy state. Answer from audio equipment: Only the VLE+ can answer from audio equipment because of jack headset connection. CLI Display (Calling Line Identification): The right information of caller can display on the screen of callee. 2.6 Reminder What’s new in OpenTouch Release R1.2.000.054 2.6.1 OT R1.2.000.054: Features on server side New Boot DVD: 5.8.010.005.x86_64  New Boot DVD to support Red Hat 5.8, hence HP G8 server will be supported  Resolution of boot corruption when using too many times update on inactive partition Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 43/193 License OpenTouch Release Control: 3 means OT 1.2 ICE_RELEASE 3 ALCFIRM Licence OpenTouch: reading e-mail from voice mail access  The control has been removed and will be used only in OT R1.3 ICE_EMAIL_READING 1 ALCFIRM OpenTouch network deployment tool: Alcatel-Lucent Enterprise Deployment Solution (ALEDS) ALEDS 2.0.5 is now part of RD delivery Web presentation application shared among several OpenTouch instances UCaaS: To minimize the number of VM needed, a unique Web Presentation virtual Machine can be used by different OpenTouch server Dimensioning / limits and Performance Non regression test for OTBE 500 OTBE 1500 OTMS 1500 OTMS-V 1500 2.6.2 OT R1.2.000.054: Device and Routing Survivability improvements for PCS and OXE CPU spatial redundancy support OT R1.1: preferred SIP server at VHE initialisation is OpenTouch, Hence if during OXE PCS activation, the VHE is rebooted, it will try to reconnect to OpenTouch, whereas IPTouch continue to work on PCS OT R1.2: if a PCS is configured it will the first tested if VHE restart OT R1.2: support of OXE spatial redundancy MyIC Phone 8082-v1 / 8082-v2 R260 evolutions  Common favorite/contact web app: 2 tabs proposed  Call log: 2 tab proposed unread and history, Viewing one call log put in history all calls of the same source  Indication that VHE load new binaries, Install happens after the communication is finished Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 44/193 MyIC Phone 8082-v1 / 8082-v2 R260 Supervision of OpenTouch user  Any ICM user can be part of supervision group. The group is defined by the administrator using 8770 configuration module. There are two role supervised ICM user and supervisor ICM user.  The supervision control is only available from MyIC Phone 8082  The supervision concerns only direct call to the OT user, if the call is forwarded it is not visible as a monitored call 8770 Configuration application Tab OT OT server NAME - System services - Applications - User Groups Search option Tab OT NAME: Group1 User: Dupont Is Supervisor [x] Is supervised [x] … General TAB Activation-de-activation of supervision service  A TUI vocal application allows to activate deactivate the supervised state  A new button allows to activate deactivate the supervised state (located in Home Page > user info) My IC Phone 8082-v2 R260 Video  MyIC Phone 8082-v1 does not support video  MyIC Phone 8082-v2 support video, The Webcam supported is Logitech C920. Logitech C920 is only available in Alcatel-Lucent European catalogue For other market, you need to find a valid reseller until we got authorization to resell it  The video is always a 2 steps, answer audio first then initialize/accept video Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 45/193 MyIC Phone 8082: Security for Bluetooth on MyIC Phones Possibility to disable the Bluetooth on MyIC Phone (security IT requirement) 2.6.3 OT R1.2.000.054: PC Application, MyIC Desktop features and integration Take call on Business Phone from PC (“Broadsoft SIP extension”) MyIC Desktop in call control mode (3PCC) cans request hands-free off-hook action on Deskphone. Such feature concerns both devices MyIC Phone 8082 and Deskphone 8002/8012.  When computer and VHE/VLE are in the ringing list, MyIC Desktop shows a popup with both capabilities to take call: on computer or on VHE/VLE Automated Attendant Dial-By Name: wait more time to let user enter letters [Report ICS 6.7] Support new browser (compatibility):  Internet Explorer 9  Firefox 7 Outlook extension  Re brand Outlook calendar scheduling add-in: named OpenTouch instead of MyTeamwork 2.6.4 OT R1.2.000.054: Voice Mail / Telephony TUI/TTS: Replace TTS based TUI by a wav-file based TUI Prompt: French Canadian [Report ICS 6.7] UM: Support of Exchange 2010 SP2  Same as Exchange 2010 support, here it is SP2 validation test. Voicemail [Report ICS 6.7]      Call-back sender confirmation prompt Email notification string improvement when mailbox is full Answer Only mode must not play system prompts but only greeting Local Storage Voice Mail should propose to hang-up after leaving a voice message Do not announce seconds for message receiving date-time 2.6.5 OT R1.2.000.054: Conferencing and Video Compatibility with ACS Front-End  OT 1.2.000.054 : OTES 9.2.6363  OT 1.3.000.043 : OTES 9.2.6427 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 46/193 Application Sharing System Tray Icon About Branding Update documentation for R9.2 additions User scheduling parameter for multipoint video Support of video during scheduled conference without external Video MCU Video interoperability matrix  The minimum requirement is peer to peer video with same kind of device 2.6.6 OT R1.2.000.054: Administration / Internal feature 8770: Meta-Profile for ICM user including its device  The development is based on OT development: provide the range of OT free number for device creation  Administrator can create a Meta-Profile OT user  8770 shortcut in Active Directory admin interface can request an OT user creation with one single device 8770: DM optimization 8770: Inventory information of VHE1/VHE2 On device application, the administrator as a new field VHE Type to save the information of VHE type: VHE1 for MyIC Phone 8082-v1 or VHE2 for MyIC Phone 8082-v2 Do not forget after update to R260 of both kind of VHE to assign the Default SIP capability SIP profile R260. OT server: Command line: Backup/Restore new API with file parameter OT server: Need to rename logs file to ease component identification OT server: Automatic activation – deactivation of traces  The command dla.sh can activate the traces according to a feature selected. It is packaged with logzipper tool OT server: Information tracking: Manual license audit documentation OT server: NSA compliancy (Wizard management for admin accounts) OT server: ICS - Software Architecture - Simplification 2.6.7 Features not yet available in R1.2.000.054 8002-8012 Deskphone: introduced with OT 1.2.000.055 Configuration setting for default multipoint video introduced with OT 1.2.000.055 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 47/193 2.6.8 Features Removed from OpenTouch R1.2 W7 8770 OTBE It was planned to move from Win 29008 to win 7 for cost reduction the Virtual Machine 8770. Finally this evolution is cancelled 2.6.9 Features postponed to OpenTouch R1.3 Licensing mechanisms for CaaS / Hosted model A unique flex server can be used to share all licenses from different OpenTouch server. Such development is targeting operator that want to deploy several OpenTouch solutions for different customer but need to have a central license server. CaaS means Communication as a Service. 2.7 Reminder: What’s new in OpenTouch Release R1.1.000.091 2.7.1 OT R1.1.000.091: New feature provided MyIC Phone: Prog key  With MyIC Phone R250 1.10.4 2.7.2 TC for R1.1.000.091 TC1762 OpenTouch – Technical Release Note R1.1.000.091 and Hotfix TC1761 OpenTouch – Upgrade procedure from R1.0.1 to R1.1.091 2.8 Reminder: What’s new in OpenTouch Release R1.1.000.080 2.8.1 OT R1.1.000.080 major restriction and feature not yet released  Feature with major restriction Two OpenTouch Releases installation on same Hard disk  OK for OTMS NOK for OTBE (issue during OXE update) Check Chapter 6 – Restriction Smooth Major Upgrade on second inactive HD partition  OK for OTMS (except FAX DATA) NOK for OTBE (issue during OXE update) Check Chapter 6 – Restriction Support of Citrix XenApp 6.0: all users (no video/VoIP/ only call control) Support of Internet Explorer 9 and latest Firefox version Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved   Ok but MyTeamwork functionality doesn't work under CITRIX (crms00372504) No MyTeamwork video on IE9 Check Chapter 6 – Restriction TC1798 Ed05 page 48/193 OpenTouch Conversation Client on iPad Tablet OpenTouch SBC use case with OTBE/OTMS  Feature not released OpenTouch user MyIC Desktop video call with third party equipment : LifeSize and Radvision MyIC Phone: Prog key OpenTouch SBC use case with MyIC Teamwork client IPv6 readiness for OpenTouch conversation client  OTC client for iPad is on apple store  VLAN segregation , no encryption VLAN segregation + encryption Homeworker, no encryption Homeworker + encryption Check Chapter 6 – Restriction  Many restrictions, Check Chapter 6 – Restriction and Chapter 8 – Video With MyIC Phone R250 1.8.4 / 1.10.3 Adding prog key can lead to losing default button: crms00392583 Not delivered    OK OK but… OK but… OK but… Internal feature 2.8.2 OT R1.1.000.080 Installation / Update / Upgrade / Migration Installation from scratch of OpenTouch release R1.1.000.080 OTBE 1.1 OTMS 1.1 on an existing OXE deployment Update from OpenTouch R1.1 Update from OTBE R1.1.100.060 towards R1.1.000.080 Update from OTMS R1.1.000.060 towards R1.1.000.080 Upgrade from previous OpenTouch release Following upgrades are allowed from R1.0.100.0x0 to R1.1.000.080: Update from OTBE R1.0.100.0x0 towards R1.1.000.080 Update from OTBE R1.0.100.0x0 Hosted towards R1.1.000.080 Update from OTMS R1.0.100.0x0 towards R1.1.000.080 As there is a new partitioning, upgrade shall be done with scratch installation + data restoration. Follow the TC1707 for upgrade OT R1.0.100.0x0 to OT R1.1.000.080 Migration from BiCS Following upgrades are allowed from BiCS to OT R1.1.000.080: Migration from BiCS R2.1.3 towards OTBE R1.1.000.080 Migration from BiCS R2.2.2 towards OTBE R1.1.000.080 Migration from BiCS R2.3 towards OTBE R1.1.000.080 Check that the server hardware is compliant and follow the TC1635 for BiCS migration to OT R1.1.000.080 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 49/193  Migration from OXE to OTBE  Migration from OXE, ICS, 4760, ACS to OTMS Tested with existing deployment of OXE J2.402.1a ICS 6.6.000.106.b 4760 5.1.06.03 ACS 8.5.0b5805 (but no data recovered from ACS) Migration from ICS 6.6.000.107 is not yet supported  Following Migrations are under control of PCS Migration from ICS 6.6.000.106 towards OpenTouch Multimedia Services Migration from BiCS towards OpenTouch Business Edition 2.8.3 OT R1.1.000.080 : New feature New Boot DVD: 5.4.102.002  Allow installation of OT R1.1 on blade server using network installation or ALEDS  Create maintenance account on inactive partition Version installation requirement: supply boot DVD  The Boot / OS DVD is required for any OpenTouch deployment type Update of OT R1.1.000.060 on active partition Update of OT R1.1.000.060 on inactive partition Fresh installation of OT R1.1.000.080 MyIC Phone 8082: synchronisation with buddylist and presence  MyContact buddylist group  This feature is released as from OT R1.1.000.080 and MyIC Phone R250 1.10.3 MyIC Phone 8082: Manager Assistant 3:1  Extension to 3 managers for 1 secretary  Administrator needs to create 3 different links: Mgr1 Ass1, Mgr2 Ass1, Mgr3 Ass1 OpenTouch Conversation Client on iPad  The status is OTC iPad can be deployed,  Release candidate on Apple Store (for evaluation) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 50/193 SBC  OpenTouch SBC use case with OTBE/OTMS VLAN segregation , no encryption VLAN segregation + encryption Homeworker, no encryption Homeworker + encryption OK OK but… OK but no Music on hold OK but no Music on hold 2.8.4 OT R1.1 Feature not released MyIC Phone 8082: programmable key  Supported keys are Phone number Contact without picture Contact with picture  This feature is released as from OT R1.1.000.091 with MyIC Phone R250 1.11.x min version SBC  OpenTouch SBC use case with MyIC Teamwork client Two OpenTouch Releases installation on same Hard disk Smooth Major Upgrade on second inactive HD partition  For OTMS this feature is released But FAX issue  For OTBE this feature is not yet released It works but need lot of workaround: conclusion it is not released Same FAX issue OXE installation on the inactive partition of OXE VM succeeds but It return an error message which stops the update process o Version.txt is marked with installation failure o 8770 is not updated OXE auto-start is not validated after update (crms00374534 fixed in OT R1.1.000.080, hence only for next update) 2.9 Reminder: What’s new in OpenTouch Release R1.1.000.060 2.9.1 OT R1.1.000.060: Installation / Upgrade / Migration  Installation from scratch of OpenTouch release R1.1.000.060 OTBE R1.1 OTMS R1.1 on an existing OXE deployment Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 51/193  Upgrade from previous OpenTouch release Following upgrades are allowed from R1.0.100.0x0 to R1.1.000.060: Update from OTBE R1.0.100.0x0 towards R1.1.000.060 Update from OTBE R1.0.100.0x0 Hosted towards R1.1.000.060 Update from OTMS R1.0.100.0x0 towards R1.1.000.060 As there is a new partitioning, upgrade shall be done with scratch installation + data restoration. Follow the TC1707 for upgrade OT R1.0.100.0x0 to OT R1.1.000.060 Migration from BiCS Following upgrades are allowed from BiCS to OT R1.1.000.060: Migration from BiCS R2.1.3 towards OTBE R1.1.000.060 Migration from BiCS R2.2.2 towards OTBE R1.1.000.060 Migration from BiCS R.2.3 to OTBE R1.1.000.060 is not supported (but ok to OTBE R1.1.000.080) 2.9.2 OT R1.1.000.060: Features on server side New Boot DVD: 5.4.101.005.x86_64  New Boot DVD for dual partition If Disk > 350 GB, the first installation will prepare the partition to host the inactive partition Example of OTBE partitioning  New partitioning for Vg_root_1: 30GB Vg_root_2: 30GB Vg_common:100GB disk > 350GB partitions specific to the system 1 partitions specific to the system 2 partitions used by both systems: VMs and backup  New partitioning for disk < 350GB (no double partition feature supported) Vg_root: 30GB Vg_common: 100GB VMs and backup New path and services organisation  Launch the command “env” to get the full list of new environment variable and associated path. Main path [root@othostname ~]$ env Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 52/193 CMS_HOME=/opt/Alcatel-Lucent/oamp/cms DATA_HOME=/var/data FLEXLM_HOME=/opt/Alcatel-Lucent/platform/flexlm LICENSES_HOME=/var/data/licenses MAINTTOOL_HOME=/opt/Alcatel-Lucent/serviceability/maintenance_tool BACKUP_HOME=/opt/Alcatel-Lucent/serviceability/backup OpenTouch User: New License control for device and mobile Control on the MAX of devices that can be associated to OpenTouch users depending on the hardware platform ICE_USER_DEVICE_ASSOCIATION Total number of device that can be associated to the total of users (1000 for OTBE 500, 3000 for OTBE1500 and OTMS ALCFIRM Number of OT user with right to use iPAD ALCFIRM Control on the iPad tablet ICE_TABLET There is no specific control on the video device LifeSize, it is counted like MyIC Phone device in the total of device that can be associated to OpenTouch users OpenTouch User: License control: Anymobile /BlackBerry / Android  An additional control on mobile type allocated to OpenTouch user has been added ICE_OFF_SITE_MOBILITY_ANY ICE_OFF_SITE_MOBILITY_BB ICE_OFF_SITE_MOBILITY_ANDROID Number of OT user with right to use Anymobile Number of OT user with right to use BB Number of OT user with right to use android ALCFIRM ALCFIRM ALCFIRM OFF-SITE mobility license for Any-Mobile, BB and android platforms  The off-site mobility is dedicated to mobile. It is unused for OXE user, MyIC Desktop Nomadic. In fact only the Desktop license is required and the remote user flag on the OXE device (OT configuration) Support of OT 8450 Fax Software R6.6  See TC1525 Ed2 for FAX server features. The license for FAX 6.5 can be used for FAX 6.6 version. Dimensioning / limits and Performance Non regression test for OTBE 500 OTBE 1500 OTMS Documentation OpenTouch IP flows The list is published in the Technical Knowledge Base Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 53/193 2.9.3 OT R1.1.000.060: Device and Routing Visibility of device model capability and SIP options supported In the below screenshot: video and take call from MyIC Desktop (auto-answer in Remote Call Control 3PCC) is disabled since the current MyIC Phone R250 version does not support such options. 8770 Configuration application Tab OT OT server NAME - System services - Applications - Telephony - SIP Phone Profiles - MyIC Phone 8082 profile - MyIC Phone 8082 R260 default profile Search option Tab OT Make Call [x] Take Call [x] Call on hold / retrieve [x] Video [x] Capacities Multidevice routing  OpenTouch user has now a complete flexibility to define and use routing profile (list of ringing devices, which is device used by MyIC Desktop for placing call) MyIC Phone shows now the same routing states as MyIC desktop.  For detail see Chapter 8 Telephony and routing My IC Phone 8082-v1 / 8082-v2 R250 evolution and compatibility with OT R1.1  Support of hardware 8082-v1 and 8082-v2  Display current software version during boot (software awareness)  Deployment without MAC address  Multidevice routing  New button Advanced in standard mode to activate preview mode (WebApp) Home button to switch back to standard mode (icon+ prog. key)  Auto Lock on backlight off 4008EE / 4018EE as OpenTouch user deskphone device Only one deskphone per OpenTouch user: either MyIC Phone 8082 or 4008/4018EE LifeSize as OpenTouch user video device  End user device (the LifeSize is one of the audio video user physical device)  Meeting room device (the meeting room is declared as an OpenTouch user) OXE Users: mobility When activating MyIC desktop nomadic GSM, the remote extension is deactivated This way, they will be no more 2 simultaneous calls reaching the mobile. This situation was leading to the call falling into mobile voicemail. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 54/193 OpenTouch Users: mobility  New Mobile creation rules / requirement give a device Number (AABBxxxxxx for instance) specify the GSM number in a new field (this allow end user to change its mobile number if needed (waiting for administrator to update the configuration) give the DISA = ACE vocal application number manage reverse proxy URL already setup in OT (even if no reverse proxy used)  New MyIC Mobile application: Android 4.1 and BlackBerry 4.1 Same feature for android 4.1 as the one provided in MYIC Blackberry but No Instant Messaging on Android 4.1 No disabling of POP UP to select Business call / Private Call when using Android native dialler and MYIC android running in background.  MyIC Mobile Android 4.1 and BlackBerry 4.1: Favorites presence Favorites and Presence synchronisation with the buddylist group My Favorites End user need to create a group My Favorites in MyIC Desktop > My Contact  MyIC Mobile Android 4.1 and BlackBerry 4.1: Manager Assistant functionality Support for manager to delegate call to assistant Call log with indication of assistant / manager supervision action 2.9.4 OT R1.1.000.060: PC Application, MyIC Desktop features and PC integration OpenTouch User: MyIC Desktop video call with third party equipment: LifeSize and Radvision Standard user (OXE): MyIC Nomadic GSM compliant with OXE mobility (REX) When activating MyIC desktop nomadic GSM, the remote extension is deactivated This way, they will be no more 2 simultaneous calls reaching the mobile. This situation was leading to the call falling into mobile voicemail. Standard user (OXE): MyIC Desktop Nomadic IP using SIP protocol  Nomadic SIP allow to easily crossing border element as session border controller / firewall Communication (signalling and voice stream) between MyIC SIP and SBC can also be secured with SIPS and SRTP Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 55/193 Standard user (OXE) MyIC Desktop: Nomadic IP get ringing tone for Call Completion on Busy Subscriber (CCBS) After placing a call back request on a busy user, as soon as this user is free, the system calls back the MyIC Desktop Nomadic IP. This development adds a ring tone to the already present pop up window Standard user (OXE) Support of Microsoft™ Lync with Windows™ Server 2008 R2 Remote Desktop RDS MyIC Desktop (in remote call control: no VoIP / no Video) can be integrated in Windows RDS Lync 2010 is also supported by Windows RDS This development add the integration of MyIC Desktop with Lync within an RDS session Support of Citrix XenApp 6.0: all users  No VoIP / no Video, only call control Support of Outlook 2010 SP1  Same as Outlook 2010 support, here it is SP1 validation test. SP2 is not validated yet New browser compatibility:  Internet Explorer 9 (but MyTeamWork video does not work with IE9)  Firefox 7 MyIC Desktop (VoIP): DTMF automatic popup window for each call can be disabled.  End user can then select to open it when needed Default Option Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved Activation on-demand TC1798 Ed05 page 56/193 MyIC Desktop: option menu to change voice mail notification by end user MyIC Desktop: Support Headset of Latest GN Netcom/Jabra devices  Check the feature list and AAPP IWR report 2.9.5 4059EE R1.2: OpenTouch user telephonic presence Retrieve OpenTouch user telephonic presence  There is NO reservation only a one shot check of OT user telephonic presence status  Quick setup and operation 2.9.6 OT R1.1.000.060: Voice Mail Call-back sender barring  An end-user doesn’t have the right to call outside the company or for instance not place international. Using call-back feature (from voice mail) he can bypass this limitation Administrator needs to change Voice mail profile parameter: Call-back sender allowed Voice Mail: Voice Messaging counters for ICS Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 57/193 Voice Mail / Voice Prompt: 3 levels of TUI verbosity for ICS (like A4635)  Short prompt can be used for Voicemail main menu Voicemail listening menu (that contains replay message, call sender, envelope info. Etc) Greetings menu  Administrator needs to change Voice mail profile parameter: Brief Prompt for TUI User TUI tab Brief Prompt Support of Polish TUI 2.9.7 OT R1.1.000.060: Conferencing and Video Webinar: ability to perform, record, replay a audio & data presentation  This feature is based on the installation of new virtual machine containing Windows™ 7 32bits English Office 2010 pro 32bits English  The DVD and product key needs to be purchased out of Alcatel-Lucent  Take care to buy only retail version  Volume version of Windows and Office are NOT supported Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 58/193 White-boarding OpenTouch Edge server The OpenTouch server cannot be installed in DMZ and Reverse Proxy placed in DMZ does not support desktop sharing application. A solution is the OpenTouch edge server placed in DMZ and managed in stack with OpenTouch The cluster name will be used for invitation to internal and external user. Media Server enhancements: ACS media server replaced by GVP  Audio/Data/Video Switching  Ad-hoc & scheduled video* Conferencing  OT R1.1 news Up to 94 A/D/V participants in a single ad-hoc conference High Quality Audio for OT user in ad-hoc & Scheduled conference Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 59/193 2.9.8 OT R1.1.000.060: Administration 8770: Increase the number of departments There is no hardcoded limit on number of department 8770: MyIC Phone deployment without MAC Address From 8770 user management you can create device without MAC address MAC Address will be discovered during the MYIC Phone request to OpenTouch The discovery key is based on a new identification KEY and Password (replace identification with MAC address for the first deployment) 8770 time to create user: API response time Creation of user toward OpenTouch is done now in a single request to OpenTouch based on template ID and not on retrieving then sending template content 8770 simplified template for user creation: Meta-Profile The Meta-Profile saves inside 8770 the selection of the user profile, the range of OXE free number to use for the user number OXE and OpenTouch node used to create the user This information is only saved in 8770 The OpenTouch ICM device is not created by the Meta-Profile Do not create ICM device or application (voice mail…) using the range for OXE free number 8770: setup of IMAP4S for IMAP access Capability for 8770 to manage the secured parameter for IMAP (instead of file edition or WebAdmin action) 8770: setup of Exchange 2007 multiple email domains Capability for 8770 to manage the server FQDN domain and the domain mail manage by this mail server (instead of file edition or WebAdmin action) 2.9.9 Features Postponed to OpenTouch R1.1.000.080 MyIC Phone 8082: synchronisation with buddylist and presence MyIC Phone 8082: Manager Assistant 3:1 OpenTouch Conversation Client on iPad 2.10 Reminder: What’s new in OpenTouch Release R1.0.100.060 New MyIC Phone R200.1.34.4:       Support of MYIC Phone 8082-V1 8082-V2 Wired handset for MyIC Phone 8082-v2 only External Power Adaptor for MyIC Phone 8082-v2 only (when no PoE present) Minor Ergonomic enhancements Directory enhancements (display first lastname that match then given name) Auto-lock (new parameter on the device settings page: Auto-lock on backlight off) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 60/193 2.11 Reminder: What’s new in OpenTouch Release R1.0.100.050 2.11.1 OT R1.1.000.050: Update / Migration Following update are allowed from R1.0.007.010 to R1.0.100.050:  Update from OTBE R1.0 towards R1.0.1  Update from OTBE R1.0 Hosted towards R1.0.1  Update from OTMS R1.0 towards R1.0.1 Follow the installation manual for the update steps Following Migrations are under control of PCS Migration from ICS 6.5 towards OpenTouch Multimedia Services Migration from BiCS R2.2 towards OpenTouch Business Edition Follow the TC1635 for BiCS Migration In case the number of users with ICS access is not important, we recommend to limit the migration to only OXE part (so no PCS is required) and to create from scratch all users. 2.11.2 OT R1.1.000.050: Features on server side New Boot DVD: 5.4.008.004  New default account for maintenance For new installation performed using this Boot DVD, htuser account is no more usable, the iceuser maintenance account has to be used 8770 adminnmc expiration date  During wizard, Adminnmc password is changed including password expiration date Openness / API evolution (numbering R6.5) This is an internal adaptation of internal API part dedicated to numbering API Single Sign On (SSO) via Kerberos In addition to NLTMV1, Kerberos is now supported for Authentication. 2.11.3 OT R1.1.000.050: OpenTouch User Experience Manager / Assistant 1:1 Concerns OpenTouch user (on ICM) equipped with a MyIC Phone8082 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 61/193 MyIC Phone PC synchronizer (1.1.8.2)  Requirement: OpenTouch user (on ICM) With a MyIC Phone 8082 1. Equipped of Outlook 32bit application (from Outlook 2000) on their PC.  This application synchronizes outlook contacts with MyIC Phone contacts. The synchronisation works in both way: deletion on MyIC Phone delete also contact in Outlook. Hence a dedicated contact folder in Outlook is recommended to synchronize only part of outlook contact. Route My Call to without "Mobile" destination Concerns OpenTouch user (on ICM) with a Mobile  When Mobile is not reachable, all incoming call falls into mobile voice mail. As from OpenTouch R1.0.1, end user can select from MyIC Desktop two destinations without mobile: “Office Phone” or “Personal Computer”.  Quick setup overview On OT configuration, Select System services > Applications > Telephony > Telephone Prefix Put a prefix value for Activate Office location  This feature is a temporary workaround; OpenTouch R1.1 will provide more flexibility for Multidevice Routing Browser compatibility:  Google-Chrome 15  FireFox 7 Homeworker: AcmePacket SBC support OpenTouch R1.0.1 has been tested with ACME SBC for remote worker use case (same test as with OT R1.0). Take care that MyIC PC settings to access SBC needs to be manually entered on MyIC Desktop options. 2.11.4 OT R1.1.000.050: MyIC Desktop features and integration MyIC Desktop: Support Headset of Latest GN Netcom/Jabra devices  Check the feature list and AAPP IWR report MyIC Desktop: Support of the "tel:" tag  MyIC Desktop will intercept the “TEL:” Tag in Web page or email to launch a call.  VM Tag is also supported (see SMS/SMTP evolution feature) but only works with Local storage voice mail. In case of local storage voice mail box, the parameter Deactivate MWI notification (in 8770 User and Devices > User > Notification) must be disabled in order to get new voice message notification in MyIC client. MyIC Desktop: Outlook 2007 Support (+Screen display issues with Outlook 2007)  Outlook extension allows placing call on a selected contact, playing a voice message received by mail, and recording a voice message Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 62/193 MyIC Desktop: Ability to dial, out of a resulting contact, phone numbers defined in the LDAP directory or Personal Information Manager (PIM)  If an LDAP or Outlook contact has a business number / mobile … these phone numbers will be presented for dialling. Standard user (OXE) Microsoft™ Office Communicator 2007 R2 integration: ability to dial phone numbers defined in MSFT AD or Outlook personal contacts - ICS Report  If an LDAP or Outlook contact has a business number / mobile … these phone numbers will be presented for dialling. Standard user (OXE) Sametime integration tab and Sametime 8.x theme Standard user (OXE) Microsoft™ Lync integration pane Lync application can use MyIC Desktop capability. Microsoft™ Window 2008 R2 SP1 RDS compatibility Remote desktop service in Windows™ Server 2008 R2 with SP1 is evolution of Terminal Services. Feature MyIC in RDS environment will allow users to use most of My Instant Communicator functionality, but without necessity to install MyIC on local client station. Only MYIC Desktop will be authorized to be deployed in RDS (no MOC/LYNC, ST integration, no VOIP, and no video). 2.11.5 OT R1.1.000.060: Voice Mail / Prompt / Automated attendant Automated attendant administration  Possibility to modify the size of the Automated Attendant design screen  Reference for each node of the tree Standard tone to leave a voicemail The .wav file played when leaving the voicemail has been modified to be similar as to what was proposed with 4645. No configuration required, this modification is applied by default. Visual Voice Mail: addition of the message controls window  MyIC Desktop has now the access to visual voice mail interface with navigation within the message.  No specific configuration is required; MyIC Desktop opens directly the Visual Voice Mail when selecting a Voice Message. The audio Message is played on the current phone device used to place call from MyIC Desktop (could be the computer or the office phone) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 63/193 SMTP/SMS Notification feature improvements The following advanced mail notification options are only available for LS voice mailbox: Wav file attached Link to My Messaging and MyIC Desktop Visual Voice Mail Call back sender link Voicemail box almost full and full notification 8400/8440 voice mail statistics - step1 Follow the administration manual to setup the voice mail statistic Support of IMAP4S for IMAP access  IMAP4S was already supported by OpenTouch R1.0, but without access to a management interface. With OpenTouch R1.0.1, the WebAdmin is able to manage the IMAP4S configuration.  The access to the IMAP4S configuration from 8770 configuration is postponed to OpenTouch R1.1 release. NTLM V2 towards MSFT CAS (Exchange web services)  On Exchange2007 no additional configuration needed  On Exchange2010 for service EWS enable Anonymous Authentication Support of latest Exchange 2007 Service Pack: SP3  SP3 supported Support of Microsoft™ Exchange 2010 DAG topology (clustering)  There is no configuration required. This feature is a pure Microsoft™ management Support of Exchange 2007 multiple email domains  Allow to manage different domain for Exchange servers FQDN and emails  With OpenTouch R1.0.1, the WebAdmin is able to manage these different domains. The access to the multiple email domains configuration from 8770 configuration is postponed to OpenTouch R1.1 release. 2.11.6 OT R1.1.000.050: Localization Following Language has been added for TTS / TUI / GUI      Danish GUI support Support of IDA voice for Danish TTS/TUI TUI language Danish TUI Language Czech + Japanese TUI language Flemish Non TTS language/Hebrew voice prompts support:  This voice prompt will be delivered in a next patch of OT R1.0.1. Single (aggregated) business card as a result from a directories search  Merge of PBX, LDAP & Internal Directory in a single card with: last name, first name, business phone number, other phone numbers (e.g. mobile), photo, email address, business phone presence. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 64/193 2.11.7 OT R1.1.000.050: Feature not released Interco with ACS Front-End for external participants  An ACS placed in DMZ, allows external participant to join a conference established on OpenTouch.  Restriction: the compliant ACS release is not yet available (Target is end of March, TBC) Configuration:  This ACS Front End and OpenTouch need to be managed in stack. The cluster name will be used for invitation to internal and external user. 2.12 Reminder: What’s new in OpenTouch Release R1.0.007.010 2.12.1 OT R1.0.007.010: Features on server side Unified communication  Telephony services  One Number services (for OXE users only)  Messaging services Local storage Unified messaging Local storage integrity Local storage encryption Secured Local storage IMAP4 o LS IMPA4 Lotus SSL (OXE and ICM users) o LS IMAP4 Outlook 2003 SSL (OXE users) o LS IMAP4 Outlook 2007 TLS (OXE and ICM users) o LS IMAP4 Thunderbird 2.x TLS  Mobility MyIC on Android, iPhone, BlackBerry 3.5, Windows™ Mobile 6.x, Nokia (OXE users) MyIC on BlackBerry 4.0 (ICM users)  MyIC on IP Touch Collaboration      Ad-hoc conferences Scheduled conferences Application sharing Presence and IM (OXE users, MyIC PC ICM users) Federation with MyTeamwork 8.5 server (only for Presence and IM) Video (P2P, conferencing) Depending of the use case, the embedded MCU or an external MCU may be used for video conferencing Management  User Unified management (UUM) for ICM and OXE users  Device Management (DM) for SIP Device/Softphone of ICM and OXE users ICM : MyIC Phone, MyIC Desktop OXE : 4008/4018 in SIP mode, MyIC Desktop SIP (OXE), Thomson ST2022/ ST2030  Mass Provisioning for ICM and OXE users Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 65/193 Infrastructure       Manual or network (silent) installation of the full software Migration (covering BiCS R2.2 and ICS R6.1) Backup & Restore procedure Supervision / solution control Centralised alarms (through OmniVista 8770) Metrics via SNMP counters (LS …) and VoIP tickets (OmniVista 8770) Miscellaneous     Compliant with Fax software (embedded) 6.5.6.26 Automated Attendant for OXE and ICM users FlexOffice 7 for OXE users CAC management between OXE and ICM 2.12.2 OT R1.0.007.010: Features on user / device side Basic telephony for ICM devices  Telephony between ICM users Broker call Call Completion on busy state or no reply Conference Enquiry call Forward Simple call Transfer Voicemail  Telephony between ICM and OXE users (interoperability) Attendant Broker call Call Completion on busy state Conference Enquiry call Forward Simple call Transfer Voicemail Advanced services (ICM devices)          Multi-devices MyLocation Media escalation Unified communication log Dynamic Virtual Assistant (DVA) Visual Voicemail (also available for OXE users with MyIC PC) Universal Directory Search (OXE phonebook, 8770 directory, LDAP(S) server) MyIC Desktop in Remote Call Control of an OXE or ICM user MyIC Desktop SIP (ICM user only) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 66/193 MyIC Phone 8082 LLDP-MED (VLAN, PoE, Inventory, Localisation) Survivability on OXE / PCS File manager (pictures, MP3 files) Appointment reminder Local directory Speed dial 802.1x MD5 / TLS authentication Openness through SDK (check for availability the MyIC Phone Tech Com) (Check http://developer-enterprise.alcatel-lucent.com/ for more information)  Magnifying glass  Bluetooth         2.12.3 OT R1.0.007.010: Ecosystem End user side  Outlook Outlook 2010 extension for ICM or OXE users Notes 8.5.1 / 8.5.2 extension for ICM or OXE users  Collaboration (only for OXE user) Microsoft™ OCS 2007 R2 Sametime 8.0 Sametime 8.5  LifeSize video (as OXE SIP device) Express 220TM, Team 220TM, Room 220TM and Conference 200TM Server side  Exchange Server Exchange 2007 on Windows™ Server 2003 (32 or 64 bits) Exchange 2007 on Windows™ Server 2008 Exchange 2010 on Windows™ Server 2008  Domino Server o Domino 8.5.1 / 8.5.2 on Windows™ Server 2003 o Domino 8.5.1 / 8.5.2 on Windows™ Server 2008  SBC interworking VLAN segmentation (voice / data) MyIC Desktop SIP home worker Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 67/193 2.12.4 Features Postponed to OpenTouch R1.0.1 Synchronization of contact between Outlook and the MyIC Phone set Manager / Assistant 1:1 on MyIC Phone 2.12.5 Features Removed from OT R1.0 MyIC Phone 8082 (R200 1.29.x) does not support IM, Presence nor Mail application.  The Presence restricted to the Manager/Assistant application will be added in R1.0.1.  The Presence restricted to the Favorite application will be added in R1. 1. 2.13 Features under PCS process If one of these features has to be deployed, contact the Technical Support for its deployment. The relative PCS forms can be found on the Business Portal at: Customer Support / Technical Support / PCS documents PCS = Premium Customer Support. The Premium Customer Support procedure allows Business Partners to benefit from assistance on features or products whose commercial availability has been announced (DR3) but which have not yet been fully released. The PCS procedure replaces the former SDP (Specific Deal Process) procedure; refer to eFlash EF_Marketing_003_260704 for additional details. List of features under PCS  BiCS R2.2/R2.3 to OTBE R1.2 Migration When only OXE part is migrated, no PCS request is required (this choice is applicable also for BiCS R2.1)  ICS R6.6 to OTMS R1.2 Migration  SBC – VLAN segmentation (voice/data)  SBC – MyIC Desktop SIP homeworker  My Teamwork multipoint video conferencing using the RADVISION SCOPIA video MCU  Lotus Domino Integration  OmniPCX Enterprise – SIP TLS for SIP Trunking  OT81x8 WLAN sets on specific WLAN infrastructure  OmniPCX Enterprise – IP DR-Link on Passive Call Server Features still under test  OmniPCX Enterprise – Public SIP Trunking interoperability tests Interoperability tests with new carriers are managed under control of SIP Bid Desk Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 68/193 3 Requirement and compatibility 3.1 Data collection Documentation Use following document to save your OpenTouch solution FQDN / IP@ / Password TC1758 2 OpenTouch R1.2 / R1.3 Prerequisites and Data Collect Guide Main preconisation for naming To simplify the choice and avoid misconfiguration and issue FQDN should include valid name and ressitent to any issue in code Lower characters only Never start by number (risk of confusion and handling by script as an IP address) No specific characters except “-“, only alphapetical and numeric characters Don t name the OT server as “ice”, “server”, for a generic name use “opentouch” Example of bad name: “8770server”, “ice”, “server-d’opentouch” And last preconisation, print on paper your datacollection of used FQDN. You will this way not confuse the different servername or IP during further management (leading to extra time to find root cause of no IP communication between machine) 3.2 Hardware and software requirements 3.2.1 General Please refer to the Cross Compatibility and Feature List document that can be found on the Business portal at: Tools and Resources / Pre Sales Corner / In-depth Product Insight / OpenTouch 3.2.2 Hardware platfrom not tested by ALU Check the documentation for recommendation on selecting a platform for OTMS deployment TC1758 2 OpenTouch R1.2 / R1.3 Prerequisites and Data Collect Guide Additional note: Due to compatibility issue and performance issues, OpenTouch solution must not be installed on top of software RAID controllers. Only physical RAID controller can provide sufficient io performance for OpenTouch needs. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 69/193 3.2.3 OTMS R1.3 / OTBE R1.3: Hardware platforms tested and supported Warning In case of hardware issue, be sure to update the firmware to the latest version available on www.hp.com, especially for the blade server. HP G8 servers have been qualified since OT 1.2.000.054. with OT 1.3 they are delivered by default by the factory HP DL380p G8 (24GB) OTMS R1.3 / OTBE R1.3 supported Tech Ref: 3BA27765ABAA 2xXEON E5-2620 2.00 GHz six core, RAM 24GB HDD 2x500GB SATA, Raid1 HP DL320e G8 (20GB) OTBE R1.3 (500 User max) Tech Ref: 3BA27753ABAA 1xXEON e3-1230v2 3,20 GHz quad core, RAM 20GB HDD 2x500GB SATA, Raid1 HP G7 servers are still supported HP DL380 G7 (20GB) OTMS R1.2 / OTBE R1.2 supported Tech Ref: 3BA27765AAAA 2xXEON E5620 2.40 GHz quad core, RAM 20GB HDD 2x500GB SATA, Raid1 HP DL120 G7 (16GB) OTBE R1.2 (500 User max) Tech Ref: 3BA27753AABA 1xXEON e3-1230 3,20 GHz quad core, RAM 16GB HDD 2x500GB SATA, Raid1 3.2.4 Virtualized requirement Hyperthreading has to be disabled on the host and in all the VMs The RAM has to be reserved for all the VMs and not shared Compared to official documentation, the VM sizing has been checked again, and some modification applied are presented here (in blue) Virtual Hard disk quatiy is not physical disk but disk space allocated ot virtual machine For a physicla OTMS installation we ask for 500 GB disk size (rendred by a 2 disks with minimum 500GB in Raid1) For a virtualized OTMS-V installation we ask for 500 GB virtual disk size (rendred by VMWare, letting VMWare expert identify what physical disk are required to show 500GB in VM creation) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 70/193 3.2.4.1 OXE-V 10.1.1 requirement OmniPCX Enterprise Virtual Machine Processing: 1 vCPU 2.5 GHz, 1 or 2 vNIC (redundancy dependant) Dedicated memory: 1 GB RAM Virtual Hard disk: 40 GB (incl. Dual partitioning) – Disk access speed: 10 Mbit/s 3.2.4.2 OTMS-V 1.3 requirement OpenTouch Multimedia Services Virtual Machine Under the minimum disk capacity, install fails… Up to 500 users: 4 vCPU 2,5 GHz 10 GB RAM Virtual Hard disk: 500 GB (including backup and 2nd installation for easy upgrade) Up to 1500 users 8 vCPU 2,5 GHz 13 GB RAM Virtual Hard disk: 500 GB (including backup and 2nd installation for easy upgrade) 3.2.4.3 8770-V 1.3 requirement OmniVista 8770 (8770-V) Processing: 2vCPU* 2,5 GHz 4 GB of RAM, Depending on user managed by virtualized 8770 1500 user 50 GB of virtual hard disk Up to 5K, 80 GB of virtual hard disk Above 5K, 120 GB of virtual hard disk Note: Not supplied by Alcatel-Lucent : Microsoft Operating System Windows 2008 R2 64 bits. 3.2.4.4 OTMS-V 1.3 Flexera Hardware platforms tested and supported The installation of the .ovf file creates a virtual machine with the following characteristics: Virtual machine name: Flexera server Operating system: CentOS OS version: based on Linux RHEL 5 64 bit Vcpu number: 1 Memory: 1 GB Disk size: ~25 GB of virtual hard disk 3.2.4.5 Document Conversion Server VM requirement Webinar virtual Machine Vcpu number: 1 Memory: 2 GB Disk size: 30 GB of virtual hard disk Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 71/193 3.2.5 OTMS/OTBE: Hardware platforms supported with capacity restriction The following 2 hardware used in BiCS can be used for OTBE 1.3 IBM MAOKONG X3250M3 (16GB, extensible to 32GB) Limited to 300 users Cannot add the CCx app server: CCS/CCA/ACR No extra VM like Webinar VM, No internal video MCU can be activated No possibility to have dual partition Tech Ref: 3BA27707ABAA XEON X3430 2.40 GHz quad core, RAM 16GB HDD 250GB 7200 RPM 3.5 Hot-Swap SATA II, Raid 1 IBM MAOKONG X3250M3 (8GB, extensible to 32GB) Limited to 300 users Cannot add the CCx app server: CCS/CCA/ACR No extra VM like Webinar VM, No internal video MCU can be activated No possibility to have dual partition 8GB Memory needs to be replaced by a 16GB Memory Tech Ref: 3BA27707AABA XEON X3430 2.40 GHz quad core, RAM 8GB HDD 250GB 7200 RPM 3.5 Hot-Swap SATA II, Raid 1 The following hardware introduced in OT R1.0 / 1.1 is still supported in OT R1.3 but with capacity restriction HP DL120 G6 (16GB) => replaced by DL120G7 , since 8 June 2011 Limited to 300 users Cannot add the CCx app server: CCS/CCA/ACR No extra VM like Webinar VM OTBE 500, No possibility to have dual partition if disk = 2x 250GB Tech Ref: 3BA27753AAAA 1xXEON X3430 2.40 GHz quad core, RAM 16GB HDD 2x500GB Raid1 3.2.6 OTMS/OTBE: Hardware platforms not supported The following 2 appliance server used by BICS product cannot be used for OTBE. Hence hardware has to be changed. Please refer to chapter 3.2 OTMS R1.3 / OTBE R1.3: Hardware platforms tested and supported IBM MABOLAS X3250M2 (6 or 8GB not extensible, not enough CPU) Cannot be used for migration to OTBE MAOLIN X3250 (4GB not extensible, not enough CPU) Cannot be used for migration to OTBE This following Blade server is no more sold within Alcatel-Lucent catalogue, HP BL 460c G7 (16GB) For a deployment inside a Data centre with blade server, use the virtualization deployment Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 72/193 3.2.7 OpenTouch SBC Hardware tested HP ProLiant DL320e G8 (4GB RAM) Commercial Ref: 3BA27792AA (Harware only not soft installed) CPU: 1 x Intel Xeon E3-1220v2 3.1 GHz quad core, 8MB Cache, RAM 4GB NICs: 4 x1GbE Ethernet ports HDD: 1x500GB SATA disk 7,2KRPM, 1 x 350W non-redundant AC power HP ProLiant DL120 G7 (4GB RAM) Commercial Ref: not in Alcatel-Lucent catalogue, and should be no more in HP catalogue CPU: Intel Xeon E3-1220 (Sandy Bridge) 3.1 GHz quad core, 8MB Cache, RAM 4GB NICs: 2x 1Gb Ethernet (+ 2 ports spare) HDD: 250 GB 3.2.8 Hardware support  In case of Hardware issue on HP server, you need to call HP support directly. Follow the process described in Technical support / Hardware support / Specific Hardware procedure / Server: HP HP_ALU_Partners_guide_V8.pdf Most of the time the first action of HP hotline in case of hardware issue is to check the BioS version and update it.  Here the web link to HP support for driver downloads of DL 120G7 http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=50759 37&prodTypeId=15351&prodSeriesId=5075933&swLang=8&taskId=135&swEnvOID=4006#12212  Here the web link to HP support for driver downloads of DL 380G7 http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=40914 32&prodTypeId=15351&prodSeriesId=4091412&swLang=8&taskId=135&swEnvOID=54 There is an alert of HP concerning DL380 G7 about kernel panic on Linux It concerns system delivered with system ROM < 5 MAY 2011. This alert has been raised and solved 6 month before OpenTouch R1.0 Commercial Availability: 8 NOV 2011. Hence any HP server bought directly to Alcatel should have the correct ROM. ** CRITICAL ** Systems ROMPaq Firmware Upgrade for HP ProLiant DL380 G7 (P67) Servers (For USB KeyMedia) 3.2.9 Delivered Software ISO and file The software of the various OpenTouch sub-systems can be downloaded from Business Portal as ISO files at: Customer Support / Software download / OpenTouch Business Edition or OpenTouch Multimedia Services / Release 1.3 Select Full release 1.3.000.043 See chapter Chapter 1.3 Software files: DVD, ISO and ZIP Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 73/193 3.2.10 Recommended versions for OpenTouch sub-systems OpenTouch is a solution, which means each OpenTouch version or patch correspond to specific version or patch of OmniPCX Enterprise, OmniVista 8770, MyIC Phone, MyIC Mobile on BlackBerry, ... The use of different versions than the ones announced officially may lead to interoperability issues. Therefore the use of OmniPCX Enterprise or OmniVista 8770 patches, different than the ones announced officially for OpenTouch systems, is forbidden. OXE compatibility The list is regularly updated in following Technical Communication TC1782 MyIC Mobile compatibilty The list is regularly updated in following Technical Communication TC1677 (MYIC Mobile 4.x for OpenTouch) Product OXE OpenTouch BES BlackBerry Mobile Android DNS server AAA server Fire Wall Reverse Proxy Minimum Version J2.501.13.e R1.1.000.091 R1.2.000.053 R1.3.000.043 4.1.X device with minimum firmware 5.0 device with minimum firmware 2.2 Not relevant Not relevant Not relevant BlueCoat SGOS 6.1.2.1 Proxy Edition Licenses / Comments Offsite Mobility for Android / BlackBerry See the devices white list on Business portal for a complete list of supported device See the devices white list on Business portal for a complete list of supported device Other RP not directly supported, but comparison can be done with bluecoat and same version MyIC Mobile openTouch to compare the issue 8770 Compatibiltiy The list is updated at each 8770 new technical release NOTE. For 8770 1.3 the TC1801 8770 version OpenTouch OpenTouch OpenTouch OpenTouch R1.0 R1.0.1 R1.1 R1.2 8770 R1.0 OK OK 8770 R1.1 OK OK OK 8770 R1.2 OK OK OK OK 8770 R1.3 OK OK OK OK OpenTouch R1.3 OK MyIC Phone 8082 Each technical release note of MyIC Phone specifiy the compliant opentouch version Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 74/193 For R260 1.11.0 the TC1781 For R260 1.12.1 the TC1819 MyIC Phone version OpenTouch R1.0 R200 1.29.x OpenTouch R1.0.1 OpenTouch R1.2.000.054 OpenTouch R1.2.0.055 R1.3 MyIC Phone 8082 v1 v2(video) MyIC v1 MyIC v1 MyIC Phone 8082 v1 R200 1.30.x MyIC Phone 8082 v1 MyIC Phone 8082 v1 v2 R200 1.34.x / 1.35.x R250 1.8.x / 1.10.x / 1.11.x R260 1.10.4 R260 1.12.x OpenTouch R1.1 1.11.0 MyIC Phone 8082 v1 v2 / Phone 8082 v2(video) Phone 8082 v2(video) 3.3 Supported languages Note: system alarms are only in English and French. Language TUI Administration Ar Arabic Catalan MyIC Phone Ca_ES Chinese (traditional) Zh  zh_TW Chinese (simplified) Zh_CN  zh_CN  Cs Czech Danish Da Dutch Nl English En Nl  English (US) Estonian Et Finnish Fi French Fr Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved En En_US Fi  Fr TC1798 Ed05 page 75/193 Language French Canadian German TUI Administration Fr_CA De MyIC Phone Fr_ca  De Greek El Hebrew He Hungarian Hu  Icelandic Italian Is It  Japanese Korean Hu It Ja Ko  Ko Latvian Lv Lithuanian Lt Norvegian No Polish PL Portuguese Pt Nb  Pl Pt  Portuguese (Brazil) Rumanian Pt_BR Ru  Russian Ru Slovak Sk Slovenian Sl Spanish Es Es  Spanish (Mexico) Es_MX Swedish Sv Sv Turkish Tr Tr Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 76/193 3.4 Software locks OmniPCX side The needs of software lock for OXE users having applicative rights on OpenTouch are almost the same as in case of OmniTouch 8400 ICS. For users distributed in a PBX network, following software locks are necessary OmniPCX side: Values of 116, 117, 119, 129, 309 and 166 locks should be equal to “e-CS Engine” (13) with a maximum value of 5000. Values of “CSTA_Bypass” (158) should be equal to 2 X “e-CS Engine” with a maximum value of 6000. Specific to OpenTouch are license 177 « SIP users » for the ‘SIP device’ declaration part of any MyIC Phone set and license 188 « SIP network links » for the SIP trunk between OXE and ESS. Note that hardware paramao 5 has to be set to ZERO for enabling network ; hence SIP interworking. OXE PBX locks eCC in PBX mode Only integrated mode is supported. « eCC integrated » license leads to following locks and provisioning: Lock label Lock number e-CS Engine 13 Centralized VPS 97 CSTA Bypass (*) 158 SIP Gateway 185 ECC Gateway 313 RSI eCC SP_RSI_agent_max remanent SIP Voice Mail Access 337 (*) CSTA_Bypass locks allow virtual Z sets monitoring. Quantity/Value calculated = 9999 500 1 2 2 calculated Set by Associated license UMA Associated license UMA Associated license Initrem UMA OXE PBX Locks for XML PBX Management service By-pass of 4635 and 4645 software locks: software locks 314 (4635) and 194 (4645) are bypassed on OmniPCX side if Messaging services licenses were bought for the Alcatel-Lucent OmniTouch 8400 ICS. Reminder: 46x5 voicemail box is not allowed on OTBE systems. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 77/193 3.5 Application compatibility (test done in validation) Official documentation Refer to official OpenTouch R1.3 feature list for the compatibility Here the test done Operating system tested OpenTouch R1.3 R1.3.000.043 Application tested My IC Desktop (IE must be installed on the PC) Windows XP Windows XP Pro / 32 bits Pro / 64 bits Windows Vista / 32 bits Windows Vista / 64bits Windows 7 / 32bits Windows 7 / 64bits OK Not tested OK Not tested OK OK Lotus Note 8.5.1, 8.5.2, 8.5.3 extensions OK Not tested OK Not tested OK Not tested Outlook 2010 extensions OK Not tested Not tested Not tested Sametime 8.5 OK Not tested OK Not tested OK OK MOC R2 OK Not tested OK Not tested OK OK LYNC 2010 OK Not tested OK Not tested OK OK Not tested Not tested Not tested not tested Not tested Not tested Not tested Not tested MyTeamwork Web MyPhone WEB MyAssistant WEB MyMessaging WEB RDS: My IC Desktop (IE must be installed on the PC) Citrix: My IC Desktop (IE must be installed on the PC) 8770 Client/Server OK according to browser OK according to browser OK according to browser OK according to browser Not tested Not tested Not tested Not tested OK according to browser OK according to browser OK according to browser OK according to browser OK in RDS OK according to browser OK according to browser OK according to browser OK according to browser Not tested Not tested Not tested Not tested OK OK Not tested Not tested Not tested Not tested Not tested Client Not tested Not tested Not tested Client Client Server Copyright © 2013 Alcatel-Lucent. All rights reserved Not tested OK OK Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Windows 2008 R2 / 64bits OK Server TC1798 Ed05 page 78/193 My IC PC (IE must be installed on the PC) Lotus 8.0 until 8.5.1 extensions Internet Explorer 7 Safari Chrome 15 Firefox 7 Firefox 3.6 Firefox 3.x Firefox 2 Internet Explorer 9 Internet Explorer 7 OpenTouch R1.2 / R1.3.000.043 Internet Explorer 8 (2) Internet browser tested OK OK OK N/A N/A N/A N/A OK OK N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Outlook 2003/7 extensions 6.5.1 N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Outlook 2010 extensions N/A N/A N/A N/A N/A N/A N/A N/A N/A N/A Sametime 8.5 N/A OK N/A N/A N/A N/A N/A N/A N/A N/A MOC R2 N/A OK N/A N/A N/A N/A N/A N/A N/A N/A LYNC 2010 N/A OK N/A N/A N/A N/A N/A N/A N/A N/A sharing viewer (not leader). sharing viewer (not leader). sharing viewer (not leader). sharing viewer (not leader). OK sharing viewer (not leader). MyTeamwork Web OK OK OK MyPhone WEB OK OK OK OK OK Not tested nc OK MyAssistant WEB OK OK OK OK OK Not tested Not tested OK MyMessaging WEB OK OK OK OK OK Not tested Not tested OK Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested Not tested OK OK OK OK OK RDS: My IC PC (IE must be installed on the PC) Citrix: My IC PC (IE must be installed on the PC) 8770 OK OK OK Not tested Not tested Not tested Not tested 3.6 Application Programming Interface (API) The objective is described below , we wait for additional info about doc to use, necessity or not to change something in the application using the API. The API present in ICS is partialy supported in OpenTouch First it does not concern OpenTouch user Second a reduce set of API is proposed for Standard user (having an Oxe device) The API list is described in OpenTouch 1.3 feature list Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 79/193 4 Installation procedures 4.1 General information The OpenTouch version R1.3.000.043 is composed of a full version When the OTMS/OTBE software is ordered with a server to Alcatel-Lucent, the version R1.3.000.043 is already installed on the server. The post installation needs to be completed. When the OTMS server is ordered directly to an HP reseller, the version R1.3.000.043 has to be installed from scratch, followed by the post installation. Note that OTBE is always distributed with a server supplied by Alcatel-Lucent. Detail procedure is described in the Installation manual, available on the Technical Knowledge Base at: https://www.technical-knowledge-base.com/km Select Product OpenTouch Business Edition or OpenTouch Multimedia Services Select menu Browse / Reference Book / Installation Manuals Warning In case of issue with hardware, you may need to update the BIOS/ROM firmware. Linux installation Use the last boot DVD version (5.8.100.xxx.x86_64) with Red Hat Enterprise 5 Update 8. ISO file  Check the MD5 checksum of each ISO/ZIP files. You can use the Linux command md5sum: md5sum filetocheck  It is not allowed to place the ISO file in the system partition (system partition is limited to 30 GB , it is reserved for system and will check it has still 5 GB free to run the update process). Either use USB storage or Network location or place ISO on /var/Backup/tmpd  It is not possible to mount an ISO file in the directory /media/cdrom on the server. You must mount iso on different directory. Here simple naming of mounting point: /media/OS /media/OT /media/OXE /media/8770 /media/TTS Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 80/193 DVD In case of installation on inactive partition (clean install), Boot DVD must not be mounted on the same mounting point as the OT DVD. Warning Check the Chapter 5 and Chapter 6 about setup recommendation and restriction, especially the remark about USB key / hard drive, as well as VNC not allowed for installation. 4.2 DNS External DNS Server:  Only external DNS is fully supported. A reverse Zone must be declared on the DNS Server with an entry corresponding to the OpenTouch Server and for OTBE an entry corresponding to the CPUA of embedded OXE. OpenTouch internal DNS Server for OT  Internal DNS is now available for OT 1.3 installation,  Internal DNS only record the FQDN of OT solution :Opentpouch, OmniVista 8770 and OmniPCXEnterprise  For MyIC Desktop, Windows setting for DNS will have to use OT DNS. DNS querry not resolved by internal OT DNS (and not in the DNS domain of OT) are relayed to external DNS.  Internal DNS preconisation in case Internal DNS installed and exisitng External DNS If you use the local DNS (the DNS server embedded in the OpenTouch), create a sub DNS domain : for example: ot.mycompany.com. you have also to configure the Forwarder 1 parameter (see below) with the customer DNS server address. The reasons of this configuration are • A DNS server has ownership of his domain (mycompany.com), and will not forward to external DNS a request to a server like mywebserver.company.com • OpenTouch internal DNS include only OpenTouch solution server: o Opentouch o 8770 o OmniPCX enterprise Hence a request to OpenTouch DNS for mywebserver.company.com will fail External fowarder DNS are used only for DNS request which are not in the subdomain authority of local DNS DNS setup and OpenTouch config file The DNS option is saved in bics.conf. during update on inactive partiton, the bics.conf is reused. Take care that it has the proper setting before trying to update OpenTouch Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 81/193 4.3 ALEDS: Alcatel-Lucent Enterprise Deployment solution 4.3.1 ALEDS: description This PC application can manage the fresh installation of the whole OpenTouch solution Product concetens are OTBE OTMS OXE-V, OTMS-V, 8770-V, external FLEX server, DCS VM The installation is based on BootPXE ALEDS will prepare a virtual machine ofdeployment This machine wait for each element to install to send it BOOT PXE request And will supply the version to install The version can be locally on drive reachable by the deployment machine or on a NFS share Example of deployment in an isolated LAN, where ALEDS PC hosqr the deployment VM and each deployment target use this PC as DHCP / BOOTPXE server Regarding virtualisatoin deployment ALEDS will generate OVF file (filedescriptor of the VM) of each element of the solution including the deployment machine 2. 3. 4. 5. 6. 7. Main steps procedure Put the Opentouch version on a NFS share The deployment machine will have path to the NFS share This OVF file has to be imported in VMWare Then on Vmware start first the deployment machine a Then start each VM, they will address the deployent machine to install their dedicated application version At the end of installation of the element you need to perform the postinstallation of the differne element of the solution Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 82/193 4.3.2 ALEDS 2.2.2: compatibility for VM deployment Component Green light Release compatible and tested OTBE OK OTMS OK OTBE-V NOK OTMS-V OK OT R1.3 OT R1.3.000.043 OXE-V NOK j2.603.10 OK since ALEDS 2.2.2 VM Flex OK but OT R1.3 OT R1.3.000.42 License not installed , copy it manually VM Esxi OK 4.1 and 5.1 4.1 for initial testing, but prefer 5.0/ 5.1 8770 OK Windows OK MS Office OK Professional plus 2010 ACS OK ACS 9_2_0b6386 ICS OK 6.7.100.000.f OT OT OT OT Remarks R1.3 R1.3.000.043 R1.3 R1.3.000.043 Not installed as single product, check the differnet componant of OTBE-V: OTMS-V, OXE-V and 8770-V 8770 R1.3 8770 R1.3.05.a Windows 7 ultimate and Windows 2008 Note: ALES 2.2.2 provide these fixes crms00429510 ALEDS : failed to install OXE J2.603.20 on ESXi 5.0 crms00429186 ALEDS 2.2.1: OXE installation through directory path is not working crms00427653 DCS installation : External Documentation Converter Server not completly installed in automatic, need to install it manually 4.3.3 ALEDS 2.2.2: additional feature for 8082 device update in lab 8082 must be in out of the box state, if used perfrom this command by SSH access $CTL erase $reset flash On ALEDS PC in the tools folder of ALEDS software, there are 2 configuration file ale-deploy-ict-cfg: to update if you need another admin password ale-deploy-ict-sip : no setting needed since we just want to update the Vhe not to provide SIP configuration Unzip the VHE binary inside a folder With ALED tools , TAB bootserver configure the IP address, mask, gateway, DNS server, … to fit your network TAB DNS, empty the list of reserved MAC and IP address TAB ixTouch give the path to the folder containing unzipped VHE binary Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 83/193 4.4 Omnivista 8770 update methodology Update of 8770 (the VM 8770 of OTBE): difference between iso and zip ISO DVD of 8770 software It is used by OTBE update wizzard (running on RedHat) to update internal 8770 VM Such feature require minimum version OTBE 1.1.000.060 ZIP of 8770 (with media.inf inside) software It is used by Windows OS to update 8770 directly in Windows session You will have to perform such update if you intend to install OTBE from scratch and reload a backup of OTBE in a previous version . 8770 version N cannot reload a backub done in version N-1. Inside 8770 windows VM, there is no ISO reader, and moreover trying to install using ISO file will lead to issue (microsoft installshield output an error “insert disk1”since it sees that the media source is changed from previous installation). The solution is to have the 8770 installation file directly available in the C: \ drive of 8770 Virtual Machine Unzip the ZIP file under C:\version8770, run serversetup.exe To save disk space, delete the version files, once installation is finished. 4.5 Installation (readme)  To check the consistency of your installation, the version readme provide information on the component and hotfix installed: [root@ice-beta-col Alcatel-Lucent]# cd /opt/Alcatel-Lucent [root@ice-beta-col Alcatel-Lucent]# more version.txt -----------------------------Product : OpenTouch Multimedia Services 1.3 Version : 1.3.000.043 -----------------------------platform Release : 1.3.000.041 management_framework Release : 8.3.000.031 ics Release : 7.3.000.041 sip_server Release : 8.3.000.041 voice_platform Release : 9.3.000.050 myic_desktop Release : 3.2.007.005 otc Release : 1.3.000.030 acs Release : 9.3.000.040 en-GB-Serena TTS Release : 4.0.12 fr-FR-Virginie TTS Release : 4.0.12 de-DE-Beate TTS Release : 4.0.12 en-US-Jennifer TTS Release : 4.0.10 pt-PT-Joana TTS Release : 4.5.00.00 faxServer Release : 6.6.0.16 ------------------------------------------------------------------------- Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 84/193 4.6 New installation 4.6.1 Main steps of OT R1.3.000.043 installation from scratch:  This operation is required for upgrade from OTMS/OTBE R1.0.1 upgrade from OTBE R1.1/R1.2 if you need the CCx feature in 8770 VM fresh installation of a server delivered without software  When receiving a server from Alcatel-Lucent, it is already loaded with version R1.3.000.043. Hence this installation from scratch can be skipped.  Operating system installation Install Redhat Enterprise on the physical server and prepare the system to install OpenTouch software. Boot on the Boot DVD and at the ‘boot:’ prompt, select the appropriate value, depending of the OpenTouch package to be installed (OTBE, OTMS). Do not change OS language it has to remain English.  OpenTouch software installation Install the OT core software, in case of OTBE, deploy the OXE and 8770 virtual machines Use /opt/Alcatel-Lucent/checkSystemLinux.sh command to check the operating system just installed. Launch the setup.bin in the ICE core DVD  Use Software Deployment Solution ALEDS 2.2.2 to simplify the installation: single action to prepare the installation and delivery, then auto-install of every component of the OpenTouch server. The ALEDS documentation is inculded in OpenTouch installation manual 4.6.2 Post installation (no factory server) For OTMS  After installation from scratch, launch the post installation Wizard For OTBE, OTBE-V, OTMS-V  Before OTBE post installation, the dongle must be plugged and associated license must be copied on the systems (OXE, OT, 8770). launch the post installation Wizard If you install/ reinstall the system : before launching post factory script of 8770, Windows VM opens without any account and you have to activate the windows license: use the virtual product key on windows license sticker and then at next windows boot choose ICE account to run postfactory.vbs under %temp%/postinstallation Warning 8770 postinstallation is a rehosting and takes 30 minutes. During 30 minimum, the windows login in 8770 VM will not appear (light blue screen). Be patient and wait until process is finished and iceuser login is proposed. Note that password alcatel1 has to be used if default icesuer password fails Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 85/193 4.6.3 Post installation (factory server)  When receiving server from factory, the windows OS is already activated and there is no need to run postfactory.vbs (located on 8770 under %temp%/postinstallation). Actually, the OTBE is able to change the 8770 network parameter on a server installed from factory.  Run post installation Wizard Warning 8770 postinstallation is a rehosting and takes 30 minutes. During 30 minimum, the windows login in 8770 VM will not appear (light blue screen). Be patient and wait until process is finished and iceuser login is proposed. Note that password alcatel1 has to be used if default icesuer password fails 4.7 New installation on virtual machine The OpenTouch solution can run on top of VMware 5.0 or 5.1, either the complete vSphere 5.x solution or the free ESXi 5.x hypervisor. Vmware 5.x qualification ensures the compatibility with all the hardware supported by VMware 5.x (server and blades, network interface cards, disk controller, mass storage …). OpenTouch Suite for MLE - Release Presentation - Virtualized offers 8AL020033239TCASA_6 January 2013 In-depth product insight Release Documentation Virtualisation with External flex server can only be setup for new installation: No update possible from OT using a internal flex server to OTBE-V or OTMS-V using an external flex serve The control mode is coded inside the DB backup and only the first post installation wizard is able to change the mode. But you can virtualize an existing OTMS by keeping the internal flex server It is expected that the BP or customer supplies the Virtualization infrastructure, any doc provided by Alcatel Lucent is only given as reference to help in discussion with Vmware administrator / expert Issue on Vmware management has to be reported to Vmware according to the Vmware license and support granted by Vmware distributor The hardware supported by Vmware is available on their website (note that you may have to download a supplier specific delivery of vmware to get the supplier drivers) http://www.vmware.com/resources/compatibility/search.php?lp=default 4.7.1 Documentation The installation requirement and steps is fully described in the OTMS installation manual Note that even if you install OTBE-V commercial, it is still an installation of OTMS (called OTMS-V) Refer to the VMware ESXi documentation for more information, see vmware web access Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 86/193 http://www.wmware.com/support/pubs/vs_pubs.html 4.7.2 Deployment topology  Rules a unique OTMS-V can be deployed per appliance Vmware ESXi when deployed, there are some restriction on the additional VM hosted : only an additional OXE and 8770 can be hosted on the same appliance Vmware ESXi compliancy with OXE R10.1.1 has been tested OK  Do not mix OTBE, OTBE-V, OTMS-V OTBE-V is only a commercial package; the real application deployed is OTMS-V, OXE-V, 8770-V.  Combining component deployment according to rules above 4.7.3 Licensing  OTMS-Hosted: released OK In such case the OTMS app is virtualised and a central external flex server is used for One or Several OTBE-V One or several OTMS-V The license file is used for several OTMS and does the differentiation between OTMS like this It contains: The dongle ID MAC of the OTMS virtual Machine (hence license need to create first OTMS VM) behavior changed in OT 1.3, the licnese do not use OTMS-V virtual MAC An OpenTouch ID called OTID Oxxxxx In addition, inside the OTMS-V, you have to copy the file alchostid.cfg which contains the OTID reference keep the default alcotuc.lic  OTBE-V or OTMS-V: with internal FLEX in OT=> this topology is not possible Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 87/193 4.7.4 Deployment Steps Short sum up of virtualisation deployment The virtualisation infrastructure should be already deployed in the customer environment To reproduce similar environment in a lab Install Vmware ESXi 5.0 Do the minimal setup at reboot Download VSphere management client form the installed Vmware ESXi server Once a virtualisation environment is present, the deployment consist in Creation of the VM Installation of the application in the VM using the console access of Sphere to the VM For OTBE-V configuration, install: The OXE-V (see: OXE-V) The 8770-V (see: 8770–V) The OTMS-V (see: OTMS-V) Optionally a document conversion server: see DCS-V(optional) In an OTMS-V configuration, install: The OTMS-V (see: OTMS-V) Optionally a document conversion server: see DCS-V(optional) Note for the license server FLEXLM If the license server is external: Install the license server virtual machine (an iso file containing the .ovf file is supplied.) There is no external management access to such flex server, the local console and tools has to be used for network setup and license file copy. During Post installation wizard of OTMS you can specify internal or external Flex Server (external only possible for new installation) 4.7.5 Advance management : SAN Media server is directly impacted by high SAN latency while running in debug mode. Thus following recommendations need to be enforce to guaranty the user experience in virtualized environment: Keep SAN latency below 30ms with peak up to 100ms Keep media server traces at standard level and ensure SAN latency is below 30ms if debug level is activated. Risk is to get voice cut as media server will not be able to manage stream in real time. SAN good practices for NFS Limit the number of VM per SAN module as each VM writing on a module is locking it. Good practice is to limit to 50 VM per module. Another track is to use datastore cluster with smaller volume, thus less concurrency on each volume and no volume locking effect. NFS optimization Net.TcpipHeapSize = 0 ( Reco = 32 ) NFS.MaxVolumes = 8 ( Reco = 256 ) Net.TcpipHeapMax = 64 ( Reco = 128 ) Dsik.QFullSampleSize = 0 ( Reco = 32 ) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 88/193 This requires a server reboot (without stopping VMs) 4.7.6 Advanced management: High Availability VSphere solution comes with defence mechanism to ensure a better availability of the system virtualized Here the list of such features: VMware vMotion  vMotion is a feature that allows to move a running virtual machine from one physical host to another one without stopping it. It is used in many scenarii and by a lot of high end cloud features (DRS …) and has to be supported. One typical use case is using vMotion to avoid downtime when upgrading a host (programmed HW or SW maintenance).  Of course VMware vMotion requires the datastore (where the VM image files are stored) is networked and accessible from all hosts. The support by OT 1.3 of VMotion is on following condition maintenance operation only no guaranty to keep communication using OT service during vMotion. to do out of traffic need an external flex server , and such external flex cannot be moved OXE standby and 8770 support vMotion without above restriction. VMware DRS (Distributed Resource Scheduler)  VMware DRS works with VMotion to provide automated resource optimization and virtual machine placement and migration, to help align available resources with pre-defined business priorities while maximizing hardware utilization. A typical use case is the automatic choice of the host in a cluster to deploy a virtual machine. When deploying a VM, there is no need to manually assign the host, DRS automatically select it according to affinity rules (VM-VM, VM-host) and hosts load. Automatic mode is not supported as it moves VM continuously for an optimal resource usage. Partially automatic mode (automatic initial placement, recommendation only for load balancing) may be used if it is possible to create rules that makes a VM always alone in its host. If physical hosts are homogeneous, it is possible to assign a VM all the physical resource of one kind of host. Then the VM will only be placed on totally free hosts. But if the cluster is composed of various hosts writing such a rule may be impossible. DRS affinity rules can also to be used to force a VM to run alone in a host. Manual mode (recommendation for both initial placement and load balancing) is useful at the same conditions as the partially automatic mode.  Of course VMware HA requires the datastore (where the VM image files are stored) is networked and accessible from all hosts. VMware storage vMotion  VMware Storage VMotion is a component of VMware vSphere that provides an intuitive interface for live migration of virtual machine disk files within and across storage arrays with no downtime or disruption in service.  Limitations are the same as the vMotion ones. It’s a nice to have feature Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 89/193 VMware HA  VMware HA leverages multiple ESXi hosts configured as a cluster to provide rapid recovery from outages and cost-effective high availability for applications running in virtual machines.  VMware HA protects application availability in the following ways: It protects against a server failure by restarting the virtual machines on other hosts within the cluster. It protects against application failure by continuously monitoring a virtual machine and resetting it in the event that a failure is detected.  VMware HA is used in datacenter to offer at moderate cost cold redundancy for most (if not all) virtualized application. Some physical spare hosts are installed in the cluster, but not used by virtual machines under normal circumstances. These hosts are used by VMware HA only when needed. Of course VMware HA requires the datastore (where the VM image files are stored) is networked and accessible from all hosts. It is also advised to put in place NIC teaming (and router duplication) for both applicative and datastore traffic and to use redundant VM image file access. VMware HA is a complement to ALU HA features (in OXE, and in OTMS). It shouldn’t require any SW modification in OXE and OTMS, but QA tests are needed to check the full compatibility.  Guidelines is currently under work to help configure VMware HA (host-VM affinity, delay when restarting a VM …) and to list HW requirements (Flexera VM uses a USB device, all hosts running it have to be the same, with the dongle plugged in the same physical USB port). The support by OT 1.3 of VmWare HA is on following condition external flex server support VMWare HA (2 dongle needed) OXE/OTMS/8770 support VMWare HA provided OTMS has a external flex server (sinceby restarting OTMS on an host without a dongle is not usefull and no double dongle possible) All communication info status (forward, call log …) is kept after HA, but not the one that were not yet stored in the DB There is a delay of around 15 mn with no service from OT, the time to restart all services VMware Fault Tolerance  vSphere HA provides a base level of protection for your virtual machines by restarting virtual machines in the event of a host failure.  vSphere Fault Tolerance provides a higher level of availability, allowing users to protect any virtual machine from a host failure with no loss of data, transactions, or connections.  Fault Tolerance provides continuous availability by ensuring that the states of the Primary and Secondary VMs are identical at any point in the instruction execution of the virtual machine. This is done using the VMware vLockstep technology on the ESXi host platform. vLockstep accomplishes this by having the Primary and Secondary VMs execute identical sequences of x86 instructions. The Primary VM captures all inputs and events (from the processor to virtual I/O devices) and replays them on the Secondary VM. The Secondary VM executes the same series of instructions as the Primary VM, while only a single virtual machine image (the Primary VM) executes the workload.  But VMware FT has a lot of limitation. Paravirtualized drivers cannot be used, USB devices like a dongle cannot be used and only VM with one vCPU (two in a near future) are supported with a some impacts on performance side. OpenTouch R1.3 is not compatible with VMware FT. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 90/193 4.8 BEFORE Update OTMS/OTBE R1.1/R1.2 to OTMS/OTBE R1.3  Ensure that backup operation of OpenTouch R1.1/R1.2 is working properly (including ACS part) Example of bad operation /logs/backup/backup_traces.log and /logs/backup/bru_start.log and look for any occurrence of this error: Save : ACS Data WARNING ! /opt/Alcatel-Lucent/serviceability/backup/bin/preBackupAcs.sh failed : exit code = 1 check To check you have the issue on active and inactive partition ll /usr/local/pgsql/bin/pg_dump ls: /usr/local/pgsql/bin/pg_dump: No such file or directory mount /mnt/inactive_partition/ ll /mnt/inactive_partition/usr/local/pgsql/bin/pg_dump ls: /usr/local/pgsql/bin/pg_dump: No such file or directory umount /mnt/inactive_partition/ solution Login as root, or sudo su to root mkdir -p /usr/local/pgsql/bin/ cd /usr/local/pgsql/bin/ ln -s /usr/bin/createdb ln -s /usr/bin/dropdb ln -s /usr/bin/pg_dump ln -s /usr/bin/psql ln -s /usr/bin/vacuumdb mount /mnt/inactive_partition/ cd /mnt/inactive_partition execute the following commands mkdir -p /usr/local/pgsql/bin/ cd /usr/local/pgsql/bin/ ln -s /usr/bin/createdb ln -s /usr/bin/dropdb ln -s /usr/bin/pg_dump ln -s /usr/bin/psql ln -s /usr/bin/vacuumdb umount /mnt/inactive_partition/ 4.9 BEFORE Update OTBE R1.1/R1.2 to OTMS/OTBE R1.3: 8770 update In additon to previous chapter on concsitency check of ACS backup The 8770 update capability by OpenTouch host has to be checked and corrected Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 91/193 8770 : how to check and solve SSH from OT to 8770 VM ssh [email protected] set |grep NMC_HOME where XXX.YYY.ZZZ.TTT has to be replaced by 8770 IP address It should return NMC_HOME=”C:\8770” If it fails check these 3 points Windows Firewall should allow port 22 connection from host Windows service Openssh SSHD (copssh) should be running SSH key stored should be correct, you can update the allowed host (SSH key) CopSSH key update From the OT host, using root account, you must execute management_cmd updatekey (enter password of ice window account) which will copy the OT root public key in C:\Program Files (x86)\ICW\home\ice\.ssh\authorized_keys 4.10 Update from OTMS R1.1/R1.2 to OTMS R1.3.000.043  Supported mode for upgrade OTMS R1.1/1.2 to OTMS R1.3.000.043 is Install OTMS R1.3 on inactive partition with CLEAN install option Due to change in OT R1.3 license version ID, the license has to be updated from OT 1.1/1.2 to OT 1.3. The update wizzard will allways ask for new license file, provide this new license at this step during install FAX service is not available and must be restarted after.  Read following Technical communication for additional info on the usage of inactive partition TC1704 3 OpenTouch OT_SW Version upgrade on inactive-partition and maintenance Preparation for OTMS update  Check before update that all features are working properly  Ensure that backup operation of OpenTouch R1.1/R1.2 is working properly (including ACS part) as explained in previous chapter  NO Need to remove Webinar VM (if one is deployed in OT 1.1), restore and upgrade operation in OT 1.3 delete it automatically  Start first to update 8770 external server form 8770 R1.1 to R1.3.05.00a  In 8770 windows session run serversetup.exe from the source 8770 1.3.05.00a Collect this file and DVD Get ACTIS file for OT 1.3 license The .ice license filename has to be different from the OT 1.2 license file ot1.3.000.043.iso bootdvd.5.8.xxx.x86_64.iso TTS DVD Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 92/193 Recommendation for files copy and system access  Do not copy version files (ISO …) on system partition because System partition is dedicated to the system By design , the system partiton has enough space for runing the system. It has not a spare space for storing version files. We recommend for the case of installation using file avaialble on the server either to use usb disk or copy iso file on a partition with large space. exemple, copy iso file on /var/backup/tmpd  It’s not possible to mount an ISO file in the directory /media/cdrom on the server. You must mount it to another directory.  Do not use VNC access (during the update, the MyTeamwork component will close the VNC port) OTMS update procedure 1. Log on as root. Use this command to get full root environment su – 2. Start an X environment startx Push the new .ice license for OT R1.3 to /var/data/licenses 3. Mount DVD or use physical DVD Mount the DVD ot1.3.000.043.iso Mount the BOOT bootdvd.5.8.xxx.x86_64.iso 4. Launch the setup.bin from the DVD ot1.3.000.043.iso 5. Select INACTIVE partition and CLEAN install option 6. Supply the new OT R1.3 licenses when requested 7. Supply the Boot DVD and TTS DVD, when requested 8. Switch partition switshover.sh –datacopy 9. Check the log file for end of Data migration 10. Apply OT Hotfix if supplied 11. Restart OT services service iced start External component update (note 1 for order of porcessing) update to J2.603.20i if not yet done, using PC installer, the Front End OXE node and any OXE node having some MyIC Phone attached, update the MyIC Phone to R260.1.12.2 + change SIP Profile for SIP Profile R260 update the Deskphone 8002/12 to R100.2.32.1 update the Deskphone 4008/18EE to 2.11.92 update MyIC BlackBerry to 4.3.0.4 if not yet done (deploy it using BES or BB manager) update MyIC Android to 4.3-2.0.31.4 if not yet done (deploy it using google play) Note and other recommendation  After update Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 93/193 Check in the file /opt/Alcatel-Lucent/version.txt that the version is correct (it must not contains Installation not completed) Restart FAX Restore ACS customized prompt Check that all features are still working properly  Note 1: There is some order in OTMS solution update First update 8770 to R1.3 Then OTMS + Fax data restore (note 2) Then OXE, Then MyIC Phone and Mobile 4.11 Update from OTBE R1.1/R1.2 to OTBE R1.3.000.043  Supported mode for upgrade OTBE R1.1/R1.2 to OT R1.3.000.043 is Install OT R1.3 on inactive partition with CLEAN install option Due to change in OT R1.3 license version ID, the license has to be copied before update OT 1.1 to OT 1.3 (this is done now during the update setup) during update, FAX service is not available and must be restarted after siwtchover.  Use following Technical communication for additional info on the usage of inactive partition TC1704 3 OpenTouch OT_SW Version upgrade on inactive-partition and maintenance Preparation  Check before update that all features are working properly  Ensure that backup operation of OpenTouch R1.1/R1.2 is working properly (including ACS part) as explained in previous chapter  NO Need to remove Webinar VM (if one is deployed in OT 1.1), restore and upgrade operation in OT 1.3 delete it automatically  Check and solve SSH access from OT Host toward 8770 VM as explained in 4.9 BEFORE Update OTBE R1.1/R1.2 to OTMS/OTBE R1.3: 8770 update Collect this file and DVD Get ACTIS file for OT 1.3 license The .ice license filename has to be differnet from the OT 1.2 license file ot1.3.000.043.iso bootdvd.5.8.xxx.x86_64.iso TTS DVD 8770.1.3.05.00a_xxx.iso bics_OXE-j2.603.20i.iso Recommendation for files copy and system access !!! DO NOT COPY ISO FILE ON SYSTEM PARTITION!!! Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 94/193 copy iso on a partition with enough space and in a directory not cleared automatically create and use /var/backup/tmpd Do not use VNC access (during the update, the MyTeamwork component will close the VNC port) It’s not possible to mount an ISO file in the directory /media/cdrom on the server. You must mount it to another directory. OTBE update Procedure 1. Log on as root. Use this command to get full root environment su 2. Start an X environment Startx Push the new .ice license for OT R1.3 to /var/data/licenses Mount the DVD in different path or use physical DVD Mount the OT ot1.3.000.043.iso Mount the BOOT bootdvd.5.8.xxx.x86_64.iso Mount the 8770 8770.1.3.05.05a_xxx.iso Mount the OXE bics_OXE-j2.603.20i.iso 3. Launch the setup.bin from the DVD ot1.3.000.043.iso 4. Select INACTIVE(2) partition and CLEAN install option 5. Supply the new OT R1.3 licenses when requested 6. Supply the ISO path to Boot ISO , TTS ISO, 8770 ISO and bics-oxe ISO when requested 7. Switch partition switshover.sh –datacopy 8. Check the log file for end of Data migration 9. Apply OT Hotfix if supplied 10. Restart OT services service iced start External component update update to J2603.20i using PC installer the PCS OXE, the duplicated CPU, and any OXE node having some MyIC Phone attached, update if there is one , the central external 8770, to 1.3.05.00a update the MyIC Phone to R260.1.12.2 + specify SIP Profile R260 update the Deskphone 8002/12 to R100.2.32.1 update the Deskphone 4008/18EE to 2.11.92 update MyIC BlackBerry to 4.3.4 if not yet done (deploy it using BES or manually via BB manager) update MyIC Android 4.3-2.0.31.4 if not yet done (deploy it using google play) Note and other recommendation  After update Check in the file /opt/Alcatel-Lucent/version.txt that the version is correct (it must not contains Installation not completed) Check that the OXE has been updated. It could failed especially if the OXE has no version on the inactive partition.(crms00406941) Restart FAX Restore ACS customized prompt Check that all features are still working properly  Note 1: There is some order in OTBE solution update First update PCS Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 95/193 Then OTBE + Fax data restore (see note 2) Then duplicated OXE Then MyIC Phone and Mobile  Handling OTBE Duplicated CPU and Passive Communication Server (PCS) CPU PCS CPU has to be updated first to the final targeted version of OmniPCX Enterprise, then you can update OTBE In case of Duplicated CPU o Do a bascul to switch to Duplicated CPU as main CPU o Update OTBE (during update only service of OXE duplicated CPU are available) o Stop TEL on OXE CPU of OTBE o Update Duplicated CPU, at reboot the OXE component are updated o Run TEL on OXE CPU of OTBE o Do a mastercopy on OXE CPU of OTBE to align it with duplicated CPU last changes o Do a bascul if you need to put embedded OTBE CPU as main CPU  Following smooth upgrade Check OXE version embedded in OTBE (if incorrect use OXE tools to update it) Check autostart Check /opt/Alcatel-Lucent/version.txt Check end of migration logs Restart server to ensure proper start-up of all services 4.12 Upgrade from OpenTouch R1.x to R1.3 with server reinstallation This is the only upgrade mode supported for OT R1.0 The upgrade is based on 1. Update of 8770 to 8770 R1.x to R1.3 using 8770 serversetup.exe 2. backup OT R1.x 3. install OT R1.3 from scratch 4. restore backup 5. Apply OT Hotfix External component update update to J2.603.20i using PC installer the PCS OXE, the duplicated CPU, and any OXE node having some MyIC Phone attached, update, if there is one, the central external 8770 to 8770 1.3.05.00a update the MyIC Phone to R260.1.12.2 + specify SIP Profile R260 update the Deskphone 8002/12 to R100.2.32.1 update the Deskphone 4008/18EE to 2.11.92 update MyIC BlackBerry to 4.3.8.4 if not yet done (deploy it using BES or manually via BB manager) update MyIC Android 4.1-2.0.31.4 if not yet done (deploy it using Goggle Play) Suhc process is described in the installationmanual in chapter 15 Upgrade for the detail process, the Technical Communication is available TC1799 1 OpenTouch – Upgrade R1.x to R1.3 with server reinstallation Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 96/193 4.12.1 ACS Patches  There is no new ACS patch  But in case of upgrade from OpenTouch R1.x to OT R1.3 You may experience continuous pop up on starting MyTeamwork client or MyIC desktop This pop is about buddy list / avatar ….  To get rid of such pop up Clears Internet Explorer cookies And Reinstall ACS application if still pop up occurs Reinstallation of ACS , process 1. Launch OT WebAdmin from 8770 2. Access to ACS admin: you can upgrade ACS 3. Select the current version of ACS : 6509 for OT 1.3.000.043 Condition The file eiab5.tar.gz.rel_9_2_0b6509 under /var/backup/acs_tar/ must be present 4.13 Migration Procedures are described in the installation manual, available on the Technical Knowledge Base at: https://www.technical-knowledge-base.com/km Select Product OpenTouch Business Edition or OpenTouch Multimedia Services Select menu Browse / Reference Book / Installation Manuals Section: Migration. Three main migration procedures, from a technical point of view, are taken into account by OpenTouch R1.3:  Migration from OmniPCX Enterprise to OTBE R1.3 This migration is not under PCS control, you just need to restore OXE data in the OXE VM and to check/update OXE settings for OpenTouch interoperability Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 97/193  Migration from BiCS R2.2/R2.3 to OTBE R1.3.000.043 The ACS part is not taken into account in this migration In case of change of the server hardware, if the first server is still in production you have to order a second dongle to install OTBE and import configuration data in OTBE Remove 4645 user mailbox and create VoiceMail box in OTBE  Migration from ICS R6.7 to OTMS R1.3 The ACS part is not taken into account in this migration 4.14 OpenTouch R1.3.000.042 Critic restriction and Hotfix installation OXE embeded in OTBE 1.3.000.042 has 2 critical restriction  uptdate to j2.603.20.g : cannot add IPTouch in following case Case of fresh install of OTBE 1.2 : empty database If no Iptouch managed yet and update to OTBE 1.3 with j2.603.20.g is done, impossible to add IPTouch Workaround = after OTBE 1.2 fresh install, make sure at least one iptouch is created  j2.603.20.g/h. crms00413114 DTMF to public trunk (auto DTMF or via prefixe on OXE set) OXE patch J2.603.20i: This oxe version correct the issue: Use PC installer to install this OXE dynamic patch 4.15 OpenTouch R1.3.000.043 Hotfix installation and manual correction OT hotfix: No Hotfix available yet. OT script to apply to correct configuration  Notification email : SMTP notification doesn't work crms00424437 the following workaround has to be done: su find /opt/Alcatel-Lucent/platform/postfix/ -group postfix -exec chgrp htgroup {} \; usermod -g htgroup postfix service scorpiod restart Webinar access right and live operation check  Take care to give all right on /slides so Webinar VM can access to document needed to be converted from DOC/EXCEL to Picture chmod –R 777 /var/data/slides/  crms00403184: After an installation from scratch and database restore, external ACS doc converter is no more working: need to save configuration again: In the ACS administration >configuration > advanced settings > Configure Access to a Remote Document Conversion VM menu, click Save of configuration again. 8770 new profile to add As of OT R1.3 there are 2 profile type for OT user, for ICM user fro OXE user Take care to have both and if not to create a new OT user profile, with user type = ACU_OXE 8770 patches Copy the .ace files provided for 8770 patches under /8770/install/patches Then run /8770/instal/patchinstaller.exe Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 98/193 5 Server post installation check and operation 5.1 Global overview of post installation action Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 99/193 5.2 OpenTouch settings 5.2.1 TTS / TUI language Configuration: Launch the OpenTouch setup to select new TTS installation Use 8770 to Configure TTS System services/Applications/Telephony/Vocal Applications/TUI Language The default TTS language is English. 8770 Configuration application Tab OT OT server NAME - System services - Applicaition - Telephony - Vocal application - TUI language Search option Tab OT Language code Fr-FR En-GB TTS not supported TTS installed Prompt default [x] [x] [x] [x] Prompt default TTS default [x] [x] System TUI language [x] In an OpenTouch system, the TTS must be administered. This means that installation of TTS languages is not sufficient: it is also necessary to specify the system which TTS are really installed and useable. Check the box of TTS really installed in this grid. TTS for EN/FR/GE are unused now in OT 1.3 (if no automated attendant or ice email reading) Update Users configuration with new TUI in User/General tab/TUI Language 5.2.2 Single Sign on authentication through Kerberos  Refer to system Documentation to set it up (xml file to update manually) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 100/193 5.3 OmniPCX Enterprise settings 5.3.1 OXE External voicemail  OmniPCX enterprise user can benefit of OpenTouch local storage voice mail. To get the voicemail new message notification, check the option “subscription on registration” This option is available as from OXE R10.0 J1.410.37, and has to be set only on the External voice Mail dedicated to OXE user. mgr path: Application > External Voice Mail ┌─Review/Modify: External Voice Mail───────────────────────────────────────────┐ │ │ │ Node Number (reserved) : 699 │ │ Instance (reserved) : 1 │ │ Voice Mail Dir.No. : 67133 │ │ │ │ Sub Type + Private │ │ Directory Name : LS_Voicemail_OXE │ │ Connection COS : 0 │ │ Public Network COS : 2 │ │ Entity Number : 1 │ │ Cost Center ID : 255 │ │ Charging COS + Justified │ │ URL UserName : 67133 │ │ URL Domain : oxedomain │ │ … │ │ External Gateway Number : -1 │ │ Subscription on registration + True │ └──────────────────────────────────────────────────────────────────────────────┘ 5.3.2 PRACK configuration  Check the External SIP gateway parameter for PRACK, 100REL, SIP in 18x mgr path: SIP > SIP Ext Gateway: ┌─Review/Modify: SIP Ext Gateway───────────────────────────────────────────────┐ │ │ │ Node Number (reserved) : 699 │ │ Instance (reserved) : 1 │ │ SIP External Gateway ID : 1 │ │ │ │ Gateway Name : To_ICE │ │ SIP Remote domain : OpenTouchFQDN │ │ … │ │ SDP in 18x : False │ │ … │ │ Dynamic Payload type for DTMF : 97 │ │ 100 REL for Outbound Calls + Supported │ │ 100 REL for Incoming Calls + Not Requested │ │ Gateway type + ICE type │ └──────────────────────────────────────────────────────────────────────────────┘ 5.3.3 CCBS timer for CCBS  The timer 389 must be set to 150 (100ms) (External services/Trunk category) on all the node of the network. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 101/193 5.4 OpenTouch user and device creation Follow the official documentation to create users and devices A technical communication gives some sample management TC1520 2 User management with the Unified User Management application For MASS provisioning, this is described also in 8770 manual The technical communication gives some sample management TC1521 3 OpenTouch mass users and devices import with UUM and DM 5.5 MyIC Phone setup 5.5.1 MyIC Phone hardware and compatibility matrix  As from July 2nd 2012, a new MyIC Phone 8082-v2 hardware is introduced The catalogues references are 3MG27036AA MyIC Phone 8082-v2 3MG27001AA MyIC Phone 8082-v1 (previous hardware)  The terminal end user features are quite the same for both kind of hardware. Differences: no Video support on MyIC Phone 8082-v1.  The terminal end user accessories are different. MyIC Phone 8082-v2 adds the support of following optional accessories 3MG27032AA 3MG27006AA 3MG27006AR 3MG27006RW Wired handset (wide band capability) 4x External Power Adaptor 48V Europe (when no PoE present) 4x External Power Adaptor 48V Argentina (when no PoE present) 4x External Power Adaptor 48V other countries (when no PoE present)  Reminder The 3MG27021AA Bluetooth has not WideBand capability. It is provided by default within the box of MyIC Phone 8082-Vx Hardware.  MyIC Phone 8082-v2 initial sound volume may be low, remind end user to update volume. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 102/193 Compatibility matrix MyIC Phone version OpenTouch R1.0 R200 1.29.x MyIC Phone 8082 v1 R200 1.30.x R200 1.34.x / 1.35.x OpenTouch R1.0.1 1.11.0 OpenTouch R1.2.000.054 OpenTouch R1.2.0.055 R1.3 MyIC Phone 8082 v1 v2(video) MyIC v1 MyIC v1 MyIC Phone 8082 v1 MyIC Phone 8082 v1 v2 R250 1.8.x / 1.10.x / 1.11.x R260 1.10.4 R260 1.12.x OpenTouch R1.1 MyIC Phone 8082 v1 v2 / Phone 8082 v2(video) Phone 8082 v2(video) * R260 1.11.0 / 1.12.x requires the minimum version OT R1.2.000.055 to be installed first before installing R260 1.11.0 / 1.12.x 5.5.2 MyIC Phone Deployment DNS / DHCP or Static IP  Configure DNS  Decide if deployment is done using DHCP (OXE or External) or using Static IP Configure DHCP Or Record a file with IP allocation for each Device Working with self signed certificates  Use following manuals / chapter System documentation > Security > Certificate Management  The certificate must be signed on the MyIC Phone 8082 dedicated to CTL signature Declare the signing set in WBM Export CTL on USE from WBM, Sign the certificate on the signing set, Export on USB the certificate Import it back in WBM CTL signature Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved CTL distribution (case of self signed certificate) TC1798 Ed05 page 103/193 PKI : Working with certificates produced by certificate authority  WBM limitation for Certificate Signing Request To generate the Certificate Signing Request on OpenTouch use directly the WebAdmin out of 8770 Compliant internet browsers for CSR are FireFox Internet Explorer with this Hotfix KB323308 (VM 8770 1.1 has now this Microsoft fix crms00377942) Template preparation  Use following manuals / chapter Administrator Manual > User Creation and Administration Configuring profiles : OXE / OT profil for OT user, OT profil for OXE user / Voicemail User / device deployment (one by one)  Use following manuals / chapter 8082 MyIC Phone Installation and Configuration on OmniVista 8770  Main steps are - Declaring the user in the 8770 Users application - Add to the user the 8082 My IC Phone set as SIP device if device is not in minimum version R250 1.8.4, With MAC address if device is in minimum version R250 1.8.4, with or without MAC address depending on your choice of deployment - Refine 8082 My IC Phone SIP device parameters - Plug the device Users / devices Mass Provisioning  Use following manuals / chapter Administrator Manual > User Creation and Administration Configuring users via mass provisioning Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 104/193 5.5.3 MyIC Phone 8082 Deployment without MAC address Management Tools:  8770 User application  8770 Configuration to create template/profile  8770 DM to update binaries Condition required using this deployment  8770 User application OXE profile created in OXE (using upper case only for profile name, entity 1 must be present) OXE profile should have this parameter "Use profile with auto. recognition" configuration OT profile created in OT configuration 8770 synchronization of OXE and OT to see the OXE and OT Profile in 8770 User application  OpenTouch system Keep deployment of MyIC Phone in HTTPS  MyIC Phone initial minimum version is R250 1.008.4 Check before trying this deployment mode if MyIC Phone current version is R250 1.008.4 or upper version Usage:  8770 User application Create a user (tag is has type OpenTouch user) Associate a new device for this user Fill up directory number of device and/or specific authentication key/password Restriction:  8770 User application Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 105/193 The order of creation: User First. That means User application does not support create a device without user link (free device), User application does not support deleting a device User/device list may be updated in real time, you must do full synchronization if data is inconsistent with 8770 configuration Devices under the user may not be displayed, do full synchronization or create again. User/device entries cannot be consulted, close 8770 User application and open it again Missing "Reset MAC address" field for the device deployed by MAC address, you have to do such operation via 8770 configuration  8770 Configuration Reset MAC for a device, you must fill up manually the authentication key and password again  Common issue VHE will get into DM survival mode in case of authentication failed or to a free device, phone will register to previous OT user with previous configuration files You must enter authentication password on VHE otherwise VHE won't send request message to OT Device with MAC not set are displayed as blank entry when you select it from device list (for example: you associate a device to user), you can fill up "Comment" attribute to help selection Missing "MAC Address" field in device attributes, you reset MAC for a device, and you can't change you deployment mode to setup again MAC address field in an already created device Note although User application is recommended to memorize the template used at the creation, the creation of users, devices and their association is also possible from the 8770 configuration application  8770 Configuration application Create a new device, fill up directory number and/or specific authentication key/password Create a user and associate it's device 5.5.4 MyIC Phones 8082 deployment using OXE DHCP DHCP mode  When MyIC Phones are declared in dynamic mode with the DHCP server of OXE, a class has to be created on OXE DHCP server for MyIC Phone: +-Consult/Modify: Classes------------------------------------------------------+ ¦ ¦ ¦ Node Number (reserved) : 2804 ¦ ¦ DHCP configuration : 1 ¦ ¦ Name : ICTouch ¦ ¦ ¦ ¦ Vendor id : alcatel.ictouch.0 ¦ ¦ TFTP server address : 135.117.104.101 ¦ ¦ Default lease time (mn) : 360 ¦ ¦ Max lease time (mn) : 720 ¦ ¦ Configuration file : --------------------------------------- ¦ ¦ ¦ +------------------------------------------------------------------------------+ With this configuration, DM server IP address is provided by TFTP filed (option 66 next server) DM path not provided, the 8002-8012 uses HTTPS protocol and default DM path value /dmictouch/. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 106/193 5.5.5 MyIC Phones 8082 mass upgrade: 100 max At server side, the total number of simultaneous request for a binary/application update of MyIC Phone is limited to 190 (crms00334528). Hence, to upgrade large number of MyIC Phones, the upgrade should be done by group of 100 MyIC Phones. Define from 8770 several scheduled upgrade with following recommendation MAX number of device included = 100 Delay between each upgrade: 1 hours Example: 250 MyIC Phone to update from R250 1.8.4 to R260 1.12.2 Step 1: create a MyIC Phone deployment package form 8770 DM: R1.12.2_Group1 Step 2: update the package and add inside the first 100 MyIC Phone Step 3: deploy the package at 20H00 Step 4: create again MyIC Phone deployment package form 8770 DM: R1.12.2_Group2 Step 5: update the package and add inside the second group of 100 MyIC Phone Step 6: deploy the package at 21H00 Step 7: create again MyIC Phone deployment package form 8770 DM: R1.12.2_Group3 Step 8: update the package and add inside the last group of 50 MyIC Phone Step 9: deploy the package at 22H00 To get the group of 100, in case your device numbers are in the range 88500 to 88800 You can filter by directory number and select all lines in the grid 5.5.6 Survivability on PCS New in OpenTouch R1.2 In OT R1.0/R1.0.1, the preferred initial SIP server of MyIC Phone was OpenTouch server In OT R1.2, the preferred initial SIP server of MyIC Phone is the PCS. This way when MyIC Phone is on PCS survivability, in case of device reboot it will again try to access the PCS. Setup A technical communication has been published on this setup Here the basic  PCS declaration: you need to define an external SIP Proxy Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 107/193  MyIC Phone setup: Note In case PCS remains active and only reboot at a schedule when the OXE is again reachable  it is better to use External SIP Proxy Policy = Persistent In case PCS reboot when OXE is again reachable  keep Transient 5.5.7 MyIC Phone / 8002-8012 Survivability set-up rule In case of No redundancy or local redundancy, the devices will be automatically configured as the table below Attributes Type of OXE redundancy No redundancy Local redundancy SIPGroupDomainName Global FQDN Global FQDN SIPServerAddress 1 Local main role IP address Local main role IP address (corresponds to the physical IP address) SIPServerAddress 2 - Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved - TC1798 Ed05 page 108/193 In case of Spacial redundancy AND if the parameter “Internal name resolver attached” is checked and if the parameter “The DNS server is remote” is checked, the devices will be automatically configured as the table below: Attributes Type of OXE redundancy Spatial redundancy SIPGroupDomainName Global FQDN SIPServerAddress 1 Local main role IP address SIPServerAddress 2 -Twin main role IP address 5.5.8 Memory consumption check MyIC phone perform a check every day at 2:00 AM. If memory needs to be clean, a reset will happens. This behaviour is controlled by 2 parameters from the configuration (activated by default since OT R1.0.1) The MyIC Phone configuration file is setup like this. 5.5.9 MyIC Phone applications Contact telephonic presence  Refer to the administration documentation manual to set it up  Quick setup overview On OT configuration, enable for each use the Telephonic presence availability 8770 DEVICES application Tab devices NMC - Network - Subnetowrk - OT node - DeviceNumber UserNAME Search option Rights .. Telephony presence availability [x]  End user action When adding a favorite from MyIC Phone, it will create the end user MyFavorites group on the OpenTouch server. Manager - Assistant  Refer to the system documentation manual to set it up Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 109/193  Quick setup overview On OT configuration, Select System services > Application > Telephony > MAlink Create a new link and specify the Manager and Assistant login using the pick list. Check the option “Enable User presence” on each Manager/Assistant MyIC Phone device MyIC Phone 8082 switching from Homepage to Standard  End user can select dynamically the current homepage display Standard with icon (activated by pressing on home button) Preview with application: Contact / History / Manager-Assistant (activated by pressing the Advanced button) MyIC Phone PC Synchronizer  Refer to MyIC Phone User Manual to set it up  Quick setup overview On User PC, install MyIC Phone PC synchronizer and refine settings (outlook contact folder) On MyIC Phone, Select Settings > Application > Synchronization Specify the user PC FQDN Specify the availability of sync button on home page At first launch a pop up will appear on the MyIC Phone and the user PC with the pairing PIN code. on MyIC Phone 8082: programmable key On MyIC Phone, Select Settings > Application > HomePage Press HomePage label Add a key Phone Contact without picture Contact with picture Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 110/193 5.6 8002 - 8012 5.6.1 8002 - 8012 Deployment as OpenTouch device Status 8002/8012 is released starting with OT R1.2.000.055 (with such version, the configuration path is /dmictouch, which is compliant with OXE DHCP) Minimum released version is 2.30.0 Deployment guide DHCP  When 8002-8012 are declared in dynamic mode with the DHCP server of OXE, a class has to be created on OXE DHCP server for 8002-8012: +-Consult/Modify: Classes------------------------------------------------------+ ¦ ¦ ¦ Node Number (reserved) : 2804 ¦ ¦ DHCP configuration : 1 ¦ ¦ Name : VLE ¦ ¦ Vendor id : alcatel.ictouch.0 ¦ TFTP server address : 135.117.104.101 <= OpenTouch IP Address ¦ ¦ Default lease time (mn) : 360 ¦ ¦ Max lease time (mn) : 720 ¦ ¦ Configuration file : --------------------------------------- ¦ +------------------------------------------------------------------------------+ ¦ With this configuration, DM server IP address is provided by TFTP filed (option 66 next server) DM path is not provided, the 8002-8012 uses HTTPS protocol and default DM path value /dmictouch Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 111/193 5.7 4008-4018 EE 5.7.1 4008-4018 EE Deployment as OpenTouch device Type of hardware supported  Only the 4008/4018 Extended Edition supports SIP protocol DHCP  When 4008EE/4018EE are declared in dynamic mode with the DHCP server of OXE, a class has to be created on OXE DHCP server for 4008/4018. Take care that 4008/18 minimum version 2.11.68 should be already present in the device to be compliant with OXE DHCP +-Consult/Modify: Classes------------------------------------------------------+ ¦ ¦ ¦ Node Number (reserved) : 2804 ¦ ¦ DHCP configuration : 1 ¦ ¦ Name : SIP40x8 ¦ ¦ Vendor id : alcatel.sip.0 ¦ ¦ TFTP server address : 135.117.104.101 <= OpenTouch IP Address ¦ ¦ Default lease time (mn) : 360 ¦ ¦ Max lease time (mn) : 720 ¦ ¦ Configuration file : --------------------------------------- ¦ +------------------------------------------------------------------------------+ With this configuration, DM server IP address is provided by TFTP filed (option 66 next server) DM path not provided, the 4008-4018 uses HTTPS protocol and default DM path value /DM/SIPTouch 4008/18EE fails to get configuration files: root cause Certificate Secured access to DM files Even if 4008/18EE are in version >= 2.11.68, download of configuration can fails, if the certificate created in T 1.0/1.1 is not deployed again from 8770, OT WBM 4008/18EE fails to get configuration files: root cause HTTPS Secured access to DM files  OT R1.2 controls the MAC address of 4008EE/4018EE device (when it tries to get its configuration files). This feature is only supported from 4008EE/4018EE >= 2.11.68. Hence in case 4008/4018EE is in lower version than 2.11.68, it cannot be configured nor updated by OpenTouch R1.2 Workaround1: Deploy 4008/4018EE on OpenTouch and copy configuration file toward 8770 Use FTP access on OpenTouch Copy the whole directory /opt/Alcatel-Lucent/oamp/cms/Device Deployment/SIPTouch Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 112/193 Toward 8770/data/deploy/SIPTouch Change 4008/4018 setup for static IP , and DM setup for 8770 IP, HTTP, and deployed DM path /DM/SIPTouch Wokaround2 : Remove the OpenTouch authentication control of 4008/18 Mac Address Launch ssh access to openotuch Go to configuration directory cd /opt/Alcatel-Lucent/oamp/dmauthent/dm_authent_app/WEB-INF/conf Do backup copy of the conf file : cp dm_authent_patterns.conf old-dm_authent_patterns.conf Edit the file dm_authent_patterns.conf Remove the line “JkMount /dm_authent_app/SIPTouch/sipconfig-*.txt tomcat” Save and exit editor. Restart apache/tomcat service Take care to configure the 4008/4018EE device timezone (it takes into account the daylight saving time DST) 8770 DEVICES application Tab devices Search option NMC TimeZone : GMT+x … - Network SNPT server : selection of SNTP defined in OT - Subnetowrk - OT node TAB SNTP - DeviceNumber UserNAME The configuration files is updated with [sntp] sntp_addr=ntpserver.alcatel-lucent.com timezone=Europe/Brussels::60:032502:102803 DST Date is 25 March 2H00 / 28 October 03H00 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 113/193 5.8 MyIC Desktop setup Requirement Microsoft™ .NET framework 3.5 Visual Studio Tools for Microsoft™ Office : URL updated (search for visual studio tools if link is broken) http://www.microsoft.com/en-us/download/details.aspx?id=35594 Flash player http://www.adobe.com/products/flashplayer/distribution3.html MyIC Desktop needs to be able to contact in HTTPS the OpenTouch server Update firewall to allow this access Take care , the MyIC Desktop PC can resolve OpenTouch DNS address (ping OTFQDN) Take care HTTP proxy in PC does not force HTTP flow to go on internet instead of intranet Certificate If you use a self-signed certificate (installed by default on OpenTouch server, do not forget the configuration of your Internet browser settings OpenTouch server URL must be added as trusted sites : https://OT_FQDN All ActiveX parameters in Internet Explorer, must be set at least to “Demand” (or authorized) for trusted site Fresh installations Using a PC Web browser , download from OT server the myIC desktop installation file http://MyOpenTouch_FQDN/my_instant_communicator_update/MyInstantCommunicator.msi Refer to OpenTouch Administration manual (in the Technical Knowledge Base) Section: Administration Manual > Implementing OmniTouch 8600 MIC Desktop Migration procedure In case of migration of ICS or BiCS to OpenTouch Uninstall the previous MyIC desktop, take care to uninstall also the outlook Extension provided by previous ICS deployment. Upgrade procedures Outlook has to be stopped first, in order to perform upgrade. Otherwise, My Instant Communicator prompts user as follow: Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 114/193 Use the automatic upgrade of MyIC Desktop: Exit MyIC Desktop and Outlook if they are launched Restart MyIC Desktop MyIC Desktop upgrade is performed in case of failure you may have to kill all Windows™ process related to MyIC Desktop After completion of the upgrade restart MyIC Desktop and Outlook. Or manually, upgrade MyIC Desktop: 1. 2. 3. 4. Exit MyIC Desktop and Outlook if they are launched Get the MyIC Desktop installation file (present on OpenTouch server) Launch MyIC Desktop setup directly and upgrade Restart MyIC Desktop and Outlook Help Online  The Help Online is not yet available. Launching Help from MyIC Desktop raise this web page http://OpenTouchFQDN:8083/documentation/otuc.htm There is no help documentation for the moment Coming soon  As a first step, the end-user pdf documentation is published on the technical knowledge base.  To provide end user a quick access to the documentation you can apply this workaround Use FTP to access to OpenTouch Browse to /opt/Alcatel-Lucent/platform/apache/htdocs/documentation Push to this folder the MyIC Desktop documentation, name the file myic.pdf Copy the file otuc.htm as otucORG.htm Get otuc.htm Edit otuc.htm and add the link to open the myic.pdf …

There is no help documentation for the moment

Coming soon...

PDF Documentation

MyIC Desktop

… Push the modified otuc.htm on OpenTouch In the capture, below, the other end user documentation has also been pushed Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 115/193  You can also use otuc.htm as a support page for end user Add this line to otuc.htm (update mail and phone to your company mail phone)

OpenTouch Hotline

E-mail [email protected]

Phone 61234

MyIC Desktop for OXE user in Nomadic SIP  Refer to the Administrator manual to set it up  Quick setup overview On OXE configuration Create a range of SIP external device in OXE Create analog device with Ghost=Yes with Ghost feature=Nomadic On OT configuration Create a pool of SIP device Create the range of Ghost Z to use Give to the device associated to the OXE user device the right User remote connection mode and GSM Give to the OXE user the right Desktop, and the Nomadic preference: Nomadic SIP (if not selected it will use H323) On MyIC Desktop Select Route My Call to Personal Computer MyIC Desktop integration with MOC (OXE user)  Quick setup overview On OT configuration, Select Eco system > IT server Create a an OCS server under On end user computer, modify the MyIC desktop deployment.xml file to specify the integration mode = MOC Take care to install also Microsoft™ Office Communicator 2007 R2 Hotfix KB: KB 976135 & KB 981410. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 116/193 MyIC Desktop integration with Lync (OXE and ICM user)  Quick setup overview On OT configuration, Select Eco system > IT server Create a an OCS server under On end user computer, modify the MyIC desktop deployment.xml file to specify the integration mode = MOC MyIC Desktop integration with Sametime (OXE user)  Quick setup overview On end user computer, modify the deployment.xml file to specify the integration mode = sametime MyIC desktop integration with Outlook After the installation of the extension, the outlook extensions are automatically launched. To enable or disable them: From outlook > Tools menu > Options menu OpenTouch = conf bridge of OpenTouch (formerly name MyTeamwork) MIC Desktop = MyIC Desktop extension inside outlook Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 117/193 5.9 My IC Mobile setup (for Opentouch user) New feature : Agnostic mode for Mobile: no more need to collect device IMEI for MyIC Mobile creation. Such rule depend on what is created in OT configuration and MYIC Mobile Version Devicre created Android Version compliant 4.1 / 4.3 Configuration rule IMEI to give BlackBerry 4.1/4.3 IMEI to give OTC Mobile (smartphone) Subtype Android 4.3 only OTC Mobile (smartphone) Subtype BlackBerry 4.3 only Leave identity empty Remove dual mode (1) Possibility to switch from android to blackberry Leave identity empty Remove dual mode Possibility to switch from android to blackberry Binary deployment By user using Google play By using BES or end user self deployment By user using Google play By using BES or end user self deployment using BB manager Configuration screenshot for dual mode removal 8770 Devices application Tab devices NMC - Network - Subnetowrk - OT node - DeviceNumber UserNAME Search option Security … Dual mode and mobility settings MyIC application download [] Dual mode [] TAB advanced To switch from old configuration where mobile type cannot be change to new configuration : no IMEI, mobile type change possible. You need to from User application of 8770 Dissociate exiting mobile Delete Mobile (Device appl) Associate new mobile with type OTC smartphone and subtype blackBerry or android If you keep exisitng confiuration mobile blackBerry and mobile android And has already deployed version MyIC Mobile 4.1 from 8770 Your end user cannot load individually by them self the MyIC Mobile 4.3 This action will happens MyIC 4.1 on device => User update to 4.3 => OT will force downgrade to 4.1 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 118/193 Hence remove the deployment of Mobile application using 8770 Device application Select a mobile device And for binarymobile filed , select the empty line to remove the binary Result Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 119/193 5.10 LifeSize setup Documentation  Refer to LifeSize documentation for Admin manual and troubleshooting (support) http://www.lifesize.com/Support/Browse_Support/Video.aspx LifeSize Express 220 and LifeSize Room version 4.11.8 and 4.11.12 was the version tested. Setup  LifeSize initialization First plug the LifeSize equipment on the network and on a Video Output Use remote control (you need to point to the camera not the LifeSize box) initialize admin and user password set up IP address  LifeSize SIP configuration Launch a web browser https://Lifesize@IP (default password is 1234) set up SIP credential Navigate to the page: Preferences > Communications > SIP Registrar Status: Registered SIP: Enabled SIP Username: 88800 <= device Number for LifeSize Authorization Name: MyLoginName <= OT User Number or OT User login Name Authorization Password: 1234xx <= OT User SIP password SIP Server Type: Auto SIP Registration: Through Proxy SIP Proxy: Enabled Proxy Hostname: OpenTouchFQDN:5260 SIP Registrar: Enabled Registrar Hostname: OpenTouchFQDN:5260 Internal Server: External Server: SIP Signaling: Auto (SIP or UDP) UDP Signaling Port: 5060 TCP Signaling Port: 5060 TLS Signaling Port: 5061 Disable Multiway call Navigate to the page Preferences > Communications > General Multiway Calls: Enabled (if you still want notification or select Disabled) Video Dialing: Auto Voice Dialing: SIP Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 120/193 Bandwidth limitation and auto-answer mode Navigate to the page Preferences > Calls Outgoing Call Bandwidth: 1472 kb/s Incoming Call Bandwidth: 1472 kb/s Outgoing Total Bandwidth: 2000 kb/s Incoming Total Bandwidth: 2000 kb/s Auto Bandwidth: Enabled Auto Answer: Disabled Auto Answer Multiway Call: Disabled (!!! mandatory !!) Debug and tuning the Packed Mode  Debug command through remote web connection http://Lifesize@IP/support username: cli <= lower case cli !!!! Password: lifesize default password for LS express and room Password: executive default password for LS Executive From this support access, you must change packet mode for H264 packet mode 1 Select Advanced Com Setting page For the field PM1 supported parameter: specify Enable  To avoid communication issue (lost register …) It is advised to reboot regularly the LifeSize system From the web Admin of lifesize select System > General > Auto Reboot: YES A reboot will occurs each day at 4:02 AM  Telnet Debug command Launch a telnet on LifeSize@IP Login: auto Password: lifesize for LS express and room Password: executive for LS Executive Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 121/193 5.11 OpenTouch maintenance and back-up & restore Troubleshooting  Refer to the following technical communication TG0064 13 Alcatel-Lucent OpenTouch R1.x Troubleshooting guide  SQL request to database must specify the SQL port 5433. Example psql –U htuser –p 5433 CMS psql –U htuser –p 5433 DIRECTORIES OpenTouch Backup Restore : single command otbr for OTBE and OTMS For more information, refer to the Administration manual and to the technical communication TC1643 OpenTouch backup / restore R1.0/R1.1 Copy of main command otbr backup : performs server backup otbr restore : performs server restore Options are “host”, “VMoxe”, “VMwin”, “VMall” (VM should be stopped) “applioxe”, “appliwin”, “appliall” Same script is called by 8770, but only to backup the OT host Edit $BiCS_DATA_HOME/BiCS-release.conf to write the actual version saved 8770 backup of OpenTouch  In order to be able to perform a backup of OpenTouch data from 8770, icesuer maintenance account needs to have backup right. If right is not properly setup Log on the OpenTouch as root (su -) and launch the command. /usr/bin/musett.sh password This issue was present after updating to 1.0.1 (crms00366820) and should not occurs anymore with OT R1.1.000.080 update BiCS Migration case When migrating a BiCS to OpenTouch system, the backup tool of the OpenTouch delivery needs to be installed on the BiCS system, see installation manual , chapter Migration Webinar virtual Machine backup There is no backup of the VM conversion of document. Use the ACS admin page for the specific backup procedure Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 122/193 5.12 OpenTouch Edge server Description OpenTouch Edge server provides external user (out of company LAN/WAN/VPN) access to The conference https URL link Application sharing and Webinar presentation (webinar is not supported by Reverse Proxy) License To order the license follows the ordering guide on business portal Order & Logistics > supply chain > order entry rules OpenTouch Edge server Order entry Guide Topology The topology and firewall rules are described in this document OpenTouchEdgeServer.pdf . You will find such document in OpenTouch software download section on business Partner Website. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 123/193 Setup and configuration Once OpenTouch Edge server is installed (installation is the same as MyTeamWork standalone) Follow the admin manual to configure both OpenTouch and the Edge server (called front end) ACS front end server to secure collaboration services Overview Front end security Configuration 5.13 Voice mail notification through mail / SMS  Refer to the Administrator manual to set it up  Quick setup overview On OT configuration, Select System services > Application > Notification > cmsNotification And update the notification mail/SMS sender name and addresses max wave file size attached in mail voicemail box threshold for full voice mailbox notification Select System services > Application > Messaging > VPIM to configure route (= mail relay and mail domain destination) to join notification mailbox address. 8770 Configuration application Tab OT Search option OT server name TAB OT -… Rules[] - System services Routes - Applications Domain name : hotmail;com - Messaging FQDN or IP : mail.company.name - Voicemail profile Port 25 - VPIM DNS routing [] - VPIM For each user, select the Notification TAB and give the right to use advanced SMTP/SMS notification  End user operation On end user PC, each user can access to MyProfile web page or MyIC desktop to check and, if right is given, to activate/deactivate the voice mail notification, Fill their mail or mobile number where they want to get such notification. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 124/193 6 List of Major issues, Restrictions and workaround 6.1 Remaining major issue detected in OT R1.3.000.043 At the step of Technical Release, following issues were detected. The list is given as reference to check if you encounter a similar issue, it may be a real software issue or linked to a configuration error or considered as normal behaviour. Anyway, if you find similar issue create a Service Request, Technical support will compare it the exisiting one to check if it confirms the initial detected issue or use previous analysis on exisitng issue to check your own issue. Check the other chapters 6.2, 6.3 … for detail restrictions.  Open Major issues : in Green workaround Product CR.Id headline 8770 crms00406427 8770 client slows down whatever application (when loading Ipticket by performance and loaded file or transfer is corrupted) 8770 crms00409739 8770:Impossible to create an OT supervision Group 8770 crms00424484 [OT][8770]: the automatic Java updates should be disable automattically after the installation the 8770 server (or 8770 doc problem) 8770 crms00428679 8770 audit: no more work after upgrade from j2.603.13.f to j2.603.20: not a problem, the FTP config was corrupted on OXE, OK after solving the config issue 8770 crms00429415 Android and BlackBerry CMS schema change due to OT CR crms00425305. 8770 cannot deploy MyIC Mobile 4.3 deploy it using googleplay or BES manager or device app manager acs crms00377025 OT1.1: IPad OTC: identity of the caller is displayed on the Ipad when he calls in secret identity acs crms00403417 Dialing a call in MTW using Dial-by using a UserDN does not route correctly acs crms00406577 ACS DocConverter : OFFICE 2010 not installed in vmConverter even if in WebAdmin message displayed is : OFFICE installed. acs crms00407343 Conference invitee doesn't see participant list. acs crms00408828 OTC iPad : Photo taken from the iPad is not automatically selected (1.2 only, ACS issue) acs crms00409454 MYTW : Delete a scheduled conf OK on the user who created the conf but NOT on the other participants of the conf acs crms00411610 muxer : bad behavior if URL contains the word "ics" acs crms00415565 OT1.3 : Scheduled conference between MyTW IVC+ MyTw IVC + MyTw IVC => joining via icon video conf list (MyTeamwork window) =>impossible Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 125/193 acs crms00421191 OT1.3.000.021 : MyTW "Share a document" pdf without Windows Office VM : some pages of shared document are not displayed on some users acs crms00428072 alpha OT MyTW : Conferencing issue on entering on two differnce conf, with same name (confidentiality) acs crms00428486 OT1.3 030- can not run DCS image from OT virtual manager: workaround run "virsh netstart default" in OT console by manually acs crms00428497 After a crash generating ACS CORE dump: no more audio on conference ecc crms00392154 [supervision] TUI activation/deactivation with programmable key does not work ecc crms00404993 OTMS 1.1 on OXE with 60K entries in phonebook, UDAS can not sync phoneboookdir //1-137839429// ecc crms00426663 User cannot listen to VM which was finished by pressing Attach button - “A voice mail server error has occurred” message pops up. ecc crms00427007 on no answer, sometimes it overflows to GSM voice mail instead of user VM ecc crms00428025 OT1.3:SBC:Can't send voice mail (mail box on LOCAL STORAGE) - "No destination found" after force merge. ecc crms00428790 if TTS=0 in license voice mail became disable and no warnings in base language about it GVP crms00390159 OXE user get disconnected if, in the conference, others joins with video GVP crms00402523 Sched Conf De-escalate from 3 party to 2 party video freezes GVP crms00409755 TUI Supervision: audio quality of the supervision (de)activation wav files NOK GVP crms00418714 Sometime, during few minutes, No data received on scheduled conference GVP crms00425926 OTMS R1.1.000.080 Voice Mail Issue_Can not understand fully Korean VM announcement in every points GVP crms00428685 GVP - Video freezes when owner drop his own video ictouch crms00408317 OT 1.2 - VLE - G711 & G729 - Hands free - Voice quality issue - No Comfort Noise generation ictouch crms00409642 alpha VGA : one user in 3 party conference didn't see the 2 particpants, only one myic_desktop crms00384843 OTC iPad : User OTC receives a "Add contact request" when a user MyIC opens ID card of this OTC user myic_desktop crms00389488 My IC PC : Menu items become on grey with dual network myic_desktop crms00389570 OTC iPad / MyIC: Profile Tablet only, incoming call, Problem when divert to Personal Computer MyIC PC myic_desktop crms00390421 [OpenTouch Cloud DT] The MyIC Desktop takes 1.25 minutes to start and login Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 126/193 myic_desktop crms00397017 when starting up, the myic_desktop doesn't see user's ipad engaged communication myic_desktop crms00400400 MyIC Nomadic SIP - problem with the caller which set "OnHold". myic_desktop crms00405939 Access to directory not available after stand-by with MyIC myic_desktop crms00406602 OT1.1 Alpha:MYIC desktop voip mode not available for win7 myic_desktop crms00408473 wrong information number on myIC when other number is used myic_desktop crms00409571 Function "Away" timer doesn't correct work for icm users in MyIC myic_desktop crms00411491 DM: Phone set profile modifications of the MyIC PC SIP Device are not taken into account on client. myic_desktop crms00411905 VGA tests: trouble with SIP stack - no more calls from MyIC Desktop of from My contact myic_desktop crms00415568 MIC-MOC uninstall issue myic_desktop crms00416825 My IC Homeworker : headset volume does not revover after dual call. myic_desktop crms00421303 MyIC OT1.3: DTMF window doesn't work when Nomadic SIP user calls to conference and tries to enter the access code myic_desktop crms00421345 MyIC OT1.3: Switching from Office phone to Personal computer (as Nomadic SIP user) the second time impossible myic_desktop crms00421927 alpha OT : Search bar on MyIC PC is no more working: Workaround is to close this ghost search bar myic_desktop crms00422523 MyIC / OT1.3 : Context menu "Call by..." does not appear in the Search/Call box after Sign Out -> Sign In myic_desktop crms00422534 MyIC / OT1.3 : It is impossible to make a call after Sign Out -> Sign In myic_desktop crms00422555 MyIC OT 1.3: DTMF for OXE user (nomadic ip mode, office phone mode) works unstable when user enters the password to get the access to his VM box\Confe myic_desktop crms00422854 MyIC / OT1.3 : It is impossible to make a call transfer between MyiC PC SIP (OXE user) and ICM user myic_desktop crms00422888 MyIC / OT1.3 : It is impossible to make a call transfer between OXE users during a call (only after connection is established) myic_desktop crms00423021 OT 1.3 MyIC Nomadic Ip: 3 party conference doesn't work: nobody hears each other and the connection lost after 10-15 seconds myic_desktop crms00423307 MyIC / OT1.3 : Does not play a sound in audio wizard (one computer) myic_desktop crms00423848 OT 1.3 MyIC Nomadic Ip: switching from one conversation to another one causes crash of Voip plug in and MyIC goes to Office phone device mode myic_desktop crms00424014 MyIC / OT1.3 : In ID card of user personal phone numbers is appear with digital prefix myic_desktop crms00424403 OT 1.3 Extensions: After User recorded message and pressed # 1 time - nothing Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 127/193 happens, second time - tui message "I didn't understand" myic_desktop crms00425498 Audc-OT1.3-MyIC : no more audio on Remote MyIC-PC-SIP when escalation to video in SIP/TLS and SRTP myic_desktop crms00429088 OL2010+MyIC/Lync: MyIC external panel isn't launched if Outlook is started before Lync. (OT1.3) OAMP crms00363765 OT1.1: noesip 4008/4018 devices show device number when i button pressed OAMP crms00388747 no automatic update for the MYICM on Android if public@ different as private@. OAMP crms00389927 CMS incorrectly maps deafult AVP to Personal Video profile when 3rd Party Video device is defined fo OAMP crms00407231 impossible to create dynamic attribute in LDAP directory OAMP crms00411815 migration voicemail failed when some users have the same name OAMP crms00418016 OXE with SIP auth: OT voicemail registation still fails when OXE external GW managed without security OAMP crms00419336 Users : TRIVIAL TUI Password error during creation of OT user OAMP crms00424543 VHE 2 - upgrade in R1260.1.10.1 Updating the set has lost the configuration of the supervision OAMP crms00425239 some MyIC phone 8082 devices seems monoligne due to bad value in SIPServer OT crms00362827 Merged Directory : no more icon in My IC PC Search Directory OT crms00374584 OT1.1 / MyIC redial list should not show videocam icon in front of contact as videocall do not work. OT crms00382298 OpenTouch 1.1 - No control of the "GSM number" field of a mobile device : impact fall back OT crms00384170 My IC - Homeworker : missed call as no way to take call before 3rd ring OT crms00388008 no automatic update for the MYICM on Android if public@ different as private@. OT crms00394722 Add-hoc viedo conference between MyIC PC & OTC IPad & Life size Express => No image on MyIC PC - audio OK OT crms00395348 OTBE communication without audio if I make a second call during conference. OT crms00402082 Interop : Non-ascii characters are badly displayed on NOE set for complex calls OT crms00403816 CBR sent from ICM to OXE user : no log on OXE device OT crms00404260 alpha OT 1.2 : addng a participant since MyIC Phone, the callee is added on auto off hook OT crms00405941 Lifesize video - Extra Leg showed up during adhoc call Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 128/193 OT crms00407361 OTBE - Video fails after transfering the call form Lifesize to MyIC Desktop OT crms00407850 OTMS - MIC Mobile for OT user communication in G.729, OT sends residual G711 RTP pac OT crms00407908 Issue after OT user creation: autocreation to setup (do not disable it) in 8770 for OXE OT crms00407912 In AA, leaving a VM thru Transfer/Mailbox Dial By Number results in user name being displayed even when the caller identity is secret. OT crms00408621 RADVISION : P2P video call - MyIC desktop nomadic (other) calls MyIC Desktop => Audio call instead of VIDEO call OT crms00408733 Switch on Device can be perform only One time from OTC iPad in a same conversation OT crms00409886 MyIC PC stop if opentouch is not reachable OT crms00410259 Sip error 503 after 45 minutes of traffic OT crms00411158 Ictaudio crash on VHE-2 with 8082 set with video OT crms00411407 [Alpha-APP]After upgrade new version for VHE ,the telephony presence icon dissapear. OT crms00411867 [OT - VHE] Field "chat" of the contact is not filled automatically when user tags it as a Favorite OT crms00412390 NFS Backup size: huge (several GB!!) and 99% useless OT crms00413851 OT1.3- merge 2nd incoming call from VLE to a conference, all correspondents are released OT crms00413892 OTMS R1.1.000.080 Voice Mail Issue_Can not understand fully Korean VM announcement in every points OT crms00415061 OT1.3 : Ad Hoc conference between MyIC Desktop + OTC iPad + Lifesize Express 220 (meeting room) => NOK OT crms00415368 MyIC Desktop - wrong picture during call OT crms00416243 alpha OT : freeze audio and video on lifesize during a conf schedules reservation less OT crms00416611 OT1.3 : GVP scheduled conf DIAL IN : MyTW IVC & LifesizeExpress & MyTW IVC : No audio for some user > No video on Lifesize Express OT crms00417452 Unknown caller when user forward UM message to another UM user thru TUI OT crms00417999 OT 1.2 restore OT from 8770 failed =>workaround restore the ACS link OT crms00418916 alpha OT : lost audio on lifesize during a conf schedules reservation less OT crms00419332 crash ICT audio on vhe OT crms00419591 OT1.3 - PREBETA - When in teamwork conf, if switch device from VHE to MIC Mobile, then demi-com. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 129/193 OT crms00419635 no more photo displayed on VHE since uppgrade in OT1.3 OT crms00421025 OT 1.3: OTC IPad :voice mails are displayed as no answer call in the Call Wall after consultation OT crms00421054 dongle lost on flex VM for OXE => solved by FLEX 1.3.000.051 via a script installed by default OT crms00421934 [VHE] [OT] IM tchat messages are logged in VHE comlog and are notified by a beep OT crms00423109 Aleds2.1 not working with HP Blade System to install ICS 6.x OT crms00423715 if make error during postinstall configuration, impossible to correct it after OT crms00423752 OT 1.3 - SIP Server errors after SIPFlood attack OT crms00424905 VHE wallpaper gone after OT upgrade to 1.3 OT crms00426445 ACS : bad audio quality during conferences (jerky voice) OT crms00428371 OTC iPad : automatic hang off on incoming call OT crms00428503 Overflow on busy is in MyIC but is missing in VHE OT crms00428658 Impossible to login on the VHE 8082 the ext loggout alone. OT crms00429515 Performance issue with MOS calculation VHE and VLE OTC_iPad crms00404979 iPad : OTC client can connect without OT device OTC_iPad crms00408847 Switch on Device can be perform only One time from OTC iPad in a same conversation OTC_iPad crms00423892 OTBE : iPad crash with error : OTCGap: onACSError OTC_iPad crms00424822 Alpha OTC Ipad : ringing not stopping on receiving call OTC_iPad crms00425010 OTC iPad : Search Directory very slow with more than 150 contacts (Outlook synchro) OTC_iPad crms00425157 alpha OTC Ipad : impossible to ativate MUTE during a conf OTC_iPad crms00425164 alpha OTC Ipad : if parameter auto lock/unlock with cover is ON, impossible to take the call with the unlock slide OTC_iPad crms00427006 OTC_IPAD: need to restart twice the application when application is closed due to the lost of the server OTC_iPad crms00427884 OTC_iPAD_US13 : Tweet cannot be displayed anymore after a background mode (OTC suspended) OTC_iPad crms00428111 OTC iPad, webinar meeting, an invited attendee sees everybody OTC_iPad crms00428521 OTC iPad : nickname not retrieved when making an outgoing call to a not favorite user oxe crms00382256 Callback on VHE does not work for external caller due to wrong number Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 130/193 oxe crms00402512 Interop : Non-ascii characters are badly displayed on NOE set for complex calls oxe crms00410463 Issue on getting message LED indicaion for missed calls//1-141517531// oxe crms00411313 directories merge: no answer from OXE phonebookdir oxe crms00419626 Auto answer does not work for OXE users oxe crms00427465 OT : OFS: Incoming FAX Issue through Automated Attendant with Routing Number. oxe crms00428303 Wrong number on mobile phone when attendant is calling OT user Serviceability crms00419769 OT 1.3: Name forward is not working correct after deployed embedded DNS server Serviceability crms00421291 ALEDS NFS showmount not working correctly Serviceability crms00423696 impossible to change centralized license server Serviceability crms00424437 SMTP notification doesn't work : workaround after installation give the good right to postfix account Serviceability crms00424691 OT1.2 : otbr.sh : ignore fatal errors from ACS backup Serviceability crms00424850 Ot 1.3: After MyIC uninstalled user starts OL and gets exception error Serviceability crms00425774 Audio quality in conf on alpha Serviceability crms00427889 In OTBE configuration the sip trunk is created in network number 15, we would like a differnet default value Serviceability crms00428369 DLA tool does not work to enable the chameleon logs Serviceability crms00428416 Logzipper file ZIP file corrupted 1-144882346 Serviceability crms00428548 OT1.3 IT3: OXE : Time Zone definition & modification : Not taken in account by OXE. Serviceability crms00429510 ALED : failed to install OXE J2.603.20 on ESXi 5.0, solved in ALED 2.2.2 SIPS crms00390200 OT R1.2 Manager-Assistant : Conference aborted if Assistant picks up the call SIPS crms00392251 [ICE] Conference N : current communication is released if trying to add a wrong external number to a conference SIPS crms00398021 Manager/assistant : Teamwork conf call with 3 managers in F1N1, 2 managers have no call log SIPS crms00398762 [OT][TRANSFER]: call is released when user transfers a call to another user who doesn't answer SIPS crms00404182 [OT][Routing][Multidevices]: call is released when destination of deflect doesn't answer SIPS crms00404737 alpha OT 1.2 : adding a participant since MyIC Phone, the callee is added on auto off hook Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 131/193 SIPS crms00405242 Mobility : When overflow occurs before the ringing of mobile a conference is started SIPS crms00407347 Ad-Hoc conference audio && video without radvidion MyTW-MyTW-MyTW+LifeSize -> last call never done SIPS crms00412154 User is busy whereas it is free SIPS crms00415631 Caller info is not updated on IPTouch 4038 after the call transfer SIPS crms00416065 CAC VIDEO Call : If CAC is configured on OT side Video cal is not working correctly SIPS crms00416520 OTC IPAD: not possible to on hook a participant in a conf add hook SIPS crms00417578 Error messages in SIPserver log : number 'XS' is not found. SIPS crms00420594 UM Domino - No Voice Stream found in this voice message error SIPS crms00422084 After placing a call on hold , the user is unable to retrieve the call, when call occurs from OXE user to ICM via WebSoftPhone or vice versa. SIPS crms00423999 [Mutil device]Overflow on external number start a conference instead of transfert the call SIPS crms00424565 [sécurité OXE-OT]- call to oxe users via OT AA, should use OT FQDN instead of IP address in FROM header SIPS crms00427838 alpha OT : in case of divert on ringing on MyIC phone, no take call button appears VITALSUITE crms00421411 8770-Vital: error for display Vital reports: "erreur de page web" XS crms00407503 M/A : Trying to recover the blind transfer to Manager releases the call 6.2 OpenTouch server 6.2.1 Fresh Installation USB key  As for BiCS systems, during the installation of the Linux OS, all the USB storage devices are formatted. Do not plug any USB key or hard drive to the OpenTouch system during this OS installation step. Once the Linux OS has been properly installed, it is possible to plug to the system an USB hard drive with the ISO files of the various OpenTouch sub-systems component or to plug the USB key with the license files. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 132/193 Dongle plugged during installation  During OTBE installation (post installation wizard /restore) and operation the dongle must be plugged. For those confused on what is a dongle: it is a key that record and hardware ID. This hardware ID is checked regularly by the license service FlexLM. Do not try to put any data on the Dongle, the license has to be provided on USB key or on any path visible from the server and of course dongle cannot be used to put inside the OT license. Software Delivery: MD5  Check the MD5 checksum of files downloaded from Business Portal. You can use the md5sum Linux command md5sum filetocheck License  During post installation wizard, do not skip license step or provide dummy license, these license files are required to create data in OT / OXE DB Hardware  Due to compatibility issue and performance issues, OpenTouch solution must not be installed on top of software RAID controllers. Only physical RAID controller can provide sufficient io performance for OpenTouch needs. Partition usage for file copy of ISO file  The system partition is small (30Go) and dedicated ot system usage. DO NOT COPY .ISO FILE IN THE SYSTEM PARTITION. It is recommended to mount USB disk or to use a temp folder in backup partition : example /var/Backup/tmpd) MyTeamwork conference INVITE from ACS crms00431766: After OT 1.3.000.04x installation from scratch, the command “service iced status” reports the following error: acs: /usr/eiab/eiab.conf: line 948: OUTLOOK_INVITE_ROLE: command not found /usr/eiab/eiab.conf: line 948: OUTLOOK_INVITE_ROLE: command not found Advanced Communications Server 9.2.0b6509 This is caused by an incorrect record in the configuration file eiab.conf after installing server OT1.3.000.043. Workaround: modify the line 948 in eiab.conf file with OUTLOOK_INVITE_ROLE=1 instead of OUTLOOK_INVITE_ROLE=0 OTBE: internal DNS This embedded DNS solution will only be supported on OTBE and for small capacities with up to 150 users, and be proposed when no possibility exists to use an external DNS. ALUE continues recommending that whenever possible, the customer must adapt its DNS so it resolves names of OT servers. The DNS service will be available on all OTBE packages, but the embedded DNS server usage will be supported by ALUE up to a limited population: IP Phones only use case : 500 hardphones (in case the embedded DNS is only used for hardphones). If computers are also allowed to use the embedded DNS server, up to 150 users, ie 150 computers (includes Computer/tablet/Mobile) and up to 500 hardphones. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 133/193 DCS crms00428486: DCS image from OT virtual manager can not run. When installing the DCS server, a new qcow2 image for Windows 7 installation will be created in OT's virtual manager, the problem is that when you run this image, you got an error saying "internal error network 'default' is not active" and the DCS installation is impossible to be started. Workaround: run "virsh net-start default" in OT console by manually Note: network 'default' is inactive with no autostart in 1.3.000.040 too. OTBE: 8770 VM and OXE VM autostart  The autostart is no longer visible in VM properties So even if you see autostart at false, the autosart is still presnet but done by srcipt OTBE: 8770 VM instalaltion  The 8770 VM DVD is expected in case of installation from scratch of OTBE R1.3 Patches up to G are included in this 8770 R1.3 VM, patch H and I are supplied separately. 6.2.2 Fresh Installation (on VMWARE)  crms00398668: During OXE installation from scratch in a VmWare virtual machine, there is a message that can be ignored: "Disk too big: use optimized up to 80000 MB only." The VM has been configured with a disk size of 80 GB (80x1024), OXE check for 80000 MB Whatever the answer yes or no, no impact, the fdormating is done and correct 6.2.3 ALEDS deployment restriction The assigned IP is getting changed after reboot of ESXi server; refer crms00414565 To overcome this behavior, do change the IP address manually after the reboot.  Flex Installation with license file is NOK. Refer crms00426808 For manual license installation fallow below mentioned steps Copy the .ice file in /opt/Alcatel-Lucent/data/licenses DO NOT Remove the default alcotuc.lic file in /opt/Alcatel-Lucent/data/licenses/ Restart the Flexlm services “service flexlmd restart  After the basic configurations, when Start VM is clicked, the VMware player will freeze on Windows 7/XP hosts. The following steps should be followed to overcome the issue: If the VMWare hangs after clicking ‘Start VM’, minimize and maximize the by clicking the “Windows + D” key. In some cases, it will give a message box “Binary translation is incompatible with long mode”. Click OK and if it hangs again after that, this would help to start the engine immediately. If it did not solve the issue, to make sure that the machine is compatible to install VMWare, the following checks should be done and tested again VMWare compatibility check:  VT technology should be enabled in VT machines. To enable, boot machine, enter boot menu --> System Configuration --> Device Configuration --> Virtualization Technology --> Enable. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 134/193 Install VM guest check (VMware-guest64check-5.5.0-18463.exe) to check whether the machine is capable to run VM Player guest. The executable can be downloaded from the VMware website  Multiple windows installation is not possible. Only first installation would be successful and other windows installation fails. Back on PVM option is not working for VM installations. If user wants to go back to previous menu, target machine should be restarted. This information is also mentioned in ALEDS user guide. 6.2.4 Active partition Update  Such feature is not used for OT 1.1.000.0xx => OT 1.3 OT 1.2.000.53/54 => OT 1.3 Reason : OS DVD is change from previous release, OT 1.3 use redHat 5.8 Only fresh install on inactive partition + clean install is supported when upgrading OT 1.1/1.2 to OT 1.3 6.2.5 Inactive partition + clean install: Update from OT R1.1/R1.2 to OT R1.3 Usage The supported mode for upgrade OT R1.1/R1.2 to OT R1.3 is Install on inactive partition with CLEAN install option Status of the feature: This feature is released Documentation For detail on the process here the Techncial communication TC1704 1 OpenTouch OT_SW Version upgrade on inactive-partition and maintenance Recommendation before upgrade  During installation on inactive partition Boot DVD must not be mounted on the same mounting point as the OT DVD.  Existing OT 1.1 VM conversion of document cannot be used You have to deploy it again Explanation: Between ot11 and ot12, the size of the virtual disk for doc conversion had to be increased from 17GB to 20GB. The reason for this is that the install instructions for ot12 require additional Microsoft patches to be installed for both Windows 7 and Office 2010. These patches brought the disk usage dangerously close to full, so in OT12 the boot DVD added extra space under /mnt/virtualmachines, and ACS used that space by increasing the size of the Doc Conversion VM disk. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 135/193 Recommendation after upgrade  Hotfix cannot be installed on inactive partition. You have to stop services after switch over script Please check in the file /opt/Alcatel-Lucent/version.txt that the version is correct (it must not contains Installation not completed)  The Flexlmd might not start immediately after the switchover but with a delay (crms00405646): In such case, perform a hardware reboot or a service iced stop/start.  OTBE: system can't read dongle after upgrade from OT R1.1 OTBE upgrade from OT R1.1.000.050 to OT R1.2.000.020 System failed to check the dongle that failure causes license issue (GVPmediacontrol, SIPserver stop) Workaround: check aksusb: service aksusbd status if it is stopped, start it. service aksusbd start  crms00405260: In case there are customized prompts for ACS, you might need to re-install them after the switchover.  file ics.keytab for SSO not correct after a restoration on a new server : crms00357370 This file must be regenerated if the restoration is made on another server. Smooth update and embedded OXE of OTBE  After smooth update + switch over, Check OXE Telephony version running Check OXE autostart option  in case OXe version is not the good one, use PC installer/ swinst to update properly OXE and switch properly to J2.603.20i. You can then reapply OTBE update, it will see OXe is properly updated and put update completed status Smooth update: Impact on FAX FAX services is stopped during installaiton on inactive partiton After siwthcover do not forget to restart FAX services. 8770  8770 : run OT and OXE synchronization from 8770 configuration module Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 136/193 6.2.6 Upgrade from from OTBE R1.1,R1.2 to OTBE R1.3 with CCxx activated Apply same proces as Upgrade from OpenTouch R1.x to R1.3 with server reinstallation 6.2.7 Upgrade from OpenTouch R1.x to R1.3 with server reinstallation This is the only upgrade mode supported if coming from R1.0, (for R1.2/R1.2 it is a choice) The upgrade is based on 1. Update of 8770 from 8770 R1.x To 8770 R1.3 2. backup OT R1.x 3. installation from scratch of OT R1.3 (with CCx acitvation if needed and if server is G7 or G8) 4. Restore OT R1.x backup Use the official documentation Istallation chapter 15 upgrade or for detail on the process consult TC1799 3 OpenTouch – Upgrade R1.x to R1.3 with server reinstallation End user impact  MyIC Phone reset in loop during a short period While installing OT R1.3, the MyIC Phone 8082 can use the OXE survivability on a duplicated OXE. But after end of OT installation, all OT services is up and the database empty Hence, the MyIC Phone will reset in loop since no configuration file available yet on OpenTouch. The reset will stop as soon as the old OT R1.0.1 database is restored on OT R1.3. Data collection  Data collection Use following document to save your OpenTouch solution FQDN / IP@ / Password Same kind of data is on OTBE bics.conf file TC1758 2 OpenTouch R1.2/R1.3 Prerequisites and Data Collect Guide 8770 of OTBE Upgrade from 8770 R1.0 to R1.3  An 8770 R1.0 backup cannot be restored inside 8770 R1.3. Before upgrading OTBE R1.0.1 to R1.3, the 8770 R1.0 must be updated inside the Windows VM For such update you need to use the ZIP file of 8770 version Unzip the 8770 version inside the 8770 VM and run the serversetup.exe  Do not use the ISO file for 8770 Version. This ISO file is reserved for OTBE 1.1 to OTBE R1.3. If you try using this ISO inside the 8770 VM (by using DVD emulator like DTLite4453-0297.exe: an error occurs « insert disk1 » because installshield record the media used for initial installation (from local disk and not from DVD).  After restoring 8770 database from server X to Y, you can’t access to admin page. (Display: Authorization denied. Cause: Your certificate cannot be found in database) you must apply the following workaround: Open a DOS Windows™ with admin property Execute 8770\bin\Regenerate_EJBCA.bat It takes about 15min, services are stopped. The server is unavailable during this time. Once the execution ended, install the new certificate generated in the internet browser Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 137/193 After update  crms00400409: After a database restore, the automatic backup configuration via a NFS server is not fully restored. The "configureStorage backupStatus" is well configured. But the crontab no more contains the backup command line.  file ics.keytab for SSO not correct after a restoration on a new server : crms00357370 This file must be regenerated if the restoration is made on another server. 6.2.8 Migration from BiCS to OTBE R1.3 Migration mode supported The migration is based on 1/ BiCS backup using OT tools on OT DVD 2/ Then OT R1.3 fresh installation (with or without CCx activated in post install wizzard) 3/ followed by backup restoration Use the offication installation manual (chpater migration) for the detailed process  No Migration from ACS standalone, double check the DAS rule of ACS after migration and before creating new users  ICS 6.7.1 standalone migration to OT R1.3 is supported  direct migration from previous ICS version is not supported, it has to be updated first to ICS 6.7  4635/4645 Voice messages are not migrated from BICS to OT R1.3  Voice Mail Box of 4645 must be deleted in OXE and crated as OT voicemail box  LS messages are not migrated from BICS or ICS to OT R1.3  OXE SIP Device After migration, in OTBE R1.3, you should (re)create the unallocated sip devices (Thomson ST2022, ST2030), do the associations manually, recreate the deployment packages and deploy them. Do not forget to modify the DM settings in SIP phones to point to the new DM (i.e. 8770 server in OTBE instead of 4760 server) Consult OT R1.3 Feature list about hardware and feature suppored by OTBE This is not a post sale action to check feature supported or not The action should take place before by presale by using the feature list. 6.2.9 Migration from ICS to OTMS R1.3  ICS 6.x standalone migration to OT1.3.000.043 is supported  No Migration from ACS standalone, double check the DAS rule of ACS after migration and before creating new users  Voicemail messages are not migrated from BICS or ICS to OpenTouch Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 138/193 6.2.10 High availability High availability  No HA is available in OpenTouch R1.3, except for OmniPCX Enterprise where the classical mechanisms of redundancy still apply.  RAID 1 mirroring with hot plug disk is available on the OpenTouch appliances. 6.2.11 Security Certificate Management  Certificate expiration No warnings about certificate expiration dates are generated. Alcatel-Lucent recommends that the administrator remains vigilant about the expiration date of OpenTouch certificates. The administrator must anticipate certificate updates before expiration dates. Expiration date information is displayed in the Certificate tab From the WBM application interface, select System services->Security>Certificate->Certificates menu -> Certificate tab. Certificate Validity Expiration Date  Certificate renewal If the MyIC Phone keeps rebooting after the expiration of the system certificat, you need to: Generate a new certificate (see Certificate Management documentation). Generate and deploy a new CTL for all SIP device (see certificat Management docuementation). If the MyIC Phone keep rebooting, restart the apache server (crms00431188)  Certificate Signing Request fails on Internet Explorer To create a CSR Launch OpenTouch WebAdmin through 8770 or by https://ICE-FQDN/WebAdmin Go in: System services > security> certificate > certificates Then, we have to select the self signed certificate and click on "Generate CSR" Several settings have to be filled at least country code then click on create. Then click save to get the CSR, a windows popup should appear With Internet Explorer or with 8770 (when default browser is Internet Explorer) nothing is happening Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 139/193 Solution To enable file downloading in HTTPS, it is necessary to edit the registry key as explained on http://support.microsoft.com/kb/323308  crms00381666: Split load certificate and deployment to avoid end-users disruption: After uploading new server certificate, Apache is restarted with new certificate and all end-users are out-of order (All 8082, My IC PC, current My Teamwork conference...) Authentication  NTLM version 2 is not supported SSO configuration  The config files web.xml.kerberos already present on the system haven't got the right configuration. The path for krb5.conf and auth.config are erroneous: Authentication by SSO not working The ics.keytab with the tool ktutil must be generated with the command addent -password -p ics_kerb@[domain.com] -k 0 -e rc4-hmac AND NOT addent -password -p ics_kerb@[domain.com] -k 1 -e rc4-hmac 6.2.12 OpenTouch server Openness  Telephony, One Number, Messaging, Teamwork, MyIC on IP Touch are available in OpenTouch for upwards compatibility. They are limited to ICS 6.1 perimeter and available only for OXE users. CSTA, TAPI, TSAPI functional API for OXE devices call control and monitoring are also available only for OXE users. Contact Center  Restrictions in OTBE: see previous chapter Migration from BiCS to OTBE Free Seating / Desktopsharing  Free Seating feature is not available for ICM users in OpenTouch R1.x.  Desktopsharing feature, available for OXE user requires the OXE minimum patch J2.501.16c integrated since OTBE 1.1.000.080. Even if there is no dedicated OXE license for Desktopsharing, the setup of desktopsharing user and desktopsharing sets impact OXE engine, IP device and 8770 total users managed. ICS  The support of Exchange 2003 server is no more present in OpenTouch R1.0 (plug-ins on exchange servers are not supported anymore). Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 140/193 6.3 MyIC Phone Check the MyIC Phone Technical Communication TC1781/TC1819 for the list of feature and main restriction. 6.3.1 MyIC Phone setup MyIC Phone minimum version for upgrade to R250 and downgrade to R200  Upgrade from R200 to R250 need a version higher than R200_01.027.2.  Downgrade from R250 to R200 need a version higher than R250_01.002.0. Max number of MyIC Phone that can be updated simultaneously  Because of a known restriction (crms00334528) it is recommended to upgrade ICTouch phones by groups of 100. MyIC Phone action before upgrading to R260: progkey setup  if PROG KEYS have been previously used on the set in R200 (only possible with an MyIC Phone version), the set may block during download. Workaround is To de-activated Prog key using an optional.xml file To make a Flash reset of the terminal. MyIC Phone action after upgrading to R2601.12.2: end user message bad password  Upgrade from version 1.10.4 to version 1.12.2: After the upgrade, the user needs to re enter his password. Beep on MyIC Phone everytime an IM is sent/receive on PC Crms00422819: The IM chat messages are logged in the VHE and are notified by a beep: Workaround: the beep can be disabled by Custom setting file by setting the parameter IMSoundActivated to false xml syntax is this one but IM entry in call log remain w/o problem To set this setting to all MyIC Phone 8082 Select all the devices of type VHE8082 Modify the field of the optional file to /DM/dmictouch/custom_IM_beep_notif_off.xml Copy this value for all devices Apply. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 141/193 . NTP  When specifying the time zone for MyIC Phone sets on the 8770 server, keep in mind not all possible values are shown. Select the first entry of the desired time zone. Ringing  In OpenTouch R1.1, MP3 files cannot be used to create ringing melody on MyIC Phone set. Bluetooth  As soon as an incoming call is taken, if the Bluetooth battery is dead or the handset is out of the Bluetooth coverage, the call is put on hold (case of a mono device user).  After set reset or upgrade, some BT handsets can produce a metallic sound: Turning the Handset OFF and ON solves the problem. USB key  USB key with more than 200 files (total of file whatever their folders) cannot be used In addition, by default, VHE expect file to be under the USK key folder “\My IC Phone” No 8082 User data backup  There are no possibility in OpenTouch R1.1 to perform a backup & restore of user’s data present in the MyIC Phone set. A workaround for keeping contact is to synchronize the MyIC Phone with Outlook using MyIC PC synchronizer tool. Then after device replacement use again this tool, your contact saved in outlook are back to MyIC Phone SDK  Check the MyIC Phone Terminal release note about availability of this tool for MyIC Phone R260 1.10.4 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 142/193 6.3.2 MyIC Phone debug Refer to the technical communications TG0065 My IC Phone OT 8082 Troubleshooting Guide Remote access to MyIC Phone set  The default value of SSH activation setting (DmSecucfgSsh) is set to false, which means SSH server is not started on the terminal, until it is activated through the DM configuration file. To enable SSH server on the phones, use 8770 application The configuration file of the MyIC Phone is updated Traces  Do not keep full traces activated on a MyIC Phone. It will slow the performance of the device and leads to critical end user issue: impossible to take calls. 6.3.3 MyIC Phone application Telephony  Busy state / camp-on management The busy state of a user can be managed according to the total number of active communication whatever the device used and the option to consider first the mobile busy state.  Numbering The numbers retrieved by the set from an external directory or the internal contacts (potentially synchronized with Outlook and so maybe a cell phone) don’t contain the trunk group seizure prefix. The set will add it automatically. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 143/193 For numbers issued manually, via the dial page, the user will have to add on a case by case basis the trunk group seizure prefix.  Dial tone It is possible to add a tone when a user enters the dial page to perform an outgoing call. For this, add in MyIC Phone’s optional file the following setting:  Dialler automatic display when off-hooked This feature can be disabled by a setting Prog keys  Prog Keys feature is released  Prog Keys can be de-activated as described using an optional.xml file with this setting Presence  It is not mandatory to specify the user presence ID, if such filed is missing the presence will rely on the user’s email. Manager / Assistant  Manager-Assistant 3-1 is released, with OT R1.1.000.080 and MYIC Phone 8082 R250 1.10.3 Take care that the last 3rd manager is not completely visible on the assistant device, to access to the button call and change delegation mode you have to scroll the list of managers After scrolling, only 2nd and 3rd manager are visible, you have to scroll up to see again the 1st one.  Manager Assistant 1-1 / see restrictions in MyIC Phone Release note TC1781  Call log can be inconsistent. When answering a pickup call, the deflect call to another user fails. The only deflect call supported is deflecting to Voice Mail (it will be the manager voice mail whatever the role of the user taking the monitored call: manager or assistant)  Call to the manager can fails into assistant voicemail if assistant receives manager call and assistant is forwarded to voice mail.  No intrude feature is supported. MyIC Phone supervision  Sup/Call pick-up: too long group and users' names are not well displayed on VHE crms00385540  8770/ OAMP cannot add OT user in a supervision group. But After OT 1.2 => 1.3 update, existing supervison group remains available Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 144/193 MyIC Phone video  Webcam supported: Logitech C920. The Logitech C920 is only available in Alcatel Lucent catalogue for European Market, To get it out of Europe , you need to find a local reseller…  OT1.2: Video Escalation MyICPC SIP / VHE. After failed video escalation On-hold RE-INVITE from VHE includes blackhole crms00396162  OT1.2: Video Escalation MyICPC SIP / VHE. Wrong SDP content in 200OK from VHE crms00396148  So far, only Peer to peer video VHE is supported. No mutliparty Video conference between VHEs MyIC PC synchronizer Main Restrictions:  On MyIC Phone, you have to specify the FQDN of the PC using lower case. (issue solved since MyIC Phone R250 1.8.4)  The total capacity of MyIC Phone contact is limited by default to 100 entries; hence a dedicated contact folder has to be created in Outlook and all the outlook contacts to synchronize needs to be moved on this folder. (The limit is extended to 500 entries since MyIC Phone R200 1.34.4 and MyIC Phone R250 1.8.4)  The synchronization will also apply delete operation. A contact deleted on MyIC Phone will be deleted also in Outlook.  Conflicts rules: means preference to take modification on MyIC Phone or on Outlook if a contact has been modified on the 2 elements before synchronising them.  MyIC PC Synch cannot synchronize an outlook contact with a huge picture size > 1 MB. 6.4 4008-4018 EE  Only 4008EE/4018EE: only the extended edition supports SIP protocol  4008EE/4018EE device perform non secured access to DM: crms00363989 Operation mode will change with 4008EE/4018EE >2.11.60: this version works in secured mode. In addition do not forget to deploy again certificate from 8770 / OT WBM / Security / Certificate 4008/4018 cannot be deployed on the updated OT platform (crms00417301). You need to deploy again the WBM certifcate  When 4008EE/4018EE are declared in dynamic mode with the DHCP server of OXE, a class has to be created on OXE DHCP server for 4008/4018. Take care that 4008/18 minimum version 2.11.68 should be already present in the device to be compliant with OXE DHCP  4008/4018 devices show device number and not user number for “Who Am I” information: crms00363765 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 145/193 Forward  Forward operation cannot be done directly, end user has to call the routing vocal Application and then refine its current routing: all device voice mail forward to a destination disable mobile. Recommendation is to add a key from 8770 Device management on the 4008EE/4018EE. Put for calling number associated to the key, the routing application “prefix”.  From menu, disable fwd / imm. voice mail fwd works but not imm. fwd to a destination  4008/4018 does not display the forwarding user's number: crms00377560  [4008/4018] The pop-up message is not correct when set overflow in "Options":crms00418105 Using My IC PC control 4008/4018/VLE: In "Options"/"Call settings", when set it's overflow,The pop-up message is not correct. Examples: Set it overflow to "Phone number" when "phone is busy". But the message pop-up is "call overflow deactived".  Voice message box for 4008 sip device still proposes a call back sender, even if sender of the message has already been called: crms00377304 6.5 8002-8012 MyIC Phone (VLE – VLE+) RELEASED since OT 1.2.55 TC1786 3 Technical Release Note for 8002-8012 Deployement :  The binary path in OT is /dmictouch instaed of /vle. This patch /dmictouch is the path used by the VHE and VLE when they are deployed in DHCP mode. (OXE or other DHCP with only option 66 to set). 6.6 OTC iPAD Refer to the technical communications TC1791 1 Technical Release Note for OTC iPad 1.2  OTC Ipad: No video on GVP scheduled conference crms00396000 Only audio is proposed for OTC Ipad to join the conf. require an OTC development not yet delivered. Note: Note : It's possible to add video from MyIC PC SIP device Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 146/193 6.7 MyIC Mobile Refer to the technical communications TC1677 7 Technical Release Note for MyIC Mobile R4.3 on OT (BB/Android) Mobility for OpenTouch user  crms00400206: When overflow to VM on Noreply occurs before the ringing of mobile, a conference is started with voicemail  In order to ensure a proper CLI on the Mobile in case of incoming call, Update OXE configuration System > Other System Param. > External Signaling Parameters Manage the ‘NPD for External Forward’ parameter AnyMobile for OpenTouch user  Only the use of cell phones with ‘anymobile’ device type is officially supported. The declaration of cell phones with this device type induces some consequences in term of multi-devices: This type of device doesn’t provide any service, except one number (all devices of a user ring simultaneously) and switch device. If the cell phone has an empty battery or is out of coverage, any incoming call to the user will end in the cell phone voice mailbox Solution is from MyIC Desktop or MyIC Phone to change the active routing for a routing without Mobile (new in OT R1.1)  Do not use the AnyMobile device to provide a DECT Number, DECT number has to be registered as other device by end user in his routing profile. MyIC Mobile for OpenTouch user  For more info on restrictions, see TC1677 Ed7 Technical Release Note for MyIC Mobile 4.x on OT (BB/Android)  A reverse proxy setup is mandatory (even if not present and/or unused)  For migration OT R1.0.1 to R1.2, do not forget to clean the user configuration in 8770 User application : only one mobile per OpenTouch User  crms00416332:Bad management of MICM device Workaround: The option Dual mode must be unchecked.  crms00418291: GSM number cannot be modified by User  crms00382283: Calls done from mobile in Fallback mode failed 3 times on 4 => instability  crms00387150: Randomly Blackberry fails to make a transfer  crms00400206: When overflow to VM on noreply occurs before the ringing of mobile, a conference is started with voicemail Mobility for OXE user  With MyIC Mobile iPhone (OXE users), the only supported mode for the iPhone gateway is the “gateway” mode, i.e. installed on a dedicated Linux server. The “proxy” mode is not supported in OT R1.0. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 147/193 6.8 PC Application / MyIC Desktop 6.8.1 Application / Browser Support IE9 & Firefox 4.0  WebSoftPhone: custom settings for call window "Display the application in the foreground/background" do not take effect (FireFox7): Crms00361309 A4980  This client is no more supported by OpenTouch. 6.8.2 MyIC Desktop Installation / Deployment / Start-up  MyTeamwork functionality under CITRIX is supported except Video. Explanation: since no video supported activating video on user license/right, will lead to full MyTamwork deactivation: Grayed MyTeamWork options)  Crms00369760: When network cable is unplugged, actions in MyIC menu remain available. If two search/call box are displayed in the windows deskband, you can fix the issue by: Exit MyIC (close, terminate) Right click on free space of taskbar Go to toolbars menu and uncheck the empty item if I recall it correctly. (maybe it has “daskband” name) Now you can open MyIC and you will see only one search deskband. 6.8.3 MyIC Desktop common feature for OXE and ICM user Directory search with entry from an LDAP server or Outlook contact Of course Telephone number value(s) must be filled for searching user on LDAP(s) Take care that an LDAP or outlook contact without LastName will not be displayed on a MyIC Desktop search. Ability to dial phone numbers  Numbers are defined in Microsoft Active Directory or Outlook personal contacts  Only concerns MyIC desktop, MyIC Phone cannot do this multiple phone number get  Take care that an outlook contact without LastName will not be displayed on a MyIC Desktop search. Support of Tel Tag  Tel Tag and Lync/Moc integration, MyIC registry key is erased when Microsoft™ client start. To avoid this problem Browse to HKEY_CURRENT_USER\Software\Microsoft\Communicator Add following variable DisabledProtocolHandlerRegistrations, and set the Value 1 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 148/193 Outlook Extension  Support of Outlook 2007, Outlook 2010 SP1 (for ICM and OXE users).  Outlook Extension is automatically deployed in Outlook provided Microsoft visual studio Tools for Office (VSTO) is installed Outlook is in a compliant version 2007/2010, and 32bit Edition (Office 64bit Edition not supported)  Does not appear in Outlook The standard tool bar of Outlook 2007 must be enabled to present the Start button of MyIC Desktop extension for Outlook 2007. From complement add-in management of Outlook program, enable the use of the Outlook extension Sometime enabling extenson fails (crms00383199) Workaround: on user PC, modify in the registry the key HKEY_CURRENT_USER\Software\Microsoft\Office\Outlook\Addins\AlcatelLucentOutlook2007Extension LoadBehavior must have the value 3 Manifest may have this value "C:\Program Files\Alcatel-Lucent\My Instant Communicator\Extensions\Outlook\OutlookExtensions2007.vsto|vstolocal" Change it to file:/// "C:\Program Files\Alcatel-Lucent\My Instant Communicator\Extensions\Outlook\OutlookExtensions2007.vsto|vstolocal”  crms00363557: Extensions, Defence test: Buttons are not disabled after server disconnect  Voice recording: the button to record message is not visible (only if you have UM on exchange)  Voice recording does not provide a beep to record the message. When recorded, the voice message appears in the not answer call.  crms00360662: VM recording via Extensions: User should be notified that the recording is ended Support of Microsoft Lync  supported For both OXE and OpenTouch users Support of lotus Note extension  For both OXE and OpenTouch users  Lotus Notes 8.5.1/8.5.2/8.5.3 can run in Standard and Basic Configuration. Alcatel-Lucent templates can use either the Basic Configuration or Standard Configuration experience from Lotus Notes 8.5.2 on.  Support of Windows 7 64-bit platforms from Lotus Notes 8.5.1 Fix Pack 1 on (refer to the IBM support site).  Support of the iCalendar standard for conference reservation via outlook calendar. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 149/193 Support of Citrix / XenApp  MyIC and IE should be published on XenApp server in basic mode.  In order to install ACS ActiveX components MyTeamwork application should be run on XenApp server before providing access to all users. Administrator should verify, that on XenApp server Teamwork ActiveX components are accessible for all users (could be checked in Internet Explorer settings page)  NO support of VoIP and NO Video  We just write : NO support of video, if user has video right, the whole MyTeamwork functionality will be disabled and appear as grey menu in MyTeamwork  NO support of Integration and extension Support of Microsoft RDS  NO support of VoIP and no Video  For launch MyIC PC as RDS RemoteApp, users must install the latest version of Microsoft RDP client. At the moment it is version 7: http://support.microsoft.com/kb/969084. If users use version 6 of Microsoft RDP client, the following issue can occur: crms00325360 - It is impossible to close system tray menu 6.8.4 MyIC Desktop specific feature for ICM user MyIC Desktop routing action  On MY IC PC, the "Overflow to Phone Number" in the condition of "no reply", "busy", and "no reply or busy" in the "Call Settings" options. The overflow cannot be applied=> MyIC Desktop error message: "Destination number cannot be an ICM user". MyIC Desktop (OpenTouch User) in Remote Call Control of MyIC Phone  Only when MyIC Desktop is supervising (RCC mode) a MyIC Phone, these limitations apply: Impossible to enter DTMF from MyIC Desktop in remote call control of a MyIC Phone Impossible to launch a second call Impossible to perform a call back from visual voice mail (to be checked) MyIC Desktop (OpenTouch User) with voice on “My Computer”  Survivability of MyIC Desktop SIP on OXE Call Server or PCS is not possible.  Crms00425498: no more audio on Remote MyIC-PC-SIP when escalation to video in SIP/TLS and SRTP.  DM: Phone set profile modifications of the MyIC PC SIP Device are not taken into account on client crms00411491. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 150/193 6.8.5 MyIC Desktop specific feature for OXE user MyIC Desktop SIP (Using an OXE SIP Extension)  Contrary to OmniTouch 8400 ICS, the Softphone MyIC PC SIP is not supported as OmniPCX Enterprise device by OpenTouch systems: it is allowed only as ICM device. MyIC Desktop Nomadic SIP (OXE User)  Crms00369760: When network cable is unplugged, actions in MyIC menu remain available.  Global regression on MyIC nomadicVoIP Nomadic SIP: When a user Nomadic SIP puts a call with a user ICM on hold, he cannot retrieve it (crms00377562). MyIC Desktop client extensions  Regarding Microsoft™ extensions, the version of MyIC Desktop of OpenTouch R1.1 is compliant with MOC 2007 R2 (only for OXE users). Lync 2010 (for OXE user and OpenTouch users)  Regarding IBM extensions, the version of MyIC Desktop of OpenTouch R1.1 is compliant only with Lotus Notes 8.5.1/ 8.5.2/8.5.3 (for OXE and OpenTouch users). SameTime  Microsoft MOC and Lotus SameTime extensions are available only for standard user (OXE) only deployed when the deployment.xml is modified 6.9 Directory, Telephony and Multidevice Directory Merge after upgrade on inactive partition wait for next merge processing Basic Telephony:  OT1.1: After the com recording requested, no Music on Hold while transfer: crms00356159 Devices SIP capabilities  Support and configure default phone set profile. You can’t create custom profile for a new kind of device. Creation/destruction is not allowed. Multi-devices  For operation/usage, check the chapter Telephony and routing  At the end of user routing management the call to TUI is not released (small ergonomic issue no functional impact): crms00362082 Switch Device  Refer to the administration manual for the use case related to switch device. When MyIC desktop operate in nomadic mode (home number), the MyIC Phone cannot get the communication initiated in nomadic mode  Switch device to mobile fails Update OXE configuration Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 151/193 System > Other System Param. > External Signalling Parameters Set the parameter DeActivate Path Replacement at True. Note that this parameter is not relative to the general Path Replacement mechanism (which remains active) but to a specific case with QSIG-GF interconnection. As from J1.410.37k, this change of parameter is not required anymore. DVA  Call from DVA to ICM user is not tagged as urgent: crms00325383 (the call is not displayed as urgent). 6.10 Voice Mail / TUI / Prompt / Automated Attendant Voicemail  A46x5 voicemails are not allowed in an OTBE system: Local Storage or UM have to be used instead.  When you activate SSL or TLS, non SSL is no more possible.  It is not possible to have SSL and TLS activated on IMAP4 Front End at the same time.  LS integrity is naturally available but is not working for IMAP. General announvement (new in OT 1.3)  crms00419795: General Announcement->GA not always plays Prerecorded file: User create GA -> listen GA -> confirm GA -> it all OK. All other users can listen to it. User set new prerecorded file in dir: var\data\general_announcement. Old was is deleted (without daectivated through menu of GA) User ring on VM (or another) ; expected result - user listen new file (prerecorded) actual result - user listen old file immediately, but over time ~30 min, user can listen new GA. Visual Voice Mail MyIC desktop  If user launches MyIC Desktop in call control of a MyIC Phone, The voice mail is played on MyIC Phone, but MyIC Phone does not show the Visual Voice Mail screen. Visual Voice Mail interface is only present on MyIC Desktop. The Call Back of message sender does not work since there is no in communication control from MyIC Desktop (no DTMF sending, no call-back) you need to end communication with voice mail first. Voice mail statistic  Statistics are only provided for local storage Voice Mailbox. Voice mail notification  Users with UM voicemail box only access the basic notification features  SMTP notification doesn't work crms00424437: the following workaround has to be done: find /opt/Alcatel-Lucent/platform/postfix/ -group postfix -exec chgrp htgroup {} \; usermod -g htgroup postfix service scorpiod restart Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 152/193 Voice mail  crms00395820: Call Back Sender not allowed by default For an installation from scratch, call-back sender is not allowed in voicemail profiles (for an update, the callback sender is kept from the updated version The original behaviour has been changed after crms00369630. TUI  crms00370101: Need 2 actions to activate Brief prompt (VM profile and User TUI preference). It should be simplified  crms00362082: At the end of user routing management the call to TUI is not released (small ergonomic issue no functional impact):. GVP  G722.2 is not supported for remote workers and overloaded network (such as Internet, or overloaded network).  crms00370016: Brief Voice Mail Prompts in German Language are not correct  crms00391003: FR-CA - User can hear a mix of male and female voices in all voicemail scenarios: the user hears a mix of both male and female voices in all voicemail scenarios when leaving a voice message Workaround: in case of using French Canadian TTS, The female TTS should be installed. Media server enhancement  crms00368772: Conference via MyTeamWork -OT user A invites OT User B routed on Fwd No Response to OXE device- User B does not ring. TUI  crms00401160 Voice application: two different speakers for en_GB wav files. Two different speakers in the wav files. Then in a same sentence we have a mix of the two different speakers. For instance: it's not the same speaker for TUI.one.wav and TUI.zero.wav  crms00412853: TTS2wav - some of promts always play on En-GB  crms00409755 TUI Supervision: audio quality of the supervision (de)activation wav files NOK Automated Attendant  crms00355678: Bad display after a transfer ICM towards OXE via AA:  crms00361309: Call customization settings "Display the application in the foreground/background" do not take effect (FireFox7).  crms00369943: AA Undo operation has limited usage (move of Ui element): seen as normal behaviour 6.11 Conferencing and ACS Federation The difference between “ACS 8.5 federated with another ACS 8.5” and “ACS 8.5 federated with an OpenTouch R1.0” is that in the latter case (OT), there is only federation for IM and presence. In the pure ACS 8.5 case, the federation supports also calling each other, whiteboard, document conversion, video, etc. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 153/193 MyIC Desktop interworking with presence  At MyIC Desktop start if several popup appears for AddAvater/ DeleteAvatar/SetAvatar Then you have to clean Browser history and cookies, and restart your browser. White boarding  White boarding is available and installed by default as soon as conference license is present Presentation sharing  License The conference license grant the internal licnese ACS-WebPresentation  Deployment This feature is available OpenTouch R1.0.1 system (internal VM to install using Acs admin web page). It has evolved in further version. Here the 3 deployment supported since OT 1.3 1/ Integrated presentation sharing Limited to pdf and poicture + annotation option Nothing to install, this feature is installed by default and enable via the conference license 2/ advance presentation sharing with internal VM Extended to excel and powerpont Use ACS WebAdmlin to create and deploy the virtual machine Supply the DVD and Product key of retail ENGLISH version for Windows7 Pro and office 2010 pro 3/ advance presentation sharing with external VM On VMWARE install a virtual machine or use a decated PC Install Windows 7 OS and Woidnwos office por application Install the DCS tools provided in OT 1.3 DVD 6.12 Video Video client supported  On user device side, video is available only several equipment MyIC Phone 8082 V2, OTC iPAd, LifeSize and PC Two clients are available on the PC, the one embedded in MyIC Desktop The MyTeamwork client (External or Internal video client).  As From OT1.1 it is recommended to connect LifeSize equipment as OT Devices (ICM devices)  MyTeamwork Conference Bridge has no device number so no direct video call Interop OXE users and OpenTouch users  There is no video interoperability supported between OT user’s equipment and OXE user’s equipments. Except if joining a schedule conference with video enabled Video client setup preconisation and restriction  In My Teamwork, it is strongly recommended to define explicitly the audio device to be used (automatic detection not recommended). Else, user can have randomly no audio and video during peer to peer calls and conferences (crms00407374). On USB audio devices, the device selection depends on USB port used.  On LifeSize, it is recommended to activate the automatic reboot during the night. Else, randomly the LifeSize do not answer calls from the OT system and sometime drop all participants connected to a bridge Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 154/193 (crms00408184/crms00408093 seen with LifeSize version 4.11.8). If LifeSize do not answer OT calls during the day, then it must be manually rebooted. MyIC Desktop interworking with conference  MY_IC_PC would be able to join a video conference without external MCU. (GVP media server is used, No external MCU declared). It's not the case. From My_IC_PC_SIP when the user add video => Video My_IC window is opened with the message “video as not been accepted” LifeSize  in Teamwork conference, no dial out toward a LifeSize, the LifeSize has to enter in conference using dialling to the bridge number; dialling established as a video call VHE video  crms00396162: OT1.2: Video Escalation MyICPC SIP / VHE. After failed video escalation On-hold REINVITE from VHE includes blackhole  crms00396148: OT1.2: Video Escalation MyICPC SIP / VHE. Wrong SDP content in 200OK from VHE 6.13 Interoperability with OXE Deployment  Only one OTBE or OTMS is allowed in an OXE network.(some call will fails,we test it already )  The configuration “OTMS and ICS R6.1 with the same OXE” is allowed only if the following two prerequisites are fulfilled: On the OTMS server, OTS and PRS have to be de-activated No OXE users will have applicative services on OTMS Except this specific case, an OXE system is managed either by an OpenTouch or an ICS 6.1 but not both simultaneously. Note: The OTBE internal OXE users are served only by the OTBE Check this Technical communication for further details. TC1629 2 Alcatel-Lucent OpenTouch R1.0 : OmniTouch 8400 ICS and OpenTouch on same OXE TCP / UDP mode  Check Topology > OXE, parameter “Transport Mode”. If no value, this means the default UDP transport mode is user. Otherwise you can force TCP or UDP. Note that 8770 1.1 put and display the mode without any issue Abbreviated Numbers by Range  Abbreviated numbers (classical or by range) are supported by OpenTouch but not abbreviated numbers by entity. Note: there is an issue with abbreviated number by range and search-by-name from an ICM user. Short numbering  Short numbers (linked to entity) is not available in OpenTouch R1.0. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 155/193 Open Numbering  If a single trunk group seizure prefix is used, the open numbering with a public network is managed directly by the OXE. The open numbering with a private network can be used only if ranges are created for any potential length of digits that could be dialled (no open numbering is allowed in the declared range). Conference - Transfer  crms00336911: When MyIC Phone user adds conference and dials an OXE user, then Ring Back Tone is heard on all sets which are in this conference  crms00353589: Display issue on OXE user IPTouch set and ICM user MyIC Phone set after transfer on ringing (Topology: network of OXE)  crms00417673: Bad display on IP touch during a transfer in communication  crms00415631: Caller info is not updated on IPTouch 4038 after the call transfer OXE user calls supervised user. Supervisor picks up the call, then he transfers the call to the supervised user. OXE callee is put on hold, then he is correctly transferred to the supervised user. But on the oxe user IPTouch screen the name of the supervisor remains. Supervised user name should be displayed instead. In case of icm users (with VHE phones) - all is ok CAC  crms00309537: Bad CAC counters when OXE incoming call is transferred to ICM user from ICM user 6.14 Management, Tools and backup 6.14.1 8770 Administration  crms00423294 UUM: identification password empty in the VHE configuration In the 8770, in the users Application: - Create a VHE with Identifcation key and password. - Validate, the creation succeeded. - Look the configuration: the field "identification password" is empty. It the 8770, in the configuration applicaton (select OT => configure) no issue  crms00409739: Supervision group can’t be created  crms00399893: it is not possible to change the Directory Number from UUM  crms00405467: You cannot use the type UA virtual when you try to create a user with the user management interface  Crms00416585 OT1.3 IT2 VHE reboot when user change lastname and firstname 6.14.2 8770 core Alarms / Event / User Management OXE Profile auto-update  After launching the 8770 on server, stop alarm server or restart 8770, this will ensure 8770 will get event from OXE  Uncheck and check alarms option from OpenTouch declaration in 8770 configuration screen OTBE: SSH access from Host to embedded 8770 windows server (backup/update) To succeed the 8770 Backup and Update from OpenTouch host. OpenTouch host needs to be able to run an SSH access toward the 8770 windows. Try an ssh connection from OT host to 8770 windows ssh [email protected] set |grep NMC_HOME Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 156/193 where XXX.YYY.ZZZ.TTT has to be replaced by 8770 IP address It should return NMC_HOME=”C:\8770” If it fails check these 3 points Windows Firewall should allow port 22 connection from host Windows service Openssh SSHD (copssh) should be running SSH key stored should be correct, you can update the allowed host (SSH key) CopSSH key update From the OT host, using root account, you must execute management_cmd updatekey (enter password of ice window account) which will copy the OT root public key in C:\Program Files (x86)\ICW\home\ice\.ssh\authorized_keys 8770 Client  Due to a “client licence” release issue, the licence is not released if you close a remote session or shutdown the PC before closing the 8770 Client. When all licences are taken you are no more able to start a new client. At this time the only known solution is to restart the server. Current workaround: close first the 8770 client and then the remote session or PC shutdown.  In case the OXE node is preconfigured during the installation time, it will be impossible to add a device type for the OXE node. This issue has been fixed in 8770 R1.1. For 8770 R1.0, If the OXE node is created after the installation, there is no issue. As a workaround, on the 8770 server execute the batch script <8770_ROOT>\bin\DMUserSyncUp.bat In 8770 Device application, it will add all OXE device types into OXE node. 6.14.3 Wireshark – how to limit disk usage  Wireshark software captures network packets and can store them on disk. In order to avoid filling the partitions on the hard drive and thus crashing the system, apply the best practice described in TG064 6.14.4 VNC Check this Technical communication for further details. TC1632 2 OpenTouch™ (OTBE & OTMS) remote connection possibility  When using a VNC session to connect to an OpenTouch system, to avoid any timeout of the VNC connection and so keep the connection opened, perform a ping of the host on itself: ping –i 30 127.0.0.1 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 157/193 6.14.5 Dynamic Log Activation  Dynamic logs activation tool : not starting: unnecessary check on OT version OT version is checked when starting dla.sh, unfortunately it is 1.2 which is checked on running OT 1.3 Delete the specific text bloc that you find at indicated lines File and lines /opt/Alcatel-Lucent/serviceability/dla/log4jscript.sh /opt/Alcatel-Lucent/serviceability/dla/find_webapp.sh scroll to line 236 scroll to line 10 Text Bloc to delete # Check OT version if ! $(grep -q "Version : 1.2." ${ECC_HOME}/version.txt); then echo "Version must be 1.2" exit 1 6.14.6 Backup - Restore You cannot use following OT backup for restoring an OT database  OpenTouch 1.1 backup  OpenTouch 1.2 backup (if OT 1.1 was initially installed then updated to OT 1.2) Those backup are corrupted and the backup log file indicate an error on ACS More info on workaround on this TC about how to redo file/folder link to get the ACS proper backup TC1785 OpenTouch R1.1 : Loss of Customer ACS data in backups (concern R1.1 and R1.1 updated to R1.2, not fresh R1.2 installation) Note that this workaround will automatically be applied when upgrading to OT 1.3  On some specific hardware platforms, the hard drive definition can change which leads the saveData and restoreData commands to detect the hard drives as usb disks. These commands exit with a “to many usb disks detected” error. It is known for DL380G7 servers but can occur on other servers… Workaround: Replace /opt/Alcatel-Lucent/serviceability/bics_applications/lib/saveFunctions by the one provided in the “Workaround” folder. Launch “ dos2unix /opt/Alcatel-Lucent/serviceability/bics_applications/lib/saveFunctions” to fix any windows conversion issue. The workaround can be supplied using a service request to technical support to get it. 6.14.7 FAX server  If it is impossible to send a fax from outlook (through exchange server) check that port 25 is not blocked by antivirus Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 158/193 7 List of Corrections 7.1 Closed OT 1.3.42 intial deilvery restriction with componant update  OXE installation through directory path in cloud deployment is not working. Refer crms00429186. Fixed in ALEDS 2.2.2 7.2 Closed OT 1.2 restrictions in OT 1.3 VIDEO  IE9 for MyTeamwork video is not supported Restriction removed since OT R1.2.000.054  My_IC_PC_SIP: add video is not allowed on scheduled conf crms00383122 MY_IC_PC would be able to join a video conference without external MCU . It's not the case. From My_IC_PC_SIP when the user add video => Video My_IC window is opened with the message “video as not been accepted” Fixed in OT R1.2.000.054  Video between IPad and VHE is delivered. Fixed in 8082 R260 1.11.0 Installation / upgrade / setup  HP server, BIOS setup There is no need to tune bios setup or to select a specific DL120G7 platform in the Linux OS setup. With OS Red Hat 5.8, the OT OS is fully compliant with the HP platform selected  OTS port not intialised properly in OT 1.2.000.054 crms00427580: Main OTS port is not updated in OT: After the fresh OTBE installation the main OTS port(3595) is not present in System services / Topology / OXE Callservers / OXE Sub Network / Physical Server / Call Server : Additional tab. Workaround: set the parameter OTS main port with the value 3595. Info : This issue is solved since OT 1.3  The OFS Backup is not done in case of upgrade through switch over (crms00408514) Fixed in OT 1.3.000.043  CMS error after migration from OT1.1 crms00401077 The services lcaproxy and omp are in the status "Service unavailable", the service cms is the status "Started", but cms is really stopped. Also the fatal error is generated in cms Workaround: restart cms service. Fixed in OT 1.3.000.041 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 159/193  Flex server : No customization scripts for external Flex server on CentOS crms00406120 It should be like OT server: a customization script should be automatically launched at first server boot. For the moment, network configuration should be done manually. Fixed in OT 1.3 : add of rpm for network/keyboard configuration. This rpm is installed during the VM gneration OTHER ISSUE SOLVED  crms00396188: Multidevices : Manager presence remains busy after a transfer from Assistant Fixed in OT 1.2.000.055  Crms00410198: Supervision defense: VHE registration on SIP server NOK after an attempt to delete the user, who is in supervision group. Fixed in OT 1.3  Crms00404312: no more "route my call to computer" in MyIC OT for OXE user (nomadic mode): After a migration, check the “multimedia option”. Its value must be set to “true” Fix in OT 1.3  Video escalation between iPad & VHE does not work (crms00387234) Solved with VHE R260 1.11.2  Dynamic logs activation tool crms00406516 : impact on routing When My location/routing (Option 8) is put in debug mode, users can't sign in anymore in CMS traces.xml all categories are in DEBUG, the CMS can't work properly when debug mode is activated. Fixed in OT 1.3  Microsoft Exchange 2007 crms00402768: A user has UM with Exchange 2K7 and configured to read e-mail through its voice mail TUI access. An e-mail is read but its title (or subnet) is not recognized and a message says "The subject is blank." Fixed in OT 1.3 7.3 Closed OT 1.1 restrictions in OT 1.2 (info updated) Initial backup  After new installation a 1st Backup is created. Then if you want to restore an older backup (i.e. from a previous release OT R1.0.100.050) you need to remove or rename the1st Backup, because the restoration always takes the most recent backup. So recommendation is to have only the backup you want to restore in the folder. This issue is fixed in R1.1.000.060 and concerns only OT R1.1 beta version  Voice mail : no OXE user access, vms directory right are incorrect and need to be changed Problem with the access to LS Voice Mail Box for OXE user: crms00389481 After installation from scratch, the directory ngvm3 can't appear in /var/data/ics-group/vms/ and also in /access/vms The directory in /access/vms is write protected and exists under root instead of vmuser,Vmgroup Workaround: cd /access/vms chmod 777 chown vmuser Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 160/193 chgrp vmgroup Info : This issue is solved since OT 1.1.000.091 and OT 1.2  crms00344805: CAC counter wrong and not released when ICM user put on hold an incoming OXE call Fixed in OT 1.2.000.054  crms00396188: Multidevices : Manager presence remains busy after a transfer from Assistant  Presence was not working properly with OT R1.1.000.060 and MyIC Phone R250 1.8.4 As from OT R1.1.000.060 and MyIC Phone R250 1.10.3, the feature can be activated Each end user needs to create the group My Favorites in MyIC desktop > MyContact application There will be 2 king of synchronization My Favorites  MyIC Mobile My Favorites  MyIC Phone 8082  crms00395601: Bad root path for MyICService log: To set up log level for MyIC service, we have to modify the file log4service.xml but the Path included in the file _MyICService.txt of the configuration log file is erroneous Workaround: The path: "%allusersprofile%/Alcatel/MPC" has to be used to find the log4service.xml file, instead of the MyICservice traces option. The path of the log file has to be specified for: XP : \WINNT\Temp\Alcatel-Lucent\MPC Vista and W7 : \Windows\Temp\Alcatel-Lucent\MPC Solved in OT 1.2  crms00383122: My_IC_PC_SIP: add video is not allowed on scheduled conf It's better than in the last release (OT1.2.000.020), add video is no more refused but My IC PC stay in "waiting for participant" and a popup is displayed: VOIP can't be initialized Solved in OT 1.2  crms00344805: CAC counter wrong and not released when ICM user put on hold an incoming OXE call Solved in OXE J2.501.19a 7.4 Closed OT R1.1.60 restrictions in OT R1.1.80 (info updated) MyIC Desktop (OXE User) Nomadic IP  If 4645 present, MYIC PC cannot receive / imitate call in Location = My Computer (this is due to profile of 4645 voice mail expected in OT configuration):crms00382712 Fixed in OT 1.1.80  Issue Doc conversion slowness, and sometimes PDF doc does not display all pages (crms00375094) Fixed in OT 1.1.60 7.5 Issues solved by VHE R260 1.11.0 and 1.12.2 R260 1.12.2: support of change of local OT user password from MyIC Phone 8082 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 161/193 1-148855549 crms00440279 VHE user with UM exchange 2010 erase the voice message all email are erased in box crms00398498 crms00418622 [ChangePassword] Loss of webservices when using some special characters crms00419057 crms00418622 Password to block the 8082 sets R260 1.11.0 : Generic issue corrected crms00431839 crms00432202 "CLISettings: Permission denied" message at SSH login crms00403787 crms00428564 Add a video defense mechanism in Presentation part crms00407842 crms00419047 No audio on VHE phone after VGA crms00407890 crms00428446 Phone can't stop ringing on alpha test crms00408771 crms00429552 VHE Enhancement:Set the code dump file size limite to unlimited crms00409921 crms00416679 VHE display "anonymous" on incoming call crms00412383 crms00429135 No ring back tone on 8082 using Remote Call Control from MY IC crms00414308 crms00419051 audiohelp command is not clean crms00415002 crms00425360 MyIC Phone R260: cannot change the volume on Plantronics BT crms00415630 crms00418800 [Alpha-TEL]VHE continuously reboot by crash, after switch second crms00416082 crms00420601 On 8082 Icons missing on suppresion popup crms00416096 crms00426775 8082 R260: mevo log: no indication of day reception when > 24h crms00416246 crms00421208 alpha OT : loosing my voicemails crms00417690 crms00417994 [OXE] Dialpad evolutions: no background on call buttons crms00418041 crms00422515 OT1.3: VHE does not change after reset mac address crms00419070 crms00419733 [video]When VHE is in local video, start video escalation, the crms00419173 crms00422557 MyICPhone:PCSync: during synchronization, device crashed (ictouch) crms00419242 crms00421513 [My IC Phone]The display of nigociation icon is no change even if crms00419569 crms00429000 [R260 video]VHE show wrong screen and can not escalation video crms00419639 crms00423438 [ergo] Top shadow missing in homepage standard crms00419833 crms00421627 no more photo displayed on VHE sine uppgrade in OT1.3 crms00420047 crms00425742 [ICE] Progkeys : Impossible to add a shortcut by "Searching local contact” crms00420540 crms00425986 VHE video between two physical site not good crms00420810 crms00426322 Call back is made for the first number of the contact only crms00420917 crms00422561 MyICPhone:R260 M/A: unable to remove numbers from white list crms00421502 crms00425853 "knltop" command can not be used in locked software version crms00421953 crms00423863 Supervision : if supervisor picks up the call after the supervised the crms00422819 crms00423766 [VHE] [OT] IM tchat messages are logged in VHE comlog and are crms00423483 crms00423773 [ergo] Search - the button Ok is not always validated crms00424702 crms00428981 Blackscreen when adding a new participant (conference creation) crms00424844 crms00427929 Support of new TouchPanel driver v5.x crms00426195 crms00429001 [OT][MyIC Phone][Video]: black video screen on VHE when crms00426215 crms00427292 G722DynPL - Codec negotiation fails when pre-annoucement is crms00426289 crms00421208 alpha OT : call log populated by only last week events Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 162/193 crms00427093 crms00427204 MMI display of "Running Mode" for "NOE Enable" feature crms00427194 crms00428801 [OT][VHE][Conference]: black screen on VHE when adding a third crms00429146 crms00429147 can not stop ring crms00429219 crms00429281 [Conference] Add-hoc conference works abnormal crms00429277 crms00429946 [comlog] After MY IC Phone reboot, comlog is empty crms00429887 crms00429960 Improve Telephony application robustness crms00430196 crms00430218 [Upgrade]:Upgrade from pre-release 01.012.0.001 to 01.012.0.013 R260 1.11.0 : correction on translation crms00419190 crms00424988 [Amercian English] [My IC PHONE] [add-hoc conference] drop crms00419211 crms00423815 [American ENGLISH] [MyIC Phone] [Software Option/Setting] crms00419217 crms00421453 English en french in same pop up on 8082 crms00419902 crms00421129 [ITalian] [My IC Phone][Outgoing call] "preferiti" instead of " crms00419911 crms00427513 [ITalian] [My IC Phone][incoming call] " ChinCors" for on going is crms00419915 crms00421136 [ITalian] [My IC Phone][dial by name]use "ricerca senza resultati" crms00419916 crms00427516 [ITalian] [My IC Phone][Forward] " casella vocale" instead of crms00419922 crms00421158 [ITalian] [My IC Phone][transfert] "in attesa" instead of "tratenutta" crms00419925 crms00427522 [ITalian] [My IC Phone][Multi device selection] Word used to stop a crms00419928 crms00427524 [ITalian] [My IC Phone][Voice mail consultation/Visual VM]use crms00419936 crms00423810 [ITalian] [My IC Phone][Voice mail consultation/Visual VM] several crms00419940 crms00423404 [ITalian] [My IC Phone][Setting] Salvaschermo instead of crms00419943 crms00423351 [ITalian] [Multi device][Multi device selection] Mei dispositivi office crms00420140 crms00427526 [PORTUGUESE] [My IC Phone][Outgoing Call] "Eliminar" button crms00420141 crms00427530 [PORTUGUESE] [My IC Phone][incoming call] ChamDec it is not crms00420142 crms00427532 [portuguese] [My IC Phone][notification] abrevation not very crms00420147 crms00427533 [portuguese] [My IC Phone][Multi device selection] "Comp.Pess" crms00420150 crms00423357 [portuguese] [My IC Phone][Multi device selection]"predefinição" crms00420160 crms00425004 [deutsch] [My IC Phone][notification] several label not translated crms00420166 crms00427536 [deutsch] [My IC Phone][incoming call] Text is "Ext. Anr Ende" crms00420168 crms00423364 [deutsch] [My IC Phone][notification] wrong translation for new crms00420441 crms00427539 [deutsch] [My IC Phone][all] several wrong traduction crms00418288 crms00420999 OT-PreBeta: 'Aucune communication' vs 'Aucun Message' crms00414937 crms00416655 OT Pre-Beta: 'Tout supprim' seems not formatted right crms00417657 crms00420736 English error message in a French window on VHE crms00417659 crms00420997 English text in a French VHE: reboot in progress crms00418290 crms00420993 OT Pre-Beta: Adding a contact displays a error. The sentence is crms00416036 crms00426957 8082 my ic phone date format in Chinese cannot display properly Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 163/193 7.6 Changes in OT R1.3.000.043 FLEXLM 1.3.000.051: OT virtualisze with external FLEXserver a script runs regularly to recover the dongle if CentOS does not se it anymore as pluggued 1.3.000.051 solves a bad firewall setup in Flexlm 1.3.000.050 OXE J2.603.20i : solve DTMF sending for outgoing OXE call 7.7 Customer issues solved in OT R1.3.000.042 Component 40x8 TSref 1-145325003 CR.id crms00425302 8770 8770 1-143457971 1-142715891 crms00414945 crms00411790 8770 1-142876071 crms00412558 8770 8770 1-146106631 1-145382236 crms00427185 crms00424117 8770 8770 8770 ecc 1-142345531 1-142332291 1-141995401 1-134133614 crms00410716 crms00410383 crms00409108 crms00374533 ecc 1-136416841 crms00384884 ecc 1-134204162 crms00374608 ictouch 1-139155271 crms00398019 ictouch 1-137293315 crms00388008 myic_desktop myic_desktop 1-141102601 1-143140388 crms00405375 crms00413628 OT OT OT OT OT 1-146096681 1-142345531 1-146163590 1-146160415 1-142382610 crms00427236 crms00410716 crms00427512 crms00428035 crms00411044 OT 1-144827091 crms00421067 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved Headline [SBD-OBS] OTBE - Calling blind transfer fails in multicodec configuration 40x8/VHE OT Accounting Tree Structure Recursive 8770 R1.2/OT configuration/randomly, no data displayed in the grid The importation adds an adminnmc sub-level for each report type (accounting, audit, Traffic observation?) 8770 R1.3/Web directory fails to start 8770 R1.3/Performance/license problem after restore with rehosting/1-145382236 UUM is out of sync with OT and OXE for some users OT restore failed (with Omnivista8770) iPad : No hang on possible on conference call back OT1.1 / MYIC-PC running on Windows7 / Search Bar information not correctly visible - display contrast. Incoming call lost after overflow to voice mail (backtrace myStop_VMU_Timer) OT1.1 / Using IVC MyTeamwork Video client, bad translation : Pav? ? touches ouvert OT1.1:OFS database not restored after OT upgrade on inactive partition no automatic update for the MYICM on Android if public@ different as private@. OT 1.2 Supervision feature incompatible with skin Pep OT: Beta 1.2 / Omnivista-8770: SIP device unavailable after dissociation from an OT User ALU Outlook extension cannot be activated (1.3.0.30) UUM is out of sync with OT and OXE for some users 8770 R1.3/Performance/license expired/1-146163590 BetaSwisspro: OTC iPad battery is running out very fast OTC Ipad - language of an invitation from ipad otc client is wrong OTMS R1.3 : DCS external shared folders diseappers after each upgrade TC1798 Ed05 page 164/193 OT 1-138433481 crms00393827 OT OTC_iPad 1-146040401 1-146160249 crms00427085 crms00428659 OTC_iPad OTC_iPad OTC_iPad oxe 1-145395331 1-141236122 1-145153410 1-136603631 crms00423804 crms00405913 crms00422658 crms00395230 Serviceability SIPS 1-142128551 1-141952821 crms00409616 crms00409355 OT 1.1 : VHE Call to mobile mexico: the number 1 of local number is removed => call failed. No Email Notification after a new voice message OTC crash with iPAD IOS 6.1.2 A6X Chip after activating video OTC iPad : some crash running OTC 1.2 on Ipad 4 iPad : OTC crashes during audio call OTC iPad : crash during audio call OT 1.0.1 : Oxe user forwarded to his VM, VHE call the oxe user and get his own VM Lost of the OT user right day after a hotfix installation. OT: 8770: SIP device unavailable after dissociation from an OT User 7.8 Customer issues solved in OT R1.2.000.055 Component eSR 1-142175987 CR Id crms00409824 Headline 8770-Backup OpenTouch FAILED 1-143368724 crms00414584 OT1.2.52+ ACS 6427 from OT teamwork bridge dialout an external number: permanentl ringing 1-142611761 crms00411700 1-143286383 crms00414274 Reset Mac address and change key impossible at same time. Partition /var/data/postgresql5433 is full 1-144395811 crms00419110 MyIC Phone 1-139513221 crms00398009 OT:8770: LDAP Directory: Value of the ?Telephone Number? attribute name parameter is limited to 22 characters. presence isn't displayed for favorite user on vhe MyIC Phone 1-141186891 crms00405669 8082 R260: no result in local contacts on search MyIC Phone 1-141425805 crms00406810 MYIC 8082 switch device. MyIC Phone 1-142346613 crms00411692 8082 langage display. MyIC Phone 1-142607921 crms00411439 Annoying pop-up on 8082 MyIC Phone 1-143225181 crms00414382 Icons to play voice message are not shown by default. 1-139155271 crms00398019 1-142735270 crms00411886 OT1.1:OFS database not restored after OT upgrade on inactive partition failed to upgrade OXE during OTBE migration to 1.2.0.53 1-143804609 crms00415890 1-144590666 crms00419948 UDAS 1-142100565 crms00409527 OT1.2 : on DL380 G8. usb disk are not seen by OpenTouch scripts Deployment of VHE and VLE in dynamic IP addressing is not easy search by name doesn't give results VAPP 1-142489281 crms00415396 OT R1.1 PPR/VMMC problem on 8082/invalid session 8770 ACS CMS CMS CMS Serviceability Serviceability Serviceability Serviceability Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 165/193 VAPP VAPP 1-143211601 crms00413800 Unified Messaging : Unable to read Voice message 1-143804716 crms00415902 Web admin 1-140963220 crms00404889 OT1.2 : impossible to read voice mail message for one end-user Java error when editing AA application tree 7.9 Customer issues solved in OT R1.2.000.054 Product TSref CR.id 8770 acs Ecc 1-135729551 1-141425810 1-140804183 crms00381376 crms00406633 crms00404139 ictouch 1-140882461 crms00404526 ictouch 1-140950761 crms00404918 ictouch ictouch 1-140984011 1-141102601 crms00405302 crms00405375 ictouch 1-141174394 crms00405668 OAMP OAMP OT 1-138443494 1-138484271 1-124308417 crms00392935 crms00393229 crms00330751 OT 1-128222907 crms00348736 OT 1-130746175 crms00359740 OT 1-136163341 crms00383046 OT OT OT OTC_iPad Serviceability 1-136163576 1-138295581 1-138755633 1-141236091 1-140928531 crms00383306 crms00394258 crms00394989 crms00405910 crms00404728 Serviceability Serviceability 1-140699948 1-139841835 crms00403669 crms00399383 Serviceability 1-141197581 crms00405998 Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved Headline Issue on new account when connecting with this new login and launching performance application Error when scheduling a conference in Outlook 2010 loglevel command does not work for imap4fe component. OT1.2.00.040 user on prebeta impossible to read voicemail list empty OT R1.2.00.040 Pre beta Colombes Window "add budy ...failed" when 8082 M/A restart Beta OT1.2 Pb Video on VHE2 position (green screens) OT R1.2 Supervision feature incompatible with skin Pep 8082 R260: error in "Select one of the lastest entries" label confusing label for OXE declaration node in OT config Translation issue for voice mail field in 8770 Not possible to make conf call from MyIC ACS federation no erreur msg when creating an ICE user, if it already exists in another ACS BDD OpenTouch // Manager Assistant / call log differ on both sets after receiving call with hidden dir Serviceability OT R1.1: request to be able to install a HotFix on inactive partition Serviceability OT R1.1: request to be able to clone active to inactive partition installation of OTBE fails with deployment tool My IC SIP using TCP or UDP iPad : search in local contact does not work /etc/profile modification has impact on command display like "service iced stop" crash of system in case of logzipper command OTBE R1.2 : after OS upgrade kvm module is not installed : no more virtualization possible Error during OTMS 1.2 installation services are not started TC1798 Ed05 page 166/193 8 Focus on This chapter is aimed at presenting more in details some topics of OpenTouch. 8.1 Licenses 8.1.1 Overview (updated with OT R1.3 news) OpenTouch solution is sold through a simplified generic model based on : Server base / options Users licenses / options (since OT R1.1 you have new device licences : anymobile, tablet) Devices licenses / options Additional bill of material (chassis, legacy boards, …) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 167/193 8.1.2 License control : by FLEX OpenTouch license control of the ICE Core part is based on Flex licensing technology. Software licenses are described in a license file, protected by an encryption mechanism. As of openTouch 1.3, One sigle vendor key is used: ALCFIRM flex key to encrypt license items controlled by ICS/ACS and Genesys components. To ensure the license file cannot be re-used on another physical platform, a specific hardware identifier is used: a MAC address or a Dongle. This identifier is also encrypted in the license file. 8.1.3 Flex Deployment For OpenTouch 1.3 offer and OXE-V offer, the table below sum up the license deployment for 6 Topology. Topology OT/FLEX deployment 1 OXE CPU no OT Control Mode (.ice License) No, pure physcial OXEdepoyed without OT Control on OT 1st Mac@, Feature granted by INCREMENT tag, no Node Lock, OTID Oxxxxx : unused deployment file alchostid.cfg published on eBuy (but not required for system) Control on Dongle 3 Feature granted by INCREMENT tag, OTBE OTBE R1.3 no Node Lock, OTID Oxxxxx : unused Appliance deployment file alchostid.cfg published on Dongle eBuy (but not required for system 2 OTMS Appliance MAC 4 OXE-V FLEX 5 OTMS-V FLEX 5 OTBE-V FLEX OTMS R1.3 only external FLEX No, since no OT depoyed Control on Dongle (external FLEX) OTMS-V Feature granted by INCREMENT tag, R1.3 Node Lock OTID Oxxxxx : used external deployment file alchostid.cfg published on FLEX eBuy ( required for system) Control on Dongle (external FLEX) OTBE-V Feature granted by INCREMENT tag, R1.3 Node Lock OTID Oxxxxx : used external deployment file alchostid.cfg published on FLEX eBuy ( required for system) OXE deployment OXE Control Mode 8770 8770 control mode deployment OXE on OXE CPU ID 8770 or 8770-v On handle4760 of OXE license OXE on OXE CPU ID 8770 or 8770-v On handle4760 of OXE license In OTBE on virtual CPU ID (Kxxxxx) present in .ice license dedicated to OTBE 8770 or 8770-v On handle4760 of OXE license OXE-V on virtual CPU ID (Kxxxxx) present in .ice license dedicated to OXE-V 8770 or 8770-v On handle4760 of OXE license OXE-V on virtual CPU ID (Kxxxxx) 8770 or 8770-v On handle4760 of OXE license OXE-V on virtual CPU ID (Kxxxxx) 8770 or 8770-v On handle4760 of OXE license Note for duplicated OXE only active CPU perform the CPUid check (check on CPUid or kxxxx) duplicated OXE on a physical CPU rely on CPUID of the CPU duplicated OXE on a virtualized CPU, use same Kxxxxx for license control as the main OXE Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 168/193 Example of license control on OTBE-V: external Flexserver serving one ore more OT In OTMS-V keep existing alcotuc.lic and copy alchostid.cfg Take care of alchostid.cfg file format: only one line, no extra empty line, carriage return Other known use case OTMS with MAC Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved OTBE with Dongle TC1798 Ed05 page 169/193 8770, OXE and OT Licenses can be checked from 8770 interface 8770 internal license: menu Help > About OpenTouch OXE: Software Package 8.1.4 ICE Core licence file description (with OT R1.3 update) Each license item includes the feature name, the vendor name, the license version (must be ICE Release=5 OpenTouch R1.3), permanent state or expiration date, the license value and the digital signature. Note that integrated Genesys license has an expiration date = jan-00 meaning no expiration date. The following table gives for each commercial package the associated FlexLM license generated by Actis / ELP. OpenTouch R1.3 new license OpenTouch R1.2 new license OpenTouch R1.1 new license OpenTouch R1.0 original license Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 170/193 Flex license name ICE_RELEASE tserver_sdn Value 5 Number of hard phone 8082 * 4 + Number of MyICDesktop + Number of Off-site mobility option (a minimum value is required if no ICM user are present) gvp_ports Calculated gvp_tts_ports Calculated mlsnmp 1 if Performance and alarms site option is selected. ACS_AMDS removed ACS_AMDS_PORTS removed 1 if conferencing user options is greater than 0 Calculated 1 if desktop user option is greater than 0 OR if conferencing user option is greater than 0 Calculated based on desktop users if desktop option is greater than 0. Calculated 1 1 if conferencing user options is greater than 0 1 if conferencing user options is greater than 0 1 1 1 if desktop user option is greater than 0 OR if conferencing user option is greater than 0 Calculated 0 (Not used in ICE R1.0/R1.0.1/R1.1) 1 1 1 1 if desktop user option is greater than 0 50 1 Total Number of users (OXE + ICM) Number of users with conferencing options Number of users with desktop option Number of encryption options Number of ICM users ACS_APPLICATION_SHARING ACS_APPSHARING_PORTS ACS_AUDIO_PORTS ACS_CALENDAR_PRESENCE ACS_CONFERENCE_RECORDING ACS_CONFERENCE_SCHEDULING ACS_CONTACT_LISTS ACS_CUSTOMER_BRANDABLE ACS_FILE_ATTACHEMENT ACS_G729_AUDIO_PORTS ACS_HIGH_AVAILABLILTY ACS_OPERATOR_CONSOLE ACS_PBX_PRESENCE_AGENT ACS_VIDEO ACS_WEB_PRESENTATION ECCSTART ICE_AUTOMATED_ATTENDANT ICE_BUSINESS_COMMUNICATION ICE_CONFERENCING ICE_DESKTOP ICE_ENCRYPTION ICE_ICM_ACU_USER ICE_IMAP_SESSION ICE_MESSAGING ICE_NUMBERTTSLANGUAGES ICE_OFF_SITE_MOBILITY ICE_OFF_SITE_MOBILITY_ANDROID ICE_OFF_SITE_MOBILITY_ANY ICE_OFF_SITE_MOBILITY_BB Number Number Number Number Number Number Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved of of of of of of users with messaging option TTS languages option user with off-site mobility option OT user with right to use android OT user with right to use anymobile OT user with right to use BB Vendor ALCFIRM Genesys ALCFIRM Genesys ALCFIRM Genesys ALCFIRM Genesys ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM TC1798 Ed05 page 171/193 Flex license name ICE_OXE_ACU_USER ICE_TABLET ICE_USER_DEVICE_ASSOCIATION ICE_EMAIL_READING OAMP_ALARMS OAMP_CONFIG OAMP_KPIPERF OAMP_SECURITY OAMP_VOIPPERF PCXTYPE Value Number of OXE users Number of OT user with right to use iPAD Total number of devices that can be associated to the total of users (1000 for OTBE 500, 3000 for OTBE1500 and OTMS 1 >0 if Performance and alarms site option is selected or if Monitoring service option is selected >0 >0 if Performance and alarms site option is selected or if Monitoring service option is selected >0 if encryption site option is selected. >0 if Performance and alarms site option is selected or if Monitoring service option is selected 1 Vendor ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM ALCFIRM 8.2 Contact and directories Directory search with multiple phone number for a contact  Quick setup overview On OT configuration, Select System services > Telephony >Search >Search Attribute: define the kind of attribute to retrieve in a search Directory Search: define search attribute Directory: for each directory server, fill LDAP phone type corresponding attribute Merge directory  A study of merge policy has to be performed first to identify the synchronization criteria and the directory priorities.  Update the syncUid parameters of each directory concerned by the merge process System Services > Application > telephony > Search > directory (Tab SynchUid) Here the synchronization will be based on 12 characters of name+ 12 character of givenname + phone number. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 172/193  Activate Merge and define directory priorities System > application > telephony > Search > directory search (Tab Merge) Add each directory concerned by the merge in correct order. Here LDAP Alcanet is processed after phonebookDir and replaces phonebooDir value if similar contact found  Old Restrictions solved force merge synchronization flag exist now During merge, the search from client no longer fails during fist merge processing If LDAP has too many entries, the merge process can fails 8.3 Telephony and routing ICM users’ outgoing call handling  Dialling Rule In ONE dialling rule a single OmniPCX Enterprise trunk group seizure prefix can be specified. All outgoing call from ICM users, starting by this prefix, will be sent to the OmniPCX Enterprise for further treatment. If this dialling rule is affected to a MyIC Desktop device, this prefix will be automatically added in case of outgoing call, if the dialled number exceeds a minimum length. In case the dialling rule is allocated to a MyIC Phone device, the prefix mentioned will only be added if the outgoing call is done via search-by-name or the local contacts. If the dialled number is made directly by the end user, it will be the responsibility of the end user to add the trunk group seizure prefix when necessary. Note: Setup in the ‘area code’ parameter the appropriate value if your country requires ‘area code’ information, otherwise leave the parameter empty. It is also possible to setup an exception to the general rule which specifies that the trunk group seizure prefix has to be added as of a specified number length. The prefix won’t be added to any number exceeding the ‘minimum length’, if this number starts by ‘exception start’ and has a length equal to ‘exception length’ (a length of ‘0’ meaning any length)  Outgoing call analysis performed by the ICM sub-system When a MyIC Phone performs an outgoing call, the called number is analyzed by the XS, using the following sequence: 1. If the called number exceeds the specified length and the call has been issued via search-by-name or the local contacts, the trunk group seizure prefix (specified in the dialling rules managed in the device) is automatically added by the phone. 2. XS checks within all dialling rules (and not only the one specified in the MyIC Phone management) if the called number starts by the specified trunk group seizure prefix. If yes, the call is forwarded to OmniPCX Enterprise system. If not : Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 173/193 3. XS checks if the called number corresponds to a local ICM user. If not : 4. XS checks if the called number belongs to any of the ranges managed on ICM side. If yes, the call is forwarded to the OmniPCX Enterprise. 5. If not, the number is considered as a wrong number When a MyIC Desktop performs an outgoing call, the called number is analyzed by the XS, using the following sequence: 1. If the called number exceeds the specified length, the trunk group seizure prefix (specified in the dialling rules managed in the device), is automatically added by MyIC Desktop (except for exception from this dialling rule) 2. XS checks within all dialling rules (and not only the one specified in the MyIC Desktop management) if the called number starts by the specified trunk group seizure prefix. If yes, the call is forwarded to OmniPCX Enterprise system. If not : 3. XS checks if the called number corresponds to a local ICM user. If not : 4. XS checks if the called number belongs to any of the ranges managed on ICM side. If yes, the call is forwarded to the OmniPCX Enterprise. 5. If not, the number is considered as a wrong number Call-back and Call Completion Call-back Request (CBR): the caller can request it at anytime; the callee is notified about a request of call-back and can choose to call back the caller or not. Call Completion on Busy State (CCBR) or No Reply (CCNR): the system decides when an automatic call-back must be offered; the caller then requests for automatic call-back and the system will try to automatically establish a call between caller and callee, as soon as they are available. There is no notification. Notes: For ICM users, the called device is the device which originally requested the automatic call-back, whatever the current Location. CCBS occurred only when the callee is “fully” busy (OXE or ICM). This happens if all lines of the devices relative to the current location (see “Route my calls to”) are occupied … unless the “consider the user busy if one device is busy’ parameter is activated for the callee and one line of the devices relative to the current location is occupied. MyIC Desktop SIP Softphone has an infinite numbers of lines, so it is never seen busy. CCBS is not proposed when the callee is forwarded on busy. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 174/193 Multidevice Routing: OpenTouch user The active routing can be either Selection of user devices. Forward to Voice Mail Forward to a MyIC Phone User Other number usage: It can be an external number do not forget to define properly the other number in MyIC desktop or MYIC Phone other= Outgoing Call Prefix + ISDN Number Example: 00612345678 Display after setup is only correct on MyIC Phone or a local number (DECT for instance) Dialling from MYIC desktop, Do not forget to specify the device used for call initiated from MYIC Desktop interface Routing vocal application A TUI access allow end user to change its current routing Welcome prompt gives current routing information Choice 1: activate default profile Choice 2: forward to voice mail Choice 3: forward to a destination Choice 4: cancel mobile ringing Routing capability per device Feature MyIC Desktop Tablet VHE Mobile TUI Display Active routing Yes Yes Yes Yes No Modify Active routing Display current profile Profile activation Profile configuration Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes No Yes Yes Yes No Partially Yes Yes No OT R1.0 clients Forward to other Yes No No No Note: 4008EE/4018EE devices use TUI only Busy state analysis  Description The user is considered busy as soon as the number of device/mobile line is reached Configuration: 3 parameters Number of Device lines When the device number of line is reached, user is in busy state Mobile priority and Mobile number of line Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 175/193 When the mobile is involved in a call, you can force the busy state as soon as the number of line in mobile is used  Configuration interface By administrator, using 8770 config/device module By end user, Using MyIC desktop or My Profile web page 3PCC: My IC Desktop call control There is a change in OpenTouch R1.2 In remote call control, MyIC desktop can trigger the answer handsfree on the the MyIC Phone To use this feature, the SIP profile of the VHE must be set to MyIC Phone 8082(V260 and higher  Your Routing profile includes When receiving a voice call , the MyIC Desktop popup has a 2 VHE and PC choice “Phone icon” or “PC icon” if you click on the green phone (marked in RED circle)  = > audio call will be on MyIC Phone,  if you click on the PC icon (marked in BLUE circle)  audio call will be on the PC, Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 176/193  Your Routing profile has PC only  Your Routing profile has VHE only When receiving a call , the MyIC desktop popup with Only a green phone icon (or video if a video call received) if you click on the green phone  audio call will be on PC, When receiving a call, the MyIC desktop popup has “no PC icon” if you click on the green phone audio call will be on 8082 MyIC Phone in hands free  Your Routing profile has dial from VHE MyIC Desktop outgoing call handling if you click on the green phone, audio call will be on 8082 MyIC Phone in hands free Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 177/193 8.4 Video - Visual collaboration This chapter is dedicated to video within OpenTouch R1.3 solution (same as OT 1.2). It presents the equipment supported, some information relative to Multipoint Control Unit (MCU) required for continuous video presence some video use cases, some deployment recommendations. Compared to the ICS 8400 suite, OpenTouch R1.3 solution brings new video elements: an embedded video MCU in the OT server. In OT R1.3 embedded MCU support also the active talker video switching a new video client embedded in the MyIC Desktop a native support of 3rd pardy video equipment : LifeSize a video capability on Deskphone : MyIC Phone 8082-V2 note that MyTeamwork video on Internet Explorer 9 is working There are four important points to take into account No Video interoperability between Standard user (OXE) and OpenTouch user (ICM), except when using scheduled video conference No Video on MyIC phone 8082-V1 Your network should allow the video traffic : thinks about the bandwith needed which for video is larger than voip. 8.4.1 Video Acronym 1PCC: First Party Call Control 3PCC: Third Party Call Control ACS: Alcatel-Lucent Collaboration Server AVP: Audio and Video profile, configuration for audio/video and audio call with My TW CAC: Call admission control DSP: Digital Signal Processor Drop video: Drop video is the capability to stop emission and reception for video and keep audio in the communication ESS: Enterprise SIP Server EVC: External video Client (for example LifeSize device) GOP: Group of Pictures GVP: Global Video Processing HD: High Definition ICM: Instant Communication Manager ICS: Instant Communication Suite IVC: Integrated Video Client for MY IC (My Teamwork with internet explorer) MCU: Multipoint Control Unit MS: Media Server MyTwk: My Teamwork Client P2P: Peer to Peer PIP: Picture in Picture RTP: Real-time Transport Protocol RTP: Real-time Transport Protocol Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 178/193 SBC: SD: SDP: SIP: SOC: SSL: Session Border Controller Simple Definition Session Description Protocol Session Initiation Protocol System on Chip Secure Sockets Layer 8.4.2 Visual equipments and version supported LifeSize: for ICM user only LifeSize can be deployed as a meeting room OT user a personal video device version 4.11.8 and 4.11.12 have been tested MyIC Desktop with video Only for ICM user MyTeamwork for ICM user or OXE user MyIC Phone: for ICM user Version R260 Need MyIC Phone 8082-V2 equipped of Webcam Logitech C920 OpenTouch Conversation on iPad for ICM user Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 179/193 8.4.3 Video equipment interface details LifeSize: using Lifesize remote control you can establish auio or video call MyIC Desktop do not forget to play video in odrer to send video flow MyTeamwork Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 180/193 8.4.4 Video Matrix Consult the OT 1.3 feature list about which video use case are supported 8.4.5 Ad hoc video conference Definition No preparation is needed. It is an unscheduled conference. This type of conference is initiated: by selecting several contacts through a user interface (e.g. MyTeamwork) and pressing call button (e.g. Phone). or by calling additional people during a communication. No conference identification is provided and needed. No conference resource is reserved. They will be picked up from a pool of resources if some are still available. If not then the conference will not be established. 8.4.6 Schedule video conference Definition A scheduled conference is a conference organized in advance where: A date, an hour and a duration are defined, Resources (audio, data and/or video ports) can be booked, Conference identification (access code) is generated. A phone number (and/or an URL) is configured by the administrator to join the conference bridge An email invitation is created with the previous information destined for all attendees. Attendees have to join the conference using the phone number (and/or the URL) and the access code received in the invitation. When the conference is ended the conference identification (access code) is no more valid. For example, MyTeamwork provides this type of conference. We consider as basic use case, users joining the scheduled video conference by dial in (all use cases) or click on URL except from a Video Equipment (meeting room or personal device). We do not consider as basic use case user joining the video conference by dial out or click in the conference list from MyTeamwork. Note: MyTW IVC & EVC Standard User can participate to scheduled video conference with internal or external MCU. 8.4.7 Video usages 8.4.7.1 LifeSize usage There is three ways to involve a LifeSize equipment in a audio/video communication: - Placing a call from the device, using the built-in interface of the LifeSize equipment (from the remote control or from the LifeSize Phone), - Placing a call from the MyIC Desktop client (Remote Call Control from MyIC Desktop) - Placing the call from MyTeamwork client (Remote Call Control from MyTeamwork client) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 181/193 There is two way to receive call on a LifeSize equipment: - Receive a call that was initiated from other devices, including MyIC Desktop - Receive a call that was initiated from a MyTeamwork client There is three way to involve the LifeSize equipment into an ad-hoc conference: - Ad-hoc conference initiated from built-in interface of the LifeSize equipment, - Ad-hoc conference initiated from MyIC Desktop client, - Ad-hoc conference initiated from MyTeamwork client, There is three way to involve the LifeSize equipment into a “scheduled” conference: - Dial-In from video equipment - Join the conference using the conference menu and request to involve LifeSize equipment for video, - Join the conference using the URL received in a email and request to involve LifeSIze equipment thanks AVP 8.4.7.2 MyIC Desktop calling OT user with a LifeSize MyIC Desktop can now call directly a LifeSize (since LifeSize is an OT user device) MyIC Desktop View LifeSize View 8.4.7.3 Initiate a video call from MyIC Desktop Video call from search by name  Operation I search a person, Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 182/193 Then, I click on video icon (*) from ID card (*) video icon is enabled only if the called party is an OpenTouch user (with or without a plugged camera)  Result Audio  & Video  with MyIC Desktop Video is always powered by embedded video MCU Media escalation: add Video to an existing audio call  Operation I dial a number from deskbar, I establish audio call I add video  Result Audio  & Video  with MyIC Desktop Video is always powered by embedded video MCU Video call from Buddylist  Operation Launch MyContact I click on video icon associated to a contact of my buddylist  Result Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 183/193 Audio  & Video  with MyIC Desktop (video powered inside MyTW UI) Audio  & Video  on LifeSize equipment 8.4.7.4 Initiate a video call from LifeSize equipment Video call from LifeSize  Operation I dial a number from LS Phone or by using UI with remote control  Result Audio  & Video  with LifeSize equipment 8.4.7.5 Initiate an ad hoc video conference from MyIC Desktop Media escalation: add Video to an existing audio conference  Operation I initiate 2 audio calls, I click on “Conference icon” I escalate to video by clicking on ‘add video” action menu  Result Audio  & Video  with MyIC Desktop Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 184/193 Video conference from Buddylist  Operation I select several contacts of my buddylist and I click on “video conference” action menu  Result Audio  & Video  with MyIC Desktop (video powered inside MyTW UI) Audio  & Video  with LifeSize equipment Video conference from the conference interface  Operation I click on video icon associated to a contact of my buddylist and I add another participant (actions done inside MyTW UI)  Result Audio  & Video  with MyIC Desktop (video powered inside MyTW UI) Audio  & Video  on LifeSize equipment Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 185/193 8.4.7.6 Join a scheduled conference – Dial out from the bridge Join scheduled conference from URL link  Operation I click on URL of the bridge (received by email)  Result Audio  & Video  on my desktop (video powered inside MyTW UI) Audio  & Video  on my video equipment Join conference from Teamwork interface  Operation I am a conference leader; I can join directly thru Teamwork UI  Result Audio  & Video  on my desktop (video powered inside MyTW UI) Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 186/193 Audio  & Video  on my LifeSize equipment 8.4.8 ACS Administration 8.4.8.1 An internal MCU is configured in ACS. 8.4.8.2 An external MCU is configured in ACS. 8.4.8.2.1 ACS Administration There is a default setting on system level in the ACS admin for using either GVP video switching or the (if present) RadVision video MCU. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 187/193 Video settings page in ACS admin with the added internal/external video MCU settingIf the administrator wants to use the external MCU by default, you have to check the parameter “Use External Video MCU by default”. 8.4.8.2.2 Video setting by the user A second setting is per scheduled or reservationless conference and can be set by the user. The default value is retrieved from the setting done on system level by the admin. The user can change the setting to either use the GVP for video or the external RadVision video MCU. If the external video MCU is selected, the selection of the video profiles will be enabled. With this version, if you want to use the external video MCU, you have to select the option “Use external video MCU”. Video settings tab for scheduling a conference showing the new internal/external video MCU setting Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 188/193 8.4.9 Video engineering rules 8.4.9.1 ITU-T G.1050 – Profile A, B & C IP network  End to end impairments levels: 8.4.9.2 Multimedia communications with MyIC Desktop  Video quality acceptability versus IP impairments: The video quality is acceptable up to 0.25% of packet loss (to be compared to 3 or 4% for acceptable audio quality). This use case is then not compliant with “managed” IP network impairments (packet loss up to 2%) and “unmanaged” IP network impairments like Internet (up to 20%)  Refer to the previous chapter regarding ITU-T G.1050 Restrictions: Multimedia home working use case not recommended Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 189/193 8.4.9.3 Multimedia conference with MyIC Desktop  The “Video Quality Acceptability versus IP impairments” results and restrictions of § 6.2.4.2 apply to this use case, once the conference is established. This is due to the GVP behaviour (video switching with NO video decoding and coding). Note: in the current release, the video switch time appears too high (5s). As a consequence, the video switch seems to be not really linked to the active speaker. Subjective tests highlight that 3s is a correct value. This point will be addressed in the next release. 8.4.9.4 MyIC Desktop / GVP video engineering rules / restrictions  Correct bandwidth has to be available: H264 Low Level: CIF, ~512kb/s (256 kb/s x2) per communication on average H264 Medium Level: VGA, ~1,536 Mb/s (768 kb/s x2) per communication on average H264 High Level: HD 720p, ~2,304 Mb/s (1152kb/s x2) per communication on average Add 50% of extra bandwidth to be on the safe side (due to punctual burst of video packets)  Very good QoS is mandatory for acceptable video quality (Max 0.25% of packet loss for Medium and High levels, Max 0.5% for Low level).  QoS Priority: Dedicated IP TOS field for Video (8770 or Client Configuration)  Video home working use case not recommended  restriction planned to be removed in a future release  Low level instead of High level  will be configured by default in the next release  3000 ms instead of 5000 ms GVP Media Control Min video switch time  will be configured by default in the next release (mpc.mixer.minvideoswitchtime parameter) 8.4.9.5 Bandwidth requirement  Audio / Video Conference Call with 3 clients (MyICDesktop / IVC) First Case: One way Audio Codec G711 IP Bandwidth : 80kbit/s One Way Video Codec H264 Baseline Profile Low level IP Bandwidth: 263kbit/s Global IP bandwidth from & to Open Touch server : 6 x ( 80 + 263 ) = 2058 kbit/s => ~2,5 Mbit/s Second Case: One way Audio Codec G711 IP Bandwidth: 80kbit/s One Way Video Codec H264 Baseline Profile Medium level IP Bandwidth: 789kbit/s Global IP bandwidth from & to Open Touch server: 6 x ( 80 + 789 ) = 5214 kbit/s => ~6 Mbit/s Third Case: One way Audio Codec G711 IP Bandwidth: 80kbit/s One Way Video Codec H264 Baseline Profile High level IP Bandwidth: 1184 kbit/s Global IP bandwidth from & to Open Touch server: 6 x ( 80 + 1184 ) = 7584 kbit/s => ~8,5 Mbit/s Add 10 % for Signalization + RTCP bandwidth, and other corresponding bandwidth for datasharing or other simultaneous use case. Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 190/193 (Estimation done for MTU 1500 bytes). QOS is not only linked to bandwidth but also to IP impairment Medium quality video = 0.5% packet lost Audio up to 4% 8.4.9.6 MyTeamwork IVC / ACS+MCU Radvision – video engineering rules  Correct bandwidth has to be available: Low level use case  Medium level use case Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 191/193  High level use case  QOS Priority: Configurable QoS priority for MTW IVC and MCU Radvision Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 192/193 Follow us on Facebook and Twitter Stay tuned on our Facebook and Twitter channels where we inform you about: New software releases New technical communications AAPP InterWorking Reports Newsletter Etc. twitter.com/ALUEnterpriseCare facebook.com/ALECustomerCare Submitting a Service Request Please connect to our eService application at: https://businessportal.alcatel-lucent.com/alugesdp/faces/gesdp/customerSupport/CustomerSupport.jspx Before submitting a Service Request, make sure that: In case a Third-Party application is involved, that application has been certified via the AAPP You have read through the Release Notes which lists new features available, system requirements, restrictions etc. available in the Technical Knowledge Base You have read through the Troubleshooting Guides and Technical Bulletins relative to this subject available in the Technical Knowledge Base - END OF DOCUMENT - Alcatel-Lucent OpenTouch - R. 1.3.000.043 Technical Release Note Release 1.3.000.043 Copyright © 2013 Alcatel-Lucent. All rights reserved TC1798 Ed05 page 193/193

Technical Release Note Release 1.3.000.043

Rating

Date

Size

Views

Categories

Share

Transcript

There is no help documentation for the moment

Coming soon...

PDF Documentation

OpenTouch Hotline