McDewey

Multi-vendor documentation library · semantic search · MCP endpoint at /mcp

Page 306

↗ View in doc context
page
306
source
unity-connection/rest-api/cupi/cupi.md
chunk_id
unity-connection::rest-api::cupi::cupi::272

Comments Operation Data Types Parameter The action to take for delivery receipt messages. Values can be: • 0: Reject the Message • 1: Accept the Message • 2: Relay the Message • 3: Accept and Relay the Message For 2 and 3, values have to provide RelayAddress. Read/Write Integer DeliveryReceiptAction Select the address to which system relays voicemail, email, fax, or delivery receipts when Connection is configured to relay that message type. This field is not editable unless you have selected Relay the Message or Accept and Relay the Message as the message action for one or more message types. In order to configure Connection to relay messages, you must first configure an SMTP Smart Host on the System Settings > SMTP Configuration > Smart Host page. Enter a combination of text and tokens that Connection replaces with a value from the user profile. (For example, Connection replaces %Alias% with the alias from each user profile when editing the corresponding user.) Note Read/Write String (320) RelayAddress Cisco Unity Connection Provisioning Interface (CUPI) API -- User Template Notification Devices User Template Notification Devices The following URI can be used to view the user template object ID: GET https://<connection-server>/vmrest/usertemplates/<usertemplateobjectid> From the above URI, get the notification devices object ID: https://<connectionserver>/vmrest/usertemplates/<usertemplateobjectid>/usertemplatenotificationdevices Cisco Unity Connection Provisioning Interface (CUPI) API 274 Cisco Unity Connection Provisioning Interface (CUPI) API for User Template Cisco Unity Connection Provisioning Interface (CUPI) API -- User Template Notification Devices