[Index]

Model: relation/HcsCUCxnScheduleREL

CUC

Full HTML Help

Overview

Cisco Unity Connection (CUC) devices provide voicemail services for HCS deployments, and can be dedicated to a customer or shared across multiple customers.

To dedicate a CUC to a single customer Configure the CUC at the customer hierarchy node.
To share a CUC across multiple customers Configure the CUC at a hierarchy node above the customer (reseller, provider, or intermediate node). The CUC device must be included in one or more Network Device Lists (NDLs), and the NDL must be assigned to one or more sites.

Scheduled Data Syncs

Configuring a CUC device on VOSS Automate creates a scheduled data sync to import model data from the device into VOSS Automate.

The scheduled data sync ensures that the VOSS Automate cache maintains the most current view of the configured device.

Note

If Holiday Schedules were added to CUC directly, update the default scheduled data sync instance to include the Model Type List called CUCXN Schedules in order to ensure that these holiday schedules are synced into VOSS Automate.

Any changes to the configuration occurring on the device, including additions, deletions, or modifications, reflect in VOSS Automate after the next data sync.

Note

The recurring sync (disabled by default) is scheduled to occur every 14 days. You can enable the sync and modify the schedule (via Apps Management > CUC > Schedules).

When determining the appropriate schedule setting, the frequency of the sync must be weighed against the additional processing and network activity associated with the data sync. You can manually run the data sync at any time, via Apps Management > Advanced > Perform Publisher Actions, or from Administration Tools > Data Sync.

Important

Allow the initial data sync to complete before doing more configuration on VOSS Automate that requires information from CUC.

The performance of a data sync can be improved by controlling the types of data that are synced. See Controlling a Data Sync with a Model Type List for more information.

Note

References to HCM-F and Shared Data Repository (SDR) are only relevant if installed.

Add a CUC Server

To add a CUC server:

  1. Log in as the appropriate hierarchy administrator.

  2. Choose the relevant hierarchy.

  3. Go to (default menus) Apps Management > CUC > Servers.

  4. Click Add.

  5. Enter a Cisco Unity Connection server name in the CUC Server Name field.

    Note

    A CUC server that has been configured in HCM-F and synced into VOSS Automate may exist at the sys.hcs hierarchy.

    If the server name you enter matches this server, the Migrate from HCM-F to VOSS Automate check box is displayed.

    Click Save to migrate this server to the current hierarchy level. The fields are populated with the values that were configured in HCM-F. If you do not want to migrate the server, enter a different server name.

  6. Select the Publisher check box if you are configuring a publisher node.

    Note

    The Publisher tab is populated only when the Publisher check box is selected.

    Provide details for the Publisher tab:

    Field Description
    Prime Collab

    Select the Prime Collaboration management application monitoring this cluster.

    To unassociate Prime Collaboration for this cluster, select None.
    Call Processing ID The Call Processing ID of this cluster
    Cluster ID The Cluster ID of this cluster.
    Multi-Tenant If creating at Provider level, this field is read-only and set to Shared. If creating at Customer level, you can choose between Dedicated and Partitioned.
    Version Select the version of Cisco Unity Connection Servers in this cluster. The available versions depend on the version of HCM-F that has been configured.
    Port The port on the Cisco Unity Connection server to connect to. Default is 8443.
    Monitoring

    For new servers and if arbitrator servers are available, monitoring can be enabled for this Unity Connection server on VOSS Insights.

    The arbitrator server check boxes can be selected to add the server as an asset. The arbitrator server will be updated.

    Existing servers can be managed from the Onboard Assets and Offboard Assets menus under VOSS Insights. The arbitrator checkboxes will then reflect the asset status.

    Note

    For details on monitoring and VOSS Insights, see VOSS Assurance Monitoring Overview.

  7. Fill in the Cluster Name field with the name you want for this cluster. A new cluster is created with this name. This field is mandatory.

    Note

    If the Publisher check box is not selected, the Cluster Name field appears as a drop-down list, from which you choose an existing cluster.

  8. Expand Network Addresses.

    1. Choose the SERVICE_PROVIDER_SPACE address space.

    2. The Hostname field is automatically populated with the Cisco Unity Connection Server Name. Edit it if necessary.

    3. Enter the IP address of the Cisco Unity Connection Server in the IPV4 Address field.

      Note

      Either the hostname or the IP address is required. Ensure that the hostname or IP address does not contain a trailing blank space. VOSS Automate cannot validate an entry that contains a blank space at the end of the hostname or IP address.

    4. Fill in the domain of the Cisco Unity Connection application.

    5. Provide an optional description for the network address.

      If NAT is used, also configure an APPLICATION_SPACE network address.

  9. Expand Credentials.

    1. Add credentials for PLATFORM, ADMIN, HTTP, and SNMP_Vx credential types. Click + to add more credentials.
    2. Fill in the user ID and password that you configured when you installed the Cisco Unity Connection.
    3. Choose RO (Read-only) or RW (Read or Write) for the Access Type. The default is RO.
    4. Provide an optional description for the credential.
      • ADMIN credentials are used by VOSS Automate to access the Cisco Unity Connection REST API interface for provisioning synchronization.
      • PLATFORM credentials are used by HCM-F (HLM service) to set the deployment mode and restart the publisher.
      • ADMIN, HTTP, and SNMP are required for PCA to manage Cisco Unity Connection. These credentials must be manually configured in Cisco Unity Connection, then configured in VOSS Automate's Device Management > CUC > Servers > Credentials section.
      • PLATFORM and ADMIN are required for Service Inventory to generate reports for UC applications.

  10. Click Save.

