Cisco Unified Communications Manager Interfaces
The interface types supported by Unified CM are divided into the following types:
The following are the provisioning interfaces of Unified CM:
Cisco Extension Mobility Service
The Administration XML (AXL) API provides a mechanism for inserting, retrieving, updating and removing data from the Unified CM configuration database using an eXtensible Markup Language (XML) Simple Object Access Protocol (SOAP) interface. This allows a programmer to access Unified CM provisioning services using XML and exchange data in XML form, instead of using a binary library or DLL. The AXL methods, referred to as requests, are performed using a combination of HTTP and SOAP. SOAP is an XML remote procedure call protocol. Users perform requests by sending XML data to the Unified CM Publisher server. The publisher then returns the AXL response, which is also a SOAP message. For more information, See the Administrative XML Tech Center on the Cisco Developer Network http://developer.cisco.com/web/axl/home.
Cisco Extension Mobility
The Cisco Extension Mobility (Extension Mobility) service, a feature of Unified CM, allows a device, usually a Cisco Unified IP Phone, to temporarily embody a new device profile, including lines, speed dials, and services. It enables users to temporarily access their individual Cisco Unified IP Phone configuration, such as their line appearances, services, and speed dials, from other Cisco Unified IP Phones. The Extension Mobility service works by downloading a new configuration file to the phone. Unified CM dynamically generates this new configuration file based on information about the user who is logging in. You can use the XML-based Extension Mobility service API with your applications, so they can take advantage of Extension Mobility service functionality.
For more information, see the Extension Mobility API Tech Center on the Cisco Developer Network https://developer.cisco.com/site/extension-mobility/develop-and-test/documentation/latest-version/emapi-developer-guide.gsp.
Also, see Cisco Unified Communications Manager XML Developers Guide for relevant release of Unified CM at the following location:
Device Monitoring and Call Control Interfaces
The following are the device monitoring and call control interfaces of Unified CM:
Cisco TAPI and Media Driver
Cisco Web Dialer
Cisco TAPI and Media Driver
Unified CM exposes sophisticated call control of IP telephony devices and soft-clients via the Computer Telephony TAPI interface. Cisco's Telephone Service Provider (TSP) and Media Driver interface enables custom applications to monitor telephony-enabled devices and call events, establish first- and third-party call control, and interact with the media layer to terminate media, play announcements, record calls.
For more information, see the TAPI and Media Driver Tech Center on the Cisco Developer Network http://developer.cisco.com/web/tapi/home.
Also, see the Cisco Unified TAPI Developers Guide for Cisco Unified Communications Manager for relevant release of Unified CM at the following location:
Cisco Web Dialer
The Web Dialer, which is installed on a Unified CM server, allows Cisco Unified IP Phone users to make calls from web and desktop applications. For example, the Web Dialer uses hyperlinked telephone numbers in a company directory to allow users to make calls from a web page by clicking the telephone number of the person that they are trying to call. The two main components of Web Dialer comprise the Web Dialer Servlet and the Redirector Servlet.
For more information, see the Web Dialer Tech Center on the Cisco Developer Network https://developer.cisco.com/site/webdialer/develop-and-test/documentation/latest-version/.
For more information on Cisco Web Dialer, see the Cisco Unified Communications Manager XML Developers Guide for relevant release of Unified CM at the following location:
The following are the serviceability interfaces of Unified CM:
A collection of services and tools designed to monitor, diagnose, and address issues specific to Unified CM serviceability XML interface:
Provides platform, service and application performance counters to monitor the health of Unified CM hardware and software
Provides real-time device and CTI connection status to monitor the health of phones, devices, and applications connected to Unified CM.
Enables remote control (Start/Stop/Restart) of Unified CM services.
Collects and packages Unified CM trace files and logs for troubleshooting and analysis.
Provides applications with Call Detail Record files based on search criteria.
Provides management consoles with SNMP data specific to Unified CM hardware and software.
For more information, see the Serviceability XML Tech Center on the Cisco Developer Network http://developer.cisco.com/web/sxml/home.
SNMP interface allows external applications to query and report various UCMgr entities. It provides information on the connectivity of the Unified Communication Manager to other devices in the network, including syslog information.
The MIBs supported by Unified CM includes:
Cisco-CCM-MIB, CISCO-CDP-MIB, Cisco-syslog-MIB
Standard Mibs like MIB II, SYSAPPL-MIB, HOST RESOURCES-MIB
For more information, see the SNMP/MIB Tech Center on the Cisco Developer Network https://developer.cisco.com/site/sxml/.
Also, see the Cisco Unified Communications Manager XML Developers Guide for relevant release of Unified CM at the following location:
Routing Rules Interface
Cisco Unified Communication Manager 8.0(1) and later supports the external call control (ECC) feature, which enables an adjunct route server to make call-routing decisions for Cisco Unified Communications Manager by using the Cisco Unified Routing Rules Interface. When you configure external call control, Cisco Unified Communications Manager issues a route request that contains the calling party and called party information to the adjunct route server. The adjunct route server receives the request, applies appropriate business logic, and returns a route response that instructs Cisco Unified Communications Manager on how the call should get routed, along with any additional call treatment that should get applied.
For more information, see the Routing Rules Interface Tech Center on the Cisco Developer Network https://developer.cisco.com/site/curri/develop-and-test/documentation/latest-version/.
Cisco Connection Interface
This interface has the APIs that can be invoked on a connection object.
Connections retain their references to calls and addresses forever. A
connection reference that is obtained from a call event can be used to obtain
the connection call
(getCall()) and address
Local Universal Unique Identifier of Party Associated with the Connection
Local Universal Unique Identifier of Party Associated on the Other Side of the Call