Feedback
Table Of Contents
Cisco Extension Mobility Service API
Cisco Extension Mobility Architecture
Cisco Extension Mobility Service Components
How Cisco Extension Mobility Works
Cisco Extension Mobility Service Module
Using the Cisco Extension Mobility API
Cisco Extension Mobility Rearchitecture
ExtensionMobilityDynamic Table
CTI Requirements for Call Processing
EMApp and EMService Requirements
AXL SOAP Database Requirements
Message Document Type Definitions
Application and Service Error Codes
Cisco Extension Mobility Service API
The Cisco Extension Mobility service, a feature of Cisco Unified Communications Manager, 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. Cisco Unified Communications Manager 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 Cisco Unified Communications Manager 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 Cisco Unified Communications Manager 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:
•
Cisco Extension Mobility Architecture
•
•
•
Cisco Extension Mobility Architecture
This section explains the Cisco Extension Mobility service components and how they work with your application. Figure 3-1 provides a functional diagram of the different Cisco Extension Mobility modules that is followed by a brief description of each module.
Figure 3-1 Cisco Extension Mobility Functional Diagram
Cisco Extension Mobility Service Components
The Cisco Extension Mobility service comprises three basic architectural components. The following paragraphs provide a brief description of each component:
•
•
•
The Cisco Extension Mobility service comprises your application, the EMApp module, the EMService module, the Database Layer (DBL), and the ancillary items that are listed in Table 3-1.
How Cisco Extension Mobility Works
This section describes what happens when your application sends a message to the EMService to use Cisco Extension Mobility functionality.
Figure 3-1 also illustrates how the Cisco Extension Mobility components communicate with each other. The high-level message flow between different Cisco Extension Mobility components remains the same as in previous releases.
Your login application submits an XML message to the EMService servlet by using the Hypertext Transfer Protocol (HTTP). 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 EMService module works, see the "Cisco Extension Mobility Service Module" 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" section.
The CTI layer notifies JTAPI and TAPI applications that are monitoring the device or user that the application control list has changed.
If the DBL completes a transaction successfully, it tells the EMService. The EMService then sends an XML response that the transaction was successful to your login application by using HTTP.
If the transaction is not successful, the EMService sends your login application an appropriate error message.
Cisco Extension Mobility Service Module
Your login application communicates with the Cisco Extension Mobility service through the Cisco Extension Mobility Service (EMService) component.
Only a single user can log in at a time on a particular device. Subsequent attempts by users to log in on a device before the previous user has logged out will fail. You also cannot log out of a device to which no user is currently logged in. These conditions generate error messages.
When the EMService component receives an HTML message from your login application, it uses HTTP to send an XML response message. The response to a request serves as success or failure message, and the response to a query serves as a query result message.
For more detailed information about these messages, see Messages
Figure 3-2 illustrates more details of the operation of the EMService module.
Figure 3-2 Cisco Extension Mobility EMService Module
The EMService component sends an appropriate XML error response to your login application if
•
•
•
•
Authentication
The Cisco Extension Mobility service allows authentication by proxy. That is, a user with Cisco Extension Mobility proxy rights can log in any user to any device.
What this means is that an application can be responsible for authenticating a user in whatever way that the designer of the application sees fit: by using a password, PIN, hardware key, biometrics, and so on. The application must provide valid credentials for itself, so the Cisco Extension Mobility Service knows the application is provisioned in the system and allowed to log users in and out.
To this end, you must ensure that a special user that corresponds to the application is configured in the Directory. This user, representing the application, has a standard LDAP UserID and PIN. The application must send a valid UserID and PIN to log a user in or log out from a device.
Note
Preconditions
The EMService Java Object Policy Validation engine checks the preconditions.
Only a single user can log in at a time on a particular device. Subsequent attempts by users to log in on a device before the previous user has logged out will fail. You also cannot log out of a device to which no user is currently logged in. These conditions generate error messages.
Automatic Logout
The Logout Scheduler in the EMService module times all login occurrences if you have specified a system maximum login time. If you have not set the login duration, the automatic logout period for that device defaults to the system maximum time.
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 an Auto-Generated or User Device Profile, as the "logged out" configuration of the device.
Two types of device profiles exist: Auto-Generated device profiles and User device profiles:
•
•
Note
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. 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 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:
•
–
–
New and Changed Information
Cisco Unified Communications Manager New and Changed Information Guide for Release 6.0(1) describes new features and or changes that are pertinent to the Cisco Extension Mobility Service in Cisco Unified Communications Manager Release 6.0(1).
Cisco Extension Mobility Rearchitecture
This section describes new features that allow Cisco Extension Mobility login/logout to complete successfully when connectivity to the publisher server is lost. Cisco Extension Mobility will now work when the publisher server is not available. The Cisco Extension Mobility rearchitecture has a positive impact on the number of Cisco Extension Mobility logins/logouts per hour.
Modifications to the Cisco Extension Mobility architecture mean that it can support the Call Processing User Facing feature architecture. These new features do not cause any changes in end point behavior.
Feature Description
The current Cisco Extension Mobility architecture requires a database update operation on the Device table, and, depending on Administrative provisioning, multiple database delete and database insert operations might be required for the following database tables:
•
•
•
•
•
•
To support database resiliency, some fields have been moved to their own tables, so they can be updated locally and replicated in a fully meshed topology. This change will break direct SQL database access by using the AXL SOAP/XML Layer for fields in columns that moved from one table to another.
The new Cisco Extension Mobility architecture provides some performance improvement over the previous release because it requires only a single database update operation on the new ExtensionMobilityDynamic table, which increases performance by reducing database stored procedure complexity in favor of increased application complexity.
Note
Cisco Unified Communications Manager adjusts database access to account for the information now available in the new ExtensionMobilityDynamic table. The Cisco Unified Communications Manager Data Dictionary for Release 6.0(1) contains a comparison of the database schema between version 6.0(1) and earlier releases.
The performance enhancements in Cisco Extension Mobility resolve the following defects:
•
•
ExtensionMobilityDynamic Table
The Cisco Extension Mobility rearchitecture requires the creation of a new simple table that supports simple timestamp conflict resolution and is writable on all nodes in the system. Table 3-2 illustrates the columns in this new table, ExtensionMobiltyDynamic.
Table 3-2 ExtensionMobilityDynamic Table
Pkid
char(36)
No
newid()
fkdevice
char(36)
No
None
fkenduser
char(36)
Yes
NULL
logintime
integer
Yes
NULL
loginduration
integer
Yes
NULL
fkdevice_currentloginprofile1
char(36)
Yes
NULL
Yes
fkenduser_lastlogin
char(36)
Yes
NULL
fkPhoneTemplate
char(36)
Yes
NULL
Yes
fkSoftkeyTemplate
char(36)
Yes
NULL
Yes
tkUserLocale
integer
Yes
NULL
Yes
UserHoldMOHAudioSourceID
integer
Yes
NULL
tkStatus_MLPPIndicationStatus
integer
No
0
Yes
tkPreemption
integer
No
2
Yes
ignorePI
boolean
No
False
allowCTIControlFlag
boolean
No
False
fkCallingSearchspace_restrict
char(36)
Yes
NULL
fkMatrix_Presence
char(36)
Yes
NULL
fkMLPPDomain
char(36)
Yes
NULL
Yes
ctiidBase2
integer
No
0
lastNumPlanIndex2
integer
Yes3
0
Yes
misMatchedLogin)2
boolean
No
False
Yes
versionstamp2
varchar(47,0)
No
see note4
Yes
1 Name changed from ikdevice_currentloginprofile to fkdevice_currentloginprofile, as per the database naming conventions.
2 This is a new field.
3 Highest numplanindex for DNs that are associated with this EM login
4 0000000000-c7a6c673-7479-46b0-839e-014d3d093963
An application can determine whether a Cisco Extension Mobility login is active on a device by testing the following conditions:
•
•
•
An application can determine whether a Cisco Extension Mobility logout is active on a device by testing the following conditions:
•
•
•
An application can determine whether neither Cisco Extension Mobility login or logout is active on a device by testing the following conditions:
•
•
•
Call-Processing Requirements
Call Processing uses the new ExtensionMobilityDynamic table to properly configure the device on Device reset, registration, or change notification. Cisco Unified Communications Manager registers for change notification on the ExtensionMobilityDynamic table and updates any internally cached information as required.
All the call-processing requirements that are described here assume that the device is enabled for Cisco Extension Mobility; that is, the Device.allowhotelingflag = `t', (TRUE).
Upon Device reset, registration, or change notification:
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
•
•
–
•
•
•
•
•
•
–
Be aware that this is required because the Administrator cannot provision special load information on a Device Profile.
–
•
•
•
If the login model does not support Ring Setting, Cisco Unified Communications Manager overwrites the RingSetting configuration to be disabled.
CTI Requirements for Call Processing
Cisco Unified Communications Manager continues to provide the same information in CtiDeviceRegister Notify and CtiDeviceUnregisterNotify upon Device reset, registration, and Extensiion Mobility login/logout.
Database Requirements
The following database requirements result from the Cisco Extension Mobility rearchitecture:
•
The system applies the same Cisco Extension Mobility business rules for the columns that moved from the Device table to the ExtensionMobilityDynamic table: Device.fkenduser_lastlogin , Device.logintime, Device.loginduration, Device.ikdevice_defaultprofile, and Device.ikdevice_currentloginprofile.
The updated reset stored procedures account for the new information that is stored in the ExtensionMobilityDynamic table.
•
•
•
All automatically generated Device Profiles get deleted during an L2 or W1.
•
•
•
–
–
–
–
–
–
–
•
–
–
–
•
–
–
–
–
–
•
•
TFTP Requirements
See the "TFTP Impacted" column in Table 3-2 for the columns in the ExtensionMobilityDynamic table that apply to TFTP, if TFTP is involved with the device that is undergoing Cisco Extension Mobility login or logout. During Cisco Extension Mobility login or logout to one of these devices, TFTP uses all the requirements from the "Call-Processing Requirements" section that are relevant to TFTP.
EMApp and EMService Requirements
EMApp and EMService requirements assume that no design change is required to work with the Cisco Extension Mobility rearchitecture. The only significant change requires that you query the table ExtensionMobilityDynamic instead of the Device table or EndUser table.
EMApp needs to figure out the login/logout status and also the last logged in user information. You now obtain these two pieces of information from the ExtensionMobilityDynamic table.
EMService does policy validation, gets device information, and selects all devices where the user has logged in. You now must query the ExtensionMobilityDynamic table to obtain this information. Also, EMAPI that is exposed by this component needs to update and query the ExtensionMobilityDynamic table.
Administration Requirements
The Administration Requirements assume that Cisco Extension Mobility is enabled on the current device.
After a Cisco Extension Mobility login
•
After a Cisco Extension Mobility logout
•
•
Administration provides a Current Configuration button, which displays the current configuration of the device after a Cisco Extension Mobility login or logout when ExtensionMobilityDynamic.fkdevice_currentdeviceprofile is non-NULL.
Administration groups the Cisco Extension Mobility impact attributes into the Cisco Extension Mobility section on the Phone Configuration Page and, if a user is currently logged in, indicates that the configuration change for the attributes under the Cisco Extension Mobility section will not take effect until the user logs out.
Administration Use Case
For a device that has a Cisco Extension Mobility login that is currently active or a Cisco Extension Mobility Logout Profile that is not active, Administration displays "--- Use Current Device Settings ---." The settings that display on the device window still reflect the device settings and not the operational settings of the device because the database tables have not been modified.
Administration now provides a link to the current EndUser Profile and the current Device Profile.
•
•
•
CTI Requirements
The following paragraphs summarize the changes that have been made in CTI.
•
•
•
•
•
–
–
–
–
–
–
CTI Use Case
From an application perspective, the functionality remains the same.
AXL SOAP Database Requirements
To allow Cisco Extension Mobility to become a CallProcessing User Facing Feature that is writable locally, required schema changes necessitate movement of columns from one table to another. Thus, this means that applications that employ direct SQL access to the database are not compatible with release 6.0(1). The Cisco Unified Communications Manager Data Dictionary, Release 6.0(1) documents all schema changes from releases 4.2 and 5.0. Tables and columns identified as present in release 4.2 or 5.0 and removed from release 6.0 are the columns where backward compatibility is broken.
AXL maintains backward compatibility in the APIs that do not use direct SQL access. AXL accesses the publisher database server specifically, instead of the local database.
CCMCIP
CCMCIP adjusts database access to account for information that is available in the ExtensionMobilityDynamic table for service button. When a user is logged in to the device, instead of retrieving the TelecasterSubscriberService records that are associated with the login device, CCMCIP retrieves the TelecasterSubscribedService records that are associated with the current login device profile.
Feature Interactions
Cisco Extension Mobility interacts with the Privacy and Do Not Disturb (DND) features.
Cisco Extension Mobility interacts with the Privacy feature as each Device Profile has a record associated with it in the DevicePrivacyDynamic table. When a Device Profile is in use and supports Privacy, updating the Privacy status will modify the record that is associated with the Device Profile and not the record that is associated with the Device.
Cisco Extension Mobility and the DND feature interact as each Device Profile has a record that is associated with it in the DNDDynamic table. When a Device Profile is in use and supports DND, updating the DND status will modify the record that is associated with the Device Profile and not the record that is associated with the Device.
Configuration
The Cisco Extension Mobility service application accompanies Cisco Unified Communications Manager. As such, all necessary Cisco Extension Mobility service API components get installed with the standard Cisco Unified Communications Manager 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" section.
The default 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" section.
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.
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.
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" section.
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))><!ELEMENT appInfo (appID, appCertificate)><!ELEMENT appID (#PCDATA)><!ELEMENT appCertificate (#PCDATA)><!ELEMENT login (deviceName, userID, deviceProfile?, exclusiveDuration?)><!ELEMENT logout (deviceName)><!ELEMENT deviceName (#PCDATA)><!ELEMENT userID (#PCDATA)><!ELEMENT deviceProfile (#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 errorcode NMTOKEN #REQUIRED>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))><!ELEMENT appInfo (appID, appCertificate)><!ELEMENT appID (#PCDATA)><!ELEMENT appCertificate (#PCDATA)><!ELEMENT deviceUserQuery (deviceName+)><!ELEMENT userDevicesQuery (userID+)><!ELEMENT deviceName (#PCDATA)><!ELEMENT userID (#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 | failure)><!ELEMENT deviceUserResults (device+)><!ELEMENT userDevicesResults (user+)><!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. Table 3-3 lists each example type, a description of the example, and a reference to the example.
Request Examples
Request examples demonstrate three different login requests and one logout request. The login requests show a simple login message and two messages that specify options like using a particular device profile or setting a login duration.
Example 3-1 Simple Login Request
<request><appInfo><appID>7960LoginApp</appID><appCertificate>password</appCertificate></appInfo><login><deviceName>SEP003094C25B15</deviceName><userID>rknotts</userID></login></request>Example 3-2 Login Request That Specifies a Profile and a Time Restriction
<request><appInfo><appID>WebLoginApp</appID><appCertificate>password</appCertificate></appInfo><login><deviceName>SEP003094C25B15</deviceName><userID>rknotts</userID><deviceProfile>RyanTravelPhone</deviceProfile><exclusiveDuration><time>60</time></exclusiveDuration></login></request>Example 3-3 Login Request That Specifies an Unlimited Duration
<request><appInfo><appID>WebLoginApp</appID><appCertificate>password</appCertificate></appInfo><login><deviceName>SEP003094C25B15</deviceName><userID>rknotts</userID><exclusiveDuration><indefinite/></exclusiveDuration></login></request>Example 3-4 Logout Request
<request><appInfo><appID>7960LoginApp</appID><appCertificate>password</appCertificate></appInfo><logout><deviceName>SEP003094C25B15</deviceName></logout></request>Request Response Examples
The request response examples show a success message (for either login or logout) and a failure message that indicates the type of error that the login or logout attempt generated.
Example 3-5 Success Response
<response><success/></response>Example 3-6 Failure Response
<response><failure><error code="3">Could not authenticate 'appid'</error></failure></response>Query Examples
Query examples show a typical Device-User Query message and a typical User-Devices Query message that an application sent to the Cisco Extension Mobility service.
Example 3-7 Device-User Query
<query><appInfo><appID>applicationName</appID><appCertificate>password</appCertificate></appInfo><deviceUserQuery><deviceName>SEP003094C25B15</deviceName></deviceUserQuery></query>Example 3-8 User-Devices Query
<query><appInfo><appID>applicationName</appID><appCertificate>password</appCertificate></appInfo><userDevicesQuery><userID>rknotts</userID><userID>fwragge</userID></userDevicesQuery></query>Query Response Examples
Query Response examples show messages that the Cisco Extension Mobility service sends to the login application after the login application has sent a Device-User query message or a User-Devices query message.
Example 3-9 Device-User 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>Example 3-10 User-Devices Response
<userDevicesResults><user id="rknotts"><deviceName>SEP003094C25B15</deviceName><deviceName>SEP003094C25B49</deviceName></user><user id="fwragge"><deviceName>SEP003094C249A6</deviceName></user></userDeviceResults></results>Application and Service Error Codes
Table 3-4 shows the new error codes the Cisco Extension Mobility Application module returns as well as the error code numbers for the previous release, and describes what each error code means.
Table 3-5 shows the current (new) error codes that the Cisco Extension Mobility Service module returns as well as the error code numbers for the previous release, and describes what each error code means. Shaded rows in this table represent error codes that are no longer used.