Delete a CUC Server

Deleting a Cisco Unity Connection (CUC) Server in VOSS Automate also deletes local data that has been synced to it from the Cisco Unity Connection Server, including:

Model Details: relation/HcsCUCxnScheduleREL

Title Description Details
Name * The name of the schedule.
  • Field Name: name
  • Type: String
  • Target: /api/data/Schedule/choices/?field=name&format=json&hierarchy=[hierarchy]&auth_token=%3D%3D%24sTrKOEdBxJ5pVj6s%24Piok78azJmWF0O5jDrlPyOcgPAyZyPT58aJL%2BtL5Odgon9Erv5MVaAEVINnUG5XS4lBQliFSS7V7vZhbYxyRT7m6er1r%2Be5gs18uFV9C3SEY3umx4HM9eP8/6p5ZdiTpdpMjZukOQFvoeFV6qBRbpac7vQrSiwJUqRp8t4Ks8qBQBCiIOhQhyakK4u98hWL/JbNpCjbrUUnOnlrJuwK7dG9w3BeBeczg1Re0ieXSA9OsnfED0f66JdblMrLxOp43pmFNNb9xCnHPhfTG7MQ4q9gNxaWOaQwNlJpN3sOmEclp1ue5uqXvmMYzlCAAwrl0ENB9MRyJ8fXqeCRREl5VstgoTYWObWgwYa1I2rUWWpG6eNzPORqn2Ytb3bpsaZE%3D%24%3D%3D
  • Target attr: name
  • Target Model Type: data/Schedule
  • MaxLength: 1024
  • Format: uri
  • Choices: []
Schedule
  • Field Name: schedule
  • Type: Object
Schedule Name * Name of this Schedule
  • Field Name: schedule.name
  • Type: String
Last Executed (UTC Time) Last time that this schedule executed
  • Field Name: schedule.last_executed
  • Type: String
Owner A business key that identifies the data/User who created the schedule.
  • Field Name: schedule.owner
  • Type: String
Schedule Type * Type of Schedule
  • Field Name: schedule.schedule_type
  • Type: String
  • Choices: ["Single Execution", "Multi Execution"]
Active Is the entire schedule active or not. Default: True
  • Field Name: schedule.active
  • Type: Boolean
  • Default: True
Skip execution on activation. Skip immediate execution on activation.
  • Field Name: schedule.skip_next
  • Type: Boolean
Scheduled resources List of resources that will be actioned
  • Field Name: scheduled_resources.[n]
  • Type: Array
  • Cardinality: [1..n]
Action * Action to perform
  • Field Name: schedule.scheduled_resources.[n].action
  • Type: String
  • Choices: ["Execute"]
Resource Type * Resource types to which this schedule will apply.
  • Field Name: schedule.scheduled_resources.[n].resource_type
  • Type: String
  • Choices: [""]
Resource Attribute * Resource attribute that will be used to filter/choose from.
  • Field Name: schedule.scheduled_resources.[n].resource_attribute
  • Type: String
  • Choices: [""]
Resource * DESCRIPTION
  • Field Name: schedule.scheduled_resources.[n].resource_instance
  • Type: String
  • Choices: [""]
Perform Action DESCRIPTION Default: True
  • Field Name: schedule.scheduled_resources.[n].perform_action
  • Type: Boolean
  • Default: True
Single Execution Single Execution
  • Field Name: single_execute
  • Type: Object
