|Attention: DocWiki has reached EOL and will be decommissioned January 25, 2019.|
Cisco Unity Connection Provisioning Interface (CUPI) API -- For End Users
Links to Other API pages: Cisco_Unity_Connection_APIs
|CUPI for End Users Guide Contents|
|API Overview |
Index of All End Users CUPI Documentation
Cisco Unity Connection Provisioning Interface (CUPI) for End Users is a provisioning API for Cisco Unity Connection that has been designed to be stable and simple to use. It is based on leading industry standards for web-based API development, and provides access to many of the account settings of the end users.
By using CUPI, end users can do the following:
- Update transfer options (basic transfer rules), unified messaging account passwords (Connection 8.5 and later), external services account passwords (Connection 8.0), and user passwords and PINs
- Record greetings and voice names
- Create, read, update, and delete private lists and private list members, alternate names, and user-defined alternate extensions
- Read SMTP proxy addresses. basic user information (for example, alias, display name, and DTMF access ID), class of service information, and administrator-defined alternate extensions
Previous provisioning APIs required knowledge of the underlying database, and were vulnerable to changes in the database schema. CUPI provides a layer over the database to make the interface more stable.
CUPI is standards based. CUPI was developed by using the latest advances in web-based interfaces. It is a REST interface that standardizes operations such as add, delete, and modify. The XML comes with standard XML schema definitions that are annotated with information about what is in them.
Other product groups in VTG are developing REST-based interfaces, and as the interfaces converge this positions CUPI well to fit in with them. REST interfaces also work well with Web 2.0 applications.
As a web-based interface, CUPI is independent of operating system and programming language and does not require any client libraries to use.
Note: It is recommended to perform provisioning only on the Publisher server in Active-Active mode and on Subscriber (Acting Primary) in case of cluster failover. The password change and password setting modification for User PIN/Web application should be provisioned on Publisher server in Active-Active mode.
In order to begin developing with the Cisco Unity Connection CUPI API, you need to obtain the following:
- Cisco Media Convergence Server (MCS) for Cisco Unity Connection version 8.0 and later
- For detailed hardware requirements, see the Cisco Unity Connection 8.x Supported Platforms List
- Cisco Unity Connection Software Ordering
- Not for Resale Kits (Must be eligible to purchase)
- Communications System Release Kit
Discounts for some of the required hardware and software may be available for participants in the Cisco Technology Developer Program.
We recommend that all developers have an up-to-date Cisco Developer Services support agreement. This provides the developer with access to professional support and assistance for application development.
Other CUPI Resources
Additional information about CUPI is also available on the Cisco Developer Network (link to CDN). Note, however, that the documentation here on the DocWiki is the most up-to-date documentation available for CUPI.
To participate in the CUPI forum, see the CUPI forum on CDN.
On the CUPI page on CDN, you will also find links to the CUPI WADL and CUPI XML schema.
See the following for information on troubleshooting all Connection APIs: