McDewey

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

Page 171

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

Comments Operations Data Type Parameter A flag indicating whether Cisco Unity Connection will say "call for <recorded name of the call handler>" when the subscriber answers the phone. Requires a "TransferType" of supervised (1). This functionality is normally used when a single extension number is being shared by multiple subscribers or a scenario where the subscriber who is the message recipient takes calls for more than one dialed extension. The introduction alerts the subscriber who answers that the call is for the call handler. Default value: false Read/Write Boolean TransferIntroduce A flag indicating whether Cisco Unity Connection prompts the subscriber to accept or refuse a call ("Press 1 to take the call or 2 and I'll take a message"). If the call is accepted, it is transferred to the subscriber phone. If the call is refused, Cisco Unity Connection plays the applicable subscriber greeting. Requires a "TransferType" of supervised (1). Typically this is used in conjunction with the call screening option ("TransferScreening" column) enabled. This combination enables the subscriber to hear the name of the caller and then decide if they want to take the call or not. Values: • false: Transfer confirm disabled • true: Transfer confirm enabled Default value: false Read/Write Boolean TransferConfirm Requires a "TransferType" of supervised (1). Normally this column is used along with "TransferConfirm" to allow the subscriber to screen calls. Values: • false: Call screening disabled • true: Ask and record caller name Default value: false Read/Write Boolean TransferScreening Cisco Unity Connection Provisioning Interface (CUPI) API 139 Cisco Unity Connection Provisioning Interface (CUPI) API -- User Transfer Rules Explanation of Data Fields