Model: device/cucm/HuntList

CUCM HuntList

When adding a new Hunt Group, the following workflow is executed:

A hunt list is added with the details input by the user.
A hunt pilot is added with the details input by the user.
One or more line groups are created with the specified directory numbers as members.

When modifying a Hunt Group, the following workflow is executed (depending on what was modified):

The line group details are modified.
Added line groups are added. Note that removed line groups are not deleted.
The hunt list is modified.
The hunt pilot is modified.

When deleting a Hunt Group, the following workflow is executed:

The line groups that are members of the hunt list are deleted (if they are not used by any other hunt list in the system).
The hunt pilot is deleted.
The hunt list is deleted.

Model Details: device/cucm/HuntList

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
Cisco Unified Communications Manager Group *															Choose a Cisco Unified Communications Manager Group from the drop-down list. The Hunt List registers to the first node in the Cisco Unified Communications Manager Group. Note If you choose a Cisco Unified Communications Manager group that has only one node that is configured, you receive a warning. To avoid this issue, choose a group that is configured with more than one node.																				Field Name: callManagerGroupName Type: ["String", "Null"] Target: device/cucm/CallManagerGroup Target attr: name Cardinality: [1..1] Format: uri
Description															Enter a description to help you identify further details about the hunt list that do not fit into the name.																				Field Name: description Type: String Cardinality: [0..1]
Enable this Hunt List (change effective on Save; no reset required)															Check this check box to enable your hunt list immediately when you click Save. No system reset is required.																				Field Name: routeListEnabled Type: Boolean Cardinality: [0..1]
Members																																			Field Name: members Type: ["Object", "Null"] Cardinality: [0..1]
		Member																																	Field Name: member.[n] Type: Array
			Selection Order																																Field Name: members.member.[n].selectionOrder Type: Integer Cardinality: [1..1]
			Line Group Name *																																Field Name: members.member.[n].lineGroupName Type: ["String", "Null"] Cardinality: [1..1]
For Voice Mail Usage															If this hunt list is to be used for voicemail, check this check box. If you this check box, the route list control process keeps a count of the setups that are being served to the hunt list, and will not allow more setups than the number of available devices. As a result, each device in the hunt list is treated as if it has a Busy Trigger and related Maximum Number of Calls of one.																				Field Name: voiceMailUsage Type: Boolean Cardinality: [0..1]
Name *															The name can comprise up to 50 alphanumeric characters and can contain any combination of spaces, periods (.), hyphens (-), and underscore characters (_). Ensure each hunt list name is unique to the route plan. Note Use concise and descriptive names for your hunt lists. The CompanynameLocationCalltype format provides enough detail and is short enough so you can easily identify a hunt list.																				Field Name: name Type: String Cardinality: [1..1]