McDewey

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

Page 663

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

C H A P T E R 44 Cisco Unity Connection Provisioning Interface (CUPI) API for Dial Plan • Cisco Unity Connection Provisioning Interface (CUPI) API -- Partition API , on page 631 • Cisco Unity Connection Provisioning Interface (CUPI) API -- Search Space API, on page 636 • Cisco Unity Connection Provisioning Interface (CUPI) API -- Search Space Member API, on page 644 Cisco Unity Connection Provisioning Interface (CUPI) API -- Partition API Partition API Administrator can use this API to create, update, delete, or fetch the partition. In Cisco Unity Connection, you create partitions as a way to group together objects to which callers and users can address messages or place calls while interacting with Connection. One or more partitions can be grouped together as members of a search space, and a partition can be a member of more than one search space. The following types of objects belong to a partition: • User Templates • Call Handler Templates • Contact Templates • Users with mailboxes (primary extension) • User alternate extensions • Contacts (including VPIM contacts) • System distribution lists • System call handlers • Directory handlers • Interview handlers • VPIM locations Extensions must be unique within a partition, although partitions can contain objects that do not have an associated extension (for example, some contacts and system distribution lists). The names of objects do not have to be unique within a partition. Administrator-defined contact phone numbers also do not need to be unique within a partition. Cisco Unity Connection Provisioning Interface (CUPI) API 631

Image 1 from page 663