Managing StarLeaf releases Earlier releasesLast updated March 11, 2020
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 August 2017.
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 version 4.6 provides the following new features:
In Cloud 4.6, the Cloud API introduces:
For more information about the Cloud API, refer to Using the Cloud API
Cloud 4.6 allows the creation of custom integrations with the StarLeaf Cloud. This is useful where you want to create a client that can access the Cloud API to, for example, create conferences or add users.
If you want to have custom integrations enabled for your organization, contact StarLeaf Technical Support
|Support for Microsoft AVMCU||
The StarLeaf Cloud now supports calls into meetings hosted by Microsoft AVMCU. This is an optional extra that can be included as part of your organization’s endpoint subscriptions.
The following calling scenarios are supported:
|Quality of Service support||
Cloud 4.6 introduces Quality of Service support. This is an optional extra that can be included as part of your organization’s endpoint subscriptions.
When enabled for an organization, you can set a DSCP value for that organization in the Portal. This will set the DSCP bits in the media packets from StarLeaf Cloud room systems, desktop systems and the Phone 2105. It will not affect traffic from Breeze or H.323 endpoints.
For organizations with Quality of Service enabled, find the setting on Edit organization > Advanced settings > DSCP value.
For more information, refer to Using QoS with the StarLeaf Cloud
Cloud 4.6 introduces conference branding for organizations with branding enabled.
Conference branding comprises:
For more information about branding, refer to Branding
The Cloud Endpoint Control API has the following additions:
For more information, refer to Cloud ECAPI: Actions
|Global dial-in telephone numbers||The dial-in telephone numbers for StarLeaf conferences that are displayed in conference invite emails and on a conference’s jump-off page will now default to those appropriate to the organization’s Country. For example, if an organization’s Country is ‘France’, the displayed dial-in number will be a telephone number in France. To see an organization’s Country setting go to Edit organization in the StarLeaf Portal|
Cloud 4.6 provides improved performance in low bandwidth conditions for Click-to-Call.
For more information about browser calling, refer to Click-to-Call and the StarLeaf Cloud
|Room systems||StarLeaf Cloud room systems now provide beta support for PC audio-in through the DVI-I connector on the rear of the codec. You need to contact StarLeaf Technical Support if you require this functionality|
Bug fixes effective in StarLeaf Cloud 4.6:
|Microsoft Skype for Business interoperability|
|In previous releases, when a Skype for Business client attempted to add video or content into a StarLeaf conference that had no other video participants, that could cause unexpected call failure. StarLeaf Cloud 4.6 fixes these issues|
|10840||In previous releases, screen sharing from a GT Mini 3330 to a Microsoft Surface Hub failed. StarLeaf Cloud 4.6 fixes this issue|
|11415||In previous releases, the video from a Microsoft Lync iPhone client failed in calls into the StarLeaf Cloud. StarLeaf Cloud 4.6 fixes this issue|
|11603||When using StarLeaf Medley (the Skype meetings connection service), video quality is improved where Microsoft clients request video streams at very low resolution|
|11249||StarLeaf Cloud 4.6 introduces full interoperability with Yealink T48G registered with Skype for Business|
|8795||In previous releases, a StarLeaf Cloud call between Polycom Real Presence Trio and Skype for Business could result in no video from the Polycom endpoint. StarLeaf Cloud 4.6 fixes this issue
|11246||In previous releases, under certain circumstances the transfer of audio SIP calls could fail. StarLeaf Cloud 4.6 fixes this issue|
|11470||StarLeaf Cloud 4.6 provides better interoperability for SIP calling between StarLeaf Cloud and Vidyo endpoints|
|11892||Video now behaves as expected for people using Lifesize Icons that have been escalated from a point-to-point call to an ad hoc StarLeaf conference|
|12008||Interoperability issues between Cisco Jabber and StarLeaf conferences are fixed in StarLeaf Cloud 4.6|
|12097||Content sharing from the Cisco SX10 now behaves as expected when calling through the StarLeaf Cloud|
|13351||In previous releases, StarLeaf endpoints did not receive video from the Sony PCS-G50. StarLeaf Cloud 4.6 fixes this issue|
|Click-to-Call (WebRTC) improvements|
|9922||Click-to-Call (browser-based calling) now allows voice-only calls in Internet Explorer and Safari (in addition to Firefox and Chrome)
Browsers running on iOS (iPhone and iPad) do not support any WebRTC calling. Therefore, you cannot use Click-to-Call on these devices. StarLeaf Cloud 4.6 provides improved feedback to users attempting to do so
|10342||Click-to-Call users calling a hunt group where nobody is available to answer will now see the unavailability message rather than an error|
|11390||Click-to-Call on Macs now correctly calculates the start time of a scheduled conference enabling everyone to join at the beginning of the conference|
|11402||In the previous release, content shared from Click-to-Call did not appear in the recording of that conference. StarLeaf Cloud 4.6 fixes this issue|
|11461||StarLeaf Cloud 4.6 improves device detection, selection and associated notification for Click-to-Call|
|13441||Czech language is now available in Click-to-Call|
|StarLeaf Cloud endpoints improvements|
|6553||In previous releases, a Dell monitor (U2410) repeatedly switched on and off when connected to a Group Telepresence 3330 (GT Mini). StarLeaf Cloud 4.6 fixes this issue|
|10205||In previous releases, the VHD-V61 camera could sometimes reset its position from a camera preset position with no user interaction. StarLeaf Cloud 4.6 fixes this issue|
|13029||Consumer Electronics Control (CEC) now behaves as expected on single-screen room systems|
|13292||Improvements to echo cancellation on Group Telepresence 3330 (GT Mini) and for the Conference Phone 2220|
|12707||StarLeaf Cloud 4.6 provides improved audio quality for Breeze on Windows|
|StarLeaf Cloud improvements|
|9024||For conference email invites, the subject line of the email is now the title of the conference. This is helpful for MS Exchange users because the subject of the email becomes the conference title in the calendar|
|10796||The StarLeaf Portal now allows more characters for the creation of the name of an organization’s domain|
|11332||In previous releases, under certain circumstances, StarLeaf users who had previously successfully shared content in a call could not do so when the call was subsequently escalated to an ad hoc conference. StarLeaf Cloud 4.6 fixes this issue|
|11842||For customers using branding: Logos and images now correctly display in the StarLeaf Portal when using Internet Explorer|
|12017||For German language users: StarLeaf Cloud 4.6 fixes a typo on the Click-to-Call landing page|
|12082||In previous releases, under certain circumstances, when a participant was joining the conference simultaneously with particular participants leaving the conference, the joining participant was not able to join. StarLeaf Cloud 4.6 fixes this issue|
|12184||The StarLeaf directory no longer includes entries for deleted or disabled users|
|12610||The StarLeaf Cloud now updates the IBM Notes 9 calendar after the details for a scheduled conference have changed and shows the meeting as ‘rescheduled’|
|12644||Calls through the StarLeaf Cloud into Webex CMR conferences now behave as expected|
|12651||From StarLeaf Cloud 4.6 and later, the StarLeaf directory no longer allows invalid addresses. For example, a video address for a user’s home/work/mobile contact number must be a valid address|
|12859||In previous releases, if the first participant put the conference on hold and then a voice-only participant dialed into the conference, that second participant’s call failed. StarLeaf Cloud 4.6 fixes this issue|
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|