For login, you could use the login URL. There is also a logout URL you can use. http://X.X.X.X/emapp/EMAppServlet?device=SEP001122334455&userid=user.name&seq=1234   Is this what you are looking for? ... View more

It depends on how accurate you want the results. If I remember correctly, PLM synchronizes once a day, which is generally acceptable for most people. ... View more

As far as I know, the definitions are not. I wrote a perl script a while back to programmatically scrape for the information, but it was kind of wonky. ... View more

The RIS DB stores data on each node for 3 days by default (this is a configurable parameter). Entries older than that are purged. What you are likely seeing is an MTP that re-registered to another node and then failed back. With that being said, I classify devices into three groups: SIP Trunks SIP Trunks will register to all call processing nodes in a cluster at the same time, even if they are not in the SIP trunk's call manager group In CUCM 10.X+, the registration status shown from polling the RIS API tells you its SIP Option PING status. In 9.X and below, it will always show as unknown. Registered = Full Service Unregistered = Partial Service Unknown = No Service H323 Gateways H323 GWs "register" to all nodes that are in their call manager group at the same time. I use quotes because the registration status in the RIS API shows as unknown if the GWs are in good standing. For example, if you poll for a single H323 GW and receive 2 Unknown entries, then repoll and see only 1 of those 2 entries missing, the H323 GW has deregistered from that node Everything Else These would be things like phones, ports, media resources, etc that follow the single registration rule. For example, a device will register to it's primary,secondary, and tertiary call manager server within its call manager group, in that order, and will fail back in reverse order as soon as a higher priority target becomes available. When doing the above, for each node, RIS will keep a record of the status for that device until it is purged from RIS (default 3 days after last registration to the node) In the case of identifying registration for one of these types of devices, you would simply check to see if the device is registered to one the nodes in the cluster, regardless of what node it is. ... View more

The object you are pulling from has instances, this can be seen by using the following URL: https://X.X.X.X/ast/AstIsapi.dll?PerfmonListObject <Object Name="Processor" HasInstances="true"> <Counter Name="% CPU Time"/> <Counter Name="IOwait Percentage"/> <Counter Name="Idle Percentage"/> <Counter Name="Irq Percentage"/> <Counter Name="Nice Percentage"/> <Counter Name="Softirq Percentage"/> <Counter Name="Steal Percentage"/> <Counter Name="System Percentage"/> <Counter Name="User Percentage"/> </Object> With that being said, how are you adding your instanced counters? They should look something like \\x.x.x.x\object(instancename)\countername You can gather the instance names via the perfmonListCounter and perfmonListInstance mechanisms. ... View more

Hello Kevin, I recently had to do something similar to what you are asking. The answer to your question is a little bit of a grey area. From an monitoring perspective, there isn't much to work with when it comes to ELM/PLM, however there are some things that you can use to get some relevant info. I recently had to do a similar request involving getting license info from CUCM itself. For my case, I used the executeSQLQuery API method to gather information. There are a couple of main tables that you can use, and although they don't give you a 100% clear view of what you would see in ELM/PLM, they might be useful to you: licenseserver - This table will provide the following items: elmname - hostname/IP of the ELM server tklicensingmode - a key that links tot the typelicensingmode table tklicensingstate - a key that links to the typelicensingstate table elmlastcontactts - unix timestamp for the last contact time between CUCM and ELM/PLM graceleftdays - number of days remaining in your grace period If you join the table above, a mix of licenseserver.graceleftdays and typelicensingstate.name will let you know if your CUCM cluster is in good standing or has an issue and how long you have to fix it. Now, you might be wondering about performing a threshold on number of licenses in use vs number of licenses available via ELM/PLM. As it currently stands, I have not been able to find a method of discovering the number of licenses available via ELM/PLM, so creating a ceiling will have to be manually defined. The other side of the coin, number of licenses in use, can be done a couple of ways. You can use the API methods that you have already discussed in your post, or create a very large and extensive SQL query to figure it out, but there is always a simpler solution. Hidden away in the informix stored procedures, there is a procedure which does a calculation of licenses. The stored procedure can be used via executeSQLQuery and looks like the following: SELECT name,value FROM TABLE (FUNCTION LicenseTotals()) (pkid,name,value,UserValue,DeviceValue) I hope this information helps solve your problem! Thanks! ... View more