[Index]

Model: relation/NumberInventoryREL

Number Inventory

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

Overview

Number inventory allows you to view and manage the number inventory at the specified hierarchy level. It allows you to track numbers and to see how they are used in the system. This is done through a number of workflows to ensure the selection of numbers is limited to those available, and includes the ability to:

• Add, modify, and delete numbers
• View the status of numbers (Used, Used-Utility, Available, Reserved, Cooling).
• Store additional business data about the numbers.

See Also:

• Number Status and Usage

Hierarchy

The number inventory can exist at a different hierarchy level to the lines for the users, services, and devices that consume them, which are typically at site level.

The inventory can also exist at customer level. This makes it easier if the allocation and availability of numbers is not site-specific. This saves moving numbers around sites to increase availability, and keeps a more central inventory of available numbers. It is also important if numbers are shared across sites. If you are a customer with multiple sites, ensure that the internal numbers you specify are unique across sites.

If the number allocation is site-specific, the numbers can be added or assigned to site level.

Number inventory can only exist at provider, customer, or site hierarchy. It is not applicable to the intermediate hierarchy.

Partition and Cluster

Number inventory is not partition or cluster aware. If the same numbers are used multiple times but in different partitions, then these all map to the same number. This should be taken into account when thinking about the hierarchy level at which the number inventory exists.

Also, not being cluster aware, if the same number exists on different clusters, this again will map back to the same inventory value unless numbers are assigned to the site level.

Reservation

Numbers can be reserved for future use. For example, for users who will soon be joining the company. When a number is reserved, it is unavailable and cannot be allocated to a subscriber, phone, device, etc. See also: Number Reservation.

Number Cooling

Numbers can be placed into a cooling period, either manually or automatically. When automated number cooling is enabled, numbers are placed into cooling for a predefined period when the subscriber or phone associated with the number is deleted.

While the number is in its cooling period, it is unavailable and cannot be allocated, for example, to a subscriber, phone, or device.

A number is released from cooling and is available for use when:

• The cooling period reaches its end date
• It is manually released from the cooling period

See also:

• Number Cooling

Number Inventory entries - End-user Provisioning Tasks

For more information on provisioning each of these tasks, refer to the relevant topics in the VOSS Automate Core Feature Guide.

Number Inventory List View

The Number Inventory list view (default menu Number Management > Number Inventory) displays the range of numbers that have been defined for the selected hierarchy.

Here you can view the list of numbers, delete a number, or select a number and edit the free text fields. Filter the numbers (by column) as needed.

The following columns are available:

• Status = Available and Usage is empty when a number is first added to the number inventory. Refer to Number Status and Usage for more information.
• Release Date (if cooling is enabled) indicates the date on which a number currently in status Cooling, becomes Available again. See: Number Cooling.
• Tag is a free text field, which is populated when adding a new number or range of numbers. It is used to identify or comment on a number or number range.
• Reservation notes is a free text field, typically used to provide more details about a status Reserved number. See: Number Reservation.
• Vendor field is an optional field typically used to designate vendor specific information for a device in a multi vendor setup.
• Internal Number Type: If Vendor = "Microsoft", then for connectivity options with MS Teams and Phone System, any of: "Direct Routing", "Calling Plan", "Operator Connect". The value can be managed and is used to determine user configuration when the number is assigned. If Vendor = "Cisco", then blank.
• Description as well as Extra1 to Extra9 fields are free text fields that are available to provide additional information for a given number or range of numbers.

You can manage a specific number by clicking on the number in the list view. See: Number Range Management.

Number Status and Usage

Administrators can now view more accurate data as to how numbers are used at a specific hierarchy level.

The Status and Usage columns on the enhanced Number Inventory form (default menu Number Management > Number Inventory) are described below:

Footnotes

Cisco-Microsoft Hybrid Number Inventory

A Cisco-Microsoft hybrid setup is an integration of Cisco and Microsoft capability where we route Microsoft calls via Cisco Unified CM.

In a hybrid setup, the Internal Number Inventory (INI) can be set up in 2 ways:

• E164 number based, for example:

  • an INI entry 3334567 is mapped to an external number of +15553334567.
  • The number 3334567 is set up in Cisco (along with routing for the mapped external number).
  • The number +15553334567 is set up in Microsoft as the line.
  • The numbers 3334567 and +15553334567 should be seen as the same number from an INI tracking perspective.

• Internal number based (site code+extension or just extension)

  • an E164 number is generated by adding a prefix (+88800) to the internal number for setup in Microsoft.

    Note

    The named macro called MultiVendorLine-InternalExt-E164Prefix is used to store the prefix - currently set to +88800.

  • For example, 3334567 is set up as an internal number for the user and no external number is mapped. The line is selected in the Hybrid setup. Then the prefix is added, so the number +1888003334567 is the number in MS Teams for that user.

  Important

  The numbers 3334567 and +888003334567 should be seen as the same number from an INI tracking perspective. The mapping is also reflected in the Run the Directory Number Inventory Audit Tool. In this case, an update of the inventory takes place so that these are not counted as two separate numbers.

The table below sums up the Number Inventory data for these cases.

Note that Extra2 and Extra4 hold the service type and E164 number (includes generated) respectively.

For details on the service type scenarios, see Multi Vendor Service Definitions in the Core Feature Guide.

Footnote

Details and Usage

Selecting a specific number from the Number Inventory list view, opens the details view for that number.

The Number Details tab shows read only details for the number, for example Internal Number, Status, Usage, as well as editable fields such as Tag, Description, Reservation Notes, etc. In the case of Cisco-Microsoft hybrid entries, the vendor added would be "Cisco, Microsoft".

The Usage tab provides links to all instances where the number is used. In the case of Cisco-Microsoft hybrid usage, the last vendor added would be appended, as seen above in the "Device, User" instances.

Wrapper relation for InternalNumberInventory. Summary attributes is defined in data-model (and in future core-versions, the FDP will define the summary-attrs)

Model Details: relation/NumberInventoryREL