Acano solution. Acano Server & VM Release Release Notes. July V

Transcription

1 Acano solution Acano Server & VM Release Release Notes July V

2 Contents Contents 1 Introduction New Features/Changes in R Calling into scheduled Lync meetings directly and via IVR Changes to screen layouts on SIP endpoints H.323 Gateway Miscellaneous Improvements Improvement in WebRTC bandwidth negotiation Summary of API Additions & Changes Improvements to diagnostics handling via the API Handling multiple cospace access methods Security improvements in accessing cospaces Additional changes Notes on Installing and Upgrading to R R1.7 Deployments Deployments using a single host server Deployments using a single split server hosted on a Core server and an Edge server Deployments for scalability and resilience Upgrading to Release R Downgrading Resolved Issues Resolved in R R and R1.7.4 not released Resolved in R R1.7.1 not released Resolved in R1.7.0 (same build as previously labelled RC1) Known Limitations Steps to upgrade Acano server in America/Montreal timezone Acano Solution: Acano Server R1.7.5 Release Notes V Page 2

3 Introduction 1 Introduction This release note describes the new features, improvements and changes in Release of the Acano solution software for both Acano Server and virtualized deployments. It assumes that you have already upgraded to R or later. If you have not, and are upgrading from 1.2.x, then read the 1.6 release notes first and follow the instructions, before following any instructions in this R1.7 release note. Before upgrading to R1.7, you are advised to take a configuration backup using the backup snapshot <filename> command and save the backup safely on a different device. See the MMP Command Reference document for full details. Note: XMPP server clustering was a beta feature in release 1.6. If you have this feature enabled contact Acano Support before upgrading to release 1.7. A revised version of XMPP server clustering will be available in a future release, but the configuration will be different from the 1.6 beta version. Until this feature is ready, only enable one XMPP server per domain in your Acano solution. Note: if you decide to revert to R1.6 after upgrading to R1.7, any self-signed certificates created on R1.7 cannot be used on R or an earlier build. You will need to recreate the certificates on R1.6. Acano Solution: Acano Server R1.7.5 Release Notes V Page 3

4 New Features/Changes in R1.7 2 New Features/Changes in R Calling into scheduled Lync meetings directly and via IVR Pre-requisite on Lync deployment: This feature requires a working Lync deployment with telephone dial-in capabilities already enabled. Release 1.7 supports calling into a scheduled Lync meeting from WebRTC, SIP or Acano clients, using the Lync call ID to join the call. This feature requires one or more Lync Front End servers to be configured. You can configure one via the Web Admin interface under the Lync Edge settings from Configuration > General, and one or more via the API (create them as TURN servers with type "lyncedge"). Refer to the Acano Solution deployment guide in the section entitled Configuration for Lync Edge for instructions on how to do this. If there are multiple FE servers in a Pool, use the Pool FQDN as the Server Address. Table 1 Configuration tasks to enable calling into scheduled Lync meetings Task On the Web Admin interface Via the API To configure the Call Bridge IVR(s) to allow entry of Lync conference IDs To allow direct dialing to Lync conference IDs from standard SIP systems Note: you may choose to extend an existing configured domain to allow Lync conference access, or to create a new one for this purpose. To allow Lync conference ID entry via the Web Bridge call join interface If you have set up an IVR via the Web Admin: Go to Configuration > General and set "Joining scheduled Lync conferences by ID" in the IVR section to "allowed" Go to Configuration > Incoming calls, and for one or more configured call matching domains, set "Targets Lync" to "yes. If you have set up the Web Bridge via the Web Admin Go to Configuration > General and ensure that "Joining scheduled Lync conferences by ID" in the "Web bridge settings" section is set to "allowed" If you have set up IVRs through the API: Set resolvelync ConferenceIds to true for the configured IVR Set resolvetolync Conferences to true on the incoming dial plan rule If you have set up Web Bridges through the API: Set resolvelync ConferenceIds to true on the Web Bridge Acano Solution: Acano Server R1.7.5 Release Notes V Page 4

5 New Features/Changes in R1.7 If a call is being matched against Lync conference IDs, the Call Bridge first checks that the call ID does not apply to a cospace, if it does not then the Call Bridge identifies a Lync Front End server that it has been configured with, that has advertised itself as having the capability to resolve IDs. The Call Bridge queries the Lync Front End server to determine whether the call ID in question corresponds to a Lync conference - if it does, the look up is deemed to have been successful and the call is joined to the Lync call. If the call ID is not recognized as corresponding to a Lync conference then no further Lync Front End servers will be queried. Note: you may get unexpected results if you add the settings of multiple Lync Front End servers that are in different Lync deployments. For instance, if multiple Lync conferences in different Lync deployments use the same call ID, then more than one Lync Front End server may respond positively to the lookup, in which case the "first" successful Lync resolution is used. The text in the invitations sent for scheduled Lync meetings can be customized to include the necessary details to allow users to join via Acano. These details should be placed in the custom footer section. For example For SIP/H.323 endpoints, join by calling join@example.com and entering the conference ID above. For WebRTC go to join.example.com and enter the conference ID above. The URIs in this must match those configured above. Please see the Microsoft documentation for more details. 2.2 Changes to screen layouts on SIP endpoints Release 1.7 introduces new screen layouts on SIP endpoints. These layouts aim to improve the user experience and focus on the activity within the call, rather than the legacy MCU style of layouts. The changes include: active speaker indication shown by a blue line below the speaker s pane refining who is shown in the all equal layouts based on recent active speakers participants will be shown in "big panes" when they become the active speaker recent active speakers will be shown in big panes, with other participants shown in a "dock" of smaller Picture in Picture (PiP) at the base of the screen people will move out of the "active speaker list" (and thus be "demoted" to the PiP bar) after a period of inactivity (not speaking) for "all equal", stacked and overlay, if there is only one other video stream to be shown then it will be shown full screen, "point to point" mode. in speaker large mode (stacked or overlay) the PIP behavior has been simplified, only showing up to 6 PiPs below the main speaker, even if there are more than 7 other callers in the meeting. other minor changes include: using a grey background instead of black when the whole screen isn't filled with video panes introducing gaps between groups of the same-sized panes (rather than bordered abutting panes) Acano Solution: Acano Server R1.7.5 Release Notes V Page 5

6 New Features/Changes in R1.7 minor changes to the rendering of on-screen pane labels (e.g. a lighter background colour on the pane names) In addition, classic arrangements of 2x2, 3x3, 4x4 or 5x5 are available as layouts through the API, but rather than being fixed pane arrangements, they are adapted to the number of streams to show. For example, if you are using the 2x2 layout and have 3 people to show, you will get a row of 2 panes (half-pane offsetted) above a row of 1, but the panes will be 1/4 screen size. See parameter: defaultlayout, in section Call Leg Methods in the Acano Solution 1.7 API Reference Guide. 2.3 H.323 Gateway The Acano H.323 Gateway enables an H.323 call to connect to the Acano Call Bridge. The H.323 Gateway does not provide firewall traversal or call control, you are recommended to deploy a H.323 Gatekeeper to perform these functions. Refer to the H.323 Gateway deployment guide for more information. With the H.323 Gateway enabled, you can now make the following calls: H.323 call > H.323 GW > cospace H.323 call > H.323 GW > Call Bridge->Lync H.323 call > H.323 GW > Call Bridge->SIP device H.323 call > H.323 GW > Call Bridge->Acano client The H323 Gateway can be enabled on the same server as the Call Bridge or on a separate one. Note: by default the H.323 Gateway uses port Miscellaneous Improvements Release 1.7 supports the following new features: Active speaker indication shown by a blue line below the speaker s pane on SIP endpoints, H.323 endpoints and WebRTC clients On-screen participant count provided on SIP endpoints, showing the total number of people in the call once they are no longer all shown on the screen Improved security options for guest and user access on Web Bridge, see section Ability to disable support for Lync presence through the Web Admin interface (Configuration>Call settings>sip settings>lync presence support). Ability to control whether a user will be allowed to send and receive messages when in a point to point call with another user Improved filtering of event logs through Web Admin interface. You can now filter for: show all messages, show errors and warnings or show only errors. Improved TIP support Allowing cascading of Lync and Acano conferences Improvements to CDRs for distributed non-cospace calls Acano Solution: Acano Server R1.7.5 Release Notes V Page 6

