[Index]

Model: relation/HcsCssREL

Calling Search Spaces

Full HTML Help

Overview

A calling search space (CSS) comprises an ordered list of route partitions that are typically assigned to devices. Calling search spaces determine the partitions that calling devices search when they are attempting to complete a call.

  1. Log in as the Provider, Reseller, or Customer Administrator.

  2. Choose an option:

  3. Choose the relevant hierarchy.

  4. Choose an option:

  5. In the popup, select from the pull-down the network device list (NDL) to which you are adding the calling search space, and click OK.

    Note

    The NDL popup will only appear when you are adding a new calling search space. If you are updating an existing calling search space, go to Step 6.

    If you are adding the calling search space to a Site hierarchy node, the NDL popup will not appear. You will go right to the Calling Search Spaces add page using the NDL associated to the site.

  6. From the Calling Search Spaces page, modify the following fields as required.

    Option Description
    Name (Mandatory)

    Enter a name in the field. The name can comprise up to 50 alphanumeric characters and can contain any combination of spaces, periods (.), hyphens (-), and underscore characters (_). Ensure each calling search space name is unique to the system.

    Note

    Use concise and descriptive names for your calling search spaces. The CompanynameLocationCalltype format usually provides a sufficient level of detail and is short enough to enable you to quickly and easily identify a calling search space. For example, CiscoDallasMetroCS identifies a calling search space for toll-free, inter-local access and transport area (LATA) calls from the Cisco office in Dallas.

    Default value: None

    Description

    Enter a description in the field. The description can include up to 50 characters in any language, but it cannot include double-quotes ("), percentage sign (%), ampersand (&), back-slash (), or angle brackets (<>).

    Default value: None

    Route Partitions Click the Add (+) button to add a partition to the calling search space. Repeat as necessary to add multiple partitions to the calling search space.
    Partition Name

    Click the drop-down list and select a partition to add to the calling search space.

    Click Add (+) to add another partition to the Route Partitions list. Repeat as necessary to add multiple partitions to the list.

    Click the Remove (-) button to remove a partition from the list.

    Click the up and down arrow buttons to change the order of a partition in the list.

    Partition Index Enter the priority number for this partition in the calling search space. The smaller the integer, the higher the priority.

    The following table provides examples of the maximum number of partitions that can be added to a calling search space if partition names are of fixed length.

    Partition Name Length Maximum Number of Partitions
    2 characters 170
    3 characters 128
    4 characters 102
    5 characters 86
    ... ...
    10 characters 46
    15 characters 32
  7. Click Save. The calling search space appears in the list.

Note

When selecting an existing CSS with a partition associated and cloning this instance for modification, the new CSS will by default show the partition populated with this associated partition.

To modify any of these properties, click the item in the list, make your changes, and click Save.

To delete a calling search space, check the box to the left of the Name column in the group list, and click Delete.

This relation wraps the default CUCM CSS element.

Model Details: relation/HcsCssREL

Title Description Details
Name *
  • Field Name: name
  • Type: String
  • Cardinality: [1..1]
  • MaxLength: 50
Description
  • Field Name: description
  • Type: ["String", "Null"]
  • Cardinality: [0..1]
  • MaxLength: 50
Members
  • Field Name: members
  • Type: ["Object", "Null"]
  • Cardinality: [0..1]
Member
  • Field Name: member.[n]
  • Type: Array
Index
  • Field Name: members.member.[n].index
  • Type: Integer
  • Cardinality: [1..1]
Route Partition Name *
  • Field Name: members.member.[n].routePartitionName
  • Type: String
  • Target: /api/device/cucm/RoutePartition/choices/?field=name&format=json&hierarchy=[hierarchy]&auth_token=%3D%3D%24ue7VqK252j5GfBVh%24jbkY8JlZ9SbZhwloWAQ32aAy2memk6/UvedjlNu/et6vUhQLwIn3irWOT7KHacVWy0F%2BlnaWUDdZkQ4pd%2BgFVUwQYxXjVhX0gid7oItTqGOvU1ZefpAbq3zz4EZWE8KrbnCmSGGnB8D%2BQFOh9j28doar64M8xBxLrs%2Bd5ZB160qC6c4QESllpoK1EYCmjd%2ByfgMV4U1Ey1JrBY8i29/zSVIjYQVD0%2Bj/czH8N30km9vrTm%2B0aB%2B3jwlnI9FdZ5sr5Fs9rGGIcrXyG1KF6tfwxyuVyhRxSkWD4PsIdsk1TMXTTzAOA5HSCRiTZFIsECKE08gd61yxi9SeUOq6awxQ3MmTMqzaA9qm04ghs3iMCvSR/gjQbPHKUiivFVQ1iVqNdZO0TOcprmFulTkfch%2BmbplLDaSNLHhH44Uc05nn7JApglJkr0mthKGoWnh9k/XCmzbWfyMK8%2B6JJf0DS04nxPodvvAv28ZcRxbWL9%2BHr8abgUCOJXfUMVmjyvd75YVz6g%3D%3D%24%3D%3D
  • Target attr: name
  • Target Model Type: device/cucm/RoutePartition
  • Cardinality: [1..1]
  • Format: uri
  • Choices: []
Partition Usage Default: General
  • Field Name: partitionUsage
  • Type: String
  • Cardinality: [0..1]
  • Default: General
  • Choices: ["Intercom", "Call Control Discovery Learned Pattern", "General", "Directory URI"]
Shadow
  • Field Name: shadow.[n]
  • Type: Array
  • Cardinality: [0..1]
Name *
  • Field Name: shadow.[n].name
  • Type: String
  • MaxLength: 1024