/mcpC H A P T E R 42 Cisco Unity Connection Provisioning Interface (CUPI) API--Message Aging Policy APIs • Cisco Unity Connection Provisioning Interface (CUPI) API -- Mailbox Store API, on page 585 • Cisco Unity Connection Provisioning Interface (CUPI) API -- Mailbox Quota alert, on page 592 • Cisco Unity Connection Provisioning Interface (CUPI) API -- Message Aging Policy, on page 595 • Cisco Unity Connection Provisioning Interface (CUPI) API -- Message Aging Rules , on page 600 • Cisco Unity Connection Provisioning Interface (CUPI) API -- Message Aging Text, on page 606 • Cisco Unity Connection Provisioning Interface (CUPI) API -- Message Expiration , on page 610 Cisco Unity Connection Provisioning Interface (CUPI) API -- Mailbox Store API Mailbox Stores Configuration Administrator can use this APIs for creating, reading, modifying and deleting mailbox stores for listing,viewing, creation, selection, and deletion. During installation, Cisco Unity Connection automatically creates: • A mailbox store database for information on voice messages (who each message was sent to,when it was sent, the location of the WAV file on the hard disk, and so on). • An operating-system directory for voice message WAV files. • An administrator with the required permissions can create up to four additional mailbox stores. Each additional mailbox store includes: • Another mailbox-store database for information on voice messages that are saved in that mailbox store. The database is pre-sized for an average of approximately 40 messages each for 10,000 users, or about 1.25 GB. (The database application currently being used for Connection cannot dynamically resize a database after it is created.) • Another operating-system directory for the voice message WAV files and other message attachments. Listing the Mailbox Stores The following is an example of the GET request that lists all the mailbox stores: GET https://<connection-server>/vmrest/mailboxstores Cisco Unity Connection Provisioning Interface (CUPI) API 585