McDewey

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

Page 13

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

C H A P T E R 4 Cisco Unity Connection Notification Interface (CUNI) API -- CUNI FAQs • CUNI FAQs, on page 9 CUNI FAQs • Where Can I Get the WSDL? The WSDL can be found at: http://<connection-server>/messageeventservice/services/MessageEventService?wsdl The WSDL is the same across versions except that for 8.0 there was a keepAlive parameter added to the subscribe method. Note • What Happens to Subscriptions if the Cisco Unity Connection Server Is Restarted? Subscriptions are stored in the database. When Cisco Unity Connection is restarted, the Notifier reads the existing subscriptions and begins sending out notifications. • What is authentication mechanism to register for CUNI events? Basic AUTH/HTTPS – requires administrative credentials. • Can several listeners subscribe for the events for same mailbox specifying different callback urls? Yes they can • Does CUNI support HTTPS for subscribing for events as well can a callback url be https? Yes, Cisco Unity Connection Release 14, 12.5(1) SU3 and later CUNI supports HTTPS for both subscribing and callback url. • Does CUNI in HTTPS mode support Multi SAN CA signed certificates configured on callback? No, CUNI in HTTPS mode only supports self signed and CA signed Certificates. • What kind of event or alerting mechanism is used in case it cannot reach the callback url? Any SNMP alert? Cisco Unity Connection Notification Interface (CUNI) API 9

Image 1 from page 13

Image 2 from page 13