Feedback
Table Of Contents
Cisco Extension Mobility Service API
New Information for Cisco Unified Communications Manager 9.1(1)
New and Changed Information in Previous Releases of Unified CM
New Information for Cisco Unified Communications Manager 9.0(1)
New Information for Cisco Unified Communications Manager 8.6(1)
New Information for Cisco Unified Communications Manager 8.5(1)
New Information for Cisco Unified Communications Manager 8.0(1)
How Cisco Extension Mobility Works
Using the Cisco Extension Mobility API
Message Document Type Definitions
Extension Mobility Service Response Codes
Cisco Extension Mobility Service API
This chapter describes the Cisco Extension Mobility (Extension Mobility) service. It contains the following sections:
•
How Cisco Extension Mobility Works
•
•
Overview
The Cisco Extension Mobility service, a feature of Cisco Unified Communications Manager (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 Cisco 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.
The system associates each Cisco Extension Mobility user with a device profile through configuration. When a user logs in to a phone, the phone temporarily embodies the device profile for that user. The two primary functions of the Cisco Extension Mobility feature comprise authenticating the user who is logging in and generating the right configuration file from the user information.
You can view the device profile as a template for a physical device. The device profile defines the attributes of a device, but it does not associate with a physical phone. A device profile includes information such as the phone template, user locale, services to which the device is subscribed, and so on. Because it does not associate with a physical phone, it does not have information such as MAC address, location, and region. When a phone downloads a device profile, the phone retains its physical attributes such as MAC address, device location information, device CSS, and so on.
The Unified CM support for the Cisco Extension Mobility service comprises the Cisco Extension Mobility Application (EMApp) and the Cisco Extension Mobility Service (EMService) modules. The application and service modules, along with other Unified CM infrastructure such as the Database Layer (DBL), User directory (either internal or an external LDAP directory), and TFTP server, provide the Cisco Extension Mobility feature.
You can use the XML-based EMService API with your applications, so they can take advantage of Cisco Extension Mobility service functionality. For details about how to use the Cisco Extension Mobility service API, see the "Using the Cisco Extension Mobility API" section.
To successfully develop an application that uses the Cisco Extension Mobility service, you need to understand how the service operates and how your application fits into the Cisco Extension Mobility service. This chapter includes the high-level concepts that are important in understanding the Cisco Extension Mobility service
New and Changed Information
The following sections provide information on the changes in the Extension Mobility APIs in Unified CM release 9.1(1) and the previous releases:
•
•
New Information for Cisco Unified Communications Manager 9.1(1)
There are no changes in the Extension Mobility API in Unified CM release 9.1(1).
New and Changed Information in Previous Releases of Unified CM
The following section provides the new and changed information in the older released of Unified CM release.
•
•
•
•
New Information for Cisco Unified Communications Manager 9.0(1)
There are no changes in the Extension Mobility API in Unified CM release 9.0(1).
New Information for Cisco Unified Communications Manager 8.6(1)
There are no changes in the Extension Mobility API inUnified CM release 8.6(1).
New Information for Cisco Unified Communications Manager 8.5(1)
There are no changes in the Extension Mobility API in Unified CM release 8.5(1).
New Information for Cisco Unified Communications Manager 8.0(1)
A new service parameter, called Maximum Concurrent Call Requests, is adde
The following sections describe API updates made in Unified CM 8.0(1):
New APIs
Table 4-1describes new APIs added in Unified CM 8.0(1).
From Unified CM release 8.0(1) onwards the Extension Mobility APIs support secure communication using HTTPS. As a result of this enhancement all communication between the various EM entities (device to EMApp, EMApp to EMService, 3rd party App to EM Service) is encrypted. But to provide backward compatibility, devices that do not support secure communications could continue to communicate with EM by using HTTP.
Note
Changed APIs
All APIs support communication using HTTPS.
How Cisco Extension Mobility Works
This section describes what happens when your application sends a message to the Extension Mobility service to use its functionality.
Your login application submits an XML message to the EMService servlet by using the Hypertext Transfer Protocol (HTTP) or Hypertext Transfer Protocol Secure (HTTPS). The EMService uses the LDAP directory to check the UserID and PIN in the message from the login application. If the UserID and PIN are valid, the EMService executes the request by communicating with the database layer (DBL) through JNI. For more details about how the Extension Mobility module works, see the Device Profiles section that follows.
If the DBL changes the device profile for a login or logout request, it tells the DBL Monitor, which passes this information on to the CallProcessing and CTI components. CallProcessing, in turn, tells the Cisco Unified IP Phone that it needs to restart itself to load the new device profile. For more information about device profiles, see the Device Profiles.
The CTI layer notifies JTAPI and TAPI applications that are monitoring the device or the user that the application control list has changed.
If the DBL completes a transaction successfully the information is passed to the EMService. The EMService then sends an XML response that the transaction was successful to your login application by using HTTP or HTTPS.
If the transaction is not successful, the EMService sends your login application an appropriate error message.
Device Profiles
Device profiles act as the basic unit of transaction for the Cisco Extension Mobility service. A device profile contains all the configuration information, such as line appearances, speed dials, and services, for a particular device. You can think of it as a virtual device. It has all the properties of a device except physical characteristics such as a Media Access Control (MAC) address and a directory URL.
When a user logs in, the User device profile replaces the current device configuration. When a user logs out, the Logout device profile replaces the User device profile.
Cisco Extension Mobility requires a Logout Device Profile for each configured device. Cisco Extension Mobility uses the Logout Device Profile, which can be either the current device settings or the User Device Profile, as the logged out configuration of the device.
Note
Using the Cisco Extension Mobility API
The Cisco Extension Mobility service provides a fairly rich API, which enables extension mobility on Cisco Unified IP Phones and allows application control over authentication, scheduling, and availability.
An application that uses Cisco Extension Mobility service represents an IP phone service that allows a user to enter a userID and PIN at the phone itself and log in to the phone. The architecture and implementation of Cisco Extension Mobility make many other applications possible; some examples follow:
•
•
The Cisco Extension Mobility API gets exposed as an Extensible Markup Language (XML) interface via HTTP or HTTPS. The administrator of the system designates a website as the entry point to the API, and all requests and queries are made through those URLs. This website also provides the document type definitions (DTDs) that define the XML for requests, queries, and responses. This document includes the DTDs, along with examples.
The XML input gets submitted via an HTTP or HTTPS POST. A field named "xml" contains the XML string that defines the request or query. The response to this HTTP POST represents a pure XML response with either a success or failure indicator for a request or the response to a query.
Note
This section includes the following topics:
–
–
Set Up and Configuration
The Cisco Extension Mobility service application accompanies Unified CM. As such, all necessary Cisco Extension Mobility service API components are installed with the standard Unified CM installation.
To use the Cisco Extension Mobility service, create a device profile for the user who is logging in and for the target device. Use the following steps to configure Cisco Extension Mobility service:
•
•
•
•
•
•
•
(You must enable Cisco Extension Mobility on a device-by-device basis.)•
•
•
Note
For details on how to configure the User Device Profile, refer to the Cisco Unified Communications Manager Administration Guide or Cisco Unified Communications Manager Features and Services Guide.
Messages
You communicate between your login application and the Cisco Extension Mobility service by sending and receiving XML messages. The XML messages that you send must follow the rules that are set by the Message DTDs that are described in the Message Document Type Definitions.
The default URL for login and logout requests and system queries is
https://<server>:8443/emservice/EMServiceServlet
If the device does not support secure communication then URL for login and logout requests and system queries is:
http://<server>:8080/emservice/EMServiceServlet
The application sends authentication information, including an Application ID and an Application Certificate, at the start of message.
A password represents the only type of certificate that is currently supported. All messages must include a valid appID and appPassword, or they do not get processed. For examples of valid Cisco Extension Mobility messages, see the Message Examples.
Login Requests
Login requests provide the cornerstone of this service, and currently they offer the most flexible and complex message type. The information that is required to process a login request must include the device that is to be logged in to and the UserID of the user who is logging in to that device. If a device profile other than the default device profile that has been associated with the user is to be used, you can specify that profile name. If the system is to automatically log the user out after a particular time, you can also specify that. To log out, you only need to provide the device name in the message.
Logout All
The LogoutAll API enables the administrator to logout all extension mobility users who are currently logged in.
Note
Device-User Queries
A Device-User query represents a query wherein the login application specifies a list of one or more devices, and the system returns the userID of the user who is currently logged on to each device.
User-Devices Queries
A User-Devices query represents a query in which the login application specifies a list of one or more users, and the system returns the list of devices to which a particular user is currently logged in.
DeviceProfileQuery
The DeviceProfileQuery API gets information of all the device profiles associated to an user. The API response provides information about all the associated device profiles for an intra cluster user, that is end user in local DB, and also indicate if the profile is the default profile for the user.
Message Document Type Definitions
A Message Document Type Definition (DTD) designates an XML list that specifies precisely which elements can appear in a request, query, or response document. It also specifies the contents and attributes of the elements.
You communicate between your login application and the Cisco Extension Mobility service by sending and receiving XML documents. These XML documents must follow the rules that the Message DTDs set. For examples of how Message DTDs are used, see the Message Examples.
Request DTD
The Request DTD defines the login and logout messages that your application can send to the Cisco Exchange Mobility service.
<!-- login requests DTD --><!ELEMENT request (appInfo, (login | logout | logoutAll))><!ELEMENT appInfo (appID, (appCertificate | appEncryptedCertificate))><!ELEMENT appID (#PCDATA)><!ELEMENT appCertificate (#PCDATA)><!ELEMENT appEncryptedCertificate (#PCDATA)><!ELEMENT login (deviceName, userID, deviceProfile?, exclusiveDuration?, remoteIPAddr?, isViaHeaderSet?)><!ELEMENT logout (deviceName, remoteIPAddr?, isViaHeaderSet?)><!ELEMENT logoutAll (remoteIPAddr?, isViaHeaderSet?)><!ELEMENT deviceName (#PCDATA)><!ELEMENT userID (#PCDATA)><!ELEMENT deviceProfile (#PCDATA)><!ELEMENT remoteIPAddr (#PCDATA)><!ELEMENT isViaHeaderSet (#PCDATA)><!ELEMENT exclusiveDuration (time | indefinite)><!ELEMENT time (#PCDATA)><!ELEMENT indefinite EMPTY>Login or Logout Response DTD
Login or Logout Response DTD defines the messages that your application receives from the Cisco Extension Mobility service when it sends a login or logout request message.
<!-- login response DTD --><!ELEMENT response (success | failure)><!ELEMENT success EMPTY><!ELEMENT failure (error)><!ELEMENT error (#PCDATA)><!ATTLIST error code NMTOKEN #REQUIRED>
Note
•
–
–
Query DTD
The Query DTD defines the Device-User and User-Devices messages that your application sends the Cisco Extension Mobility service to find out which user is logged in to a device or to which devices users are logged in.
<!-- login query DTD --><!ELEMENT query (appInfo, (deviceUserQuery | userDevicesQuery | checkUser | deviceProfileQuery))><!ELEMENT appInfo (appID, (appCertificate | appEncryptedCertificate))><!ELEMENT appID (#PCDATA)><!ELEMENT appCertificate (#PCDATA)><!ELEMENT appEncryptedCertificate (#PCDATA)><!ELEMENT deviceUserQuery (deviceName+,remoteIPAddr?)><!ELEMENT userDevicesQuery (userID+,remoteIPAddr?)><!ELEMENT checkUser (userID+,remoteIPAddr?,isViaHeaderSet?)><!ELEMENT deviceProfileQuery (userID+,remoteIPAddr?,isViaHeaderSet?)><!ELEMENT deviceName (#PCDATA)><!ELEMENT userID (#PCDATA)><!ELEMENT remoteIPAddr (#PCDATA)><!ELEMENT isViaHeaderSet (#PCDATA)>Query Response DTD
The Query Response DTD defines the messages that your application receives from the Cisco Extension Mobility service when it sends the service a Device-User or User-Devices query.
<!-- login query results DTD --><!ELEMENT response (deviceUserResults | userDevicesResults | deviceProfileResults| failure)><!ELEMENT deviceUserResults (device+)><!ELEMENT userDevicesResults (user+)><!ELEMENT deviceProfileResults (userID+)><!ELEMENT device (userID | lastlogin | none | doesNotExist)><!ATTLIST devicename NMTOKEN #REQUIRED><!ELEMENT user (deviceName+ | none | doesNotExist)><!ATTLIST userid NMTOKEN #REQUIRED><!ELEMENT userID (#PCDATA)><!ELEMENT lastlogin (#PCDATA)><!ELEMENT deviceName (#PCDATA)><!ELEMENT none EMPTY><!ELEMENT doesNotExist EMPTY><!ELEMENT failure (errorMessage)><!ELEMENT errorMessage (#PCDATA)>Message Examples
This section provides examples of various types of messages to aid in understanding how to use the message DTDs to communicate between your login application and the Cisco Extension Mobility service.
Login Operation
The Login operation logs in a single user using the specified device profile.
Sample Login Code
The following example logs in userID "john" to device SEP003094C25B15 using the User Device Profile UserDevProf:
<request><appInfo><appID>appid</appID><appCertificate>apppasswd</appCertificate></appInfo><login><deviceName>SEP003094C25B15</deviceName><userID>john</userID><deviceProfile>UserDevProf</deviceProfile><exclusiveDuration><time>60</time></exclusiveDuration></login></request>Success Response
<response><success/></response>Failure Response
<response><failure><error code="3">Could not authenticate 'appid'</error></failure></response>Logout Operation
The Logout operation logs out a single user from the specified device.
Sample Logout Code
The following example logs out a user who is logged into device SEP003094C25B15:
<request><appInfo><appID>appid</appID><appCertificate>apppasswd</appCertificate></appInfo><logout><deviceName>SEP003094C25B15</deviceName></logout></request>Success Response
<response><success/></response>Failure Response
<response><failure><error code="3">Could not authenticate 'appid'</error></failure></response>LogoutAll Operation
The LogoutAll operation logs out all the users from the device.
Sample LogoutAll Request
<request><appInfo><appID>appid</appID><appCertificate>apppasswd</appCertificate></appInfo><logout><deviceName>SEP003094C25B15</deviceName></logout></request>Sample LogoutALL Response
<request><appInfo><appID>appid</appID><appCertificate>apppasswd</appCertificate></appInfo><logoutAll></logoutAll></request>UserQuery Operation
The UserQuery operation returns the user ID that is logged in to the specified device.
Sample UserQuery Request
The following example finds the user who is logged in to the device SEP003094C25B15:
<query><appInfo><appID>appid</appID><appCertificate>apppasswd</appCertificate></appInfo><deviceUserQuery><deviceName>SEP003094C25B15</deviceName></deviceUserQuery></query>Sample UserQuery Response
If you log in to the phone for the first time, the response is as follows:
<response><deviceUserResults><device name="SEP00016CEA6616"><userID>one</userID><none/></device></deviceUserResults></response>If you have previously logged in to the phone, the response is as follows:
<response><deviceUserResults><device name="SEP......"><userID>one</userID><lastlogin>one</lastlogin></device></deviceUserResults></response>DeviceQuery Operation
The DeviceQuery operation returns all device IDs (MAC addresses) for the specified user ID.
Sample DeviceQuery Request
The following example finds the devices that user ID "john" is logged in to:
<query><appInfo><appID>appid</appID><appCertificate>apppasswd</appCertificate></appInfo><userDevicesQuery><userID>john</userID></userDevicesQuery></query>Sample DeviceQuery Response
<response><userDevicesResults><user id="rknotts"><deviceName>SEP003094C25B15</deviceName><deviceName>SEP003094C25B49</deviceName></user><user id="fwragge"><deviceName>SEP003094C249A6</deviceName></user></userDeviceResults></response>Device Profile Query
The DeviceProfileQuery API gets information of all the device profiles associated to an user.
Sample Device Profile Query Request
<query><appInfo><appID>appid</appID><appCertificate>apppasswd</appCertificate></appInfo><userDeviceProfileQuery><userID>john</userID></userDeviceProfileQuery></query>Sample DeviceProfile Query Response
<results><deviceProfileResults><user id="john"><deviceProfileName>UDP1</deviceProfileName><deviceProfileName>UDP2</deviceProfileName></user></deviceProfileResults></results>Extension Mobility Service Response Codes
Table 4-2 describes the response codes and messages that can be returned by the Extension Mobility service. A response contains a code and a response string, formatted as an XML string.
