RELEASE NOTE FOR OMNIPCX OFFICE RCE RELEASE 10.1 VERSION

Release Note Alcatel-Lucent OmniPCX Office Release 10.1 RELEASE NOTE FOR OMNIPCX OFFICE RCE RELEASE 10.1 VERSION 014.001 This document gives all general details about OmniPCX Office Release 10.1/014.001. Revision History Edition 1: April 21, 2015 creation of the document Legal notice: The information presented is subject to change without notice. ALE International assumes no responsibility for inaccuracies contained herein. Copyright ALE International 2015

Table of contents 1 INTRODUCTION... 4 2 TECHNICAL COMMUNICATIONS... 4 3 New features... 5 3.1 OMC R10.1... 5 3.1.1 OMC R10.1 New Services... 5 3.1.1.1 Default Subscribers Password... 5 3.1.1.2 Management password... 5 3.1.1.3 Selection of voice mailbox for Forwarded Call... 5 3.1.1.4 Support of In-Band DTMF... 5 3.1.1.5 Support of RFC 4904... 5 3.1.1.6 SIP Trunk Profile evolution... 5 3.1.1.7 Callback in VM Consultation... 5 3.1.1.8 Dynamic Routing Cascading... 5 3.1.1.9 Support of Israel target... 5 3.1.1.10 8340-C IP-DECT... 5 3.1.1.11 Split RPN... 5 3.2 Hebrew and Arabic targets support... 6 3.2.1 Terminals display... 6 3.2.2 Israel target... 6 3.2.3 Arabic target support... 6 3.3 8242 IP-Dect... 6 3.4 OTCV Android Dual Mode... 7 3.4.1 SIP Companion... 7 3.4.2 Easy VPN Client... 7 3.5 IP-DECT... 7 3.5.1 IP-Dect R170 SW... 7 3.5.2 Compatibility of DAP with Windows 8.1 and Windows server 2012 R2... 7 3.5.3 IP DECT DAP lite split RPN... 8 3.5.4 Serviceability... 8 3.5.4.1 Multicast connectivity diagnostic... 8 3.5.4.2 Status of IP DECT DAP DECT synchronization... 8 3.6 AP-8340-C... 8 3.7 PIMphony Touch... 9 3.8 OTCV Windows... 9 3.9 New Telephony Features... 9 3.9.1 Voice Mailbox selection for Forwarded Calls... 9 3.9.1.1 Presentation... 9 3.9.1.2 Feature activation...10 3.9.2 Dynamic routing cascading... 10 3.9.2.1 Presentation...10 3.9.2.2 Feature activation...10 Copyright ALE International 2015 page 2/21

3.9.3 GET CALL from Deskphone to DECT handset... 11 3.10 SIP Trunking... 11 3.10.1 In-band DTMF support on OmniPCX Office SIP TRUNK for outgoing call... 11 3.10.2 RFC 4904... 12 3.10.3 Update of the list of emergency numbers for FRANCE... 12 3.11 Security... 12 3.11.1 Telekom Austria Features Rights default values... 12 3.11.2 Feature right options disabled by default for all targets... 12 3.11.3 Free-dialing option in Automated Attendant... 13 3.11.4 Systems with default password... 13 3.11.5 Customized user default password... 13 3.11.6 Disable callback in consultation mode by default... 13 4 OmniPCX Office R10.1 Licence... 13 5 MIGRATION... 13 6 Known restrictions... 14 7 SOFTWARE REFERENCES... 19 7.1 Software versions level... 19 7.2 Software details... 19 Copyright ALE International 2015 page 3/21

1 INTRODUCTION This technical communication summarizes the new functionalities coming with the OmniPCX Office R10.1. The OmniPCX Office RCE release 10.1 is a minor release based on OmniPCX Office R10.0 This release 10.1 / 014.001 is installed on the systems going out of manufacturing since week 17 2015 for generic market. For more details about Release 10.1 new features, please see R10.1 OmniPCX Office Expert documentation and Installation documentation. For new applications, Help On Line of concerned applications may be read. Warning OmniPCX Office 10.1 / 014.001 has the same level of modifications as OmniPCX Office 10.0/044.001. Consequently it is recommended not to migrate an OmniPCX Office 10.0 site to R10.1 when it is already running 10.0 version higher than 044.001. You will be informed when OmniPCX Office R10.1 will officially become support release of OmniPCX Office R10.0. 2 TECHNICAL COMMUNICATIONS Following technical communications provide additional information for OmniPCX Office Release 10.1: 8001 SIP Phone : Reference 2003 8242 DECT : Reference 1942 Limits and dimensioning : Reference 1972 Migration : Reference 1973 OTCV for Android : Reference 1664 Security Recommendations : Reference 1143 PIMphony Touch : Reference 2039 OTCV Windows : Reference 2038 IP-Dect : Reference 1872 Copyright ALE International 2015 page 4/21

