McDewey

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

Page 236

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

<RetriesOnBusy>0</RetriesOnBusy> <RetriesOnRna>0</RetriesOnRna> <RingsToWait>0</RingsToWait> <RnaRetryInterval>0</RnaRetryInterval> <SendCount>true</SendCount> <WaitConnect>false</WaitConnect> <TransmitForcedAuthorizationCode>false</TransmitForcedAuthorizationCode> <DeviceName>SMTP</DeviceName> <PromptForId>false</PromptForId> <SendCallerId>true</SendCallerId> <SendPcaLink>false</SendPcaLink> <Undeletable>true</Undeletable> <DetectTransferLoop>false</DetectTransferLoop> <SuccessRetryInterval>0</SuccessRetryInterval> <RetriesOnSuccess>0</RetriesOnSuccess> <EventList>NewVoiceMail</EventList> <ScheduleSetObjectId>d7ea64ca-e3fc-4d0a-8bd5-ef2337a31b97</ScheduleSetObjectId> <InitialDelay>0</InitialDelay> <RepeatInterval>0</RepeatInterval> <RepeatNotify>false</RepeatNotify> </NotificationDevice> </NotificationDevices> Listing and Viewing Specialized Devices The following is an example of a GET that lists all Phone Devices for the specified User. Listing all specialized devices of other types is very similar; simply do a GET to the pagerdevices, smsdevices, or smtpdevices resource, rather than to the phonedevices resource. GET https://<connection-server>/vmrest/users/<UserObjectId>/notificationdevices/phonedevices The following is the response from the above GET request. Note that each returned resource is a Phone Device rather than a Notification Device since the request was for Phone Devices only. Cisco Unity Connection Provisioning Interface (CUPI) API 204 Cisco Unity Connection Provisioning Interface (CUPI) API for User Account Settings Listing and Viewing Specialized Devices