Fixed issues
Fixed in VQ Conference Manager 3.12.1
| Task Name |
|
DMA - Address Books contact page returning incorrect data |
|
DMA - Temperature state set to unknown when device state is unknown |
| DMA - Device state graph counting devices from the past skewing data |
| DMA - Devices that have never been in-call/online metrics don't react to filters |
|
DMA - Add IP validation to DMA activity API |
| DMA - Enabled Template Modules showing as disabled in the Device Template |
| DMA - Settings cannot be fetched for newer room OS versions |
| DMA API - Device Name change not reflected in other endpoints |
| Meeting Services - Core services writing to Vault on save for all endpoints placing high load on the system |
| Meeting Services - Role detection on multi-Role Spaces didn’t function correctly on outgoing calls |
| Meeting Services - Scheduling a weekly Recurring Meeting over 3 weeks only yields two meetings listed in the Recurring Meeting booked email |
| Meeting Services - Recurring Meetings sometimes fail to unlock call on Temporary Space |
Fixed in VQ Conference Manager 3.12.0
| Task Name |
|
Temporary Spaces not being deleted |
|
All users required to have a Tenant; impacted Local Users |
| Left menu doesn’t help users visually see which page they are on |
| Add Missing “Chat Allowed” property to Call Profile |
|
Add Email to filter parameter on User List API |
| In certain circumstances, Activity API returned duplicated Spaces data |
| URI Generator ignored on Recurring Meetings |
| Deleting a VQ Space directly from CMS (Web UI or API) can cause VQ’s state for the Space to get stuck in “Updating” |
| Change Exchange Mailbox comparisons to become case-insensitive |
| API address comparison when creating temporary devices is case sensitive |
| Incorrect “details” information being returned from MeetingTemplate Delete API |
| Unable to schedule a Recurring Call on a temporary Space when the Space Template has a max pin length < 6 |