McDewey

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

Page 27

↗ View in doc context
page
27
source
unity-connection/rest-api/cumi/cumi.md
chunk_id
unity-connection::rest-api::cumi::cumi::20

C H A P T E R 4 Cisco Unity Connection Messaging Interface (CUMI) API -- Sending a Voice Message with One or More Attachments • About Sending Voice Messages with One or More Attachments , on page 21 • Sending a Voice Message with Attachments, on page 21 About Sending Voice Messages with One or More Attachments In Cisco Unity Connection 8.5 and later, CUMI will allow voice mails to be sent that have additional attachments of any type. (In earlier versions of Connection, CUMI allows only voice messages with one audio attachment to be sent.) • Sending a Voice Message with Attachments The basics of sending a voice message involve a creating multipart HTTP form that contains an object representation of a Message, an object representation of a Recipient list and a set of zero or more additional parts that will be added as message attachments. If there are parts beyond the first two, then the third one must be either audio/wav data or an object representation of a CallControl object (the CallControl object is used when the stream resides on the server after using CUTI to record over the phone). The third part is considered to be the "primary" body of the voice message. The parts beyond the third part are passed transparently to the message system to be added as an attachment. These additional parts must have a content type and some data. HTTP example for a send message POST request: Cisco Unity Connection Messaging Interface (CUMI) API 21

Image 1 from page 27