3 New features 3.1 OMC R10.1 OMC release 10.1 is designed to be used with OmniPCX Office release 10.1. It also provides backward compatibility for existing OmniPCX Office releases : 10.x, 9.x, 8.x, 7.x, 6.x, 5.x, 4.x, 3.x, 2.x and 1.x. 3.1.1 OMC R10.1 New Services 3.1.1.1 Default Subscribers Password Provides an option to set the customized default password for subscribers in OmniPCX Office. 3.1.1.2 Management password To facilitate security enhancement for all Management / Subscribers passwords. 3.1.1.3 Selection of voice mailbox for Forwarded Call Provides an option to choose voice mailbox for forwarded calls on destination sets. 3.1.1.4 Support of In-Band DTMF To allow configuring the In-Band DTMF for both incoming and outgoing call via SIP Trunk. 3.1.1.5 Support of RFC 4904 To allow configuring SIP / Tel Uniform Resource Identifiers (URIs) to convey trunk group information in SIP messages. 3.1.1.6 SIP Trunk Profile evolution The SIP Trunk Profile has been updated, mainly to include new configuration data introduced by the following SIP trunk features: support of In-Band DTMF and support of RFC4904. 3.1.1.7 Callback in VM Consultation Provides an option to enable or disable callback in VM consultation mode for individual subscribers in OmniPCX Office. 3.1.1.8 Dynamic Routing Cascading To allow a subscriber or hunting group to enable or disable dynamic routing cascading. 3.1.1.9 Support of Israel target To support Israel country target. 3.1.1.10 8340-C IP-DECT To support new IP-DECT base station 8340-C IP-DECT. 3.1.1.11 Split RPN Split RPN feature configuration checkbox. Copyright ALE International 2015 page 5/21

3.2 Hebrew and Arabic targets support 3.2.1 Terminals display The following terminals support Hebrew display. - NOE-2G : 4028, 4029, 4038, 4039, 4068 - NOE-3G : 8028, 8029, 8038, 8039, 8068 The following terminals support Arabic display. - NOE-2G IPTOUCH : 4028, 4038, 4068 - NOE-3G IPTOUCH : 8028, 8038, 8068 Note 8082 My IC Phone supports display of Hebrew and Arabic characters. This display is managed locally by 8082 My IC Phone. Also, OTCV iphone supports Hebrew and Arabic characters. User should configure the language manually from the application. 3.2.2 Israel target Israel country target and Hebrew language are newly introduced since OmniPCX Office R10.1. Hebrew language is available by default in Israel target. When Hebrew language is selected for a subscriber, voice prompts are played in Hebrew and if the terminal supports the display of Hebrew characters, text (labels, menus and call information) is displayed in Hebrew. Note If the terminal does not support Hebrew characters, text is displayed in English 3.2.3 Arabic target support Arabic language is already available in OmniPCX Office releases prior to R10.1, but only voice prompts are played in Arabic while text is displayed in French or English (according to the terminal language configured). There are two variants of Arabic language, Arabic Male voice and Arabic Female voice. From OmniPCX Office R10.1, when Arabic language is selected for a subscriber, voice prompts are played in Arabic and text is displayed in Arabic on terminals supporting Arabic characters. Note If the terminal does not support Arabic characters, text is displayed in French or English (according to the terminal language configured). 3.3 8242 IP-Dect See Technical Communication Dect 8242 Reference 1942. Warning IP-Dect 8242 SW will become available from BP Portal in the next coming weeks. Support of 8242 DECT in CAT-iq/GAP mode on IP-DECT: for the SW version, please refer to Dect 8242 Technical Communication. Copyright ALE International 2015 page 6/21

