[Index]

Model: relation/HcsDpDnRangeREL

Directory Number Routing

Full HTML Help

Overview

Directory number routing is a translation pattern that is put into the PreISR and ISR partitions to route intrasite and intersite calls to extensions (directory numbers). This is similar to the way site location codes (SLCs) are used as short codes for Type 1, 2, and 3 customer dial plans.

Typically, directory number routing is used for Type 4 (flat dial plans) so that from a customer and site perspective, you can see which patterns are directory numbers because there are no SLCs available.

Add a Directory Number Routing

This procedure adds a directory number routing.

  1. Log in as provider, reseller, customer, or site administrator.

    Warning:

    When adding directory number routing, you must select a valid site under your customer in the hierarchy node breadcrumb at the top of the view. Adding a directory number routing at any other node in the hierarchy triggers a system error indicating that you must be at a site.

  2. Go to (default menu) Cisco Dial Plan Management > Site > Directory Number Routing, then click Add.

  3. In the Directory Number Routing Prefix, enter a prefix, using up to 30 characters (for example, 234)

  4. In the Directory Number Mask Length field, enter a DN mask length. For example, if you enter 4, the Directory Number Routing would be 234XXXX, where XXXX is the mask.

  5. Click Save. The Directory Number Routing is added.

    The new Directory Number Routing appears in the table and it can be edited or deleted as required.

Model Details: relation/HcsDpDnRangeREL

Title Description Details
Customer Name *
  • Field Name: custName
  • Type: String
  • Target: /api/data/BaseCustomerDAT/choices/?field=CustomerName&format=json&hierarchy=[hierarchy]&auth_token=%3D%3D%24pVLnDzyc0supgCCF%24%2BF%2BPFKgnd1kqRpYK5EPEdQHXa5ZHAZe0FAfEscvddDftXQnU07mHC3jcLrXwYopVXIbif%2BhGQalm%2BtBemdFIeAyX06Ev2g0P/FjxWtesfSVZFPxP6ExrANkb2jCJHwviLrKLe1yJ6sgArbMsBKr8AQ2cHN0hlsFg0aF%2Bm0vweMPSe0pC5%2B%2BVA2VEyS8Ns1LgVrUT77VgFM5WLFUU9IRJRSYV465heURH%2BSZ9hOZMyZ8foJXqBcnIgs5jI94NzElGMelTi2h9IO3quVATDmtMm9rbPIUxJnvkpywEI3Cxmc5M1nmC9jXajrKGFlhr25cH/qHLr9MqJIHcI302u/QLFOt7AVUQZpeYkEh9kYEBnzMs21kB0zox8FiKHydEqwboLYVo7LPT1sToa8ItkctbNk88vjw0Sa2ASgkCK0fWt1wZLWlVpL9YsHeEtxuAyRCYdwFUeK%2B6%2BMnZTh769RZEtrgDoCuAQEBxmcF7NyxUHMyD8a7WXCp8UuUhvU4ZpUPE/NhF9t2rDcfJ%24%3D%3D
  • Target attr: CustomerName
  • Target Model Type: data/BaseCustomerDAT
  • MaxLength: 1024
  • Format: uri
  • Choices: []
Directory Number Range * DN Range. String composed of one of more digits in the range 0 to 9 and must be unique within the customer network. The string can also begin with \+ which represents the international escape character + or *. Used to group a set of directory numbers, to a site that has similar characteristics. The length may be determined on a site-by-site bases. The DN Range should not 1) have a first portion that matches an existing, shorter DN Range or site location code or 2) match the first portion of an existing, longer DN Range or site location code.
  • Field Name: dnRange
  • Type: String
  • MaxLength: 30
Directory Number Range Mask * Directory Number Range mask. Number of wildcard 'X' characters to append to the specified directory number range. For example, 2 would indicate XX. A range of 0 indicates that no mask will be used and the Directory Number Range will be an explicit directory number that should be internally routable.
  • Field Name: dnRangeMask
  • Type: String
  • MaxLength: 2
  • Pattern: ^([0-9]|[1][01])$
Shadow
  • Field Name: shadow.[n]
  • Type: Array
  • Cardinality: [0..1]
Name *
  • Field Name: shadow.[n].name
  • Type: String
  • MaxLength: 1024