<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: CUCM API error - Automation Anywhere - Could not parse the WSDL https://10.20.3.85:8443/axl/ for SOAP request in Call Control</title>
    <link>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422059#M3111</link>
    <description>&lt;P&gt;Have not used AXL with ServiceNow, however based on the screenshot, I would note that CUCM does not serve the AXL WSDL itself by URL - you have to download it via the AXL SQL Toolkit from the CUCM admin "Applications" menu.&lt;/P&gt;
&lt;P&gt;So, in&amp;nbsp; 'Connect to WSDL by' would probably need to be 'File', uploading the AXLAPI.wsdl file from the Tookit, and "Address location (optional)" would need to be the actual CUCM host AXL endpoint, e.g. "&lt;A href="https://cucmserver:8443/axl/" target="_blank"&gt;https://cucmserver:8443/axl/&lt;/A&gt;'&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, the AXLAPI.wsdl file refers-to/imports an additional schema file AXLSoap.xsd, which is necessary for WSDL-based automation to use the WSDL.&amp;nbsp; It doesn't appear that the ServiceNow form anticipates this possibility...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You might be able to combine the AXLAPI.wsdl and AXLSoap.xsd into a single, larger AXLAPI.wsdl, i.e. by replacing the &amp;lt;import ... /&amp;gt; line in AXLAPI.wsdl with the entire contents of AXLSoap.xsd (minus its first &amp;lt;?XML ...?&amp;gt; line).&lt;/P&gt;</description>
    <pubDate>Tue, 22 Jun 2021 18:37:18 GMT</pubDate>
    <dc:creator>dstaudt</dc:creator>
    <dc:date>2021-06-22T18:37:18Z</dc:date>
    <item>
      <title>CUCM API error - Automation Anywhere - Could not parse the WSDL https://10.20.3.85:8443/axl/ for SOAP request</title>
      <link>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4421621#M3110</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are sending SOAP web service from Automation anywhere towards CUCM and we are getting below error .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;"Could not parse the WSDL &lt;A href="https://10.20.3.85:8443/axl/" target="_blank" rel="noopener"&gt;https://10.20.3.85:8443/axl/&lt;/A&gt; for SOAP request."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can anyone 1 guide how we can resolve this issue . Same is working with POSTMAN .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attched screenshot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance .&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jun 2021 08:44:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4421621#M3110</guid>
      <dc:creator>Vinod.s</dc:creator>
      <dc:date>2021-06-22T08:44:02Z</dc:date>
    </item>
    <item>
      <title>Re: CUCM API error - Automation Anywhere - Could not parse the WSDL https://10.20.3.85:8443/axl/ for SOAP request</title>
      <link>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422059#M3111</link>
      <description>&lt;P&gt;Have not used AXL with ServiceNow, however based on the screenshot, I would note that CUCM does not serve the AXL WSDL itself by URL - you have to download it via the AXL SQL Toolkit from the CUCM admin "Applications" menu.&lt;/P&gt;
&lt;P&gt;So, in&amp;nbsp; 'Connect to WSDL by' would probably need to be 'File', uploading the AXLAPI.wsdl file from the Tookit, and "Address location (optional)" would need to be the actual CUCM host AXL endpoint, e.g. "&lt;A href="https://cucmserver:8443/axl/" target="_blank"&gt;https://cucmserver:8443/axl/&lt;/A&gt;'&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;However, the AXLAPI.wsdl file refers-to/imports an additional schema file AXLSoap.xsd, which is necessary for WSDL-based automation to use the WSDL.&amp;nbsp; It doesn't appear that the ServiceNow form anticipates this possibility...&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You might be able to combine the AXLAPI.wsdl and AXLSoap.xsd into a single, larger AXLAPI.wsdl, i.e. by replacing the &amp;lt;import ... /&amp;gt; line in AXLAPI.wsdl with the entire contents of AXLSoap.xsd (minus its first &amp;lt;?XML ...?&amp;gt; line).&lt;/P&gt;</description>
      <pubDate>Tue, 22 Jun 2021 18:37:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422059#M3111</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2021-06-22T18:37:18Z</dc:date>
    </item>
    <item>
      <title>Re: CUCM API error - Automation Anywhere - Could not parse the WSDL https://10.20.3.85:8443/axl/ for SOAP request</title>
      <link>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422200#M3114</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;SPAN class="user-badges-list"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/168718"&gt;@dstaudt&lt;/a&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Cisco-Employee lia-component-message-view-widget-author-username"&gt;Thanks for your help .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Cisco-Employee lia-component-message-view-widget-author-username"&gt;Now i can see some different error " &lt;SPAN&gt;401 Unauthorized. Authentication failed for SOAP URI "&amp;nbsp;&lt;/SPAN&gt;attached .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Cisco-Employee lia-component-message-view-widget-author-username"&gt;Application user is correct with there role - standard axl api access . Attached .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Cisco-Employee lia-component-message-view-widget-author-username"&gt;I was thinking i have to add credential in header or link but not sure how to perform this ….&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Cisco-Employee lia-component-message-view-widget-author-username"&gt;Waiting for your kind response&amp;nbsp; .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="UserName lia-user-name lia-user-rank-Cisco-Employee lia-component-message-view-widget-author-username"&gt;Thanks&amp;nbsp; .&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 01:39:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422200#M3114</guid>
      <dc:creator>Vinod.s</dc:creator>
      <dc:date>2021-06-23T01:39:01Z</dc:date>
    </item>
    <item>
      <title>Re: CUCM API error - Automation Anywhere - Could not parse the WSDL https://10.20.3.85:8443/axl/ for SOAP request</title>
      <link>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422206#M3115</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also tried with Basic Authorization but issue is still same for Auth. See attachment ,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please let me know if i miss something here .&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks .&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 02:12:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422206#M3115</guid>
      <dc:creator>Vinod.s</dc:creator>
      <dc:date>2021-06-23T02:12:01Z</dc:date>
    </item>
    <item>
      <title>Re: CUCM API error - Automation Anywhere - Could not parse the WSDL https://10.20.3.85:8443/axl/ for SOAP request</title>
      <link>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422810#M3119</link>
      <description>&lt;P&gt;Not sure what the difference is for credential/variable/insecure-string: maybe try credential?&lt;/P&gt;
&lt;P&gt;AXL requires Basic auth, with base64-encoded credentials in "username:password" format.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, make sure the AXL service URL includes the trailing '/' as this is significant.&lt;/P&gt;
&lt;P&gt;If you can get the service to provide you with the raw HTTP request it is sending to AXL, that may prove helpful&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 19:38:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422810#M3119</guid>
      <dc:creator>dstaudt</dc:creator>
      <dc:date>2021-06-23T19:38:44Z</dc:date>
    </item>
    <item>
      <title>Re: CUCM API error - Automation Anywhere - Could not parse the WSDL https://10.20.3.85:8443/axl/ for SOAP request</title>
      <link>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422955#M3120</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/168718"&gt;@dstaudt&lt;/a&gt;&amp;nbsp; , &lt;SPAN&gt;AXL service URL includes the trailing '/' as this is significant Is works for me .&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your guidance .&lt;/P&gt;</description>
      <pubDate>Thu, 24 Jun 2021 05:20:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/call-control/cucm-api-error-automation-anywhere-could-not-parse-the-wsdl/m-p/4422955#M3120</guid>
      <dc:creator>Vinod.s</dc:creator>
      <dc:date>2021-06-24T05:20:50Z</dc:date>
    </item>
  </channel>
</rss>

