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

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

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

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

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.

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.

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

Field	Description
CUCxn Server Name	Mandatory. Fill out the Cisco Unity Connection (CUC) server name.
Publisher	Select this checkbox only if you're configuring a publisher node. Note The Publisher tab/panel displays only when this checkbox is selected.
Cluster Name	Mandatory. Fill out the name you want to use for this cluster. The new cluster is created with this name. Note If the Publisher checkbox is not selected, the Cluster Name field appears as a drop-down list so that you can choose an existing cluster.
Network Addresses	Expand this field, then: At Address Space, select SERVICE_PROVIDER_SPACE. At IPV4 Address, fill out the IP address of the CUC server. The Hostname field is automatically populated with the CUC server name. Edit this value if necessary. 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. At Domain, fill out the domain of the CUC application. At Description, fill out a description for the network address. If NAT is used, also configure an APPLICATION_SPACE network address.

Field	Description
Credentials	Expand this field then add credentials for PLATFORM, ADMIN, HTTP, and SNMP_Vx credential types. Click the Plus icon (+) to add more credentials: Fill out the user ID and password that you configured when you installed the CUC. Choose RO (Read-only) or RW (Read or Write) for the Access Type. The default is RO. Optionally, provide a description for the credential. Note ADMIN credentials are used by Automate to access the CUC REST API interface for provisioning synchronization. These credentials must be manually configured in Cisco Unity Connection, then configured in VOSS Automate, via (default menus) Apps Management > CUC > Servers, Credentials fields. PLATFORM and ADMIN are required for Service Inventory to generate reports for UC applications.

Field	Description
Call Processing ID	The Call Processing ID of this cluster
SDR Cluster ID	The Shared Data Repository (SDR) CUC cluster ID.
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.
Port	The port on the CUC server to connect to. The default is 8443.
Monitoring	For new servers and if Arbitrator servers are available, monitoring can be enabled for this CUC server on VOSS Insights. The Arbitrator server checkboxes 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.

An asterisk * in the title indicates the field is mandatory.
If a field has a default value, it is shown in the Description column.
If the field type is an array, the Field Name has a .[n] suffix, where n is the array index placeholder.
Object and array field names are listed to provide context. If a field belongs to an object or an array, the full field name is shown in dot separated notation.

Title					Description	Details
Name *					The name of the schedule.	Field Name: name Type: String Target: data/Schedule Target attr: name MaxLength: 1024 Format: uri
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

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.

Model: relation/HcsCUCxnScheduleREL

CUC

Model Details: relation/HcsCUCxnScheduleREL