The 8242 DECT handset is already available for IBS DECT from release 10.0 and on IP-DECT from release 10.1. New features Support on IP-DECT in CAT-iq (in addition to AGAP support on IBS/RBS): CAT-iq/GAP. Tooltip display CAT-iq. SD card for local contacts & messages in CAT-iq (500 contacts, 200 messages, config save). Bluetooth support. Dock settings: for special configurations when set is in the dock. PC Parallel Firmware Upgrade tool (PFWU): Mandatory for the Dect 8242 Bluetooth upgrade. 3.4 OTCV Android Dual Mode See Technical Communication OTCV for Android Reference 1664. New services described are available since OTCV Android SW version 2.10.15.8. 3.4.1 SIP Companion Support of the SIP companion (Dual Mode, Wifi) for OTCV Android. 3.4.2 Easy VPN Client Easy VPN is a feature allowing OTCV (Android and iphone) to connect the corporate network through a VPN tunnel using the OAW switch and the VIA VPN client. The VIA (Virtual Intranet Access) application from Aruba provides secure VPN connectivity to an OAW Networks Mobility Controller. This application must be installed in the mobile devices (iphone and Android) on which OpenTouch Conversation (OTCV) is running in Dual Mode. Note Restriction on OTCV Android : the Easy VPN feature support is only possible with WiFi connections. It does not work with 3G / cellular connections. 3.5 IP-DECT See Technical Communication IP-Dect Reference 1872. 3.5.1 IP-Dect R170 SW IP-Dect Software R170 availability since OmniPCX Office Release 10.1. R170 applicable to all IP-Dect base stations : 4080, 8340, 8340-C. 3.5.2 Compatibility of DAP with Windows 8.1 and Windows server 2012 R2 OMC : support DAP in Windows 8.1 and Windows Server 2012 R2. Copyright ALE International 2015 page 7/21

3.5.3 IP DECT DAP lite split RPN From OmniPCX Office Release 10.1, Split RPN is supported. Only two synchronization clusters one in main and another in remote site is allowed. DAPs in main site must be in one synchronization cluster, not split up into more synchronization clusters. DAPs in remote site must be in one synchronization cluster, not split up into more synchronization clusters. If split RPN is not enabled then there must be only one location. A new Checkbox is introduced in the OMC DAP Configurator for Split RPN : IP Dect / DAP Configurator / Misc Setting / Split RPN (at the bottom of the page). By default the value is unchecked. 3.5.4 Serviceability 3.5.4.1 Multicast connectivity diagnostic OmniPCX Office R10.1 provides in Webdiag interface, a Multicast diagnostic tool. Results can be retrieved in a text file or directly displayed in the Webdiag. One click to retrieve the Multicast information from the DAPs (can be done remotely) : Retrieve data file from DAP Include data file in the archive Display the content of the data file 3.5.4.2 Status of IP DECT DAP DECT synchronization OmniPCX Office R10.1 provides in Webdiag interface, a Synchronization diagnostic tool. Results can be retrieved in a text file or directly displayed in the Webdiag. One click to retrieve the synchronization information from the DAPs (can be done remotely) : Retrieve data file from DAP Include data file in the archive Display the content of the data file 3.6 AP-8340-C From R10.1, the new DAP 8340-C IP-DECT is supported in addition of the previous DAP models. Optimized IP-DECT AP 8340-C without G729 Daughter board / without support for G729 codec. Note AP-8340-C can be installed in mix topology with AP 4080 and AP 8340 (sites where G729 is not used with present installed APs). Warning G729 protocol in use or not in use is a global system configuration. When AP-8340-C is installed on OmniPCX Office system : OMC / IP-Dect / DAP Configurator / Misc Settings : G729 mode : G729 not supported must be selected. If G729 protocol is enabled, AP-8340-C will not start. Copyright ALE International 2015 page 8/21

