Incorrect WSDL

Version 1
    This document was generated from CDN thread

    Created by: Enda McManemy on 21-08-2013 10:01:05 AM
    Posted this message here as have already posted it on
    but have received no feedback.
    I have downloaded the AXLAPI.WSDL file for both version 7.1 and 8.6 of Call Manager.Neither file contains the API methods relating to LicenseCapabilities• getLicenseCapabilities
    • updateLicenseCapabilities  Both API methods are available on both versions and documented.The axlsoap.xsd file contains references to these but I would have expected these to be listed as an "operation" in the WSDL.Any reason for this?
    If the WSDL does not conatin all supported API methods it is effiectively useless.

    Subject: RE: Incorrect WSDL
    Replied by: David Staudt on 21-08-2013 12:30:06 PM
    Checking the AXLAPI.wsdl associated with 8.5 (covers 8.6), both operations seem to be there:
    1<operation name="getLicenseCapabilities"><soap:operation soapAction="CUCM:DB ver=8.5 getLicenseCapabilities" style="document"/><input><soap:body use="literal"/></input><output><soap:body use="literal"/></output></operation>
    3<operation name="updateLicenseCapabilities"><soap:operation soapAction="CUCM:DB ver=8.5 updateLicenseCapabilities" style="document"/><input><soap:body use="literal"/></input><output><soap:body use="literal"/></output></operation>
    soapUI imports the WSDL and the license requests are auto generated like the others.  The request works:
     1POST HTTP/1.1
     2Accept-Encoding: gzip,deflate
     3Content-Type: text/xml;charset=UTF-8
     4SOAPAction: "CUCM:DB ver=8.5 getLicenseCapabilities"
     5Authorization: Basic QWRtaW5pc3RyYXRvcjpjaXNjbyExMjM=
     6Content-Length: 314
     8Connection: Keep-Alive
     9User-Agent: Apache-HttpClient/4.1.1 (java 1.5)
    11<soapenv:Envelope xmlns:soapenv="" xmlns:ns="">
    12   <soapenv:Header/>
    13   <soapenv:Body>
    14      <ns:getLicenseCapabilities sequence="1">
    15         <userid>dstaudt</userid>
    16      </ns:getLicenseCapabilities>
    17   </soapenv:Body>
     1HTTP/1.1 200 OK
     2Set-Cookie: JSESSIONIDSSO=CFFEC482BA174B4C45E2A2E0FD9274CB; Path=/; Secure
     3Set-Cookie: JSESSIONID=9CCBFBC87E46FD699E955EC9D6CFBA08; Path=/axl; Secure
     4Content-Type: text/xml;charset=UTF-8
     5Content-Length: 461
     6Date: Wed, 21 Aug 2013 17:24:26 GMT
     9<soapenv:Envelope xmlns:soapenv="">
    10  <soapenv:Body>
    11    <ns:getLicenseCapabilitiesResponse xmlns:ns="">
    12      <return>
    13        <licenseCapabilities uuid="{56B5979D-695B-7D5D-429F-596AC1D75DE6}">
    14          <userid>dstaudt</userid>
    15          <enableUps>true</enableUps>
    16          <enableUpc>true</enableUpc>
    17        </licenseCapabilities>
    18      </return>
    19    </ns:getLicenseCapabilitiesResponse>
    20  </soapenv:Body>
    The WSDL for 7.1 seems to also contain these...can you clarify?  Are you making these requests against another version of UCM?

    Subject: RE: Incorrect WSDL
    Replied by: Enda McManemy on 22-08-2013 03:39:46 AM
    I download Cisco CallManager AXL SQL Toolkit from CUCM System version: Unzipped the file and navigated to the file schema\7.1\AXLAPI.wsdl.
    The WSDL does not contain either of these methods.

    I download Cisco CallManager AXL SQL Toolkit from CUCM System version:
    Unzipped the file and navigated to the file schema\8.5\AXLAPI.wsdl. You are correct It does contain these methods.

    CUCM is still supported within our organisation, I had hoped to build a generic service using the WSDLs from the supported CUCM platforms however the fact that the WSDL does not conatin all supported API methods renders this approach effiectively useless regardless of the version.