Introduction

These release notes provide you with information about the latest upgrade to the StarLeaf Cloud, Portal, and endpoints. This is a feature release and is effective from November 2017.

All upgrades take place outside of normal office hours for all regions. Endpoints automatically restart and reconnect to the Cloud after the upgrade.

StarLeaf operates a system of rolling upgrades across our data centers, which are distributed globally. New features may be enabled separately.

New features

Everyone can now download and sign into the new StarLeaf app. (Go to our app download page ).

The StarLeaf app is a simple, secure and reliable application for messaging, meetings and calling. It works from anywhere, on any device, so colleagues can collaborate, share and discuss as easily on the move as at work, and it is completely interoperable with other third party video conferencing systems.

Cloud version 5.3 provides the following new features:

Feature Description

App localization

StarLeaf is now localized on iOS, Windows, macOS and Android for the following languages:

  • Brazilian Portuguese (macOS only)
  • Chinese (Simplified)
  • Chinese (Traditional)
  • Czech
  • Danish
  • Dutch
  • English (US)
  • Finnish
  • French
  • German
  • Italian
  • Japanese
  • Korean
  • Spanish
  • Swedish

The language that the app uses will depend on a user’s own device settings. For example, if a user’s iPhone is set to use German, then the app will be in German.

When a user signs up through the app, that user’s device language will be used to set the language for that user in the StarLeaf Portal (if that language is one of the supported languages). However, you cannot control the language setting for the app through the StarLeaf Portal. The language setting for a user in the Portal does not override the device settings and has no effect on the localization of the app.

For information about localization and the StarLeaf Cloud, refer to Localization of StarLeaf endpoints, apps, and Portal

Option to hide directory entries

By default, all users in an organization will appear in the directory for that organization. Cloud 5.3 introduces the ability to hide a user in the directory. If this is a requirement for an organization, contact StarLeaf Support.

For more information, refer to About the directory

Cloud API

In Cloud 5.3, the response to a GET request for an occurrence of a recurring meeting will include a boolean indicating whether or not that meeting has been canceled.

For more information, refer to Using the StarLeaf Cloud API

Issues resolved

Cloud 5.3

Bug fixes effective in StarLeaf Cloud 5.3:

ID Description
13736 Improved audio for StarLeaf on iOS
13809 Cloud ECAPI will now always fetch every page of requested contacts immediately
14785 In the previous release, the encryption status of a call was not visible in the Portal call detail records. Cloud 5.3 fixes this issue
14523 In the previous releases, under certain circumstance, a Cisco Acano call into a StarLeaf scheduled meeting could sometimes fail to connect. Cloud 5.3 fixes this issue
  A number of general improvements to stability and performance of StarLeaf Cloud endpoints

Known limitations

For per-vendor interoperability information, refer here.

Reference ID Description
5454 Breeze full screen mode is not supported on Mac OSX versions below 10.7
10858 Internet Explorer 11: When you access a user page on the Portal using Internet Explorer 11, the time zone selection box automatically opens
11755 There is a BFCP interoperability issue between Cisco VCS and the StarLeaf Cloud which can cause screen share to be disabled mid call
12040 Using Click-to-Call in the Safari browser on OSX sometimes results in difficulties receiving shared content and dropped calls when the Safari tab is minimized for longer than 10 seconds. This is due to the AppNap feature on OSX that puts background applications to sleep if they are not in the foreground
12067 In some circumstances, when a Skype for Business client attempts to add video or content into a StarLeaf conference with no other video participants there can be unexpected call failure
12134 For calls where one participant is using a Polycom Trio, audio and/or video might stop when starting or stopping content share