Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents
Microsoft Teams Line URI

Line URI data collection - additional authorisation options

Enabling Line URI data collection will produce a daily document which contains all users and their associated information including Line URI details. The documents are produced daily at 01:20 UTC and will be available in Files and Folders in the Teams Cloud Service folder.


We've added the option to use either Application-based Authentication or Service Account to retrieve Line URI for a Microsoft Teams Cloud Service. Leaving account SKU Id blank will collect all data for all SKU. If you wish to limit data collection to users of a specific O365 AccountName and SkuPartNumber then this field will need to be populated. Information on how to configure can be found here...


To stop collecting Line URI data, then uncheck the tick box to disable Line URI collection.


Image Added

Alarm notification when credentials fail

We have also added an alarm notification if a Line URI Command fails - if incorrect credentials have been entered then the error message is Access Denied


Microsoft Teams Call Summary dashlet - include summary period in the heading

In the Microsoft Teams Call Summary dashlet settings you can select a time period of 1, 6,12 and 24 hours. We've now included the time period in the heading of the dashlet. This is the same format as other historical summary dashlets, like Voice Quality Management (VQM) Summary and Alarms Overview.

Bug Fixes

Editing the Genesys Cloud Service in VSM would sometimes result in the loading icon but the popup never populatingpopulated. This has now been fixed.

Updated We've updated the Feedback Ratings to use the manufacturer names. No Rating or Undefined is now Not Rated in line with the JSON document.

The User Feedback page was not loading due to receiving NULL values. This has now been fixed and correct feedback values are received. (Not Rated, Bad, Poor, Fair, Good, Excellent)

For new Change Calendar entries in some time zones there was an error when entering the start time (Event must be in the future). This has now been fixed.

VSM-E users with a new PC weren't showing drill down data in the Microsoft Teams Call records, for some customers. A recent change had been applied to only one region. This has now been applied to all regions. 

When editing the Microsoft Teams Cloud service the certificate authentication would be incorrectly revalidated by the back end even though the certificate has not changed. Now, if the certificate has not changed, we do not revalidate.