McDewey

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

Page 5

↗ View in doc context
page
5
source
unity-connection/rest-api/cuni/cuni.md
chunk_id
unity-connection::rest-api::cuni::cuni::0

C H A P T E R 1 API Overview • Introduction, on page 1 • Technical Details , on page 1 • Getting Started with CUNI , on page 2 • Other CUNI Resources , on page 2 • Troubleshooting , on page 2 Introduction The Cisco Unity Connection Notification Interface (CUNI) API is a web service interface for managing subscriptions to events from Cisco Unity Connection systems. It provides a way to get asynchronous notifications when voice mail messages are received, deleted, or changed. CUNI can be used to integrate Connection into an existing enterprise-wide portal. CUNI is designed to provide a simple, stable method of accessing the notification functionality on Connection systems through a standards based interface using XML and HTTPS. Through CUNI, you can do the following: • Subscribe for message events • Subscribe for one or many users on a single channel Note: All the above functions associated with CUNI API support both the IPv4 and IPv6 addresses. However, the IPv6 address works only when Connection platform is configured in Dual (IPv4/IPv6) mode. Note that CUNI is intended for use in server-to-server applications where receiving notifications for many users over a single connection is required. As such, it is designed to handle a small number of clients that are each subscribing for notifications on a large set of subscribers. It also requires Administrative credentials, making it inappropriate for browser applications to use directly. CUNI is composed of two parts: a SOAP interface for subscribing, and an asynchronous piece (the Notifier) that delivers events as XML over HTTP. Technical Details • CUNI is standards-based: it implements a standard SOAP-based interface for managing subscriptions. Message events are sent as standard XML over HTTP. Cisco Unity Connection Notification Interface (CUNI) API 1

Image 1 from page 5