topic Re: Getting AxlCode -1 error when addRemoteDestination in Management

Getting AxlCode -1 error when addRemoteDestination

Wynand Jordaan — Thu, 15 Sep 2022 20:55:51 GMT

Hi there,

We have recently upgraded to 12.5 and now the request that must add the Remote Destination fails with a -1 error. I have tried a setting a few other properties in the payload, but cannot get it to work. We are using .net to generate the SOAP request

My payload:

<?xml version="1.0" encoding="utf-8"?>

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Body>

<name>Mobile</name>

</lineAssociation>

</lineAssociations>

</remoteDestination>

</addRemoteDestination>

</soap:Body>

</soap:Envelope>

Response with a 500 error.

<?xml version='1.0' encoding='utf-8'?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Body>

<soapenv:Fault>

<faultcode>soapenv:Server</faultcode>

<request>addRemoteDestination</request>

</axlError>

</detail>

</soapenv:Fault>

</soapenv:Body>

</soapenv:Envelope>

There is no detail as why it fails, the Remote Destination Profile exists. I have found a few other issues on the forum similar to this, but all of them had a failure reason.

Kind regards,

Re: Getting AxlCode -1 error when addRemoteDestination

npetrele — Fri, 16 Sep 2022 14:15:41 GMT

Try the operation with SoapUI first. It's the easiest way to experiment with the request. Off-hand, I'm not sure if this xsi:nil="true" works:

But I do know that this works:

Re: Getting AxlCode -1 error when addRemoteDestination

dstaudt — Fri, 16 Sep 2022 18:59:28 GMT

Per npetrele, same with <dualModeDeviceName xsi:nil="true" />: I think you should provide only one of the three options in the request. Can you try ommitting the <dualModeDeviceName> and <ctiRemoteDeviceName> elements completely?

There is a Python sample for <addRemoteDestintion> here: https://github.com/CiscoDevNet/axl-python-zeep-samples/blob/master/axl_add_Remote_Destination.py
It includes some special code to work around an issue similar to what you're seeing above, though the error message reported in the defect (CSCvq98025) is different.

Re: Getting AxlCode -1 error when addRemoteDestination

Wynand Jordaan — Mon, 19 Sep 2022 20:30:50 GMT

I managed to solve the issue.

The problem was with the nil=true attributes that gets added by dotnet.

I had to remove the "IsNullable=true" on the C# XML attribute in the AXLAPIService file. So I think the WDSL is wrong when parsed for dotnet. I did have a look at CSCvq98025.

Thanks