Managing StarLeaf releases Earlier releasesLast updated December 17, 2019
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 June 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.
Cloud 7.2 provides the following new features:
Single sign-on for Office 365
The StarLeaf Outlook add-in for Office 365 now uses single sign-on. This means that users only need to authenticate with their Microsoft email service for the purpose of scheduling meetings using the add-in. Previously, you were required to sign into both Microsoft and your StarLeaf account before being able to use the add-in.
After the upgrade, anyone using the add-in will need to sign in again. This is a one-time sign in.
The email address that you use to sign in to Microsoft must be the same email address that is associated with your StarLeaf account. If this is not the case, contact StarLeaf Support.
|Disable user activation emails||When users are added to the Cloud either through the Portal or through an integration such as Okta, the Cloud sends the user an ‘account activation’ email. You can now elect to disable the sending of this email and instead inform your users in whatever way you choose. To disable the sending of activation emails, in the StarLeaf Portal choose Edit organization > Advanced settings and deselect Automatically notify users added in the Portal, or through an integration, by email|
|Hide users in the directory||
You can choose whether individual users will appear in the directory or not. By default, every user will appear in the directory. To hide a user from the directory, in the StarLeaf Portal:
|Localization||StarLeaf on iOS is now available in Norwegian. For more information about localization, refer to Localization of StarLeaf endpoints, apps, and Portal|
Bug fixes effective in StarLeaf Cloud 7.2:
|StarLeaf on iOS|
|13301||The number keypad is now always available in audio calls|
|15648||In the previous version, for meeting participants using StarLeaf on iOS, if the call went from being a video call to being an audio-only call, the iOS participant could experience display issues. Cloud 7.2 fixes this issue|
|16368||Improvements for the app display for iPhone X|
|16428||When answering an incoming call from the lock screen, the audio will always default to the handset. If the user then decides to use video in the call (by pressing the video button), the audio will automatically use the speakerphone|
|17079||In the previous version, choosing the ‘send feedback’ control twice could cause the app to stop working. Cloud 7.2 fixes this issue|
|StarLeaf on Windows, macOS, iOS and Android|
|16457||The details view for a permanent meeting will now show the dialable number for that meeting as the 7-digit meeting ID|
|17211||In the Meetings view, where multiple meetings are listed, they will always be listed in the order in which they will take place|
|Component||Minimum version in Cloud 7.2|
For per-vendor interoperability information, refer here.
|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|