[Index]

Model: relation/HcsDpManageCustomerREL

Create a Customer Dial Plan

This procedure determines the type of Cisco HCS dial plan schema (Type 1 to 4) to be used, depending on how you fill in the form.

Note

You can have only one dial plan per customer. If you try to add a second dial plan, the dial plan will fail. Once you have created the customer dial plan, Enable CSS filtering is the only setting that you can modify.

Procedure

  1. Log in as provider or customer administrator. For a list of the roles and tasks that can be done at each level, see see Cisco Hosted Collaboration Solution Roles and Privileges.

  2. Choose Dial Plan Management > Customer > Dial Plan.

  3. Click Add to add a Customer Dial Plan.

  4. Perform one of the following:

  5. Perform one of the following:

  6. If the ISP should be included in the directory number, select the Is ISP included in directory number? check box. If not, go to Step 8.

  7. If the ISP should be included as part of the Voice Mail ID, select the Is ISP included in Voice Mail ID? check box. If not, go to the next step.

  8. Select the Enable CSS filtering check box to filter the calling search spaces available when configuring a Subscriber, Phone, or Line, to site level Class of Service calling search spaces. Filtering is disabled by default, which results in all available Cisco Unified Communications Manager calling search spaces being available when configuring a Subscriber, Phone, or Line.

  9. Click Save to add the Customer Dial Plan you defined.

    Note:

    The Customer ID is a unique, auto-generated, read-only number allocated to the customer. The Customer ID is particularly useful in shared deployments (where a cluster may be shared across multiple customers) to correlate specific elements to a customer. It appears in the Cisco Unified Communications Manager as an prefix to elements (for example Cu2Si7 identifies Customer 2, Site 7).

    Note:

    The Cisco HCS dial plan schemas are configured such that the customer-level dial plan elements are not pushed to the Cisco Unified Communications Manager until the first site for the customer is deployed. Therefore, you will not see any dial plan elements provisioned on the Cisco Unified Communications Manager until at least one site is deployed for the customer. See Create a Site Dial Plan.

    Note:

    When adding lines (DNs) at the site level, you must remember to define your DNs appropriately (that is, you are responsible for using ISP+SLC+EXT if you deploy a Type 2 dial plan). Otherwise your inter/intra site calls won't route. To define your directory numbers, refer to Add Directory Number Inventory.

Model Details

Title Description Details
Customer Name * The name of the customer. Default: {{ macro.HcsDpCustomerName }}
  • Field Name: custName
  • Type: String
  • Target: data/BaseCustomerDAT
  • Target attr: CustomerName
  • Default: {{ macro.HcsDpCustomerName }}
  • MaxLength: 1024
  • Format: uri
External breakout number * Default external breakout number for this customer. Default: 9
  • Field Name: ext
  • Type: String
  • Default: 9
  • MaxLength: 1
  • Pattern: ^[0-9]*$
Site-Location Code (SLC) Based Dial Plan * Indicates whether or not Site Location Code is required for this customer. Default: false
  • Field Name: slcBased
  • Type: Boolean
  • Default: false
Enable CSS filtering * Indicates enabling or disabling the CSS filtering in the Day 2 templates. Default: false
  • Field Name: isCSSEnable
  • Type: Boolean
  • Default: false
Inter-Site Prefix (ISP) Required Indicates whether or not ISP is required for inter-site dialing. Default: false
  • Field Name: ispReq
  • Type: Boolean
  • Default: false
Inter-Site Prefix Inter-site prefix if ISP required for inter-site dialing.
  • Field Name: isp
  • Type: String
  • MaxLength: 1
  • Pattern: ^$|^[0-9]+$
ISP included in SLC If ISP is required, indicates whether ISP is included in SLC. Default: false
  • Field Name: ispInSlc
  • Type: Boolean
  • Default: false
ISP included in Voice Mail ID If ISP is required, indicates whether ISP is included in the VMID. Default: false
  • Field Name: ispInVMID
  • Type: Boolean
  • Default: false
Use extension prefix? If selected, an extension prefix can be specified which can be used on sites for this customer. Default: false
  • Field Name: extPrefixInUse
  • Type: Boolean
  • Default: false
Extension prefix Specify an optional extension prefix for this customer. Each site can select whether this extension prefix will be required.
  • Field Name: extPrefix
  • Type: String
  • MaxLength: 1
  • Pattern: ^$|^[0-9#*]+$
Dial Plan Type * This is an internal field to store the DP type. Default: Unknown
  • Field Name: dpType
  • Type: String
  • Default: Unknown
  • MaxLength: 1024
Customer ID * Unique ID for this customer. Default: {{ macro.HcsDpCustomerId }}
  • Field Name: customerId
  • Type: String
  • Default: {{ macro.HcsDpCustomerId }}
  • MaxLength: 1024
Debug Info This is an internal field to store debug info. Default: ** Bogus DP customer **
  • Field Name: debug
  • Type: String
  • Default: ** Bogus DP customer **
  • MaxLength: 1024
Shadow
  • Field Name: shadow.[n]
  • Type: Array
  • Cardinality: [0..1]
Name *
  • Field Name: shadow.[n].name
  • Type: String
  • MaxLength: 1024
API reference for relation/HcsDpManageCustomerREL