Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
427
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-24-2014 12:00 PM
This document was generated from CDN thread
Created by: CANDACE HOLMAN on 30-04-2009 08:46:14 PM
I have developed some query code over SOAP that works well for CCM 5/6 and would like to do the same for CUCME. I've only found one document (http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/xml/developer/guide/xmldev.html) that specifically references XML API in CUCME, but that doesn't mean it can't be done. While I'm waiting for the equipment to test, can anyone confirm that CUCME provides support similar to CCM, in terms of Serviceability?
We are looking at version 7.x, and supporting UC-500 series as well as ISRs.
Subject: RE: CUCME
Replied by: David Staudt on 01-05-2009 01:42:19 AM
CME AXL is pretty thin. It provides a small handful of config requests, but mainly provides a passthrough for IOS CLI commands. There is no Serviceability AXL-like capability - best bet for obtaining performance information is via SNMP.
Subject: RE: CUCME
Replied by: CANDACE HOLMAN on 20-05-2009 05:15:14 PM
Thanks, that's really helpful. I may end up needing the CLI commands to fill some gaps for data that I'm not finding in a nicely formatted way in the mibs. For example, number of calls in progress, # of failed calls, etc. I configured/tested the API via the xml-test.html routine, but when I try to execute a read-only command like "show ephone-dn summary" I get back only: <IsExecCliResponse>1</IsExecCliResponse>. I expected it would attempt to list out all the data in the response or give an error. Do you have any experience with this? Do I have to issue the CLI command in a different format?
Subject: RE: CUCME
Replied by: David Staudt on 20-05-2009 08:56:03 PM
Not sure why only '1' would be returned here. If you want to attach the full request/response XML, and a dump of the same command on the same machine execute via regular CLI, maybe we can track something down.
Subject: RE: New Message from David Staudt in Serviceability XML (SXML) - Serviceabi
Replied by: CANDACE HOLMAN on 20-05-2009 09:36:55 PM
Thanks again. On the UC-520 system the command shows:
UC520#show ephone-dn summary
PORT CH DN STATE MWI_STATE CODEC VAD VTSP STATE
VPM STATE
======== == ======== ========= ===== === ===========
=========
50/0/5 1 DOWN NONE - - -
EFXS_INIT
50/0/5 2 DOWN NONE - - -
EFXS_INIT
50/0/6 1 DOWN NONE - - -
EFXS_INIT
50/0/6 2 DOWN NONE - - -
EFXS_INIT
50/0/7 1 DOWN NONE - - -
EFXS_INIT
50/0/7 2 DOWN NONE - - -
EFXS_INIT
50/0/8 1 DOWN NONE - - -
EFXS_INIT
50/0/8 2 DOWN NONE - - -
EFXS_INIT
50/0/9 1 CONNECTED NONE g711ulaw n S_CONNECT
EFXS_CONNECT
50/0/10 1 DOWN NONE - - -
EFXS_INIT
50/0/10 2 DOWN NONE - - -
EFXS_INIT
50/0/11 1 DOWN NONE - - -
EFXS_INIT
50/0/11 2 DOWN NONE - - -
EFXS_INIT
50/0/12 1 DOWN NONE - - -
EFXS_INIT
50/0/12 2 DOWN NONE - - -
EFXS_INIT
50/0/13 1 DOWN NONE - - -
EFXS_INIT
50/0/13 2 DOWN NONE - - -
EFXS_INIT
50/0/14 1 DOWN NONE - - -
EFXS_INIT
50/0/14 2 DOWN NONE - - -
EFXS_INIT
50/0/15 1 DOWN NONE - - -
EFXS_INIT
50/0/15 2 DOWN NONE - - -
EFXS_INIT
50/0/16 1 DOWN NONE - - -
EFXS_INIT
50/0/16 2 DOWN NONE - - -
EFXS_INIT
50/0/17 1 DOWN NONE - - -
EFXS_INIT
50/0/17 2 DOWN NONE - - -
EFXS_INIT
50/0/18 1 DOWN NONE - - -
EFXS_INIT
50/0/18 2 DOWN NONE - - -
EFXS_INIT
50/0/19 1 DOWN NONE - - -
EFXS_INIT
50/0/19 2 DOWN NONE - - -
EFXS_INIT
50/0/1 1 DOWN NONE - - -
EFXS_INIT
The SOAP request that was generated for same command:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="request"
xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0
http://gkar.cisco.com/schema/axlsoap.xsd">
<request xsi:type="ISexecCLI">
<ISexecCLI>
<CLI>show ephone-dn summary</CLI>
</ISexecCLI>
</request>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
SOAP response:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="response" xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0 srst-its.xsd">
<response xsi:type="ISexecCLIResponse">
<ISexecCLIResponse>1</ISexecCLIResponse>
</response>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Here's an invalid cli request "abcd":
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="request"
xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0
http://gkar.cisco.com/schema/axlsoap.xsd">
<request xsi:type="ISexecCLI">
<ISexecCLI>
<CLI>abcd</CLI>
</ISexecCLI>
</request>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response is also "1":
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="response" xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0 srst-its.xsd">
<response xsi:type="ISexecCLIResponse">
<ISexecCLIResponse>1</ISexecCLIResponse>
</response>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Here's a blank cli request:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="request"
xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0
http://gkar.cisco.com/schema/axlsoap.xsd">
<request xsi:type="ISexecCLI">
<ISexecCLI>
</ISexecCLI>
</request>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response says blank is okay (0):
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/> "
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance
<http://www.w3.org/2000/10/XMLSchema-instance> "
xmlns:xsd="http://www.w3.org/1999/XMLSchema
<http://www.w3.org/1999/XMLSchema> ">
<SOAP-ENV:Body>
<axl xsi:type="response" xmlns="http://www.cisco.com/AXL/1.0
<http://www.cisco.com/AXL/1.0> "
xsi:schemaLocation="http://www.cisco.com/AXL/1.0
<http://www.cisco.com/AXL/1.0> srst-its.xsd">
<response xsi:type="ISexecCLIResponse">
<ISexecCLIResponse>0</ISexecCLIResponse>
</response>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Subject: RE: CUCME
Replied by: CANDACE HOLMAN on 28-05-2009 04:27:56 PM
Is it possible that the ISExecCLI can only be used for configuration commands and not for 'show' commands?
Subject: RE: CUCME
Replied by: David Staudt on 28-05-2009 07:00:42 PM
Well, engineering confirms that the interface is intended for CLI configuration commands - unfortunately not 'show' commands.
ISgetExtension is available for retrieving individual phone info...as you probably are aware the level of details is not as great as via show ephone-dn. My understanding is that expanding the level of details reported via AXL to include all the ephone ephone-dn info is roadmapped for a future CME release.
Created by: CANDACE HOLMAN on 30-04-2009 08:46:14 PM
I have developed some query code over SOAP that works well for CCM 5/6 and would like to do the same for CUCME. I've only found one document (http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/xml/developer/guide/xmldev.html) that specifically references XML API in CUCME, but that doesn't mean it can't be done. While I'm waiting for the equipment to test, can anyone confirm that CUCME provides support similar to CCM, in terms of Serviceability?
We are looking at version 7.x, and supporting UC-500 series as well as ISRs.
Subject: RE: CUCME
Replied by: David Staudt on 01-05-2009 01:42:19 AM
CME AXL is pretty thin. It provides a small handful of config requests, but mainly provides a passthrough for IOS CLI commands. There is no Serviceability AXL-like capability - best bet for obtaining performance information is via SNMP.
Subject: RE: CUCME
Replied by: CANDACE HOLMAN on 20-05-2009 05:15:14 PM
Thanks, that's really helpful. I may end up needing the CLI commands to fill some gaps for data that I'm not finding in a nicely formatted way in the mibs. For example, number of calls in progress, # of failed calls, etc. I configured/tested the API via the xml-test.html routine, but when I try to execute a read-only command like "show ephone-dn summary" I get back only: <IsExecCliResponse>1</IsExecCliResponse>. I expected it would attempt to list out all the data in the response or give an error. Do you have any experience with this? Do I have to issue the CLI command in a different format?
Subject: RE: CUCME
Replied by: David Staudt on 20-05-2009 08:56:03 PM
Not sure why only '1' would be returned here. If you want to attach the full request/response XML, and a dump of the same command on the same machine execute via regular CLI, maybe we can track something down.
Subject: RE: New Message from David Staudt in Serviceability XML (SXML) - Serviceabi
Replied by: CANDACE HOLMAN on 20-05-2009 09:36:55 PM
Thanks again. On the UC-520 system the command shows:
UC520#show ephone-dn summary
PORT CH DN STATE MWI_STATE CODEC VAD VTSP STATE
VPM STATE
======== == ======== ========= ===== === ===========
=========
50/0/5 1 DOWN NONE - - -
EFXS_INIT
50/0/5 2 DOWN NONE - - -
EFXS_INIT
50/0/6 1 DOWN NONE - - -
EFXS_INIT
50/0/6 2 DOWN NONE - - -
EFXS_INIT
50/0/7 1 DOWN NONE - - -
EFXS_INIT
50/0/7 2 DOWN NONE - - -
EFXS_INIT
50/0/8 1 DOWN NONE - - -
EFXS_INIT
50/0/8 2 DOWN NONE - - -
EFXS_INIT
50/0/9 1 CONNECTED NONE g711ulaw n S_CONNECT
EFXS_CONNECT
50/0/10 1 DOWN NONE - - -
EFXS_INIT
50/0/10 2 DOWN NONE - - -
EFXS_INIT
50/0/11 1 DOWN NONE - - -
EFXS_INIT
50/0/11 2 DOWN NONE - - -
EFXS_INIT
50/0/12 1 DOWN NONE - - -
EFXS_INIT
50/0/12 2 DOWN NONE - - -
EFXS_INIT
50/0/13 1 DOWN NONE - - -
EFXS_INIT
50/0/13 2 DOWN NONE - - -
EFXS_INIT
50/0/14 1 DOWN NONE - - -
EFXS_INIT
50/0/14 2 DOWN NONE - - -
EFXS_INIT
50/0/15 1 DOWN NONE - - -
EFXS_INIT
50/0/15 2 DOWN NONE - - -
EFXS_INIT
50/0/16 1 DOWN NONE - - -
EFXS_INIT
50/0/16 2 DOWN NONE - - -
EFXS_INIT
50/0/17 1 DOWN NONE - - -
EFXS_INIT
50/0/17 2 DOWN NONE - - -
EFXS_INIT
50/0/18 1 DOWN NONE - - -
EFXS_INIT
50/0/18 2 DOWN NONE - - -
EFXS_INIT
50/0/19 1 DOWN NONE - - -
EFXS_INIT
50/0/19 2 DOWN NONE - - -
EFXS_INIT
50/0/1 1 DOWN NONE - - -
EFXS_INIT
The SOAP request that was generated for same command:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="request"
xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0
http://gkar.cisco.com/schema/axlsoap.xsd">
<request xsi:type="ISexecCLI">
<ISexecCLI>
<CLI>show ephone-dn summary</CLI>
</ISexecCLI>
</request>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
SOAP response:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="response" xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0 srst-its.xsd">
<response xsi:type="ISexecCLIResponse">
<ISexecCLIResponse>1</ISexecCLIResponse>
</response>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Here's an invalid cli request "abcd":
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="request"
xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0
http://gkar.cisco.com/schema/axlsoap.xsd">
<request xsi:type="ISexecCLI">
<ISexecCLI>
<CLI>abcd</CLI>
</ISexecCLI>
</request>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response is also "1":
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="response" xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0 srst-its.xsd">
<response xsi:type="ISexecCLIResponse">
<ISexecCLIResponse>1</ISexecCLIResponse>
</response>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Here's a blank cli request:
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/1999/XMLSchema">
<SOAP-ENV:Body>
<axl xsi:type="request"
xmlns="http://www.cisco.com/AXL/1.0"
xsi:schemaLocation="http://www.cisco.com/AXL/1.0
http://gkar.cisco.com/schema/axlsoap.xsd">
<request xsi:type="ISexecCLI">
<ISexecCLI>
</ISexecCLI>
</request>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Response says blank is okay (0):
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
<http://schemas.xmlsoap.org/soap/envelope/> "
xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance
<http://www.w3.org/2000/10/XMLSchema-instance> "
xmlns:xsd="http://www.w3.org/1999/XMLSchema
<http://www.w3.org/1999/XMLSchema> ">
<SOAP-ENV:Body>
<axl xsi:type="response" xmlns="http://www.cisco.com/AXL/1.0
<http://www.cisco.com/AXL/1.0> "
xsi:schemaLocation="http://www.cisco.com/AXL/1.0
<http://www.cisco.com/AXL/1.0> srst-its.xsd">
<response xsi:type="ISexecCLIResponse">
<ISexecCLIResponse>0</ISexecCLIResponse>
</response>
</axl>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Subject: RE: CUCME
Replied by: CANDACE HOLMAN on 28-05-2009 04:27:56 PM
Is it possible that the ISExecCLI can only be used for configuration commands and not for 'show' commands?
Subject: RE: CUCME
Replied by: David Staudt on 28-05-2009 07:00:42 PM
Well, engineering confirms that the interface is intended for CLI configuration commands - unfortunately not 'show' commands.
ISgetExtension is available for retrieving individual phone info...as you probably are aware the level of details is not as great as via show ephone-dn. My understanding is that expanding the level of details reported via AXL to include all the ephone ephone-dn info is roadmapped for a future CME release.
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents