08-20-2019 03:38 PM
11.5 schema
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Body>
<ns0:addRemoteDestination xmlns:ns0="http://www.cisco.com/AXL/API/11.5">
<remoteDestination>
<name>rd-test</name>
<destination>8675309</destination>
<answerTooSoonTimer>1500</answerTooSoonTimer>
<answerTooLateTimer>19000</answerTooLateTimer>
<delayBeforeRingingCell>4000</delayBeforeRingingCell>
<ownerUserId>testuser</ownerUserId>
<enableUnifiedMobility>true</enableUnifiedMobility>
<remoteDestinationProfileName>RDP-Test</remoteDestinationProfileName>
<isMobilePhone>true</isMobilePhone>
<enableMobileConnect>true</enableMobileConnect>
</remoteDestination>
</ns0:addRemoteDestination>
</soap-env:Body>
</soap-env:Envelope>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring/>
<detail>
<axlError>
<axlcode>-1</axlcode>
<axlmessage/>
<request>addRemoteDestination</request>
</axlError>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
I have tried putting in a user that doesn't exist and I get a valid error response. For this though, all I get is the -1 error. Any thoughts? Thanks in advance.
Solved! Go to Solution.
08-20-2019 07:51 PM
I ran into this when the target Remote Destination Profile did not have a Line associated...might check?
08-20-2019 07:51 PM
I ran into this when the target Remote Destination Profile did not have a Line associated...might check?
08-20-2019 10:22 PM
Also found an issue with the AXL schema (11.5/12.5) which causes Python Zeep to fail unexpectedly on <addRemoteDestination>. I did find a workaround and added a sample to this collection: https://github.com/CiscoDevNet/axl-python-zeep-samples
08-21-2019 09:19 AM
That was the issue. I appreciate it.
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