Execution Date (YYYY-MM-DD. Local date) Execution Date
  • Field Name: schedule.single_execute.single_date
  • Type: String
  • Pattern: ^\d{4}\-(0[1-9]|1[012])\-(0[1-9]|[12]\d|3[01])$
Execution Time (HH:MM:SS. Local time) Execution Time
  • Field Name: schedule.single_execute.single_time
  • Type: String
  • Pattern: ^([0-1]\d|2[0-3]):(0[0-9]|[1-5]\d):(0[0-9]|[1-5]\d)$
Execution Timezone (Local timezone) Timezone for Execution Default: 0
  • Field Name: schedule.single_execute.single_timezone
  • Type: String
  • Default: 0
  • Pattern: ^[-+]?\d+$
Multiple Executions Multi Execution
  • Field Name: multi_execute
  • Type: Object
Use Specific Executions Use specific executions.
  • Field Name: schedule.multi_execute.use_specific
  • Type: Boolean
Use Calendar Executions Use calendar executions.
  • Field Name: schedule.multi_execute.use_calender
  • Type: Boolean
Use Timed Executions Use timed executions.
  • Field Name: schedule.multi_execute.use_timed
  • Type: Boolean
Specific Execution Dates Specific Execution Dates
  • Field Name: specific_execute.[n]
  • Type: Array
Execution Date (YYYY-MM-DD. Local date) Execution Date
  • Field Name: schedule.multi_execute.specific_execute.[n].specific_date
  • Type: String
  • Pattern: ^\d{4}\-(0[1-9]|1[012])\-(0[1-9]|[12]\d|3[01])$
Execution Time (HH:MM:SS. Local time) Execution Time
  • Field Name: schedule.multi_execute.specific_execute.[n].specific_time
  • Type: String
  • Pattern: ^([0-1]\d|2[0-3]):(0[0-9]|[1-5]\d):(0[0-9]|[1-5]\d)$
Execution Timezone (Local timezone) Timezone for Execution Default: 0
  • Field Name: schedule.multi_execute.specific_execute.[n].specific_timezone
  • Type: String
  • Default: 0
  • Pattern: ^[-+]?\d+$
Calendar Executions Repeated Execution by Calendar
  • Field Name: calender_execute
  • Type: Object
Calendar Month Calendar Month
  • Field Name: schedule.multi_execute.calender_execute.calender_month
  • Type: Integer
  • Minimum: 1
  • Maximum: 12
Calendar Day Calendar Day
  • Field Name: schedule.multi_execute.calender_execute.calender_day
  • Type: Integer
  • Minimum: 1
  • Maximum: 31
Calendar Hour Calendar Hour
  • Field Name: schedule.multi_execute.calender_execute.calender_hour
  • Type: Integer
  • Maximum: 23
Calendar Minute Calendar Minute
  • Field Name: schedule.multi_execute.calender_execute.calender_minute
  • Type: Integer
  • Maximum: 59
Execution Timezone (Local timezone) Timezone for Execution Default: 0
  • Field Name: schedule.multi_execute.calender_execute.calender_timezone
  • Type: String
  • Default: 0
  • Pattern: ^[-+]?\d+$
Timed Executions Timed Execution
  • Field Name: timed_execute
  • Type: Object
First Execution Date (YYYY-MM-DD. Local date) Execution Date
  • Field Name: schedule.multi_execute.timed_execute.first_date
  • Type: String
  • Pattern: ^\d{4}\-(0[1-9]|1[012])\-(0[1-9]|[12]\d|3[01])$
First Execution Time (HH:MM:SS. Local time) Execution Time
  • Field Name: schedule.multi_execute.timed_execute.first_time
  • Type: String
  • Pattern: ^([0-1]\d|2[0-3]):(0[0-9]|[1-5]\d):(0[0-9]|[1-5]\d)$
First Execution Timezone (Local timezone) Timezone for Execution Default: 0
  • Field Name: schedule.multi_execute.timed_execute.first_timezone
  • Type: String
  • Default: 0
  • Pattern: ^[-+]?\d+$
Repeat after (x) Days Repeat Days
  • Field Name: schedule.multi_execute.timed_execute.repeat_day
  • Type: Integer
Repeat after (x) Hours Repeat Hours
  • Field Name: schedule.multi_execute.timed_execute.repeat_hour
  • Type: Integer
Repeat after (x) Minutes Repeat Minutes
  • Field Name: schedule.multi_execute.timed_execute.repeat_minute
  • Type: Integer
Number of Repeats (0 = infinite) Number of Repeats
  • Field Name: schedule.multi_execute.timed_execute.repeat_number
  • Type: Integer