| Table of Contents |
|---|
Additional 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.
Line URI data collection
Line URI - Minimum Viable Product has been released.
An additional tab called Line URI has been added to the Add Service tab modal for Microsoft Teams Cloud Service. This enables collection of the Line URI data. Customer must provide Account and Credential .details to configure. These daily documents are located within 'Files and Folders > Teams Cloud Service'.
Existing Microsoft Teams Cloud Services can be edited to enable Line URI data collection. Find more information on configuration here...
...
For those with "Auto-start dashboards" enabled, this will auto-launch in the new service.
Please move to using the new Dashboard service and let us know what you think.
Bug Fixes
Voice Quality Management (VQM) grid was not loading for large data sets. This has now been fixed. Note that this UI is intended for expressions that will return up to 1 million stream records only.
Avaya LSP and ESS alarms were being received but were not displaying in the Alarms report. These now display on the Alarms report under their parent Avaya Communication Manager (ACM).
Files and Folders was not displaying all received Back Up files in the UI. This has now been fixed.
...