"devicelistx.asp has a finite future" - Would you care to elaborate on that point? We have many inhouse applications that rely on devicelistx.asp, so if it were to go away these would have to be reprogrammed.<br>
<br>
<div><span class="gmail_quote">On 1/30/06, <b class="gmail_sendername">Wes Sisk</b> <<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">As this is such a frequently asked question and devicelistx.asp has a<br>finite future, I will test as soon as I get a few minutes. My
<br>initial sources say:<br><br>SNMP MIB<br>ccmPhoneInetAddress - .1.3.6.1.4.1.9.9.156.1.2.1.1.15<br>ccmPhoneInetAddressType - .1.3.6.1.4.1.9.9.156.1.2.1.1.14<br><br>AXL<br>request string - listPhoneByName<br>parameter - searchstring %
<br><br>/Wes<br><br>On Jan 28, 2006, at 9:56 AM, Seth Call wrote:<br><br>For real-time reg info, dlx is the only way.<br><br>You could also use JTAPI to monitor the device, but that's obviously<br>pretty heavy, depending on how many phones we are talking about.
<br><br>-----Original Message-----<br>From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net
</a>] On Behalf Of Andrea Cerioli<br>Sent: Saturday, January 28, 2006 4:10 AM<br>To: Justin Steinberg<br>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] Retrieving device information from CISCO
<br><br><br>Thanks all for the useful hints.<br>This saved us a lot of time.<br><br>I just have a last question.<br><br>I've reviewed the sample application in the SDK,<br>and it uses DeviceListX.asp.<br>i.e. to retrieve the IP address of a phone, it gets the complete list,
<br>loads it in a vector, then searches the phone name to extract the IP<br>address.<br>This looks to be the only way to do this.<br><br>Unfortunately this way can be quite heavvy if you need<br>to query the resident http server of hundreds, or even thousands of
<br>IP Phones independently from each other.<br>However we can "optimize" getting the list once per a time interval,<br>but is still an overhead and prevent us from working asynchronously,<br>I mean we will need to build a synchronous application that will batch
<br>al operations at fixed time intervals, then get the current list at that<br>time, perform all batched operations, and the sleeps for next time<br>interval.<br>Not very nice IMHO, but looks to be the only way out.<br><br>
I would have expected a smarter API, something like<br>GetIPPhoneRegInfoByName,<br>using the SEP name to retrieve registration info of the phone from<br>the callmanager.<br>This would be a natural complement of the DeviceListX.asp
report.<br><br>Is there any way, perhaps undocumented, to obtain regstration info<br>for a single IP phone at a time, or are we bound to retrieving the<br>complete list?<br><br>Thanks in advance for your comments.<br><br>
Andrea<br><br>Justin Steinberg wrote:<br>> Andrea,<br>><br>> You should download the IP Phone Services SDK for ccm 4.1(3). There<br>> is quite a few example applications that run on asp and some that run<br>
> on jsp. I've played around with several and know that some have code<br>> that query's for the phone IP. I know the Push2Phone app query's for<br>> IP in order to push the xml post to the phone's IP address.
<br>><br>><br><a href="http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programmin">http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programmin</a><br>g_reference_guide_chapter09186a0080405759.html
<br>><br>> Justin<br>><br>><br>><br>>> Date: Thu, 26 Jan 2006 22:03:09 +0100<br>>> From: Andrea Cerioli <<a href="mailto:cerioli@alternet.it">cerioli@alternet.it</a>><br>>> Subject: Re: [cisco-voip] Retrieving device information from CISCO
<br>>> CallManager<br>>> To: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>> Message-ID: <<a href="mailto:43D9390D.7010807@alternet.it">43D9390D.7010807@alternet.it
</a>><br>>> Content-Type: text/plain; charset=us-ascii; format=flowed<br>>><br>>> Thanks to all for your support.<br>>> The very ugly way is not for us, and SNMP does not return this info<br>>> since
ccmPhoneInfo.ccmPhoneTable.ccmPhoneEntry.ccmPhoneIpAddress<br>>> looks to be always empty.<br>>><br>>> THe supported SOAP interface is the one we investigated, but although<br>>> we are using 4.1(3) we could not find the right query to do.
<br>>> We manage to extract any sort of info but not the IP address.<br>>><br>>> Perhaps we don't have the greatest and latest documentation.<br>>> Can you please point us to the right query?<br>>>
<br>>> Thanks in advance for any further help.<br>>><br>>> Andrea.<br>>> Wes Sisk wrote:<br>>><br>>>> There are several versions of SOAP. In CallManager 4.1(3) there<br>>>> is a
<br>>>> new SOAP interface that includes device registered status.<br>>>><br>>>> In older versions the file<br>http://<ip>/CCMAdmin/reports/DeviceListX.asp<br>>>> provides a list of almost all devices (7902/05/12, ATA, and a few
<br>other<br>>>> devices excluded), their registration status, and IP.<br>>>><br>>>> The very ugly way to retrieve the data is via unofficial unsupported<br>>>> mmfspy from cmd prompt on the CM server.
<br>>>><br>>>> The AXL/SOAP interface is the officially supported interface for all<br>>>> versions going forward.<br>>>><br>>>> /Wes<br>>>><br>>>> Andrea Cerioli wrote:
<br>>>><br>>>><br>>>>> We are writing an application that need to query the CallManager<br>>>>> to obtain the list of registered Phones, including current IP<br>address<br>>>>> for each phone.
<br>>>>><br>>>>> We have tried with AXL SOAP interface, and also looked into the DC<br>>>>> directory<br>>>>> and the SQL database, but we couldn't find this information.<br>
>>>> We obtained plenty of information about phones, but not their IP<br>address.<br>>>>><br>>>>> The information must be there, since it is there in<br>>>>> the web based administration interface ...
<br>>>>><br>>>>> This is driving us mad.<br>>>>> Where are we wrong?<br>>>>> Do we miss the right documentation? (we use the publicly available<br>docs<br>>>>> on AXL SOAP from the CISCO web site).
<br>>>>><br>>>>> Thanks for any help (or direction to the proper place to ask this<br>>>>> question).<br>>>>><br>>>>><br>>><br>>> --<br>>> | Andrea Cerioli
<a href="http://alter.net">alter.net</a> Srl |<br>>> | e-mail: <a href="mailto:cerioli@alter.it">cerioli@alter.it</a> Via Attilio Ambrosini, 177 |<br>>> | VOICE: +39-6-5405740 I-00147 Rome |
<br>>> | FAX: +39-6-5405883 Italy |<br>>><br>>><br>>><br><br>--<br>| Andrea Cerioli <a href="http://alter.net">alter.net</a> Srl |<br>| e-mail:
<a href="mailto:cerioli@alter.it">cerioli@alter.it</a> Via Attilio Ambrosini, 177 |<br>| VOICE: +39-6-5405740 I-00147 Rome |<br>| FAX: +39-6-5405883 Italy |<br><br>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip
</a><br><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br></blockquote></div><br><br clear="all"><br>-- <br><br>_________________________________________<br><br>Adam Blomfield<br>8989 West 61st Street, Tulsa OK 74131<br>
Tel: 918-447-1593<br>Cell: 918-625-1739<br>E-mail mailto:<a href="mailto:adman@adman.net">adman@adman.net</a><br>Internet <a href="http://www.adman.net">http://www.adman.net</a><br>_________________________________________
<br>