Managing StarLeaf releasesLast updated November 13, 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 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.
Cloud 8.5 provides the following new features:
|Joining scheduled meetings||
In previous Cloud versions, you could join scheduled meetings ten minutes before the scheduled start time and never after the scheduled end time.
You can now join scheduled meetings as soon as they are created and for up to four weeks after the scheduled end time. This is especially useful if you want to join a meeting early to be prepared
|ECAPI control of video screen layout||It is now possible to control the on/off behavior of self-view and picture-in-picture on the touchscreen of a room system by using the Endpoint Control API. For more information about the Cloud ECAPI, go to Introduction to endpoint control|
|New SIP trunk provider: Weblink||StarLeaf integration with PSTN SIP trunks, known as VoiceConnect, now supports Weblink (SE) as another SIP trunk provider. For a full list of supported SIP providers, see Portal configuration for PSTN SIP trunks|
BETA Join button on Polycom endpoints
StarLeaf has improved its integration with Polycom endpoints. When a StarLeaf meeting is due to start, the Join button on a Polycom endpoint now lights up.
This feature is in beta and is intended as an early preview for testing. Beta versions of features may not be as stable as those on general release
|Single sign-in: StarLeaf Scheduler for Outlook Exchange Server||
If you are a StarLeaf user, you no longer need to enter your username and password to use the StarLeaf Scheduler for Outlook Exchange Server. The scheduler automatically uses your credentials from when you signed into the StarLeaf app for Windows.
From Cloud 8.5 :
|StarLeaf Slack App||
The StarLeaf Slack App has been redesigned to improve the user experience when joining a meeting.
StarLeaf for Slack is a Slack integration developed and supported by StarLeaf, which allows users to easily escalate instant messaging sessions to audio and video meetings by simply typing the /starleaf command in Slack.
For more information about using the StarLeaf Slack App, go to Integrating video calling and data sharing into Slack
|OneLogin user provisioning||
Organizations that use OneLogin for user management can now integrate that with their StarLeaf account. OneLogin integration is available for organizations with a StarLeaf Enterprise account.
For more information about integrating StarLeaf and OneLogin, go to Configuring provisioning for StarLeaf using OneLogin
Meeting privacy can now be set when you create a StarLeaf meeting using any of the StarLeaf scheduling integrations.
When a meeting is set to private, only the name of the meeting organizer appears beside the word ‘Meeting’ in public spaces such as on the Join button of a room system touchscreen controller.
StarLeaf Scheduler for Outlook Exchange Server or Office 365: When scheduling a meeting, select the lock icon in the meeting invitation toolbar to edit meeting privacy
StarLeaf Scheduler for Google Calendar: When scheduling a meeting, select the Default visibility field to edit meeting privacy
Bug fixes and improvements effective in StarLeaf Cloud 8.5:
|9806||In previous Cloud versions, it was not possible to reschedule a past meeting to a time/date in the future. Cloud 8.5 fixes this issue|
|10293||The green Join button for meetings now stays lit and active for up to five minutes after the scheduled end time or up to five minutes after the last participant leaves the meeting (if this is a time after the scheduled end time). Previously, the Join button would disappear at the scheduled meeting end time|
|12007||Improvement to the appearance of MeetNow calls|
|14598||In certain circumstances, after an admin installs and authorizes the StarLeaf Slack integration on their Slack account, the admin may be redirected to a blank web page. Cloud 8.5 fixes this issue and the admin is instead redirected to the Portal integrations page|
|14756||In previous versions, if the StarLeaf Scheduler for Outlook Exchange Server was mass-deployed using the ALLUSERS flag, the add-in could incorrectly check for upgrades and prompt individual users to upgrade. Cloud 8.5 fixes this issue and users are not prompted to upgrade|
|17369, 17370||General improvements to VoiceConnect when configured to Australian locations|
|18249||In previous Cloud versions, room systems with a call.sl style address that were added to scheduled meetings and subsequently removed on the Portal continued to show the green Join button. From Cloud 8.5, the room system updates correctly and the Join button disappears if the room system is removed from the meeting|
|19068||Previously, in a series of recurring meetings in the Office 365 calendar, it was not possible to make a single occurrence meeting a StarLeaf meeting. From Cloud 8.5, this is possible using the StarLeaf Scheduler for Outlook Office 365|
|19102||In the Branding section of the StarLeaf Portal for resellers, the ‘Cancel’ button redirected you to an incorrect page. Cloud 8.5 fixes this issue|
|StarLeaf room systems|
|12059||From Cloud 8.5, SSH access to StarLeaf room systems has been removed|
|StarLeaf on Windows|
|19366||Improvement to the user interface text within group chats|
|StarLeaf on macOS|
|17273, 19151, 19214||General improvements to the user interface|
|19341||In previous versions, if a user’s organization was set to use the 12-hour time format, the timestamps on messages within chats could still appear in 24-hour format. Cloud 8.5 fixes this issues and the chosen time format is consistent across the app|
|19344||Improvement to the user interface text within group chats|
|StarLeaf on Android|
|19189||Improvement to the behavior of in-call audio controls|
|17370||In previous versions, some users were unable to sign into the StarLeaf Scheduler for Outlook Office 365 due to a customized time zone setting. From Cloud 8.5, users see a request to change this customization and can then successfully sign into the integration|
|19493||In previous versions, if a user created a meeting using the StarLeaf Scheduler for Outlook Office 365 and the user was not registered for a Microsoft webhook, a meeting invite appeared as usual in the Outlook Calendar but the meeting would fail to be created in the StarLeaf Portal. Cloud 8.5 fixes this issue|
|19071||In previous versions, when using the StarLeaf Scheduler for Outlook Office 365, it was not possible to create a recurring StarLeaf meeting in the format ‘Every Nth <Day of the Week> of the month’, for example, ‘Every 3rd Tuesday of the month’. Cloud 8.5 fixes this issue|
|Component||Minimum version in Cloud 8.5|
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 and StarLeaf Cloud
|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|