[Index]

Model: data/HcsNumberManagementLogDAT

Directory Number Inventory Audit Tool

When you run the Directory Number Inventory (DNI) Audit Tool, the tool checks and updates your directory number inventory since the last data sync. A sync of device/cucm/Line from the Unified CM will result in various line types being brought in - including lines assigned to devices, CTI devices, and so on - essentially anything that would be seen under Directory Numbers in Unified CM.

This will create a number inventory entry for all the device/cucm/Lines that are in the system and at the site level. Any lines not at the site level will not be processed in the audit tool.

Note

This can result in inventory entries being created for lines that are not just user device related, for example CTI ports, CTI route points, and so on. The Audit will not remove number inventory entries if a corresponding device/cucm/Line does not exist, for example if it is removed outside of VOSS-4-UC.

The Number Inventory audit then includes logic to then determine if a number is used or not and to set the number inventory value accordingly. That logic handles the following cases:

The tool is run from the Dial Plan Management > Number Management menu. When you run the tool, it creates new DNs for lines that don't have them.

You specify where you want the tool to run and create a new DN inventory:

For sites using Site Location Code-based dial plans, DN inventories can be created only at the Site hierarchy. The option to create DN inventories at the Customer hierarchy is unavailable in this case.

The DN Inventory Audit Tool will mark data/InternalNumberInventory instances as Shared across sites if a line is associated with multiple devices.

From Dial Plan Management > Number Management > Directory Number Inventory, you can see a list of DNs and move, delete, and export them as desired.

Dial Plan Management > Number Management > Log Messages provides information and warning messages generated by the Directory Number Inventory Audit Tool.

Note

You cannot run the Directory Number Inventory Audit Tool if number management has been disabled for the customer.

Common Errors and Caveats

Procedure

  1. Log in to VOSS-4-UC as provider or reseller administrator.

  2. Choose Dial Plan Management > Number Management > Directory Number Inventory Audit Tool.

  3. If prompted, choose the correct hierarchy and click OK.

    Note

    The tool can only be run from Customer hierarchies. If you run the tool from a hierarchy that is not of type Customer, the tool will automatically provide you with a valid Customer hierarchy choice.

  4. From the Directory Number Inventory Creation Policy drop-down, choose an option.

    Note

    Customers with Site Location Code-based dial plans will not see the Customer Create option.

  5. Click Save.

The DN inventory is updated at the hierarchy you specified and below.

Audit Number Inventory

Audit Number Inventory

Overview

Automate allows you to perform an audit of the number inventory to ensure that the status and usage values of each number aligns to the devices or services configured with these matching numbers.

Note

For Microsoft environments, available numbers are added (else updated if present) to the inventory, with:

Note

For details, see: Audit Process in Microsoft Environments

The audit creates new numbers for devices or services that don't already exist, and updates existing number entries so that the Status and Usage fields display accurate information at the time the audit is run. Importantly, number entries are not deleted.

To access the flowcharts, view the topic via the release documentation at: https://documentation.voss-solutions.com/automate.html

Number Inventory Audit and Hierarchies

The table describes the difference between running a number audit inventory at the customer level compared to the site level:

Customer
  • Running the number inventory audit at customer level adds directory numbers at the customer level for services that exist at site or customer level, provided that there is not already a directory number for that service at site level.

    If there are already directory numbers at the site level, then those numbers are also updated.

    This is a mixed mode of audit, which audits directory numbers at both customer and site level. For example, if directory numbers only exist at customer level, then the audit only adds and updates directory numbers that exist at the customer.

    If there are directory numbers at site level, the audit will still add new directory numbers at the customer level, but will also update the existing directory numbers at site level.

Site
  • Running the number inventory audit at site level adds directory numbers at site level, and updates any existing directory numbers at site level only. No customer level directory numbers will be audited and no directory numbers will be added to customer level for customer level services.
  • You can choose to audit either all the sites for the customer, or selected sites

Note

For sites using Site Location Code-based dial plans, number inventories can be created only at the site hierarchy. The customer hierarchy won't be available.

Audit Number Inventory Common Errors

The table describes common errors and steps to resolve, when running audit number inventory:

Error Resolution
Duplicate device profiles (same profile name) in different clusters Ensure that device profiles are not duplicated across the sites.
Duplicate phones (same MAC) in different clusters Ensure that phones are not duplicated across the clusters.
Same internal number in one or more clusters Ensure that internal numbers (even in different partitions) are not duplicated across clusters.

Run a Number Inventory Audit

Note

You can only run Audit Number Inventory from a customer hierarchy. If you try to run it from a hierarchy that is not of type Customer, you will be prompted to choose a valid customer hierarchy.

  1. Log in to VOSS Automate as provider or reseller administrator.

  2. Select the relevant Customer hierarchy level.

  3. Go to Audit Number Inventory (via, default menu Number Management > Audit Number Inventory).

  4. From the Is Number Inventory deployed at Customer or Site Level drop-down, select an option, either of the following:

  5. View transaction progress. The number inventory is updated at the hierarchy you specified, and below.

HcsNumberManagementLogDAT

Model Details: data/HcsNumberManagementLogDAT

Title Description Details
Timestamp * When the event occurred.
  • Field Name: timestamp
  • Type: String
  • MaxLength: 1024
Level * Log level.
  • Field Name: level
  • Type: String
  • MaxLength: 1024
  • Choices: ["ERROR", "WARNING", "INFO"]
Component * The name of the component.
  • Field Name: component
  • Type: String
  • MaxLength: 1024
Identifier * An identifier that can be used to link this log with other entities in the system.
  • Field Name: identifier
  • Type: String
  • MaxLength: 1024
Message * Message indicating why the log was generated.
  • Field Name: message
  • Type: String
  • MaxLength: 1024
Recommended Action(s)
  • Field Name: actions.[n]
  • Type: Array
Details
  • Field Name: details.[n]
  • Type: Array