7 New Features/Changes in R1.7 Overlay screen layout: PiPs now only partially cover bottom of large pane, previously they completely covered the bottom of the large pane. Support for new look and feel, and additional features in Acano Client v1.6 separate presentation stream - i.e. allowing clients to receive main and presentation video as separate streams clients informed of "last used time" for configured slave SIP endpoints with the list presented in "most recently used" order more per-participant indications (video muted etc.) Improvement in WebRTC bandwidth negotiation In addition, we have added some improvements to the way WebRTC bandwidth is negotiated in R In the past, because Chrome browsers didn't support dynamic bandwidth estimation, the Acano server used a very low bandwidth to accommodate for lossy/low bandwidth links (even if the user had higher bandwidth). However, newer Chrome browsers have implemented bandwidth estimation and therefore, Acano WebRTC clients can now correctly utilise the available bandwidth for clients. Currently it is not possible to manually set a bandwidth limit for WebRTC client. 2.5 Summary of API Additions & Changes Improvements to diagnostics handling via the API Diagnostic improvements include: allowing access to call diagnostics via the API (POST to initiate new diagnostics, GET and DELETE to manage diagnostics) automatically generating call diagnostics on remote call bridge peers for distributed calls We now allow generating diagnostics to be triggered via the API on a per-cospace basis (you supply the ID of an active cospace), or by specifying the ID of an active call (the call may or may not be made within a cospace). Whether the diagnostics are triggered via this new mechanism or from a client, other call bridges that are hosting a distributed instance of the same call should generate their own diagnostics at that point. All such linked diagnostics should end up with the same GUID on each call bridge, and you are also able to filter the diagnostics (when enumerating via the API) by cospace ID. New profile objects: /calls/<call id>/diagnostics /cospaces/<cospace id>/diagnostics /system/diagnostics /system/diagnostics/<diagnostics id> /system/diagnostics/<diagnostics id>/contents Acano Solution: Acano Server R1.7.5 Release Notes V Page 7

8 New Features/Changes in R Handling multiple cospace access methods In Release 1.7, an administrator can decide which access details are shown in invitations generated by clients. Using the API, specify the scope parameter of accessmethod as either public or private. Those marked as public will be communicated to clients when retrieving the information to show in invitations. If scope is left unset for an accessmethod, by default it is equivalent to private. If a cospace has one access method with scope set to public, the client will be advised of that access method's URI / call ID / passcode / weblink rather than the corresponding cospace-level values. Currently, if a cospace has multiple access methods set to public, the Call Bridge will pick one to send to the client. Note: cospace members are not permitted to edit the URI (etc.) of a cospace that has any public access methods Security improvements in accessing cospaces To prevent someone guessing the call ID of a cospace and gaining access, security improvements have been implemented on the Call Bridge and Web Bridge. An optional additional parameter secret has been added to accessmethod to associate a "secret" passcode per-cospace or per-access method. This secret is included in the link in the invite text and allows direct connection to the cospace. The complexity of the secret prevents brute force attacks. Note: The optional parameter secret will be automatically generated if it is not specified. Ability to disable access via the web link, manual entry of call details or user login on the Web Bridge. Additional modes to control manual entry of cospace details. It is now possible to configure a cospace so that guests must supply the call ID and passcode at the same time, rather than the call ID first, and if it's found to be valid, then supplying the passcode. This prevents brute force attack on call IDs followed by an attack on passcodes Additional changes Additional parameters for the following methods: Call methods calllegprofile methods cospace methods cospace accessmethods inbounddialplanrule methods IVR methods Web Bridge methods User Profile methods Acano Solution: Acano Server R1.7.5 Release Notes V Page 8

9 New Features/Changes in R1.7 New failure reason duplicatecospacesecret New options in defaultlayout parameter allequalquarters allequalninths allequalsixteenths allequaltwentyfifths Refer to the Acano Solution 1.7 API Reference Guide for further information. Additions to the guide for R1.7 are shown in red for easy reference. Acano Solution: Acano Server R1.7.5 Release Notes V Page 9

