09-15-2022 01:55 PM
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:
Response with a 500 error.
Solved! Go to Solution.
09-16-2022 11:56 AM - edited 09-16-2022 11:59 AM
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.
09-19-2022 01:30 PM
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
09-16-2022 07:15 AM
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 />
09-16-2022 11:56 AM - edited 09-16-2022 11:59 AM
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.
09-19-2022 01:30 PM
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
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