Getting AxlCode -1 error when addRemoteDestination

[Wynand Jordaan]

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>

        <addRemoteDestination xmlns="http://www.cisco.com/AXL/API/12.5">

            <remoteDestination xmlns="">

                <name>Mobile</name>

                <destination>6666</destination>

                <answerTooSoonTimer>1500</answerTooSoonTimer>

                <answerTooLateTimer>19000</answerTooLateTimer>

                <delayBeforeRingingCell>1000</delayBeforeRingingCell>

                <ownerUserId>8test</ownerUserId>

                <enableUnifiedMobility>True</enableUnifiedMobility>

                <remoteDestinationProfileName>RDP74860B1ED9D0</remoteDestinationProfileName>

                <ctiRemoteDeviceName xsi:nil="true" />

                <dualModeDeviceName xsi:nil="true" />

                <isMobilePhone>True</isMobilePhone>

                <enableMobileConnect>True</enableMobileConnect>

                <lineAssociations>

                    <lineAssociation>

                        <pattern>444555013</pattern>

                        <routePartitionName>UO009_MTB</routePartitionName>

                    </lineAssociation>

                </lineAssociations>

                <todAccessName xsi:nil="true" />

                <mobileSmartClientName xsi:nil="true" />

                <mobilityProfileName xsi:nil="true" />

                <singleNumberReachVoicemail>True</singleNumberReachVoicemail>

                <accessListName />

            </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>

            <faultstring></faultstring>

            <detail>

                <axlError>

                    <axlcode>-1</axlcode>

                    <axlmessage></axlmessage>

                    <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,

[npetrele]

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:

<ctiRemoteDeviceName xsi:nil="true" />

But I do know that this works:

<ctiRemoteDeviceName />

[dstaudt · Accepted solution]

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.

[Wynand Jordaan · Accepted solution]

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