topic Re: AXL DB12 SOAPAction header correction needed: Api is malformed or in Management

AXL DB12 SOAPAction header correction needed: Api is malformed or miss

Jason Aarons — Mon, 24 Jan 2022 14:42:48 GMT

My request works fine in 14.0.1.10000-20 but gives back 599 unsupported header in 14.0.1.11900-132. DId something change in SU1 ? I have tried with both v12 and v14 database and fails with SU1. Works fine in older verson of CallManager 14, just not SU1.

[24/Jan/2022:05:23:04 +0000] 10.177.160.51 127.0.0.1 ctmodadmin - 8443 8443 POST /axl/ HTTP/1.0 200 309 479

2022-01-24 05:23:04,278 INFO [http-nio-9446-exec-9] filters.TimingFilter - Request 1642170059555 received from user1 at ip 172.26.6.1 was processed in 276ms
2022-01-24 05:23:04,390 WARN [http-nio-9446-exec-14] wrappers.RequestHeaderWrapper - Client sent an unsupported header, SOAPAction= ["CUCM:DB ver=12.0"], attempting to auto correct.
2022-01-24 05:23:04,390 WARN [http-nio-9446-exec-14] wrappers.RequestHeaderWrapper - SOAPAction header correction needed: Api is malformed or missing
2022-01-24 05:23:04,390 INFO [http-nio-9446-exec-14] filters.AuthenticationFilter - Write into Audit Log -->

Re: AXL DB12 SOAPAction header correction needed: Api is malformed or

npetrele — Mon, 24 Jan 2022 15:20:00 GMT

Did you download and use the AXLAPI.wsdl in axlsqltoolkit.zip from 14.0.1.11900-132?

What does your XML request look like? If the first line looks something like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/12.5">

(or 12.0 at the end) then you're using the wrong version. It should look like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/14.0">

Those are my guesses - could be something else.

Re: AXL DB12 SOAPAction header correction needed: Api is malformed or

dstaudt — Tue, 25 Jan 2022 17:49:23 GMT

I would not have expected anything about AXL behaviour to change in an SR.

Can you post the full HTTP packet contents of a sample request? Looking at the log message, the SOAPAction header you're sending is probably OK, but just in case...

If it is, then I would suggest opening a ticket with DevNet Developer Support so we can dig into the logs in more detail and possibly escalate to the AXL engineering team, as this could be a defect.

Re: AXL DB12 SOAPAction header correction needed: Api is malformed or

JaysonRCCL — Fri, 28 Jan 2022 15:57:55 GMT

