Hosted CUAE Services - Wiki
Hosted CUAE Services
This article describes the Cisco Unified Application Environment hosted services.
Cisco Unified Communications Manager#
A central aspect of Unified Communications is the phone and phone call. The Cisco Unified Communications Manager allows you to run Cisco IP Phones, make and receive phone calls, and programmatically access and control its other features.
The following API namespaces exposed by the Cisco Unified Application Environment are related to Cisco Unified Communications Manager:
- cisco.uc.cuae.legacy.CallControl---Provides the developer with 1st-party call control (making and receiving calls). These methods and events require a Cisco Unified Communications Manager to make the call or receive the call.
- cisco.uc.cuae.legacy.MediaControl---In a very technical sense, it does not require a Cisco Unified Communications Manager itself, because generally audio streams are sent to call endpoints such as Cisco IP Phones. However, this API is used implicitly by almost every action and event of cisco.uc.cuae.legacy.CallControl.
- cisco.uc.cuae.legacy.JTapi---Provides the developer with 3rd-party call control (monitoring and control over phone calls). These methods and events require a Cisco Unified Communications Manager with which to communicate.
- cisco.uc.cuae.legacy.AxlSoap---Allows the developer to manipulate the Cisco Unified Communications Manager database in real-time. These methods require a Cisco Unified Communications Manager running the AXL-SOAP web service with which to communicate.
- cisco.uc.cuae.legacy.ExtensionMobility---Allows the developer to programmatically control the Extension Mobility service. These methods require a Cisco Unified Communications Manager running the Extension Mobility service with which to communicate. For more general background information on Extension Mobility, see the following PDF: http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/6_1_1/ccmfeat/fsgd.pdf
- cisco.uc.cuae.legacy.CiscoDeviceList---Provides the developer with cached information for devices registered against Cisco Unified Communications Manager, so that queries of device information only impact the Cisco Unified Application Server and not Cisco Unified Communications Manager.
Cisco Unified IP Phones#
In general, you need IP Phones if you want to build applications that call user's phones, are called by user's phones, or monitor and control these phones to fulfill business process requirements.The Cisco IP Phones also support an XML-based API that allows you to control their large screen, providing an alternate avenue for an application's UI other than the desktop.
The following API namespaces exposed by the Cisco Unified Application Environment are related to Cisco Unified IP Phones:
- cisco.uc.cuae.legacy.CiscoIpPhone---Allows the developer to control the user interface for phones that support IP Phone Services (XSI).
- cisco.uc.cuae.legacy.MediaControl---Allows the developer to stream audio directly to and from an IP Phone, outside of the context of a phone call.
- cisco.uc.cuae.legacy.CallControl---Allows the developer to call endpoints and answer calls from telephony endpoints, such as the Cisco IP Phone. While you do not strictly need a Cisco Unified IP Phone to exert the cisco.uc.cuae.legacy.CallControl namespace, having one or more IP phones available is the most common way to manually test applications which use these APIs.
- cisco.uc.cuae.legacy.Providers.JTapi--- Allows the developer to monitor and control Cisco Unified IP Phone endpoints.
Cisco Unified Presence#
Cisco Unified Presence allows you to know the status, availability, preferences, and other real-time information related to a user's or group of users' availability to communicate. The Cisco Unified Application Environment can communicate directly with Cisco Unified Presence using SIP/SIMPLE.
The following API namespaces exposed by the Cisco Unified Application Environment are related to Cisco Unified Presence:
- cisco.uc.cuae.legacy.Presence---Allows you to receive real-time notifications of changes to the presence, availability, and other user status changes.