McDewey

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

Page 240

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

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <HtmlDevice> <URI>/vmrest/users/24cb82fc-5153-4c3f-abc7-ef442b27b4e9/notificationdevices/htmldevices/64d260ca-7f09-46df-be87-88cd3ba9c5e3</URI> <Active>false</Active> <DeviceName>SMTP</DeviceName> <DisableMobileNumberFromPCA>true</DisableMobileNumberFromPCA> <DisplayName>HTML_3</DisplayName> <NotificationTemplateID>103c4514-db6e-489b-bc08-e9e131b60099</NotificationTemplateID> <ObjectId>64d260ca-7f09-46df-be87-88cd3ba9c5e3</ObjectId> <Undeletable>true</Undeletable> <SubscriberObjectId>24cb82fc-5153-4c3f-abc7-ef442b27b4e9</SubscriberObjectId> <UserURI>/vmrest/users/24cb82fc-5153-4c3f-abc7-ef442b27b4e9</UserURI> <EventList>NewVoiceMail</EventList> <ScheduleSetObjectId>e6706d47-257f-4e24-bf9f-a182bb3b2633</ScheduleSetObjectId> <InitialDelay>0</InitialDelay> <RepeatInterval>0</RepeatInterval> <RepeatNotify>false</RepeatNotify> </HtmlDevice> Searching To retrieve a list of Notification Devices that meet a specified search criteria, add the following query parameter to a GET: query=(column [is | startswith] value) For example, to find all Notification Devices with a DisplayName that starts with "Phone": GET https://<connection-server>/vmrest/users/<UserObjectId/notificationdevices?query=(DisplayName%20startswith%20Home) Search criteria can also be used when doing a GET to the specialized Device resources. Creating A generic Notification Device resource is read-only, so new ones cannot be created. However, the four specialized Device resources are not read-only, so new ones can be created. Each of the four specialized Device resources has different required parameters during creation. Updating A generic Notification Device resource is read-only, so Notification Devices cannot be updated. However, the five specialized Device resources are not read-only, so an API user can update the appropriate specialized Device resource. Updating an Existing Phone Device The following is an example of a PUT request that modifies the FailDeviceObjectId of an existing Phone Device. The FailDeviceObjectId indicates which Notification Device to try if notification fails to the current device, which allows you to setup a chain of Notification Devices. Cisco Unity Connection Provisioning Interface (CUPI) API 208 Cisco Unity Connection Provisioning Interface (CUPI) API for User Account Settings Searching