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

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.

Issues resolved

Bug fixes and improvements effective in StarLeaf Cloud 8.4.1:

ID Description
StarLeaf Cloud
11832 In previous Cloud versions, screen sharing in a StarLeaf meeting between a Polycom HDX endpoint and a Skype for Business client was not always successful until a StarLeaf app user joined the meeting. Similarly, screen sharing from a Polycom HDX endpoint registered to StarLeaf Cloud into a Skype for Business meeting was not always successful. Cloud 8.4.1 fixes both these issues
StarLeaf on Windows
19260 In a previous French version of the app, some text in the Join with meeting ID dialog was cut off. Cloud 8.4.1 fixes this issue
StarLeaf on macOS
18104 In a previous version, under rare circumstances, the app temporarily froze after a user entered the one-time code to sign in. Cloud 8.4.1 fixes this issue
19234 In a previous version, when you read or replied to a message on the StarLeaf app for macOS, the client did not always update that message to ‘read’ and the unread message count in the Chats list persisted. Cloud 8.4.1 fixes this issue

Versions in Cloud 8.4.1

Component Minimum version in Cloud 8.4.1
StarLeaf Windows 2.19.56
StarLeaf macOS 2.19.57
StarLeaf iOS 2.19.55
StarLeaf Android 2.19.54

Known limitations

For per-vendor interoperability information, refer here.

Reference ID Description
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

Using Click-to-Call (WebRTC) 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

Click-to-Call is not supported on Safari from version 11.2 onwards. This is due to changes in Safari that mean the browser no longer supports plugins. For more information on browser support and compatibility, refer to Click-to-Call

12067 In some circumstances, when a Skype for Business client attempts to add video or content into a StarLeaf meeting with no other video participants there can be unexpected call failure