Direct Routing Phone Number Ranges
Rule description
This report queries a telephone number range definition file, finds the assigned numbers in each range and returns the aggregate information on number usage for each range.
When to use this rule
NOTE: Before using this rule, navigate to Configuration > Connected Systems Extensions > Microsoft 365 and set Connect to Microsoft Teams to Yes.
Use this rule when you need to get the usage information for each defined number range. Also use this rule if you need to get a notification report when the percentage of free numbers in a range fall below a configurable threshold.
This rule requires the configuration of two CSV files:
Phone ranges - specifies phone number ranges, possible extensions, and corresponding locations;
Reserved numbers - specifies phone numbers that are reserved and can not be assigned to users;
You can use the template CSV file provided with the rule, or create a file in Microsoft Excel and export as CSV.
TIP: You should normally use the same CSV files that are configured for the related AD Users | Direct Routing Assignmentrule.
Rule settings
Query section
| Setting name | Description |
|---|---|
Phone Number Ranges | |
Phone ranges data source |
Specifies the CSV file where ranges data are defined. The […] button allows to browse for the file and the Create/Edit button allows the creation or editing of the existing file in the built-in Data Source editor. |
Separator used in file |
Specify the separator used in the source CSV file. |
|
Range Start Range End |
You should specify the number format in range start and range end columns and select these columns here. The number should be in standard E.164 format like +123456789 NOTE: To query ranges built on extensions of the same number, use the following format: |
Ignore assigned extension |
When set to Yes, the currently assigned extension will be ignored for matching the assigned number with the range. |
| Warning threshold % | Specify the warning threshold in %. When the free numbers in a given range fall below this value, the range is considered as having a warning status |
| Group by | Select a column to group ranges for threshold calculation by this attribute. |
| Show ranges |
Select which ranges should be displayed in the report:
NOTE: Set your warning threshold and this setting to Warnings only to get a report that contains only warning ranges. You can receive this report on schedule into your inbox by configuring the output section |
| Filter CSV data | The filter can be used to filter by the values in the CSV file columns like {$_.ColumnName -eq 'value'}
|
Reserved Numbers | |
Reserved numbers data source |
Specifies the CSV file to be used with the list of reserved numbers. Reserved numbers that fall into one of the ranges defined in the Phone Number Ranges file above will be counted as used and will go towards calculating the warning threshold. |
Reserved number |
Select the column in the data source that contains reserved telephone numbers. |
More Options | |
Returned Properties |
To display additional properties for each object found by the query, add those properties to the list. |
Sort by |
Sort result object list. |
Exclude disabled AD users |
Specify if disabled AD user accounts should be excluded. |
Maximum number of users |
By default, all objects that you have provisioned in Microsoft Office 365 are returned. TIP: It is possible to change the default value in the extension settings. |
Post filter |
To hide unwanted data based on criteria, not supported by the Microsoft 365 query criteria above, set the filtering conditions here. TIP: For optimal performance, use the Query criteria above to filter objects whenever possible. |
Initialization Script | |
Script |
Usually, rules use query criteria to limit the query search scope. It improves the performance of the executed rule. Due to the PowerShell limitations, it is not possible to use calculated expressions in query criteria. That is the point where the initialization script can help. You can initialize a global variable in this setting and then use it in query criteria. IMPORTANT: To use a variable, declared in the initialization script, in the query scope, it must be global: Example: Update AD users, created in the last ten days.
|
Output section
This section defines the output format of this rule.
To get more information about this section, please see the Rule Output section article.
Enforce/Schedule section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Rule Enforce/Schedule section article.
Comments
0 comments
Please sign in to leave a comment.