[Index]

Model: relation/HcsDpManageCustomerREL

Customer HCS Dial Plan

Full HTML Help

PROVIDER ONLY

CISCO

Tip

Use the Action search to navigate Automate

Overview

For Cisco HCS dial plans, you must create a customer dial plan before you create the site dial plan.

Cisco HCS dial plan schemas are configured such that the customer-level dial plan elements are not pushed to UCM until the first site for the customer is deployed. Therefore, you won't see any dial plan elements provisioned on the UCM until at least one site is deployed for the customer.

Once you add a customer dial plan, the only change allowed is to enable CSS filtering.

Related topics

Add a Cisco HCS customer dial plan

This procedure adds a new Cisco HCS dial plan for a customer.

Note

  1. Log in to the Admin portal as Provider or Customer admin.

    Note

    For details around tasks that can be performed for each admin level, see Cisco Hosted Collaboration Solution Roles and Privileges.

  2. Go to Dialplan Tools > Customer HCS Dial Plan.

  3. Click the Plus icon (+) to add a new customer dial plan.

  4. Select the customer to open the Customer HCS Dial Plan > New Record page.

    Note

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

  5. Optionally, at Default External Breakout Number add a PSTN Access prefix, if required.

  6. Is a site-location (SLC) required?

  7. Define whether to Enable CSS filtering.

  8. Save the form to add the new customer dial plan.

    For add, update, or delete, you can view transaction progress and details in the Transaction Logs.

    Note

    When adding lines (DNs) at the site level, you must 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. For details around defining directory numbers, see Number Range Management.

Related topics

Transaction logging and audit in the Core Feature Guide

Model Details: relation/HcsDpManageCustomerREL

Title Description Details
Customer Name * The name of the customer. Default: {{ macro.HcsDpCustomerName }}
  • Field Name: custName
  • Type: String
  • Target: /api/data/BaseCustomerDAT/choices/?field=CustomerName&format=json&hierarchy=[hierarchy]&auth_token=%3D%3D%24cfdPxMp17Yc12wzZ%24TZaHN%2BXBrvEvKrlxmqDmuhIwtKqvaUTr3AU6OS2ENWGoL6MJxbyJir5zzGX8w1Kv8N/qsRBuKc9XCjTJKYOApBibQ25kwkOvobbQWlpw/Z1zfeUDJQHbqvOY9v39tbGNlPZHRKIiWBSCqdMyQ7FIwfvzE9s8EIYqggXSvkR7qBhI%2BSkyEU4V02/L1juGJXJ4w2AmsqrUjZ/h44LiB4yH5qAdGvBA93AkReM2QFmUazBL2hZdyhaIb4zIZrID3WGtICbgzaC7ouwzvgSRcSykEtSJ59v202fhIrx%2BxMcW27i6FMJ/kqijSAOfP4FtOB6/ZE2mZWaD6qzi%2BdfkSP0dOlGtLit%2BPZTCTP63G227aQ8BG5K%2BgalQVNqfgdlt6Z1TwLqXC4UkX0R5BOPOgtMaqzK%2Bt2QHEDMQvoAeccbk2wq46c/dyJYTpw91Jnnp2RqYooHJxIpdz%2BZufi78tVtUXYOVX2bOrQkIbh9gtfiqkIZGs7g1bo%2BCZ%2BZ33PLn1rNqesFThltk1Ogn1LfJNkawAQ%3D%3D%24%3D%3D
  • Target attr: CustomerName
  • Target Model Type: data/BaseCustomerDAT
  • Default: {{ macro.HcsDpCustomerName }}
  • MaxLength: 1024
  • Format: uri
  • Choices: []
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