You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Microsoft Teams Cloud Service - authentication methods

Microsoft Teams Cloud Service can now use a shared secret or a certificate as the authentication method.

We've added the ability to upload a certificate to be used as the authentication method. The uploaded certificate must be associated with the customer's Application Id and the Tenant Id configured for the service. Valid file types for certificates are PFX and PEM only.

Avaya SBC Access concentrator update

We've made access to Avaya Session Border Controller (SBC) via Access Concentrator easier for our partners with two SSH options. You'll now find the Secure Shell protocol SSH 222 Connect available to choose.  Both the SSH Connect and SSH 222 Connect options use the same launch script and options already administered for SSH.

  • SSH uses port 22
  • SSH 222 uses port 222

New Dashboard Service Promoted from preview

You can access the new dashboard service by simply right-clicking on one of your dashboard names and select Open Dashboard from the menu select. To view in the old dashboard service, simply right-click on your dashboard name and select Open Dashboard Classic.

For those with "Auto-start dashboards" enabled, this will auto-launch in the new service.


Bug Fixes

Avaya LSP and ESS alarms were being received but were not displaying in the Alarms report. These now display on the Alarms report.

Files and Folders was not displaying all Back Ups files in the UI. This has now been fixed.

On the Microsoft Teams Call Records grid, calls with feedback of notRated will now show as" Has Feedback = No". The User Feedback page will still show users that have not rated their call when the Teams feedback form was presented.




  • No labels