2022-01-27 19:15:29 AXL Request
POST /axl/ HTTP/1.0
Host: 172.26.160.21:8443
SOAPAction: "CUCM:DB ver=12.0"
User-Agent: CTMaker2
Accept: text/*
Authorization: Basic Y3Rtb2RhZG1pbjo5d29uZGVyOA==
Content-Type: text/xml; charset="utf-8"
Content-Length: 1430

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/12.0"><soapenv:Body>
<ns:updatePhone>
<name>SEP14AEDB0C324A</name>
<lines><line uuid="{8FE74746-7FB6-67C0-6D2E-5F43439010CC}"><index>1</index><label>LASSE TASKINEN</label><display>LASSE TASKINEN</display><dirn uuid="{44087D2B-197C-07D2-7A38-FB8DE3F6812D}"><pattern>12620</pattern><routePartitionName uuid="{90767557-2476-4C11-93EB-EFF162A5AD10}">PAX_Cabin_PT</routePartitionName></dirn><ringSetting>Ring</ringSetting><consecutiveRingSetting>Use System Default</consecutiveRingSetting><ringSettingIdlePickupAlert xsi:nil="true"/><ringSettingActivePickupAlert xsi:nil="true"/><displayAscii/><e164Mask xsi:nil="true"/><dialPlanWizardId xsi:nil="true"/><mwlPolicy>Use System Policy</mwlPolicy><maxNumCalls>2</maxNumCalls><busyTrigger>1</busyTrigger><callInfoDisplay><callerName>true</callerName><callerNumber>true</callerNumber><redirectedNumber>true</redirectedNumber><dialedNumber>true</dialedNumber></callInfoDisplay><recordingProfileName/><monitoringCssName/><recordingFlag>Call Recording Disabled</recordingFlag><audibleMwi>Default</audibleMwi><speedDial xsi:nil="true"/><partitionUsage>General</partitionUsage><associatedEndusers/><missedCallLogging>true</missedCallLogging><recordingMediaSource>Gateway Preferred</recordingMediaSource></line></lines>
</ns:updatePhone>
</soapenv:Body>
</soapenv:Envelope>

2022-01-27 19:15:29 AXL Response (Retry=0)
HTTP/1.1 599
Set-Cookie: JSESSIONIDSSO=141EED10B568EDFD430506265D1FC099; Path=/; Secure; HttpOnly
Set-Cookie: JSESSIONID=0F81F19CEC3F4B89EC61367CE3784496; Path=/axl; Secure; HttpOnly
Content-Type: text/html;charset=utf-8
Content-Length: 2283
Date: Thu, 27 Jan 2022 18:15:29 GMT
Connection: close
Server:

<html> <head> <title> Cisco System - null </title> <style type="text/css"> a { color: #316984; text-decoration: none; } a:hover { color: #316984; text-decoration: underline; } a:visted { color: #316984; text-decoration: none; } body { background-attachment: fixed; background-color: #ffffff; background-repeat: no-repeat; color: #316984; font-family: arial,helvetica,sans-serif; } #content { border: 1px solid #d6d7d6; font-size: 93.5%; margin: 0px 10% 30px 10%; } #content-header { background-color: #eeeeee; border-bottom: 1px solid #666666; color: #666666; font-size: 124.5%; padding: 5px 15px 5px 15px; } #copyright { font-size: 75%; margin: 0px 10% 0px 10%; padding: 3px 0px 0px 0px; text-align: right; } img { display: block; margin: 0px 0px 20px 0px; } #logo { margin: 30px 10% 0px 10%; } p { padding: 5px 15px 5px 15px; } pre { padding: 5px 15px 5px 30px; } </style> </head> <body> <div id="logo"> <img src="/ciscologo.gif" alt="Cisco Systems, Inc." /> </div> <div id="content"> <div id="content-header">HTTP Status 599 – Incorrect axl version. Supported axl versions are 11.x, 12.x and 14.x. </div> <p> <b> type: </b> Status Report </p> <p> <b>Message: </b> Incorrect axl version. Supported axl versions are 11.x, 12.x and 14.x. </p> <p> <b>Description: </b> http.599 </p> </div> </body></html>

Re: AXL DB12 SOAPAction header correction needed: Api is malformed or

JaysonRCCL — Fri, 28 Jan 2022 17:40:46 GMT

2022-01-28 00:10:19,445 WARN [http-nio-9446-exec-3] wrappers.RequestHeaderWrapper - Client sent an unsupported header, SOAPAction= ["CUCM:DB ver=12.0"], attempting to auto correct.
2022-01-28 00:10:19,445 WARN [http-nio-9446-exec-3] wrappers.RequestHeaderWrapper - SOAPAction header correction needed: Api is malformed or missing
2022-01-28 00:10:19,445 INFO [http-nio-9446-exec-3] filters.AuthenticationFilter - Write into Audit Log -->
2022-01-28 00:10:19,446 INFO [http-nio-9446-exec-3] servletRouters.AXLAlpha - Executing api: getLine in axis

Re: AXL DB12 SOAPAction header correction needed: Api is malformed or

JaysonRCCL — Fri, 28 Jan 2022 20:02:59 GMT

Cisco Supported has escalated SR 692879057 to the BU for review of logs etc.

Re: AXL DB12 SOAPAction header correction needed: Api is malformed or

dstaudt — Fri, 28 Jan 2022 22:24:48 GMT

If the eventual solution is interesting, I would be curious to know what it was...

FYI:

Regular Cisco TAC/support generally does not support API/interface integration issues; apparently they are not demurring for this SR...more power to them 🙂

Cisco has a dedicated group - DevNet Developer Support - targeted at supporting developers/APIs. DevNet case tickets directly reach a team of dedicated API experts, who daily handle these kinds of API issues and can usually get to understanding/troubleshooting/resolution much quicker than TAC (who often end up sending the developer to DevNet in the end anyway...)

https://developer.cisco.com/site/support/

Re: AXL DB12 SOAPAction header correction needed: Api is malformed or

JaysonRCCL — Tue, 08 Feb 2022 13:05:41 GMT

They are still working on identifying a bug as nothing is supposed to change with AXL when applying a SU;

According to our BU engineers, the current issue:

What you are experiencing is the following:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/12.0">

Should be this instead:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/12.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

if you add the xmlns:xsi element to the tag, the request will work.

Re: AXL DB12 SOAPAction header correction needed: Api is malformed or

Jason Aarons — Tue, 07 Nov 2023 23:10:19 GMT

Just to clarify there was an undocumented change in CallManager 14 SU2. If you add the xmlns:xsi element to the tag, the request will work