10 Notes on Installing and Upgrading to R1.7 3 Notes on Installing and Upgrading to R1.7 This release note assumes that you have already upgraded to R or later. If you have not, and are upgrading from 1.2.x, then read the 1.6 release notes first and follow the instructions, before following any instructions in this R1.7 release note. CAUTION: Before upgrading to R1.7 you must take a configuration backup using the backup snapshot <filename> command and save the backup safely on a different device. See the MMP Command Reference document for full details. 3.1 R1.7 Deployments R1.7 supports the new deployments introduced in R1.6: the single combined Acano server, the single split server and the deployment for scalability and resilience Deployments using a single host server If you are installing the Acano solution for the first time on a single host server (a combined deployment), we recommend that you read and follow the documentation in the following order: 1. Appropriate Installation Guide for your Acano Server or virtualized host. 2. The Acano solution 1.7 Single Combined Acano server Deployment Guide enabling all the solution components on the single host. This guide refers out to the Acano Certificate Guidelines for Single Combined Acano Server Deployments for details on obtaining and installing certificates for this deployment Deployments using a single split server hosted on a Core server and an Edge server If you are installing the Acano solution for the first time in a split server model, we recommend that you deploy the XMPP server on the Core server, and deploy the Load Balancer on the Edge server. Read and follow the documentation in the following order: 1. Appropriate Installation Guide for your Acano server or virtualized deployment 2. The Acano solution 1.7 Single Split Acano server Deployment Guide. This guide refers out to the Acano Certificate Guidelines for Single Split Acano Server Deployments for details on obtaining and installing certificates for this deployment Deployments for scalability and resilience If you are installing the Acano solution for scalability and resilience using multiple host servers, we recommend that you deploy the XMPP server on Core servers, and deploy Load Balancers on the Edge server. Read and follow the documentation in the following order: 1. Appropriate Installation Guide for your Acano server or virtualized deployment 2. The Acano solution 1.7 Scalability and Resilience Deployment Guide. This guide refers out to the Acano Certificate Guidelines for Scalable and Resilient Acano Server Deployments for details on obtaining and installing certificates for this deployment Acano Solution: Acano Server R1.7.5 Release Notes V Page 10

