inconsistent result RISService70 selectCmDevice

[tanxiongzhe]

I am using the following query

<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>Registered</soap:Status>
<soap:NodeName></soap:NodeName>
<soap:SelectBy>Name</soap:SelectBy>
<soap:SelectItems>
<!--Zero or more repetitions:-->
<soap:item><soap:Item>phone1</soap:Item></soap:item>
...
<soap:item><soap:Item>phone1000</soap:Item></soap:item>
</soap:SelectItems>
<soap:Protocol>Any</soap:Protocol>
<soap:DownloadStatus>Any</soap:DownloadStatus>
</soap:CmSelectionCriteria>
</soap:selectCmDevice>
</soapenv:Body>
</soapenv:Envelope>

I am getting either <ns1:TotalDevicesFound>400</ns1:TotalDevicesFound>  or <ns1:TotalDevicesFound>700</ns1:TotalDevicesFound>. Sometimes 400 and sometimes 700.

I have 4 x subscribers: cucm01, cucm02, cucm03 and cucm04. After a closer look, I found when there is no registered phones/entries from cucm04, the totalDevicesFound is 400. And when there is registered phones/entries from cucm04, the totalDevicesFound is 700. phones/entries from cucm01, cucm02 and cucm03 are consistent. RTMT shows phones registered with cucm04.

I suspect something is wrong with cucm04, But I don't know where to check/verify. Can someone help?

[dstaudt]

Sounds like some sort of intermittent connection issue between CUCM nodes or possibly some problem within the Risport SOAP service.  Possibly restarting some services on the problematic node, restarting the node entirely, and/or restarting the cluster could resolve.  If the problem is intermittent but reproducible, might be worth opening a ticket with DevNet, so see if we can capture the issue with some detailed logs to get input from engineering: https://developer.cisco.com/site/support/

[tanxiongzhe]

Thanks dstaudt for your assistance,

In terms of restarting services on the problematic node, can you please suggest what service(s)?

Regarding opening a ticket with DevNet, do I need to pay for it? If so what's the price?

Thanks again,

Sean

[dstaudt]

Without understanding the root cause, restarting services is a crap-shoot, but possibly (in order of intuited likelihood:)

• Cisco RIS Data Collector
• SOAP -Real-Time Service APIs
• Cisco CallManager Serviceability
• Cisco CallManager
• (node reboot)
• (cluster reboot)

Currently opening a DevNet Developer Support ticket is not charged (follow the tiny 'contact us' link), however that may change at some point.

[tanxiongzhe]

Many thanks!