3.7 PIMphony Touch See Technical Communication PIMphony Touch Reference 2039. Warning PIMphony Touch application will become available for downloading on Windows Store Week 20 (TBC) 2015. PIMphony Touch application runs on PC OS Windows 8.1, 32-bit and 64-bit. PIMphony Touch application requires the network connection via wired or Wi-Fi with internet access to interact with OmniPCX Office in order to use the enterprise telephony services. 3.8 OTCV Windows See Technical Communication OTCV for Windows Reference 2038. Warning OTCV Windows application is available for downloading on Windows Phone Store since Week 18 2015 : OmniPCX Office SW version 10.1_017.004 (and above) must be used. If OTCV Windows application is used with OmniPCX Office SW version R10.1_014.001, Central Services server reboot may occur + OmniPCX Office system reset. OTCV Windows is a soft phone installed on a Windows phone, based on Microsoft OS Windows Phone 8.1. OTCV Windows application requires the network connection via 3G/4G data network or Wi-Fi with internet access to interact with OmniPCX Office in order to use the enterprise telephony services. Note There is no check in the software to avoid connecting PIMphony Touch and OTCV windows applications to older OmniPCX Office Release 10.0. But, in order to support PIMphony Touch and OTCV windows applications with all their features (i.e. WNS notifications : Windows Push Notification Service used for live tile update and toast notification, Favorites, Presence), OmniPCX Office Release 10.1 (and above) is mandatory. 3.9 New Telephony Features 3.9.1 Voice Mailbox selection for Forwarded Calls 3.9.1.1 Presentation From R10.1, subscriber is provided with a new configuration option Mailbox of initial called party in OMC to select either the initial called party s mailbox or the forwarded destination s mailbox when a forwarded call is routed to the Voice Mail. Copyright ALE International 2015 page 9/21

3.9.1.2 Feature activation This new feature right Mailbox of initial Called party can be configured with OMC in menu: Subscribers/Base Stations List -> Select Subscriber -> Details -> Features -> Part3. When the feature right Mailbox of initial called party is enabled in the Initial called party, the destination mailbox is the initial called party s mailbox (same as OXO R10.0 and before). When the Feature right Mailbox of initial called party is disabled in initial called party, the destination mailbox is the forwarded destination s mailbox. Dynamic routed call cannot be re-routed to VMU. In R10.1, there is no change in this behavior. Selection of voice mailbox feature is not applicable when dynamically routed calls re-routed to VMU. Note Feature right Mailbox of initial called party is : - enabled for all terminals by default in OmniPCX Office Release 10.1 new installation and after cold reset, - is retained after warm reset of the system, - is enabled after migration from OXO release <= R10.0 to R10.1, - retained after migration from OXO release R10.1 to >=R10.1. 3.9.2 Dynamic routing cascading 3.9.2.1 Presentation From 10.1, if a subscriber/group receives a dynamically routed call and if the call is not answered by the receiver, then the new cascading mechanism enhances the call distribution. Note - Dynamic Routing cascading is supported for subscribers and Hunting groups. - Dynamic Routing configured on the resource key of cascaded destination is not taken into account by the initial called party, while implementing Dynamic Routing cascading. - Attendant overflow behavior is not changed in R10.1. 3.9.2.2 Feature activation This new feature right Maximum Number of Dynamic Routing Cascading Levels can be configured with OMC in menu : Subscribers/Base Stations List or Hunting Groups -> Select Subscriber -> Details -> Dynamic Routing, modify «Maximum Number of Dynamic Routing Cascading Levels». The default value is 1 and corresponds to the same behavior as in R10.0 and before : Dynamic Routing Cascading disabled. Maximum value allowed (maximum number of Dynamic Routing cascading levels) : 5 The maximum number of Dynamic Routing cascading levels is configurable in OMC for each Subscriber and Hunting group. Copyright ALE International 2015 page 10/21