11 Notes on Installing and Upgrading to R Upgrading to Release R1.7 The instructions in this section apply to both Acano Server and virtualized deployments with a previous Acano solution release already installed. Upgrading the firmware is a two-stage process: first, upload the upgraded firmware image; then issue the upgrade command. (This restarts the Acano solution: the restart process interrupts all active calls running on the Acano solution; therefore, this stage should be done at a suitable time so as not to impact users or users should be warned in advance. To install the latest firmware on the Acano server follow these steps: 1. Obtain the upgrade image from the secure partner section of the Acano website. You should have obtained a file called upgrade.img. If this is not the case rename the file to upgrade.img. Note: If you are using WinSCP for the file transfer, ensure that the Transfer Settings option is binary not text. Using the incorrect setting results in the transferred file being slightly smaller than the original and this prevents successful upgrade. 2. Using a SFTP client, log into the MMP using its IP address. The login credentials will be the ones set for the MMP admin account. If you are using Windows, we recommend using the WinSCP tool. Note 1: You can find the IP address of the MMP s interface with the ipv4 admin command or the equivalent ipv6 command. Note 2: The SFTP server runs on the standard port, 22. Note 3: After copying the upgrade.img file, you will not be able to see it listed as being in the file system; this is normal. 3. Copy the software to the Acano Server/ virtualized server. 4. To apply the upgrade, issue the upgrade command. a. Establish a SSH connection to the MMP and log in. b. Initiate the upgrade by executing the upgrade command. upgrade The Acano Server/ virtualized server restarts automatically: allow 10 minutes for the process to complete. 5. Verify that the Acano solution is running the upgraded image by re-establishing the SSH connection to the MMP and typing: version 6. Check the Configuration > Outbound Calls rules updating the Local Contact Domain field and completing the new Local From Domain field if necessary. 7. Update the customization archive file when available. 8. Only if you are deploying a scaled or resilient deployment (with more than one server host Acano server, virtualized host or a combination) read the Scalability & Resilience Deployment Guide and plan the rest of your deployment order and configuration. 9. Go on to the next section. Acano Solution: Acano Server R1.7.5 Release Notes V Page 11

12 Notes on Installing and Upgrading to R Downgrading To return to the older version of the Acano solution, use the regular upgrade procedure to upgrade to the appropriate version, and then restore the configuration backup for that version. Acano Solution: Acano Server R1.7.5 Release Notes V Page 12

13 Resolved Issues 4 Resolved Issues Resolved in R1.7.5 Reference Issue Summary 5649/7991 Occasional loss of video for WebRTC client 8271 Web Bridge stability issues under heavy load 8299 Remote mute options not shown for Guest Users Occasionally, when using the Chrome WebRTC client, starting or stopping the content stream or changing the audio/video source, may cause the incoming video from the Acano server to fail. An error message similar to 'WebRTC video playback issue detected' or 'Loading media - please wait' with a spinning icon, may display on the WebRTC client. If the video does not recover within a short period, the work-around is for the WebRTC client to leave the cospace and rejoin to recover media. Fixed in R Issues were seen with some webrtc connections in large meetings. Fixed in R1.7.5 Fixed in R SIP Timer Support Changing 200OK responses for the handling of timers will now use require: timer only when timers were supported in the Invite. Fixed in R Information leak via misconfigured webbridge 8414 Lync clients reject 200OK when edge server is configured Webbridge mistakenly listens on port The webbridge application, without the protection of the HTTP security proxy, allows files on the root filesystem to be read. See security alert 023 in the Security Alert Information. Fixed in R Issues with support of the Alternate Server Attribute to handle deployments with multiple TURN servers. Fixed in R Crash seen during LDAP Sync Fixed in R Not possible to customize the color of the arrows on the WebRTC login page Following the invited.sf?id=1 link when already logged in redirects to main.html 8502 Interoperability problems reported when sending a zero m-line in an SDP with dynamic payload types without an accompanying rtpmap parameter Fixed in R Fixed in R Fixed in R Issues with writing to the Server log In certain circumstances the server s log file was not being updated correctly. Fixed in No more than one call via H323_gateway is allowed to join a lync meeting Fixed in R OpenSSL Vulnerabilities This issue is reported as Security Alert 024. Fixed in R1.7.5 Acano Solution: Acano Server R1.7.5 Release Notes V Page 13

14 Resolved Issues 8611 Server crashes when receiving malformed SDP Vulnerability to Denial of Service during XMPP authentication This issue is reported as Security Alert 025. Fixed in R This issue is reported as Security Alert 026. Fixed in R R and R1.7.4 not released. Resolved in R1.7.2 Reference Issue Summary 7205 Incoming PSTN call failure Fixed in R Multiple new subscriber uri error messages displayed in log file Wrong voice prompt sometimes heard when joining tenant cospace using IVR 8260 Problems restoring backup snapshot taken from to a server running release DTMF relay not supported by Acano H323 gateway 8304 Inter Call Bridge link fails to reestablish after network partition 8329 Video quality issues seen with Skype for Business Incorrect handling of SIP SUBSCRIBE messages led to multiple error messages displayed in log file: Warning: new subscriber uri:.. doesn't match original subscriber uri. Fixed in R Joining a tenant cospace from the IVR to an additional accessmethod on a cospace results in the default voice prompt being heard. Fixed in R The problem was not with the backup file but with the restore process. Fixed in R H.323 gateway does not support alphanumeric H.245 from far end. Fixed in R In some circumstances the inter Call Bridge link would not be correctly disconnected, which could lead to inconsistencies in distributed calls. Fixed in R1.7.2 The Acano server was repeatedly requesting I-Frames for the incoming video. Fixed in R R1.7.1 not released. Resolved in R1.7.0 (same build as previously labelled RC1) Reference Issue Summary 5448 GUID displayed in weblink rather than call ID 5687 Cannot change branded logo on connected SIP endpoint 5932 Grey bar at bottom of Web Bridge landing page always displayed If a user receives a direct call from another Acano user (i.e. not a call in a cospace) and the user then clicks the information button, the web link is displayed with a GUID instead of a URI/call ID/passcode. Fixed in R1.7.0, see section in this release note. If a user dials into a meeting using a connected SIP endpoint, the endpoint displays the Acano logo and the callbrandingprofile is not applied to the endpoint. Fixed in R Footer at bottom of Web Bridge landing page cannot be customized. Fixed in R showfooter option added to sign_in_settings.json. Acano Solution: Acano Server R1.7.5 Release Notes V Page 14

15 Resolved Issues 6766 WebRTC clients do not support DTMF tones 6894 Malformed API calls return information 6898 Using the WebRTC client to call a contact who is not logged in, takes you to an empty conference rather than tell you that the call has failed 7429 G.722.1c issues with non-interworked call to LifeSize endpoint Fixed in R DTMF keypad now displayed in Web clients and DTMF tones are proxied to the remote system or interpreted from the remote system by the Call Bridge. Fixed in R API calls need to be formed properly otherwise they display an error. This makes it feel like the user has successfully entered an empty cospace instead of failing to call out to a user who is off line. Fixed in R1.7.0 Fixed in R Acano media module restart A bug in the Acano H.264 encoder can very occasionally cause a media module to restart, but not cause a full server restart. Fixed in R Lync audio client disconnected in cospace when Acano client starts sharing content 7862 Calls made within a cospace fail to Lync clients, while point-to-point calls are successful 7900 Directory searching fails if 1 search location does not work 7940 Activity list cleared of some entries after client logs out of clustered deployment 8049 Chat between Lync clients on different Call Bridges in a distributed call does not work Fixed in R Fixed in R If one directorysearchlocations fails, then all directory searches fail. Fixed in Point-to-point calls and calls to cospaces that have no chat in them are wiped from the activity list after only a few minutes of the client logging out. Fixed in R Lync clients can only chat between each other if they land on the same Call Bridge. Fixed in R Loss of video from 2010 Lync client cospace no longer displays video from 2010 Lync client after video is stopped and then restarted. Fixed in R1.7.0 System level CallProfile not applied to ad hoc conferences created by tenanted users If a system level call profile is set, ad hoc calls created by a user who is a member of a tenant will not always have the call profile applied. In particular, the profile is not applied if the system has been rebooted since it was set. Fixed in R Acano Solution: Acano Server R1.7.5 Release Notes V Page 15

16 Known Limitations 5 Known Limitations If you encounter any of the following issues, contact support@acano.com because we are likely to have test builds to send you with fixes for many or all of them by the time you find them. Reference Issue Summary 3965 Unable to stop pcap capture on serial/ssh 4132 Prevent logging in to the Web Admin Interface Occasionally users running pcap from the serial console for a few minutes are unable to stop the capture with a Ctr+C. If this happens try Ctr+\ or contact Acano support. By going to the Web Admin Interface login page, clicking OK to login and then holding down F5, all the sessions will be used without even logging in. This prevents anyone else from logging in until those sessions expire. This issue will be addressed in a future release No DNS failover for AD sync Although the initial problem of the Call Bridge not falling back to a second AD server address after the LDAP connection to the first failed has been fixed in R1.2, there remains the issue that trying to connect to a non-existent/non-responding remote address can take a long time to time out Sharing a presentation in full screen mode does not work using Chrome Firefox 37+ WebRTC client cannot connect to cospace Using the WebRTC client through Chrome, and sharing a presentation in full screen mode, the web client continues to only show the application. Possible work-arounds are: - share screen rather than application - share the Powerpoint only after starting the presentation Various issues experienced joining a cospace using Firefox 37+ web browser, including the browser crashing Wiggling panes in dock area Participant panes in dock at bottom of screen may appear unsteady participantlimit field per tenant does not apply across calls hosted on multiple Call Bridges The participantlimit field, which may be set through the API, can be applied in two places: on a tenant or as part of a callprofile. When participantlimit is configured for a tenant, it acts to limit the number of participants across all calls corresponding to that tenant. However this only works correctly in single Call Bridge deployments. In a scalable and resilient deployment, with distributed Call Bridges, the limit is applied per Call Bridge. When participantlimit is used as part of a callprofile it works correctly in both the single and distributed Call Bridge cases Syscall errors in logs If a WAN optimiser is deployed between clustered database nodes, it may prevent keep-alive checks from completing, causing SYSCALL errors to appear in logs. In cases where a WAN optimizer is being used between cluster nodes, it is important to ensure that all keep alive traffic is sent in a timely manner. Consult your WAN optimizer documentation on how to either disable this functionality between specific IP addresses, or for options that control which optimisations are applied Upgrading server to R1.7.5 or later fails for America/Montreal time zone This is caused by the link for America/Montreal being removed from the timezone data. Follow the steps outlined in section 5.1. Acano Solution: Acano Server R1.7.5 Release Notes V Page 16

17 Known Limitations 5.1 Steps to upgrade Acano server in America/Montreal time zone Follow the steps below to successfully upgrade an Acano Server to R1.7.5 in the America/Montreal time zone: 1. Using the MMP command line, set timezone to an allowed time zone for example America/Toronto, other than America/Montreal on the server to be upgraded timezone America/Toronto 2. Reboot the server, and log back into the MMP reboot 3. Create a backup file of the time zone backup snapshot timezone 4. Overwrite the current configuration file with the backup backup rollback timezone 5. Copy the new software to the server and upgrade the server Acano Solution: Acano Server R1.7.5 Release Notes V Page 17

18 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 is a trademark of Acano (UK) Ltd. Other names may be trademarks of their respective owners. Acano Solution: Acano Server R1.7.5 Release Notes V Page 18