06-29-2022 10:49 AM
After updating call manager to 12.5 when trying to connect from UCDT to Call manager 12.5:
Axl error:
Connectivity Results: Axl test has failed, unable to connect to the server. We can connect to CUC on version 12.5.1 but not call manager 12.5.1
Here is log output:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <SOAP-ENV:Body> <axl:executeSQLQuery xmlns:axl="http://www.cisco.com/AXL/API/9.0" xsi:schemaLocation="http://www.cisco.com/AXL/API/9.0 http://<ip address>/schema/axlsoap.xsd" sequence="1656427838955"><sql>SELECT COUNT(*) FROM Device</sql></axl:executeSQLQuery> </SOAP-ENV:Body></SOAP-ENV:Envelope>
2022-06-28 09:50:38,955 [http-bio-8443-exec-7] INFO com.cisco.as.uctools.ucspt.provision.engine.provisioners.common.ProvisonerSSLClient connect - Connection to host:<ip address> on port:8443 Success
**Do we need to update: ="http://www.cisco.com/AXL/API/9.0" to ="http://www.cisco.com/AXL/API/12.5"??
If so where in the code is this variable so we can update it?
UCDT is out of support so any ideas would be greatly appreciated.
07-01-2022 11:50 AM
You shouldn't have to update the AXL that servers use internally. If it's sending 9.0 when all your servers are 12.5.1, that would be a defect, perhaps caused by a incomplete or corrupted upgrade. If you're sure all your servers are 12.5.1, I suggest opening a TAC case.
If you're talking about YOUR use of AXL, then yes, you need to change "http://www.cisco.com/AXL/API/9.0" to ="http://www.cisco.com/AXL/API/12.5". I don't know how you're using it - maybe you need to change your code, or if you're using SoapUI, load up a new project with the 12.5 WSDL.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide