Overview
The RisPort70 (Real-Time Information Port) service provides an API for querying the current connection status of phones, devices, and applications connected to Cisco Unified Communications Manager (Unified CM). Details provided by RisPort70 include last known connection and registration state, IP address, and model information. The API provides queries, for example by name, for single device or application instances, and wildcard queries which return the status of multiple devices at once.
The RisPort70 API allows clients to:
- Query Cisco Unified CM for the status and details of phones and other telephony devices
- Query Cisco Unified CM for the status and details of CTI applications
Use the RisPort70 WSDL:
https://<server>:8443/realtimeservice2/services/RISService70?wsdl
Deprecated Methods
The RisPort WSDL is deprecated. Use the RisPort70 WSDL.
RisPort70 SelectCmDevice
This method allows clients to perform Cisco Unified CM device-related queries. The method returns a snapshot of real-time device registration status from each Cisco Unified CM node. The data includes registration status, IP address, model info, and CTI application connections to the device. A single device may appear in multiple elements if the device has registered to multiple nodes. Devices may be requested by wildcard using an asterisk, *
.
SelectCmDevice Request Format
<!--RisPort70 API - SelectCmDevice - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
<soapenv:Header/>
<soapenv:Body>
<soap:selectCmDevice>
<soap:StateInfo></soap:StateInfo>
<soap:CmSelectionCriteria>
<soap:MaxReturnedDevices>1000</soap:MaxReturnedDevices>
<soap:DeviceClass>Any</soap:DeviceClass>
<soap:Model>255</soap:Model>
<soap:Status>Any</soap:Status>
<soap:NodeName></soap:NodeName>
<soap:SelectBy>DirNumber</soap:SelectBy>
<soap:SelectItems>
<!--Zero or more repetitions:-->
<soap:item>
<soap:Item>6961</soap:Item>
</soap:item>
</soap:SelectItems>
<soap:Protocol>Any</soap:Protocol>
<soap:DownloadStatus>Any</soap:DownloadStatus>
</soap:CmSelectionCriteria>
</soap:selectCmDevice>
</soapenv:Body>
</soapenv:Envelope>
Parameter | Description |
---|---|
StateInfo | The StateInfo string as returned by a previous execution of the current query. Refer to the StateInfo Usage section. |
CmSelectionCriteria | A Cisco Unified CM Selection criteria. |
MaxReturnedDevices | The maximum number of devices to return. The maximum parameter value is 1000 |
DeviceClass | The device class to query for real-time status. Device classes include:
|
Model | The parameter value refers to the Cisco Unified CM internal model number of a particular device or 255 for "any model." Click here for an example listing of model numbers. The complete list of available model numbers is stored in the Cisco Unified CM 'typemodel' database table. |
Status | Allows device searches by status (or state):
|
NodeName | The UC Manager node name to query. If no NodeName is given, all nodes in the cluster are queried. |
SelectBy | Search by:
|
SelectItems | An array of one or more item elements, which may include names, IP addresses, or directory numbers, depending on the SelectBy parameter. The item value can include a * to return wildcard matches. |
Protocol | Search by device protocol:
|
DownloadStatus | Use this parameter to search for devices that may be in the process of upgrading their internal firmware. It is possible to identify devices that are currently in the process of upgrading or have failed to upgrade using this parameter. The parameter choices are:
|
Enum | Model |
---|---|
1 | Cisco 30 SP+ |
2 | Cisco 12 SP+ |
3 | Cisco 12 SP |
4 | Cisco 12 S |
5 | Cisco 30 VIP |
6 | Cisco 7910 |
7 | Cisco 7960 |
8 | Cisco 7940 |
9 | Cisco 7935 |
10 | Cisco VGC Phone |
11 | Cisco VGC Virtual Phone |
12 | Cisco ATA 186 |
15 | EMCC Base Phone |
20 | SCCP Phone |
30 | Analog Access |
40 | Digital Access |
42 | Digital Access+ |
43 | Digital Access WS-X6608 |
47 | Analog Access WS-X6624 |
48 | VGC Gateway |
50 | Conference Bridge |
51 | Conference Bridge WS-X6608 |
52 | Cisco IOS Conference Bridge (HDV2) |
53 | Cisco Conference Bridge (WS-SVC-CMM) |
61 | H.323 Phone |
62 | H.323 Gateway |
70 | Music On Hold |
71 | Device Pilot |
72 | CTI Port |
73 | CTI Route Point |
80 | Voice Mail Port |
83 | Cisco IOS Software Media Termination Point (HDV2) |
84 | Cisco Media Server (WS-SVC-CMM-MS) |
85 | Cisco Video Conference Bridge (IPVC-35xx) |
86 | Cisco IOS Heterogeneous Video Conference Bridge |
87 | Cisco IOS Guaranteed Audio Video Conference Bridge |
88 | Cisco IOS Homogeneous Video Conference Bridge |
90 | Route List |
100 | Load Simulator |
110 | Media Termination Point |
111 | Media Termination Point Hardware |
112 | Cisco IOS Media Termination Point (HDV2) |
113 | Cisco Media Termination Point (WS-SVC-CMM) |
115 | Cisco 7941 |
119 | Cisco 7971 |
120 | MGCP Station |
121 | MGCP Trunk |
122 | GateKeeper |
124 | 7914 14-Button Line Expansion Module |
125 | Trunk |
126 | Tone Announcement Player |
131 | SIP Trunk |
132 | SIP Gateway |
133 | WSM Trunk |
134 | Remote Destination Profile |
227 | 7915 12-Button Line Expansion Module |
228 | 7915 24-Button Line Expansion Module |
229 | 7916 12-Button Line Expansion Module |
230 | 7916 24-Button Line Expansion Module |
232 | CKEM 36-Button Line Expansion Module |
253 | SPA8800 |
254 | Unknown MGCP Gateway |
255 | Unknown |
302 | Cisco 7985 |
307 | Cisco 7911 |
308 | Cisco 7961G-GE |
309 | Cisco 7941G-GE |
335 | Motorola CN622 |
336 | Third-party SIP Device (Basic) |
348 | Cisco 7931 |
358 | Cisco Unified Personal Communicator |
365 | Cisco 7921 |
369 | Cisco 7906 |
374 | Third-party SIP Device (Advanced) |
375 | Cisco TelePresence |
376 | Nokia S60 |
404 | Cisco 7962 |
412 | Cisco 3951 |
431 | Cisco 7937 |
434 | Cisco 7942 |
435 | Cisco 7945 |
436 | Cisco 7965 |
437 | Cisco 7975 |
446 | Cisco 3911 |
468 | Cisco Unified Mobile Communicator |
478 | Cisco TelePresence 1000 |
479 | Cisco TelePresence 3000 |
480 | Cisco TelePresence 3200 |
481 | Cisco TelePresence 500-37 |
484 | Cisco 7925 |
486 | Syn-Apps Virtual Phone |
493 | Cisco 9971 |
495 | Cisco 6921 |
496 | Cisco 6941 |
497 | Cisco 6961 |
503 | Cisco Unified Client Services Framework |
505 | Cisco TelePresence 1300-65 |
520 | Cisco TelePresence 1100 |
521 | Transnova S3 |
522 | BlackBerry MVS VoWifi |
527 | IPTrade TAD |
537 | Cisco 9951 |
540 | Cisco 8961 |
547 | Cisco 6901 |
548 | Cisco 6911 |
550 | Cisco ATA 187 |
557 | Cisco TelePresence 200 |
558 | Cisco TelePresence 400 |
562 | Cisco Dual Mode for iPhone |
564 | Cisco 6945 |
575 | Cisco Dual Mode for Android |
577 | Cisco 7926 |
580 | Cisco E20 |
582 | Generic Single Screen Room System |
583 | Generic Multiple Screen Room System |
584 | Cisco TelePresence EX90 |
585 | Cisco 8945 |
586 | Cisco 8941 |
588 | Generic Desktop Video Endpoint |
590 | Cisco TelePresence 500-32 |
591 | Cisco TelePresence 1300-47 |
592 | Cisco 3905 |
593 | Cisco Cius |
594 | VKEM 36-Button Line Expansion Module |
596 | Cisco TelePresence TX1310-65 |
597 | Cisco TelePresence MCU |
598 | Ascom IP-DECT Device |
599 | Cisco TelePresence Exchange System |
604 | Cisco TelePresence EX60 |
606 | Cisco TelePresence Codec C90 |
607 | Cisco TelePresence Codec C60 |
608 | Cisco TelePresence Codec C40 |
609 | Cisco TelePresence Quick Set C20 |
610 | Cisco TelePresence Profile 42 (C20) |
611 | Cisco TelePresence Profile 42 (C60) |
612 | Cisco TelePresence Profile 52 (C40) |
613 | Cisco TelePresence Profile 52 (C60) |
614 | Cisco TelePresence Profile 52 Dual (C60) |
615 | Cisco TelePresence Profile 65 (C60) |
616 | Cisco TelePresence Profile 65 Dual (C90) |
617 | Cisco TelePresence MX200 |
619 | Cisco TelePresence TX9000 |
621 | Cisco 7821 |
620 | Cisco TelePresence TX9200 |
622 | Cisco 7841 |
623 | Cisco 7861 |
626 | Cisco TelePresence SX20 |
627 | Cisco TelePresence MX300 |
628 | IMS-integrated Mobile (Basic) |
631 | Third-party AS-SIP Endpoint |
632 | Cisco Cius SP |
633 | Cisco TelePresence Profile 42 (C40) |
634 | Cisco VXC 6215 |
635 | CTI Remote Device |
640 | Usage Profile |
642 | Carrier-integrated Mobile |
645 | Universal Device Template |
647 | Cisco DX650 |
648 | Cisco Unified Communications for RTX |
652 | Cisco Jabber for Tablet |
659 | Cisco 8831 |
682 | Cisco TelePresence SX10 |
683 | Cisco 8841 |
684 | Cisco 8851 |
685 | Cisco 8861 |
688 | Cisco TelePresence SX80 |
689 | Cisco TelePresence MX200 G2 |
690 | Cisco TelePresence MX300 G2 |
20000 | Cisco 7905 |
30002 | Cisco 7920 |
30006 | Cisco 7970 |
30007 | Cisco 7912 |
30008 | Cisco 7902 |
30016 | Cisco IP Communicator |
30018 | Cisco 7961 |
30019 | Cisco 7936 |
30027 | Analog Phone |
30028 | ISDN BRI Phone |
30032 | SCCP gateway virtual phone |
30035 | IP-STE |
36041 | Cisco TelePresence Conductor |
36042 | Cisco DX80 |
36043 | Cisco DX70 |
36049 | BEKEM 36-Button Line Expansion Module |
36207 | Cisco TelePresence MX700 |
36208 | Cisco TelePresence MX800 |
<!-- Example: -->
<ns1:StateInfo><StateInfo ClusterWide="1"><Node Name="DS-UCM105" SubsystemStartTime="1412580217" StateId="61" TotalItemsFound="1" TotalItemsReturned="1"/></StateInfo></ns1:StateInfo>
<!-- Example: -->
<ns1:SelectCmDeviceResult>
<ns1:TotalDevicesFound>0</ns1:TotalDevicesFound>
<ns1:CmNodes>
<ns1:item>
<ns1:ReturnCode>Ok</ns1:ReturnCode>
<ns1:Name>DS-UCM105</ns1:Name>
<ns1:NoChange>true</ns1:NoChange>
<ns1:CmDevices xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</ns1:item>
</ns1:CmNodes>
</ns1:SelectCmDeviceResult>
The StateInfo
feature is an optional mechanism for applications to receive full RisPort70 data updates only if the state of one or more devices returned by a previous, identical query changed. This can reduce RisPort70 and application-side processing impact when queries are large and device state changes are infrequent. Benefits are improved performance and request latency which allows applications to poll for state changes more frequently.
How It Works
As part of each successful RisPort70 response, the StateInfo
field is populated with a string value representing an internal RisPort70 state. This StateInfo
value is specific to the parameters and timestamp of the query, and is a snapshot of the device state of all devices queried at the time of the request.
If an application performs a RisPort70 query identical to a previously executed query, it may provide the associated StateInfo
string in the request. RisPort70 will then compare the previous RisPort70 state snapshot with the current device states, and determine if they exactly match. If the state of all devices is unchanged, RisPort70 returns a response with TotalDevicesFound
= 0 and NoChange
= true.
If any of the devices have changed state, then the standard RisPort70 response will be provided, including full state data for all queried devices. An updated StateInfo
value represents the new state snapshot.
Using RisPort70 With Bulk Requests
Applications using RisPort70 to perform queries on large numbers of devices, for example in order to update a devicename
to IP address
lookup table, need to balance:
- Request rate throttle (15 requests per minute maximum)
- The number of devices per request (up to 1000)
- The possibility of duplicate records (from
selectCmDevice
) - Truncated results if more than 1000 results returned
- Keeping device state information as up-to-date as possible
Obtain the right balance by testing and observation of Cisco Unified CM system performance, for example via the RTMT tool.
<!-- Example: Multiple `item` elements -->
<soap:SelectBy>Name</soap:SelectBy>
<soap:SelectItems>
<soap:item>
<soap:Item>IPCMRAEU5UCM5X7</soap:Item>
</soap:item>
<soap:item>
<soap:Item>IPCXYZAU4UCM4X3</soap:Item>
</soap:item>
</soap:SelectItems>
Applications can perform bulk query operations by providing multiple Item
elements in the SelectItems
list, see the XML code sample.
<!-- Example: wildcard, partial Name match -->
<soap:SelectBy>Name</soap:SelectBy>
<soap:SelectItems>
<soap:item>
<soap:Item>IPC*</soap:Item>
</soap:item>
</soap:SelectItems>
<!-- Example: wildcard, "all" Name match -->
<soap:SelectBy>Name</soap:SelectBy>
<soap:SelectItems>
<soap:item>
<soap:Item>*</soap:Item>
</soap:item>
</soap:SelectItems>
Or use the *
wildcard to return partial SelectItems
matches or "all" devices (not supported with selectCmDeviceExt
). See the XML code sample.
The application can specify the maximum number of results it is able to accept with MaxReturnedDevices.
However, the upper limit on returned results for RisPort70 itself is 1000. If the number of devices found by the query exceeds 1000, only the first 1000 results are returned.
Note: The RisPort70 response does not indicate if results greater than 1000 have been truncated.
In practice, wildcard queries should be used with care, as systems with greater than 1000 devices are common, and results truncation can occur. Applications may want to consider results with exactly 1000 results as truncated.
One approach to retrieving bulk RisPort70 data is to submit requests specifying multiple individual Item
elements in the request (see the XML example.) In this way an application can gather large collections of device names, for example 500 devices at a time, with good assurance of getting complete results.
Note: selectCmDevice
can return multiple results per unique device if a device has registered on more than one Cisco Unified CM node at some point, for example due to failover. selectCmDeviceExt
returns only the most recent result.
Applications can obtain device names individually or in bulk via the Cisco Unified CM AXL SOAP API, for example getPhone and listPhone.
RisPort70 Request Throttling
By default RisPort70 accepts up to 15 requests per minute, combined across all RisPort70 applications. Configure this maximum via the Cisco Unified CM Enterprise Parameter Allowed Device Queries Per Minute
, up to a limit of 15 requests per minute. If RisPort70 receives more requests in a minute than the current maximum, requests may fail with a SOAP fault error. It is recommend that applications pace requests, especially large ones, to correspond to a rate of approximately 15 per minute or the configured maximum value.
SelectCMDevice Response Format
<!--RisPort70 API - SelectCmDevice - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns1:selectCmDeviceResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
<ns1:selectCmDeviceReturn>
<ns1:SelectCmDeviceResult>
<ns1:TotalDevicesFound>1</ns1:TotalDevicesFound>
<ns1:CmNodes>
<ns1:item>
<ns1:ReturnCode>Ok</ns1:ReturnCode>
<ns1:Name>cucm3</ns1:Name>
<ns1:NoChange>false</ns1:NoChange>
<ns1:CmDevices>
<ns1:item>
<ns1:Name>SEPE8B7480316D6</ns1:Name>
<ns1:DirNumber>6961-Registered</ns1:DirNumber>
<ns1:DeviceClass>Phone</ns1:DeviceClass>
<ns1:Model>497</ns1:Model>
<ns1:Product>384</ns1:Product>
<ns1:BoxProduct>0</ns1:BoxProduct>
<ns1:Httpd>Yes</ns1:Httpd>
<ns1:RegistrationAttempts>0</ns1:RegistrationAttempts>
<ns1:IsCtiControllable>true</ns1:IsCtiControllable>
<ns1:LoginUserId xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:Status>Registered</ns1:Status>
<ns1:StatusReason>0</ns1:StatusReason>
<ns1:PerfMonObject>2</ns1:PerfMonObject>
<ns1:DChannel>0</ns1:DChannel>
<ns1:Description>SEPE8B7480316D6</ns1:Description>
<ns1:H323Trunk>
<ns1:ConfigName xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:TechPrefix xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:Zone xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:RemoteCmServer1 xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:RemoteCmServer2 xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:RemoteCmServer3 xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:AltGkList xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:ActiveGk xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:CallSignalAddr xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:RasAddr xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</ns1:H323Trunk>
<ns1:TimeStamp>1411595208</ns1:TimeStamp>
<ns1:Protocol>SCCP</ns1:Protocol>
<ns1:NumOfLines>1</ns1:NumOfLines>
<ns1:LinesStatus>
<ns1:item>
<ns1:DirectoryNumber>6961</ns1:DirectoryNumber>
<ns1:Status>Registered</ns1:Status>
</ns1:item>
</ns1:LinesStatus>
<ns1:ActiveLoadID>SCCP69xx.9-4-1-3SR1</ns1:ActiveLoadID>
<ns1:InactiveLoadID xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:DownloadStatus>Unknown</ns1:DownloadStatus>
<ns1:DownloadFailureReason xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:DownloadServer xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:IPAddress>
<ns1:item>
<ns1:IP>192.168.168.186</ns1:IP>
<ns1:IPAddrType>ipv4</ns1:IPAddrType>
<ns1:Attribute>AdministrativeAndSignaling</ns1:Attribute>
</ns1:item>
</ns1:IPAddress>
</ns1:item>
</ns1:CmDevices>
</ns1:item>
</ns1:CmNodes>
</ns1:SelectCmDeviceResult>
<ns1:StateInfo><StateInfo ClusterWide="1"><Node Name="cucm3" SubsystemStartTime="1411513436" StateId="84" TotalItemsFound="1" TotalItemsReturned="1"/></StateInfo></ns1:StateInfo>
</ns1:selectCmDeviceReturn>
</ns1:selectCmDeviceResponse>
</soapenv:Body>
</soapenv:Envelope>
The response includes information requested using the SelectCmDevice
request, and can include information for one or more Cisco Unified CM nodes.
Parameter | Description |
---|---|
TotalDevicesFound | The total number of devices found. |
CmNodes | An array of requested node information for one or more nodes. Each CmNode contains a sequence of devices and their registration status including:
|
ReturnCode | Returns Real-Time Information Service return codes:
|
Name | The Host Name or IP address. |
NoChange | True or false. Refer to the StateInfo Usage section for more details. |
A CmDevice in the CmNode contains the following information:
Parameter | Description |
---|---|
Name | The name of the device. |
DirNumber | The directory number. |
DeviceClass | The type of device. |
Model | The parameter value refers to the Cisco Unified CM internal model number of a particular device or 255 for "any model." Click here for an example listing of model numbers. The complete list of available model numbers is stored in the Cisco Unified CM 'typemodel' database table. |
Product | The product type. |
BoxProduct | Displays the integer value (0 or 1) for box products. |
Httpd | Indicates whether the device has an onboard HTTP web server. Values:
|
RegistrationAttempts | Number of registration attempts. |
IsCtiControllable | True or False |
LoginUserId | Displays EM (Extension Mobility) login User ID. This is used for the Cisco Unified CM Extension Mobility feature. |
Status | The device registration status type:
|
StatusReason | Indicates the reason code for the current device status, if known. Click here for the Reason Code table. |
PerfMonObject | The PerfMonObject ID. |
DChannel | The number of D channels supported for PRI devices. |
Description | Description of the device. |
H323Trunk | The H323 trunk details. |
TimeStamp | The UTC format time-stamp. |
Protocol | The device protocol type including:
|
NumOfLines | The number of lines. |
LinesStatus | The status of each line:
|
ActiveLoadID | Displays the currently active firmware on the phone. |
InactiveLoadID | Displays the inactive phone load. |
DownloadStatus | Displays the current firmware download status. Possible values are:
|
DownloadFailureReason | Displays firmware download failure reason, if any. |
DownloadServer | Displays the current firmware download server. |
IPAddress | An array list of device IP Addresses. IPAddrType indicates the IP version type:
Attribute indicates the IP address function:
|
SelectCmDevice Status Reason Codes
If the device is Registered on the server, the StatusReason
is 0. If the device is Unregistered, then one of the following values will be displayed in the response.
Reason Code | Description |
---|---|
1 | Unknown - The device has unregistered for an unknown reason. If the device does not re-register within 5 minutes, verify that it is powered up and there is network connectivity between the device and Cisco Unified CM. |
2 | ConnectivityError - Network communication between the device and Cisco Unified CM has been interrupted. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, or packet corruption. It is also possible to receive this error if the Cisco Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, network connectivity exists between the device and Cisco Unified CM, and the CPU utilization is in the safe range. Monitor CPU utilization via the CPU Pegging Alert in RTMT. |
8 | DeviceInitiatedReset - The device has initiated a reset, possibly due to a power cycle or internal error. No action required; the device will re-register automatically. |
9 | CallManagerReset - A device reset was initiated from Cisco Unified CM Administration, either due to an explicit command from an administrator, or due to internal errors encountered. No action necessary; the device will re-register automatically. |
10 | DeviceUnregistered - The device has explicitly unregistered. Possible causes include a change in the IP address or port of the device. No action is necessary; the device will re-register automatically. |
11 | MalformedRegisterMsg - (SIP only) A SIP REGISTER message could not be processed because of an illegal format. Possible causes include a missing Call-ID header, a missing AoR in the To header, or an expires value that is too small. Check the REGISTER message for any of these issues and correct the issue, if found. |
12 | SCCPDeviceThrottling - (SCCP only) The indicated SCCP device exceeded the maximum number of events allowed per-SCCP device. Events can be phone calls, KeepAlive messages, or excessive SCCP or non-SCCP messages. The maximum number of allowed events is controlled by the Cisco Unified CM service parameter Max Events Allowed. When an individual device exceeds the number configured in that service parameter, Cisco Unified CM closes the TCP connection to the device; automatic re-registration generally follows. This action is an attempt to stop malicious attacks on Cisco Unified CM or to ward off excessive CPU usage. |
13 | KeepAliveTimeout - A KeepAlive message was not received. Possible causes include device power outage, network power outage, network configuration error, network delay, packet drops, and packet corruption. It is also possible to receive this error if the Cisco Unified CM node is experiencing high CPU usage. Verify that the device is powered up and operating, there is network connectivity between the device and Cisco Unified CM, and the CPU utilization is in the safe range. Monitor CPU utilization via the CPU Pegging Alert in RTMT. |
14 | ConfigurationMismatch - (SIP only) The configuration on the device does not match the configuration in Cisco Unified CM. This can be caused by database replication errors or other internal Cisco Unified CM communication errors. Using the Cisco Unified Reporting web page, generate a Cisco Unified CM Database Status report and verify that all servers have a good replication status. Another method is using the Real-Time Reporting Tool (RTMT) and checking the Replication Status in the Database Summary page. If the status shows 2, then replication is working. If this device continues to unregister with this reason code, go to the Device Configuration page in Cisco Unified CM Administration for the device indicated in this alarm and click Save. This generates a change notify message to the Cisco Unified CM and TFTP services and rebuilds a new configuration file for the device. If the problem still persists, restart the TFTP service and the Cisco Unified CM service. |
15 | CallManagerRestart - A device restart was initiated from Cisco Unified CM Administration, either due to an explicit command from an administrator or due to a configuration change such as adding, deleting, or changing a directory number associated with the device. No action is necessary; the device will re-register automatically. |
16 | DuplicateRegistration - Cisco Unified CM detected that the device attempted to register to two nodes at the same time. Cisco Unified CM initiated a restart to the phone to force it to re-home to a single node. No action is necessary; the device will re-register automatically. |
17 | CallManagerApplyConfig - An ApplyConfig action was performed in Cisco Unified CM Administration resulting in an unregistration. No action is necessary; the device will re-register automatically. |
18 | DeviceNoResponse - The device did not respond to a reset or restart notification. The device is being forcibly reset. If the device does not re-register within 5 minutes, confirm that it is powered up and confirm that there is network connectivity between the device and Cisco Unified CM. |
19 | PowerSavePlus - The device powered off as a result of the Power Save Plus feature that is enabled for this device. When the device powers off, it remains unregistered from Cisco Unified CM for the duration specified in the Phone On Time parameter in the Product Specific Configuration for this device |
RisPort70 SelectCMDeviceExt
<!--RisPort70 API - SelectCmDeviceExt - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
<soapenv:Header/>
<soapenv:Body>
<soap:selectCmDeviceExt>
<soap:StateInfo></soap:StateInfo>
<soap:CmSelectionCriteria>
<soap:MaxReturnedDevices>1000</soap:MaxReturnedDevices>
<soap:DeviceClass>Any</soap:DeviceClass>
<soap:Model>255</soap:Model>
<soap:Status>Any</soap:Status>
<soap:NodeName></soap:NodeName>
<soap:SelectBy>Name</soap:SelectBy>
<soap:SelectItems>
<!--Zero or more repetitions:-->
<soap:item>
<soap:Item>SEPE8B7480316D6</soap:Item>
</soap:item>
</soap:SelectItems>
<soap:Protocol>Any</soap:Protocol>
<soap:DownloadStatus>Any</soap:DownloadStatus>
</soap:CmSelectionCriteria>
</soap:selectCmDeviceExt>
</soapenv:Body>
</soapenv:Envelope>
<!--RisPort70 API - SelectCmDeviceExt - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns1:selectCmDeviceResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
<ns1:selectCmDeviceReturn>
<ns1:SelectCmDeviceResult>
<ns1:TotalDevicesFound>1</ns1:TotalDevicesFound>
<ns1:CmNodes>
<ns1:item>
<ns1:ReturnCode>Ok</ns1:ReturnCode>
<ns1:Name>cucm3</ns1:Name>
<ns1:NoChange>false</ns1:NoChange>
<ns1:CmDevices>
<ns1:item>
<ns1:Name>SEPE8B7480316D6</ns1:Name>
<ns1:DirNumber>6961-Registered</ns1:DirNumber>
<ns1:DeviceClass>Phone</ns1:DeviceClass>
<ns1:Model>497</ns1:Model>
<ns1:Product>384</ns1:Product>
<ns1:BoxProduct>0</ns1:BoxProduct>
<ns1:Httpd>Yes</ns1:Httpd>
<ns1:RegistrationAttempts>0</ns1:RegistrationAttempts>
<ns1:IsCtiControllable>true</ns1:IsCtiControllable>
<ns1:LoginUserId xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:Status>Registered</ns1:Status>
<ns1:StatusReason>0</ns1:StatusReason>
<ns1:PerfMonObject>2</ns1:PerfMonObject>
<ns1:DChannel>0</ns1:DChannel>
<ns1:Description>SEPE8B7480316D6</ns1:Description>
<ns1:H323Trunk>
<ns1:ConfigName xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:TechPrefix xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:Zone xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:RemoteCmServer1 xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:RemoteCmServer2 xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:RemoteCmServer3 xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:AltGkList xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:ActiveGk xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:CallSignalAddr xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:RasAddr xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</ns1:H323Trunk>
<ns1:TimeStamp>1411595208</ns1:TimeStamp>
<ns1:Protocol>SCCP</ns1:Protocol>
<ns1:NumOfLines>1</ns1:NumOfLines>
<ns1:LinesStatus>
<ns1:item>
<ns1:DirectoryNumber>6961</ns1:DirectoryNumber>
<ns1:Status>Registered</ns1:Status>
</ns1:item>
</ns1:LinesStatus>
<ns1:ActiveLoadID>SCCP69xx.9-4-1-3SR1</ns1:ActiveLoadID>
<ns1:InactiveLoadID xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:DownloadStatus>Unknown</ns1:DownloadStatus>
<ns1:DownloadFailureReason xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:DownloadServer xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:IPAddress>
<ns1:item>
<ns1:IP>192.168.168.186</ns1:IP>
<ns1:IPAddrType>ipv4</ns1:IPAddrType>
<ns1:Attribute>AdministrativeAndSignaling</ns1:Attribute>
</ns1:item>
</ns1:IPAddress>
</ns1:item>
</ns1:CmDevices>
</ns1:item>
</ns1:CmNodes>
</ns1:SelectCmDeviceResult>
<ns1:StateInfo><StateInfo ClusterWide="1"><Node Name="cucm3" SubsystemStartTime="1411513436" StateId="84" TotalItemsFound="1" TotalItemsReturned="1"/></StateInfo></ns1:StateInfo>
</ns1:selectCmDeviceReturn>
</ns1:selectCmDeviceResponse>
</soapenv:Body>
</soapenv:Envelope>
The request and response schema format for SelectCmDevice
and SelectCmDeviceExt
are identical, with the exception of the base request name. See SelectCmDevice
for usage and parameter values.
The difference is in functionality. SelectCmDeviceExt
collates device status records across nodes, eliminating any duplicates.
This API returns a snapshot of the real-time device state from each Cisco Unified CM node. This data includes registration status, IP address, and model info. This request consolidates device records across nodes, returning only the device info for the latest registration.
Note: SelectCMDeviceExt
does not support using the *
wildcard for SelectItems
matching.
RisPort70 SelectCtiItem
This method allows clients to perform CTI manager related queries. The method returns a snapshot of real-time CTI application status from each Cisco Unified CM node. This data includes application name, authenticated user, IP address, controlled CTI devices, and connection status.
SelectCtiItem Request Format
<!--RisPort70 API - SelectCtiItem - Request-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.cisco.com/ast/soap">
<soapenv:Header/>
<soapenv:Body>
<soap:selectCtiItem>
<soap:StateInfo></soap:StateInfo>
<soap:CtiSelectionCriteria>
<soap:MaxReturnedItems>1000</soap:MaxReturnedItems>
<soap:CtiMgrClass>Line</soap:CtiMgrClass>
<soap:Status>Any</soap:Status>
<soap:NodeName></soap:NodeName>
<soap:SelectAppBy>AppId</soap:SelectAppBy>
<soap:AppItems>
<!--Zero or more repetitions:-->
<soap:item>
<soap:AppItem>cucmuser-192.168.168.169-4963</soap:AppItem>
</soap:item>
</soap:AppItems>
<soap:DevNames>
<!--Zero or more repetitions:-->
<soap:item>
<soap:DevName>SEPF01FAF38ABC2</soap:DevName>
</soap:item>
</soap:DevNames>
<soap:DirNumbers>
<!--Zero or more repetitions:-->
<soap:item>
<soap:DirNumber>1002</soap:DirNumber>
</soap:item>
</soap:DirNumbers>
</soap:CtiSelectionCriteria>
</soap:selectCtiItem>
</soapenv:Body>
</soapenv:Envelope>
Parameter | Description |
---|---|
StateInfo | Returns state information for the items in the request. The StateInfo returned can be used to determine if a change has occurred since a previous request. Refer to the StateInfo Usage section. |
CtiSelectionCriteria | See the following table for parameters. |
CtiSelectionCriteria includes:
Parameter | Description |
---|---|
MaxReturnedItems | The maximum number of devices to return. The maximum parameter value is 1000. |
CtiMgrClass | A search is requested on Provider, Device, or Line. |
Status | The status or class on which to search:
|
NodeName | The server to search. If no node name is given and clusters are configured, all servers in the cluster will be searched. |
SelectAppBy | Selection criteria to search for an application:
|
AppItems | AppItems is the result set. Each item is a string representing a unique CTI application connection with the format:
|
DevNames | List of devices controlled by the CTI application(s). |
DirNumbers | List of directory numbers controlled by the CTI application(s). Note: DirNumber lookup only works if specifying "Line" in the soap:CtiMgrClass tag. |
SelectCtiitem Response Format
<!--RisPort70 API - SelectCtiItem - Response-->
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns1:selectCtiItemResponse xmlns:ns1="http://schemas.cisco.com/ast/soap">
<ns1:selectCtiItemReturn>
<ns1:SelectCtiItemResult>
<ns1:TotalItemsFound>1</ns1:TotalItemsFound>
<ns1:CtiNodes>
<ns1:item>
<ns1:ReturnCode>Ok</ns1:ReturnCode>
<ns1:Name>cucm3</ns1:Name>
<ns1:NoChange>false</ns1:NoChange>
<ns1:CtiItems>
<ns1:item>
<ns1:AppId>cucmuser-192.168.168.169-4963</ns1:AppId>
<ns1:UserId>cucmuser</ns1:UserId>
<ns1:AppIpAddr>192.168.168.169</ns1:AppIpAddr>
<ns1:AppIpv6Addr xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:AppStatus>Closed</ns1:AppStatus>
<ns1:AppStatusReason>2</ns1:AppStatusReason>
<ns1:AppTimeStamp>1412194696</ns1:AppTimeStamp>
<ns1:CtiDevice>
<ns1:AppControlsMedia>false</ns1:AppControlsMedia>
<ns1:DeviceName>SEPF01FAF38ABC2</ns1:DeviceName>
<ns1:DeviceStatus>Open</ns1:DeviceStatus>
<ns1:DeviceStatusReason xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
<ns1:DeviceTimeStamp xsi:nil="1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
</ns1:CtiDevice>
<ns1:CtiLine>
<ns1:DirNumber>1002</ns1:DirNumber>
<ns1:LineStatus>Closed</ns1:LineStatus>
<ns1:LineStatusReason>0</ns1:LineStatusReason>
<ns1:LineTimeStamp>1412194696</ns1:LineTimeStamp>
</ns1:CtiLine>
</ns1:item>
</ns1:CtiItems>
</ns1:item>
</ns1:CtiNodes>
</ns1:SelectCtiItemResult>
<ns1:StateInfo><StateInfo ClusterWide="1"><Node Name="cucm3" SubsystemStartTime="1411513254" StateId="621" TotalItemsFound="1" TotalItemsReturned="1"/></StateInfo></ns1:StateInfo>
</ns1:selectCtiItemReturn>
</ns1:selectCtiItemResponse>
</soapenv:Body>
</soapenv:Envelope>
Parameter | Description |
---|---|
TotalItemsFound | The total number of items found. |
CtiNodes | An array of requested information for one or more items. Each CtiNode contains a sequence of items and their registration status:
|
CtiNodes
contains the following information:
Parameter | Description |
---|---|
ReturnCode | Returns Real-Time Information Service return codes:
|
Name | The name of the node. |
NoChange | True or false. Refer to the StateInfo Usage section for more details. |
CtiItems | An array of requested information for one or more items. |
CtiItems
contains the following information:
Parameter | Description |
---|---|
AppId | The application ID. |
UserId | The user ID. |
AppIpAddr | The IP address of the application. |
AppIpv6Addr | The IPv6 address of the application, if applicable. |
AppStatus | The status of the application:
|
AppStatusReason | The reason for the application status. |
AppTimeStamp | The UNIX time stamp. |
CtiDevice | One or more CtiDevice elements. |
CtiLine | One or more CtiLine elements. |
CtiDevice
contains the following information:
Parameter | Description |
---|---|
AppControlsMedia | True or false. |
DeviceName | Name of the device. |
DeviceStatus | The status of the device:
|
DeviceStatusReason | The reason for the device status. |
DeviceTimeStamp | The UNIX time stamp. |
CtiLine
contains the following information:
Parameter | Description |
---|---|
DirNumber | The directory number. |
LineStatus | The status of the line:
|
LineStatusReason | The reason for the line status. |
LineTimeStamp | The UNIX time stamp. |