Device status information sample request for large systems

Version 1
    This document was generated from CDN thread

    Created by: Gitansh Chadha on 05-01-2009 06:59:13 PM
    Can I get a pointer to sample requests used to query RIS for large systems (using node change flag). I looked at the link below and had some questions on the session string and the request format.

    http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/devguide/6_0_1/ccmdvCh2.html#wp72672

    Thanks.

    Subject: Re: Device status information sample request for large systems
    Replied by: Stephan Steiner on 07-01-2009 08:52:18 AM
    The following forum post contains an example with two phones.. it can be blown up to do 200 phones (the limit for the risport): http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Phone%20Services%20for%20Developers&topicID=.ee94c94&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40^1%40%40.2cbff352/2#selected_message

    Now for the StateInfo - an element not properly explained in the documentation if you ask me. Your response will contain a StateInfo tag. If after some time you run the exact same query again, you can extract that StateInfo tag from the response to the last identical request (must be from the proper response.. things can get unpredictable if you don't even though it's not supposed to matter and just return all devices anyway) and add it to your next request (make sure you pack the value into a CDATA tag or you'll get a service side error (response code 500).

    So suppose you make 10 requests for 200 phones each, req1 - req10 and you get 10 responses res1 - res10.

    Next time you run req1, add the StateInfo tag from res1 so that in case there are no changes, the response will just tell you that instead of listing all the devices again (or in case there have been changes you just see the changes).

    And as I said, if you slightly modify req1, then you should not use StateInfo at all - I have a software which is tracking changes to the system (new IPCs, IPCs that are no longer active because the computer has been swapped out).. so my serviceability queries can very slightly between runs and initially I was using StateInfo that at times that gave us some weird effects (e.g. missing certain phones - they were in the request but not the response.. but if I ran a query on just those phones the results were proper)

    Also, since you extract the device list via axl, make sure you also check out this blog post about the changes in 6.1.3 and the next 7.x release: http://developer.cisco.com/web/axl/blogroll/-/blogs/534139?_33_redirect=%2Fweb%2Faxl%2Fblogroll