Managing StarLeaf releases Earlier releasesLast updated October 7, 2021
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 February 2019. Cloud 8.7 supersedes Cloud 8.6.1.
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 8.7 provides the following new features:
|Multiple dial-in numbers||Accessibility to StarLeaf meetings using PSTN / dial-in numbers for certain countries has been improved. If you want to join a StarLeaf meeting using a telephone for audio, you now have a choice of two dial-in numbers instead of just one. The dial-in numbers are included on all meeting invites and in the joining instructions provided to invitees|
|Higher bandwidth calls when sharing content||
Improvements have been made to call quality by increasing the bandwidth when you are in a video call and sharing content. Various bandwidths up to a maximum of 2496kbps are now available.
For admins: In the Portal, you can set maximum send and receive rates at a site level. By default these are set to ‘Automatic’, meaning the maximum rate possible, but you can choose to specify a fixed value between 64kbps and 2496kbps instead if you need to. To adjust these rates, go to Portal > Sites > Edit sites
|Room system sleep controls||CEC and HDMI sleep controls are now available to configure in the Portal in the Audio and video settings of a room system. There are two new settings that you can choose to tick / untick: Enable HDMI output sleep and/or Enable CEC|
|Room system audio improvements||General audio improvements when sharing content through HDMI connection to a GT Mini which also results in improvements to echo canceling|
|Changes to user interface of the touchscreen and phone||
Cloud 8.7 includes changes to the UI of the StarLeaf Phone and touchscreen controller for room systems. Following user feedback, updates were made to various tab controls, icons, colors, and shadows to improve usability and optimize user experience
|StarLeaf Scheduler for Google Calendar||
Following a Google update, the StarLeaf Scheduler button was hidden from view on the Google Calendar. In the coming weeks, a new StarLeaf Scheduler button will be available in the top left-hand corner of the Google Calendar window as shown below.
Join button on Polycom endpoints
StarLeaf can now be integrated with Polycom endpoints so that when a StarLeaf meeting is due to start, the Join button on a Polycom endpoint lights up. You can then join the StarLeaf meeting with one press of the Join button.
For admins: To enable the Polycom Join button integration on your StarLeaf account, contact StarLeaf support.
For more information about configuring the Join button on Polycom endpoints, go to How to configure Poly Join button integration
|Azure Active Directory user provisioning||
Organizations that use Azure Active Directory user provisioning (Azure AD) for user management can now integrate it with their StarLeaf account.
Azure AD integration is an additional option on your StarLeaf Enterprise account. For more information, go to Azure Active Directory
Bug fixes and improvements effective in StarLeaf Cloud 8.7:
|StarLeaf PT Mini|
|19640||ECAPI controls for ‘next’ and ‘previous’ video layout were not functioning correctly. From Cloud 8.7, they are now working as intended|
|19755||General improvements to audio in poor network conditions|
|StarLeaf room systems|
|19783||General improvements to audio and echo canceling|
|StarLeaf on Windows, macOS, iOS, and Android|
|17952||When switching from Wi-Fi to 3G/4G, or VPN to no VPN, the app showed the ‘Waiting for network’ page and could continue to do this until you restarted the app. Cloud 8.7 fixes this issue, and network changes no longer cause a delay|
|StarLeaf on Windows|
|11302||Improvements to the UI and notification that appears when you close the app for the first time after a fresh start which informs you that StarLeaf is still running in the background|
|16089||Improvements to the resizing and scalability of the app window|
|16860, 19366||Improvements to the user experience when you are creating a group in the app and to in-chat messages which let everyone in a group know that you added a member|
|18399||In certain circumstances, if you shared a JPEG image from your computer into the app, the orientation of the image in the share preview may have differed to the original. Cloud 8.7 fixes this issue and image preview is consistent with the original|
|19576||Improvements to the appearance of icons in the app|
|StarLeaf on iOS|
|17113||In rare circumstances, the app could crash when you attempted to attach a 1GB zip file. Cloud 8.7 fixes this issue|
|19964||When you shared an image using the ‘Choose from files’ sharing option, the full image was not always visible in the chat. Cloud 8.7 fixes this issue|
|StarLeaf on Android|
|19929||Android 4.4 and 4.4.4 are no longer supported by StarLeaf. The minimum supported version is now Android 5.0|
|19934||Improvements to the user interface when you are in an audio-only call|
|19936||In rare circumstances, if you were in a call but the app was sent to the background, a second incoming would cause the call screen to appear but only show the original call, not the second incoming call. Cloud 8.7 fixes this issue and the second incoming call becomes visible on the call screen|
|19812||StarLeaf Scheduler for Google Calendar : General bug fixes and improvements that will be visible in the coming weeks|
|19851||StarLeaf Scheduler for Outlook Exchange Server: Bug fix to the process of editing one meeting in a series of recurring meetings when the privacy setting is enabled. This fix will be visible in the coming weeks|
|20210||StarLeaf Scheduler for Outlook Exchange Server: Under certain circumstances, if the scheduler was mass-installed using the MSI installer, a request to install the StarLeaf app could appear when you launch the scheduler even if the StarLeaf app is already installed. Cloud 8.7 fixes this issue and this will be visible in the coming weeks|
|19994||StarLeaf Scheduler for Outlook Office 365: Under certain circumstances, when you created a meeting using the scheduler, the meeting ID generated in the invite text differs from the meeting ID provided in the additional StarLeaf instructions for joining. Cloud 8.7 fixes this issue and meeting IDs will remain consistent. This fix will be visible in the coming weeks|
|Component||Minimum version in Cloud 8.7|
|Scheduler for Outlook Exchange Server||18.104.22.1685|
For per-vendor interoperability information, refer here.
|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|
|20328||StarLeaf Scheduler for Office 365: In rare circumstances when you are using a Mac computer, if you change the time of a StarLeaf meeting that you created with the scheduler, the scheduler attempts to create a new meeting instead of editing the existing one. If you choose to create a second meeting, the joining details of this meeting will not work; only the preexisting details can be used to join the meeting. This issue is under investigation and will be fixed as soon as possible|