Cloud 4.6

In Cloud 4.6, the Cloud API introduces:

• a new method of authentication for the clients you develop. This is the authentication header method and it allows a client to authenticate with the StarLeaf Cloud as an integration. The integration behaves like a ‘user’ and can have administrator access to an organization or not. If you develop a client for creating and managing conferences and that client uses this method of authentication, those conferences will be ‘owned’ by the integration rather than by a real user. The authentication header method of authentication is preferred where it is appropriate because it is easier to implement
• greater support for adding, editing, and removing users for both organization admins and resellers through the API
• the ability to choose to exclude permanent conferences from an organization’s directory
• the ability to set a locale for an organization, or a user
• the ability to add, edit and delete custom integrations for both organization admins and resellers through the API

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.

You create a new integration using the StarLeaf Portal:

If you want to have custom integrations enabled for your organization, contact StarLeaf Technical Support

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:

• From inside a Skype for Business meeting, you can add a StarLeaf Cloud registered endpoint to it. Use the Add participant control in the top right of the Skype for Business meeting:

  

  This scenario includes all StarLeaf and third-party endpoint that are registered to the StarLeaf Cloud and includes both on-premise Skype for Business and Office 365 deployments

• You can escalate a point-to-point Skype for Business call into an AVMCU meeting by ‘inviting’ a StarLeaf Cloud registered endpoint to that call. Use the Add participant control in the top right of the Skype-for Business call screen.

  This scenario includes all StarLeaf and third-party endpoint that are registered to the StarLeaf Cloud and includes both on-premise Skype for Business and Office 365 deployments

• You can cause the Join Now button on StarLeaf Cloud room systems to light for AVMCU-scheduled meetings. To do this, schedule a Skype for Business meeting and invite the StarLeaf Cloud room system to that meeting. This invite must be sent to the room’s subdomain.call.sl video address. This video address must be in the format <room_system_name>@<subdomain>.call.sl. In the example below, we invite london@example.call.sl:
  

  This scenario includes both on-premise Skype for Business and Office 365 deployments.

  Forwarding a Skype for Business meeting invite to a room system’s subdomain.call.sl video address also causes the green button to light for AVMCU-scheduled meetings.

• Registered endpoints, including H.323 endpoints can call into an on-premise Skype for Business hosted conferences by utilizing the Skype for Business audio IVR. For more details, contact StarLeaf Technical 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:

• background image for conferences
• waiting screen image for conferences
• lock screen image for conferences
• logo for conferences

For more information about branding, refer to Branding

The Cloud Endpoint Control API has the following additions:

• Action: stop_camera. Stops moving the camera
• Action and state: self_view. Allows you to set the display mode for self view and request the state of that mode

For more information, refer to Cloud ECAPI: Actions

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

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

• The camera on StarLeaf Cloud room systems will no longer be active during the sharing of local content
• USB cameras now go to sleep when not in use