Acano Solution Acano Manager Release 1.6 Release Notes Acano February 2015 76-1033-04-D Contents Contents 1 Introduction 2 2.1 Features in AM1.6 3 Cluster Support ................................................................................................................. 3 3 3.1 3.2 3.3 Notes on Installing Acano Manager 1.6 4 New Installation ................................................................................................................. 4 Upgrading to AM1.6 from AM1.1.x .................................................................................... 4 Rolling Back to AM1.1.x .................................................................................................... 5 4 Resolved Issues 5 Known Limitations Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D 3 6 11 Page 2 Introduction 1 Introduction This release note describes the features in Release 1.6 of the Acano Manager software, and lists the fixes and known issues in the AM1.6 release. If you are deploying Acano Manager for the first time, follow the Acano Manager Installation Guide for instructions on how to install and configure Acano Manager. If you are upgrading, instructions are provided in this release note. CAUTIONS: AM1.6 requires Release 1.6.10 or later of the Acano solution (an Acano Server, a virtual deployment or a combined deployment). Do not use it with an earlier version. It is essential that you back up the database before upgrading. 2 Features in AM1.6 2.1 Cluster Support Acano Manager has been updated to support multiple Acano servers running in clustered mode (R1.6.10 and later). This means that Acano Manager will correctly group together participants and calls that span multiple Call Bridges. Acano Manager will also be able to send commands to the correct Call Bridge to retrieve data from, or perform actions on, specific distributed callLegs. Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 3 Notes on Installing Acano Manager 1.6 3 Notes on Installing Acano Manager 1.6 CAUTIONS: If you are upgrading from an earlier version of the Acano Manager, you must backup the database and then uninstall that version as described later in this document before following the procedure on this section. 3.1 New Installation Follow the instructions in the Acano Manager Installation Guide, being sure to check that all the prerequisites mentioned there are in place before you start the procedure itself. 3.2 Upgrading to AM1.6 from AM1.1.x CAUTION: When upgrading from an earlier version, you will lose any changes made to the default email templates unless you complete step 1 below. 1. To keep any email customizations that you made, copy the contents of EmailTemplates folder (a subfolder of the AcanoManager service folder) to another server. 2. For security and data integrity perform a SQL database backup (see one of the following):  2012 : http://msdn.microsoft.com/en-gb/library/ms187510%28v=sql.110%29.aspx  2008 R2 : http://msdn.microsoft.com/en-gb/library/ms187510%28v=sql.105%29.aspx 3. Store the backup on another system somewhere safe. 4. Stop the Acano Manager Service (from Windows Services). 5. Uninstall the existing software. a. In the Control Panel, go to the Add/remove programs function. In the list you see two entries: Acano Manger Service & Acano Manager Interface. b. Uninstall the Acano Manager Interface first. c. Uninstall the Acano Manager Service second. This removes the software. 6. Install the new Acano Service first (right-click and select Run as administrator), following the wizard prompts and accepting the defaults. When upgrading, there is a pause while the prerequisites are checked and the SQL database found. 7. Install the new Acano Interface (right-click and select Run as Administrator), following the wizard prompts and accepting the defaults. The configuration files are updated. 8. Start the Acano Manager Service. 9. Check that you can still monitor and edit calls using the Calls in Progress page. Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 4 Notes on Installing Acano Manager 1.6 10. Copy the contents of the backed-up EmailTemplates folder back to restore your email customizations. 11. If you are using Call Bridge clustering perform these steps now: a. Change the CDR listener port for each Call Bridge so that each Call Bridge has a unique CDR listener port. b. Using the API perform a GET method on the /callbridges node of one of the clustered Call Bridges to determine the name of all the Call Bridges. c. Modify the current MCU in Acano Manager to have the correct name (MCU names must match the Call Bridge name exactly). d. Set up the other Call Bridges as MCUs in Acano Manager one at a time, using the name returned by the API call as the MCU name and the CDR listener port configured above. 3.3 Rolling Back to AM1.1.x In the unlikely event that you need to roll back to AM1.1.x follow these steps. CAUTION: You will lose all the data for period in-between the upgrade and rollback. 1. Un-install Acano Manager 1.6. 2. Re-install Acano Manager 1.1. Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 5 Resolved Issues 4 Resolved Issues Fixed in AM1.6 Reference Issue Summary 44967 Scheduling a recurring call on a coSpace resulted in a call sequence in which the first call was correct but the remainder had incorrect properties (e.g. URI). This is fixed in AM1.6 44995 When expanding a call’s details on the Call List page, the panel displayed the call’s ID (Acano Manager’s internal identifier for the call). This was confusing for users who interpreted it as the Call Identifier which is used on an Acano Call Bridge to route participants into the call. The call’s ID is no longer displayed and this issue is fixed in AM1.6 45014, 45107, 45115 Directory Services Configuration. Attribute Mapping could fail in the following situations: the mapping contained multiple attributes (e.g., $givenName$.$sn$), the replacement string in a pipe command was the empty string(“//”), or when multiple pipe commands were defined. These mappings now work and the issue is fixed in AM1.6 45005 If a user booked a call in Outlook, added 2 endpoints (e.g., Paris and London) and then updated the call using Outlook to remove London and add New York, London was removed but New York was not added. This is fixed in AM1.6 45007 In Acano Server 1.2 the ldapSync object is removed as soon as it has completed. If Acano Manager could not find the ldapSync object, it was incorrectly timing out and reporting that the LDAP sync had failed. This is fixed in AM1.6 45026 In earlier versions of Acano Manager when columns in tables had been sorted (e.g., sorting coSpace names in the coSpace list page), users might have experienced a page error and seen the message “an error has occurred”. This is fixed in AM1.6 45029 Directory Services Configuration. LDAP Attribute Mapping. Specifying an Attribute other than $samAccountName$ for “UserName” (e.g., $cn$) resulted in the LDAP Import failing when connected to a Microsoft Active Directory Server. This is fixed in AM1.6 45030 When scheduling a number of calls to use a CoSpace, if the calls were not scheduled in the sequence they were due to execute, the first call starting resulted in the second call being deleted. For example, 2 calls A and B. A starts at 2PM and B starts at 4PM. If B was scheduled first, call B would be deleted when This is fixed in AM1.6 and both calls run Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 6 Resolved Issues call A started at 2PM. 45049 In certain circumstances, Microsoft Lync Instant Messages could result in an additional participant being displayed in the Calls In Progress page. This is fixed in AM1.6 45050 Acano Manager uses the callLeg GUID to delete participants; but was not disconnecting participants on a distributed Call Bridge call. This is fixed in AM1.6 45051 When running on a non-clustered 1.6 Call Bridge, Acano Manager did not associate point-to-point calls with the correct Customer (Tenant). This is fixed in AM1.6 45071 If a user requested call data records to be exported when the coSpace had been inactive for more than 3 days, the export would fail and the user interface would display the message “An error has occurred…” This is fixed in AM1.6 45073 In certain circumstances, Microsoft Lync Content Sharing could result in an additional participant being displayed in the Calls In Progress page. This is fixed in AM1.6 45005 Outlook plugin update not working properly This is fixed in Acano Manager AM1.6 45008 LDAP Sync is timing out for the Acano server running X1.2 This is fixed in Acano Manager AM1.6 34122 Crash on fetching large amounts of MCU port usage data on systems with very large sets of call usage data This was a memory issue and is fixed in Acano Manager AM1.6 34315 MCU port usage execution time exceeded 90 seconds and page timed out with large volumes of data when requesting a large data rang. This issue is fixed in AM1.6 44753 Didn’t generate call.Started and call.Stopped emails for calls dynamically created on coSpaces. This issue is fixed in AM1.6 44779 When scheduling a call via Outlook, Acano Manager did not set the call's timezone to that of the owning user This issue is fixed in AM1.6 44790 Clicking View button on MCU List page displayed all calls in the Calls In Progress page rather than only those on the selected MCU This issue is fixed in AM1.6 44792 The MCU Port Usage page could display inconsistent port usage when multiple MCUs had been configured (when hosting multiple legacy MCUs) This issue is fixed in AM1.6 44799 The Directory Service configuration page only allowed 4 digit ports to be defined. This has been extended to allowed 5 digits. This issue is fixed in AM1.6 44867 Outlook error when trying to add a group email (distribution list) to the meeting This issue is fixed in AM1.6 Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 7 Resolved Issues 44715 AM 1.1 did not support OpenLDAP. This functionality has been added in AM1.6 44875 When an MCU cannot be deleted because there are still URIs/coSpaces on the MCU, display a meaningful error message and a recommended action This issue is fixed in AM1.6 44788 The Directory Services configuration page allows Pipe Commands to be defined on each field to transform values (via Regular Expressions) This functionality has been added in AM1.6 44869 Non-Acano Manager-created coSpaces not showing in the Calls In Progress page This issue is fixed in AM1.6 44877 Phantom activity in MCU port usage page This was caused by activity from a deleted MCU being counted and the issue is fixed in AM1.6 44880 The coSpace autocomplete filter did not detect and display coSpaces with alphabetic URIs. This issue is fixed in AM1.6 44881 Acano Manager 1.1 did not display nonEnglish characters This has been fixed in AM1.6 44883 Allow logged in admin/operator level users to specify a user in the coSpace List so that the Acano server can respond with the coSpaces and coSpace members for the user This issue is fixed in AM1.6 44886 The maximum number of participants allowed in a meeting cannot be extended for an Acano server-hosted meeting that is active This issue is fixed in AM1.6 44890 MCU port usage for a very long period dataset causes page to time-out when the graph is generated from dataset This issue is fixed in AM1.6 44905 MCU port usage doesn’t take user's time zone into consideration This issue is fixed in AM1.6 44911 Catch empty user name on AD/LDAP import Additional logging has been added and this issue is fixed in AM1.6 44912 When creating a new coSpace and defining the “All Equal” video layout, the coSpace was created but participants didn’t see the “All Equal” layout. This issue is fixed in AM1.6 44914 In the Outlook plugin, if you leave the cursor in either Subject or Location when you book the call you see a warning message The message is no longer displayed and this issue is fixed in AM1.6 44915 Typo in warning message of "befor" when you try to book a call via the Outlook plugin and it is not configured The typo is corrected and this issue is fixed in AM1.6 44926 If a user that had not been created via Active Directory/ LDAP tried to create a coSpace, Acano Manager displayed a warning message to the user after it tried to add the non-Acano User as a member of the coSpace. Now in AM1.6, if a non-AD/LDAP created user creates a coSpace, Acano Manager does not set the user as a coSpace member and this issue is fixed in AM1.6 44928 Allow the administrator to choose whether Acano Manager or Acano Server creates coSpaces during the Active Directory/LDAP This feature was added in AM1.6 Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 8 Resolved Issues import process 44929 Allow Acano Manager to modify non-Acano Manager-created coSpaces This issue is fixed in AM1.6 44931 Audio-only participants appeared as video participants in the Calls In Progress page This issue is fixed in AM1.6 44944 44963 When importing large numbers of users from AD/LDAP, Acano Manager’s Importer could prematurely resume processing before the SYNC process had completed on the Acano server. This issue is fixed in AM1.6 44945 If an AD/LDAP configuration had been defined for a system-wide customer (i.e. customer not set), Acano Manager would delete all other users on other customers. This issue is fixed in AM1.6 44952 AD/LDAP import failed to set CallId when CallId was longer than 9 characters. This issue is fixed in AM1.6 44953 During the AD/LDAP import process, users with non-English characters in their names would not be correctly identified within Acano Manager and were deleted from Acano Manager. They would then be recreated but any additional coSpace member associations would have been lost. This issue is fixed in AM1.6 44965 Long running calls created by users dialing into a CoSpace not created by Acano Manager were not automatically extended and were terminated at 12 hours. This issue is fixed in AM1.6 44966 Certain characters (e.g., apostrophe (‘)) where not correctly escaped when passed to the Acano Server resulting in users with an apostrophe in their name not being found. This issue is fixed in AM1.6 44967 When scheduling a recurring call on a coSpace, the 2nd and subsequent call instances did not have the coSpace’s URI (and other defaults). This issue is fixed in AM1.6 44969 We increased the time that Acano Manager waits for the LDAP Synchronize to complete on the Acano server from 25 seconds to 5 minutes. This issue is fixed in AM1.6 44786 Acano Manager was incorrectly sending an empty tenant GUID when creating LDAP objects on the Acano server. Acano Manager now does not send a tenant GUID when creating LDAP objects that do not have a tenant. This is fixed in Acano Manager AM1.6 44785 Acano Manager-created coSpaces were not created with a tenant GUID. In this version Acano Manager creates coSpaces with the appropriate tenant GUID if the coSpace belongs to a tenant/customer. This is fixed in Acano Manager AM1.6 34588 AcanoMcu did not accept an apostrophe (') characater as valid in an alpha URI (optional config key 'AcanoAlphaUriRegex' added) We now support apostrophes as valid characters in alphanumeric URIs by default. This behavior can be modified by adding a regex value as a config value called “AcanoAlphaUriRegex”. This is fixed in Acano Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 9 Resolved Issues Manager AM1.6 Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 10 Known Limitations 5 Known Limitations Reference Issue Summary 34177 Video layouts offered need to be updated The set of video layouts needs to be re-assessed. 34207 Call Quality Records We are unable to generate full call quality records at the moment. However you can get call quality records for selected participants from the Calls in Progress page by clicking on the Statistics icon (three dots). (This turns sampling on.) Drilling down into the statistics data shows the data being received. This data is written to the database and will be available in call quality reports. 44711 User accounts cannot log in when there is no Acano server online If you log in with a user level account when no Acano servers are online, you see "There are no online Acano MCUs configured for this system" as an unhandled asp.net exception. Administrator and Operator users do not see this message. This will be added in a maintenance release but currently the workaround is to ask an administrator should set the Acano server online. The following are known limitations in Acano Manager AM1.6:  There are certain conditions under which coSpaces/calls created when Acano Manager is not running will not be detected when Acano Manager starts  Acano Manager does not obtain dial-in information from the Acano Server  The scripts used to inject text into Outlook calendar appointments/email templates needs manually editing to allow Microsoft Lync click to call (the domain needs to be added because AM1.6 does not get this information from the Acano Server). Please contact your reseller for details of how to do this Known issues in AM1.6:  On large databases (in the order of 1.6m records), the MCU port usage page has problems and the page may time out after 90 seconds  There is an ambiguity on the coSpace List page when signed in as an Administrator. The All button infers that the administrator will be able to see all coSpaces by clicking this button. This is not the case; the Go button finds all coSpaces on the Acano Server whose name matches the filter value. “*” (or wildcard) is not supported.  coSpaces will be deleted and recreated when migrating the AD import from the Acano Server UI to Acano Manager.  In certain cases coSpaces do not show up in the coSpace list when logged in as a user. Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 11 © 2015 Acano (UK) Ltd. All rights reserved. This document is provided for information purposes only and its contents are subject to change without notice. This document may not be reproduced or transmitted in any form or by any means, for any purpose other than the recipient’s personal use, without our prior written permission. Acano and coSpace are trademarks of Acano. Other names may be trademarks of their respective owners. Acano Solution: Acano Manager Release 1.6 Release Notes 76-1033-04-D Page 12