Model: relation/HcsDpAssociateVmSvcToCustomerREL

Associate Voice Mail Service to Customer

Prerequisites

To associate Voice Mail Service with a customer, the Voice Mail Service must be created before starting this procedure. See Create Voice Mail Service.

If the Integrate with Cisco Unified CM check box was selected when the Voice Mail services was created, a customer dial plan and a site dial plan must be created before a Voice Mail Service can be associated with a customer; otherwise the association will fail.

If the Integrate with Cisco Unified CM Webex DI check box was selected when the Voice Mail services was created, the selected Cisco Unified CM Cluster provides the Voice Mail Trunk Address selection.

Perform these steps:

Set the hierarchy path to the customer to which you want to associate the Voice Mail Service.

Choose Services > Voice Mail > Associate Voice Mail Service to Customer.

Click Add to associate Voice Mail Service to a customer.

From the Voice Mail Service drop-down, choose the name of the Voice Mail Service that has been defined by the provider and available to this customer.

Click Save to associate the Voice Mail Service with the customer. The association appears in the list.

When the Voice Mail Service is associated with a customer and the Integrate with Cisco Unified CM check box was selected for the Voice Mail Service, the following is provisioned based on the deployment mode of the Voice Mail server:

Voice Mail Deployment Mode	Cisco Unified Communications Manager	Cisco Unity Connection
Dedicated	Creates Integration at customer level: SipTrunk, Route Group, AllowVm route partition	Creates customer-specific Port Group, ports (3), route partition, calling search space and user template
Partitioned	Creates Integration at customer level: SipTrunk, Route Group, AllowVm route partition	Creates new tenant (partition), port group, ports (3), route partition, calling search space and user template

Note: The deployment mode for the Voice Mail service is determined by the mode selected when the Cisco Unity Connection is first added to VOSS Automate using Device Management > CUC.

When the Integrate with Cisco Unified CM Webex DI check box was selected for the Voice Mail Service, the Voice Mail Trunk Address selected from the selected Cisco Unified CM Cluster - will be associated with the Route Group as a part of the Route List and Route Group provisioning.

Associating the voice mail service to the customer will configure the Cisco Unity Connection (CUC) specified in the Voice Mail Service with the data required for use by the customer.

Model Details: relation/HcsDpAssociateVmSvcToCustomerREL

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
Customer Name				Field Name: customerName Type: String Target: /api/data/BaseCustomerDAT/choices/?field=CustomerName&format=json&hierarchy=[hierarchy]&auth_token=%3D%3D%24WkgJDhnL6ZJ6EgVQ%24LK617K3Wr50LT3ZayxCeQKPYPQyes3LpwWnvkHMIWwlCy6CPR5VC/aT9RYmNoOuyetLwgTLxIhhHGUG2x4ZDUdoSA4q8AQIHyfq0yMleeaWq7mN0TvbJ4ByKnjJ7LIIpLUIR2E85VcJHW5TlNVfF%2BBX/so4vxzjGl%2B%2BOOPHwSTcLnv5CJRQyPjD%2B4Q80zJkNKZm2bikhQb/GNVTixQL3OBiX4yXASir38CGbnv%2BpVTUezLCKcwj5cd%2BtPrdN62uq4vNnjrRfoo%2BPyGJBG73yUOP496r/BfBSQvvtoy6sMCU6Ao5yRLOg0a6Mdhf227zIKjh3j4HoxruAdXUZTVv5K4VEFRx7FUeti1Oc/llTpEfMRPjg%2BlnOeUJHBfgQkbk%2BY4ODO/xHKuYwg2URdGaWaBq%2BP8jZZ8M6eC7c%24%3D%3D Target attr: CustomerName Target Model Type: data/BaseCustomerDAT MaxLength: 1024 Format: uri Choices: []
Voice Mail Service *			The selected voice mail service will identify the Cisco Unity Connection server to be provisioned with the customer information.	Field Name: voiceMailService Type: String Target: /api/data/HcsDpVmServiceDAT/choices/?field=name&format=json&hierarchy=[hierarchy]&auth_token=%3D%3D%24Y6StKTKUDZt8J6to%24NclF/cMJxmpUmVrei/K53ZISgSt3PvzftA33xhmI5/O08fihGDALu6T968fPUnCOvGjo%2BDIeMJ3JvBrwXuVx6cMSeN4b2rIUwSYp5Qphm61FWqwu6rUKieRzsSUZFT9lCWjDgkRtJalCzIpG1ThFCIpF60y1KmeBOd/eBqSH0%2BQeQ7rRDxJQZpBI26SQY1d7vdddZxyuDGLj6tCRcRraiVKshcF5dDtfA/1SbclUl1ted3tJMpN2rO9DAYoNtVrN1ObQcJGqEqhEGBIT%2BoaBXZGjWQO1y39YbJNOX4Qmdn2z615rlMdbiArNj8vDc9VuYFUQc8CDikJt/pDCaC0HHqle72k4MQjZcesulkRZ4ZM6S%2Ba5GcMVifgJFuMcjL4NLRC50kbiep8iuL3GsQwNlHkVDRBL%24%3D%3D Target attr: name Target Model Type: data/HcsDpVmServiceDAT MaxLength: 1024 Format: uri Choices: []
	Shadow			Field Name: shadow.[n] Type: Array Cardinality: [0..1]
		Name *		Field Name: shadow.[n].name Type: String MaxLength: 1024