1. Home
  2. DN & DID Management
  3. Configuring DID Block Number Mapping Exception for CUCM Hunt Pilot/Group Number

Configuring DID Block Number Mapping Exception for CUCM Hunt Pilot/Group Number

Variphy’s DID Management can quickly identify DID number status and availability based upon directory and other numbers in 1 or multiple CUCM Clusters.

How each number in a DID Block is “mapped” to a directory or hunt pilot number in CUCM is one of the most important aspects of how each DID Block is configured in Variphy’s DID Management.

“Normal” Mapping

Each DID Block in Variphy can be configured to map to 1 or multiple CUCM clusters to support various different configurations, based upon matching digits from the DID number to numbers in CUCM Clusters, with optional prefixes and partitions.

For more information on configuring DID Blocks and CUCM Cluster association read the full guide for Configuring DID Blocks in Variphy.

Mapping Exceptions

As is often the case, sometimes a DID number is actually routing calls to a specific unrelated number, such as for a CUCM Pilot, that doesn’t quite fit in with the “normal” mapping rules as described above.

Configuring mapping exceptions for a DID Block is designed to handle this specific use case. Mapping exceptions take precedence over normal CUCM Cluster association settings when mapping DID numbers to numbers in CUCM.

The following example shows a mapping exception for a DID Block which identifies that DID Number (702) - 341 - 3097 maps to CUCM Number 9700 with route partition PT-Directory-Numbers 

Continuing this example, in CUCM, 9700 is configured as a Hunt Pilot as follows:

In Variphy’s DID Management, searching for this DID Number would reveal that it is “Active” since it maps (via a mapping Exception) to an existing number assigned to the CUCM Hunt Pilot above.

Updated on November 22, 2019

Related Articles