Managing StarLeaf releases Earlier releasesLast updated February 4, 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 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.
You can now edit your audio and video settings before you make a call in Windows and macOS. To do so go to Account > Audio and video settings. You can select from available cameras, microphones, and speakers. You can also adjust the audio level of your microphone and enable/disable microphone and camera.
You can now search for permanent StarLeaf meetings (sometimes known as VMRs or meet-me) in the StarLeaf app omnisearch. You can also add a permanent meeting as a favorite. Permanent meetings can be identified by their avatar (shown on the left).
Unless you have muted your camera, self view is now always displayed in a StarLeaf app video call.
The Cloud API now supports the getting and setting of MyProfile. This could be useful, for example, where a client needs to set a user’s default conference layout. For more information, refer to User-level requests.
Bug fixes effective in StarLeaf Cloud 5.4:
|10224, 15285||Skype for Business and Bluejeans green-button integration now works for all StarLeaf Cloud room systems even if they have an email address configured in the portal.|
|13475||In previous releases, under certain circumstances, if the StarLeaf app was not active when a call was incoming, app might not ring. Cloud 5.4 fixes this issue|
|14640||Interoperability when using BFCP with Cisco CUCM and StarLeaf Cloud is now fixed|
|15081||The personal jump off page for conferences now include the dialing details to join the meeting from Skype for Business|
|15162||Breeze users now get a favorite and a personal contact for everyone that they invite to use StarLeaf, even if the invitee uses the StarLeaf app|
|15362||The Cloud will no longer generate push notifications for meetings that a person has declined|
|15388||In the previous release, a meeting organizer’s join now button did not light green for a meeting where another participant who was not in the same organization had declined the meeting. Cloud 5.4 fixes this issue|
|15494||DTMF now behaves as expected with Cisco Webex on a StarLeaf-Cloud- registered Polycom endpoint|
|15539||In the previous release, under certain circumstances, a Click-to-Call (WebRTC) user could unexpectedly quit a conference on ending screen share. Cloud 5.4 fixes this issue|
|15541||In the previous release, there could be display issues for a Click-to-Call (WebRTC) user rejoining a conference that was an audio-only conference when the user left it, but had since become a video conference|
For per-vendor interoperability information, refer here.
|Samsung Galaxy Note 8 incorrectly reports that StarLeaf app is accessing the device camera and microphone randomly and in between calls. The StarLeaf app only accesses a device camera and microphone during a call|
|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|