If one level is not defined in the cascaded destinations, cascading ends before reaching limit defined for the initial subscriber who receives the call. So there is an overflow to the General Level (if defined). If one level is an external destination, cascading ends after routing the call to external destination. All the calls are released (initial call & cascaded destinations). If one level number is the same than level 1 of the initial called party, then the cascading ends before reaching limit defined for the initial subscriber who receives the call. So there is an overflow to the General Level (if defined). If one set is out of service in the cascaded destination, the cascading continues. Note Configuration of Maximum Number of Dynamic Routing Cascading Levels is : - reset to default value after cold reset. - retained after warm reset. - set to default value after migration from OXO release <= R10.0 to R10.1. - retained after migration from OXO release R10.1 to >=R10.1. 3.9.3 GET CALL from Deskphone to DECT handset From OmniPCX Office Release 10.1, support of Get call feature Fixed Desktop phone to Mobile DECT via a soft key or Feature Code from the DECT handset 400/8232/8242 in IBS mode and with Feature Code with IP- DECT mode. DECT sets other than 400/8232/8242 with Feature Code in IBS/IP-DECT mode. Get Call feature facilitates the user to switch a call from one terminal to another terminal with a simple action, when both terminals are part of multiset. Note Call switching from Desktop Phone to OTCV or WLAN Handsets is not supported. 3.10 SIP Trunking 3.10.1 In-band DTMF support on OmniPCX Office SIP TRUNK for outgoing call Support of In band DTMF on SIP trunk per SIP gateway. This parameter allows to select the method used to send and receive DTMF. Till R10.0, SIPdtmflnB noteworthy address is used to enable the InBand DTMF digits detection on SIP trunk. This noteworthy does not support InBand DTMF transmission from OXO SIP trunk gateway. From R10.1, new DTMF list box is introduced in : OMC -> Numbering -> ARS -> Gateway Parameters -> Line selection -> Details -> Media Tab -> DTMF. DTMF list box has two options : Out-Of-Band (RFC4733) mode and In-Band mode. Default value is Out-Of-Band (RFC4733) for all targets Copyright ALE International 2015 page 11/21

3.10.2 RFC 4904 Support of RFC 4904 in SIP trunking. Standardized mechanism to convey trunk group parameters in SIP and Tel Uniform Resource Identifiers (URIs). From R10.1 two new SIP/Tel URI parameters Trunk Group ID and Trunk Context are introduced in : OMC -> Numbering -> ARS -> Gateway Parameters -> Line selection -> Details -> Protocol to convey trunk group information in SIP messages as per RFC4904. Trunk Group ID parameter specifies trunk group label or identifier. "Trunk Context" parameter establishes a scope of Trunk group specified in the "Trunk Group ID" parameter. 3.10.3 Update of the list of emergency numbers for FRANCE For the system targets France and OBS, the following numbers have been added to the list of emergency numbers: 115 (SAMU Social - SOS Sans Abri) 119 (enfance maltraitée) 116 000 (enfants disparus) 196 (secours maritime) 911 3.11 Security 3.11.1 Telekom Austria Features Rights default values Following feature right options are disabled by default in Austria and Telecom Austria target. Paging Selective diversion Intrusion allowed UUS allowed Inhibit flag DND override allowed Remote Substitution Inhibition time ranges 3.11.2 Feature right options disabled by default for all targets Following feature right options are disabled by default for all targets. Remote Substitution Inhibit flag Inhibition time ranges Note Remote Substitution is not available by default in Public Numbering Plan in OMC (Numbering -> Numbering Plans -> Public Numbering Plans) for all targets. Copyright ALE International 2015 page 12/21

3.11.3 Free-dialing option in Automated Attendant Free-dialing option is not available by default in Automated Attendant Menu configuration (OMC -> Voice Processing -> Automated Attendant -> AA Menu) for all country targets. 3.11.4 Systems with default password From R10.1, at first connection the installer is forced to change default passwords of all accounts that can be used to access management services of the system. 3.11.5 Customized user default password From R10.1, Subscribers EDN default password is randomly generated after fresh installation or after upgrade to Release 10.1. This default password is specific to each system and only known by the users of the system. Installer also can define the EDN user password from OMC. 3.11.6 Disable callback in consultation mode by default Callback option is enabled / disabled by a new feature right Callback in VM Consultation for each user. By default, this feature right is disabled for all country targets. 4 OmniPCX Office R10.1 Licence No new licence (same licence level than for OmniPCX Office R10.0) but following existing licences must be available in the OmniPCX Office system for : PIMphony Touch : PIMphony PRO licence (same PRO licence as for PIMphony v6.8 legacy application). OTCV Windows : My IC Mobile licence At Offer level / catalog : introduction of OTCV for windows mobile license. 5 MIGRATION See OmniPCX Office Migration technical communication reference 1808 for more details. For migrations from R10.0 SW to R10.1 SW you may use : OMC_10.1_8.1a (and above) : automatic upgrade with database save and restore can be performed with OMC_10.1a_8.1a (and above). LOLA version 15.1 with database restore, For migrations < R10.0 (i.e. R920, R820) to R10.1 software you may use. LOLA version 15.1 with database restore. Copyright ALE International 2015 page 13/21

