This is done to limit the response buffer to the first 200 devices per server even though the client may have given search criteria to get all the devices in a large deployment. Searches in call processing servers are expensive in terms of CPU cycles. Call processing servers need to service IP phone calls. The device requests from clients should consume less memory and CPU resources. Device requests cannot exceed 20% of CPU resources in call processing servers. Many clients may be requesting this information, but we have limited the information to the first 200 devices.
To get all configured device information, clients must use the AXL-DB API. Use the device information from the AXL-DB API in "SelectItems" of the "CmSelectionCriteria" Serviceability SOAP APIs to get first 200 device's real-time information. "
Re: Help! SelectCmDevices is returning only 200 phones
Thanks. This was very useful and I will rate it accordingly.
My follow up question is if I send multiple AXL requests to recieve 200 devices at a time, would it return the same 200 devices or is it going to iterate through it? I mean, is there a paramter which tells AXL to send next set of 200 devices?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...