ZPM 9.6 Release Notes
Validation of Usage Location
Usage Location with Operator Connect and Calling Plans
Before assigning a user an Operator Connect or Microsoft Calling Plan number, verifying that the user’s usage location matches the unassigned number’s usage location is crucial. This is because users can only be assigned an Operator Connect or Microsoft Calling Plan number if the usage location of the unassigned number matches the user’s.
Usage Location for Direct Routing
Unlike with Operator Connect or Microsoft Calling Plan numbers, Teams does not enforce rules regarding usage location when assigning Direct Routing numbers, which can lead to users having numbers with incompatible usage locations.
When this happens, it causes outgoing calls to fail because their dialled strings can be normalized or prefixed with the incorrect country/region code (e.g. “+1” for North America) by Teams based on their configured usage location. (ref. What are dial plans? - Microsoft Teams | Microsoft Learn)
This situation commonly occurs with tenants who set up group-based license assignments because the user is licensed with the tenant’s default usage location, which is sometimes forgotten to be changed.
Validation of the Usage Location when Assigning a Number
ZPM now provides this important feedback before assigning the number, blocking the user from making a mistake.
The ZIRO Platform automatically determines the required usage location for Operator Connect and Microsoft Calling Plan numbers.
For Direct Routing, Administrators need to configure the usage location to enforce for numbers from the dial plan management page.
Unassigned Numbers (Single Number Rules) are automatically blocked
Routing rules for unassigned numbers are usually set up using regular expressions to capture all unassigned dialled numbers. These rules are often configured to route to a receptionist or auto attendant or play an announcement until the number is assigned to an employee.
In other cases, rules are sometimes established for specific numbers (for example, a secondary number for a user or call queue) where the number should never be assigned to anyone else. These are known as Single Number Rules.
Given Single Number Rules are more specific and permanent in nature, they are now automatically marked as unavailable in the number selector. A tooltip containing the rule name is shown, and users are not allowed to assign them until the rule is removed via the Teams Admin Center.
Other Enhancements
- Condensed Port-in Order details to see more information on the page with less scrolling
- Removed Certificate Expiry+Low VM HD Space Warnings from ZPM since it can only be actioned by ZIRO Support
- Enhanced the message on SSO login failures to include the value sent to ZPM by the IDP to help with troubleshooting SSO configuration issues
- Changed Teams user search results from 15 to 250
- Moved the ZIRO Support Admin menu item to the top of the left sidebar
Fixed Bugs
- First few requests to ZPM are slow due to client tokens being out of date
- Fixed duplicate Usage Location options mapping to the same name
- Bulk Provisioning page errors outs when CSV contains invalid rows
- Powershell errors are not returned and logged properly in audits
- Tenant not shown as string in our swagger documentation
- Fixed inaccessible pages being clickable and erroring out by disabling the links and displaying tooltip
- Fixed display issue in custom select component related to the Default Value
- Fixed the issue with requiring a Calling Plan license for resource accounts to be assigned a Calling Plan number.
- Fixed Microsoft 360 view not showing disabled device tiles as disabled
- Improved efficiency of the Dial Plan Inventory View call for Calling Plans and Operator Connect dial plan groups
- Fixed Microsoft Dial Plan Field Config lookup inefficiency due to unnecessary RBAC lookup
- Fixed “Write Down to On-Premise AD” fields missing required star
- Fixed Bandwidth DLR Misconfigurations Report not returning correct geolocation in certain situations
- Updates to AD via ZPM proxy are not being logged to ldap.log
- Adjusted Language on ZPM Number Selector Grid to say number instead of extension
- Port In Status does not check against main numbers of extension based dial plan groups
- Incorrect Page Title in browser for ZPM Homepage
- Dubber field-config incorrectly enforcing case-sensitivity of the UPN
- “Numbers in Teams missing Bandwidth DLR” Gauge Drops in Prometheus
- Inability to save Group Membership Settings due to invalid 422 error related to licensing role
- Fixed Audit View where the “Peformed By” column overlaps with other columns
- 422 error/toast on group management page causes save button to spin indefinitely
- SSO fails when using an alternate name (alias)
- Microsoft 360 view fails when user is licensed for audio conferencing but does not yet have the correct feature type
- Emergency Location Places not displayed correctly
- Fetching Status of SBC Misconfig Report That Failed Causes Oops