Note Always save first the present database via OMC_10.1 before performing migration to system Release 10.1. Warning Due to the security features delivered in the Release 10.1, after migration to R10.1, at the first connection all the default management password must be manually changed. The default subscribers password will be generated randomly in an automatic manner. 6 Known restrictions This chapter lists the known restrictions in the SW version OmniPCX Office R10.1_014.001. For some of the known issues, fixes will be provided in a further patch or maintenance. # Feature Sub Topic Status Problem Description Workaround Correction 1 OTCV Windows Usability Restriction OTCV Windows application must not be used with OXO R10.1 TR binary (RCE101/014.001) NA R10.1_017.004 Central Services Server crash may occur while using OTCV Windows with OXO TR binary (RCE101/014.001) + OmniPCX Office system reboot. 2 PIMphony Touch 3 8242 IP DECT Availablity Availablity Information PIM Touch application is not yet available in Windows Application Store Information 8242 IP DECT solution is not delivered with OXO TR binary RCE101/014.001 4 8770 Usability Restriction Unable to launch OMC via 8770 for maintenance activities. Manually connect OMC for maintenance WK 1520 (TBC) TBD R10.1_017.004 Copyright ALE International 2015 page 14/21

5 SIP phone 6 OTCV Android 7 OTCV Android 8 OTCV Android Usability Restriction 8001 terminal will not work in G722 codec Battery Information OTCV Android app with consumption SIP companion is draining the mobile battery abnormally fast when its connected via enterprise network. This issue occurs in Android OS v4.4.2 & v5.0 Easy VPN Restriction On OTCV Android, Easy VPN feature support is possible only with WiFi connections. It does not work with 3G/4G (cellular) connections. Network Connectivity Information Nexus 5 - Android OS 5.0 In Android mobile, both Mobile data and Wifi are switched on. OTCV android App is connected to OXO. Vowifi mode is active-- OK When the user goes out of the wifi range, 3G is activated --OK. Vowifi mode is deactivated--ok Issue: When the user returns to the wifi coverage the phone's network shows that 3G is still active inspite of getting connected with Wifi. The app gets connected using 3 G and hence Vowifi is deactivated even when the user is in enterprise wifi. TBD NA 2.10.15.5 - Correction is given for the case when Mobile is outside enterprise network. NA OXO R10.2 User must manually deactivate Mobile data, so that OTCV android app connects to enterprise netwlork over wifi. Due to Android OS 5.0 issue (issue is not linked to OmniPCX Office neither to OTCV Android application ) Copyright ALE International 2015 page 15/21

9 OTCV Android Notification priority Limitation Android 5.0 has introduced a new priority mechanism for notifications. When the user puts the device in priority mode (a star icon is displayed in the status bar), only high priority notifications are displayed. NA NA If the user has chosen this priority mode, the device will return to standard mode at first make call from OTC Android application. In other words, it is not possible to use the priority mode while using the OTC Android. 10 IP-DECT DAP Restriction 3 DAPs are connected to OXO. To change master DAP, in OMC/DAP configurator use copy/paste option to interchange the mac address of DAP with RPN002 with mac address of DAP with RPN000. Issue: DAP with RPN000 does not start at all. In OMC/DAP configurator: 1) Delete all the entries of RPN details in DAP configurator. 2) Save & Exit 3) Enter the new RPN details (All entries) in DAP configurator. 4) Save & Exit Now all the DAP are registered properly. R10.1_017.004 Copyright ALE International 2015 page 16/21

11 IP-DECT Transfer display Restriction IPDect Set Set B (4035):100 (name : set110) Set C(4018):111 (name : set111) IPDECT Set calls Set B. Set B answers the call. Both are in conversation. The display on IPDECT set shows "set110" Set B puts IPDECT set's call on hold and calls Set C. Set B makes a transfer on ringing and set C answers the call. NA TBC - Enhancem ent to be done on OTCV Android application. 12 Password Subscriber Password 13 Password Subscriber Password 14 SIP phone Issue: The display of set A shows "111" (KO) instead "set111". Restriction When migrated with default password (1515/151515) for a user from R920 or R820 to R10.1, this is retained as not default password in R10.1. And the user can log in MyIC Office with default password (1515/151515) Restriction When migrated with 4- digit default password for a user from R710 to R10.1, 6-digit random password is generated for whereas system still recognises only 4-digit password. SIP call Restriction Outgoing call from 8001 set does not work when dialing '#' to route the call via SIP public trunk. Reset the user password manually in Subscriber Basestations List\Subscriber -> Details-> Passowrd Default Subscriber password to be manually set in System Miscellaneous\ Passwords\Sub scribers Password NA R10.1_017.004 R10.1_017.004 TBD Copyright ALE International 2015 page 17/21

15 SIP call Display Restriction SetA1 is connected with OXO1. SetB1 is connected with OXO2. SIP private trunk is configured between OXO1 & OXO2. SetA1 calls SetB1. SetB1 answers the call. SetA1 and SetB1 in conv. Display in SetB1 shows "4800" and Display in SetA1 shows "3800" NA OXO Patch2 SW : Week 20 2015 16 OTCV Android Issue: SetA1 puts SetB1 on hold, display in SetB1 changes to "48" When SetA1 unholds SetB1 call, the display in SetB1 is still "48". Voicepath Restriction Nexus 5 with Android OS version 5.0.1 NA TBD OTCV Android (dual mode) & Set A is connected with OXO. OTCV android makes a call to a Set A. 17 IP-DECT 8232 Display issue Restriction Issue: There is no voicepath in Set A for 10 secs 8232 DECT set is configured with DAP connected to OXO. A call is made to 8232 from any other set connected to OXO. 8232 is in conversation with called set. Another call is made to 8232 set. If name is configured for both or any one set which is in conversation, then there is display alert on 8232 set screen. TBD Issue: A beep tone is heard Copyright ALE International 2015 page 18/21

for second call, but there is no display alert shown on the screen for the second call. 7 SOFTWARE REFERENCES 7.1 Software versions level RCE 10.1_014.001 SW version is at the same level of correction than R10.0_044.001. OMC 10.1_8.1a contains all bug fixes and changes delivered in OMC 10.0_13.1a. 7.2 Software details Following table provides the list of application SW versions associated to OminPCX Office RCE 10.1/014.001. Component Build Comment OMC OMC10.1/8.1a Separate SW package ACD application Package 10.060.01 Separate SW package OLD appli 2.3.11 Separate SW package MLAA appli 10.060.01 Available in OMC ACD-SRC Services(MSM) 10.060.01 Available in OMC AST appli 2.3 build 0.0 Separate SW package OSC appli 3.2.020 Available in OMC DBAdapter 2.3 build 2.0 Separate SW package DAP Configurator version V 2.2.0.3 Available in OMC Copyright ALE International 2015 page 19/21

IP Dect DAP base (AP 300 and 400) R170/4920b629 Available in OXO LabelSet 310/6.1 Separate SW package LoLa400 15.1 Separate SW package 8082 My IC Phone R300 R300/1.15.03 Available in OXO 8002/8012 R110 R110/V03.39.00 Available in OXO 80x8 IP Phones 4.51.21 Available in OXO OT4135 1.5.25 Available in OXO External Component to be updated Manually Component Build Comment DECT 500 R120 v1084 Separate SW package DECT 8232 R110 - v4881b0005 Separate SW package DECT 8242 TBC Separate SW package ASCOM ASCOM : 05.01.30 Separate SW package OTCV Android R2.10.15.8 Download application from Android Store OTCV Windows 1.5.6.1 Download application from Microsoft Phone Store OTCV iphone 3.0.3 #40 Download application from Apple store MyIC social Network 3.3.0.4454 Separate SW package PIMphony 6.8 Build 3170 Separate SW package PIMphony Touch 1.5.6.0 Separate SW package Copyright ALE International 2015 page 20/21

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/alue_care facebook.com/alecustomercare Submitting a Service Request Please connect to our eservice Request application. 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 Documentation Library You have read through the Troubleshooting Guides and Technical Bulletins relative to this subject available in the Technical Documentation Library You have read through the self-service information on commonly asked support questions, known issues and workarounds available in the Technical Knowledge Center - END OF DOCUMENT - Copyright ALE International 2015 page 21/21