Status about update BLF via updateDeviceProfile and the error in wsld

[christophegauder2]

Good Morning, 

We recently upgraded our call manager to version 12.5.

We are using since version 8 AXL apis and updateDeviceProfile.

It is widely known that the WSDL definition has errors when dealing with BLFs and in the past, we corrected in the xsd file the famous 'minOccurs' filed.

https://community.cisco.com/t5/management/axl-bug-within-xbusylampfield-since-version-8/td-p/3584624

https://community.cisco.com/t5/management/xbusylampfield-specifies-minoccurs-1-which-contradicts/td-p/3576658

With the version 12.5, it seems not be working any more.

If we provide within busyLampFields a blfDest -> perfect, that's working.

If we do not provide it but gave  bldDirn + routePartition, we got the error (php) encoding object has no blfDest property.

We have a serious issue with this.

My Question : with 12.5, does someone known what to to   I have a serious issue.

Thank you for your time,

[dstaudt]

I've added a sample to this project that demonstrates a workaround using just Zeep code (without modifying the WSDL): https://github.com/CiscoDevNet/axl-python-zeep-samples/blob/master/axl_add_Phone_busyLampField.py

Re-reading your question, it seems you might be using PHP (the project above is Python-based) - not quite sure how to do the equivalent in PHP, but the XML sent should end up looking like this:

        <busyLampFields>
          <busyLampField>
            <blfDest>1000</blfDest>
            <index>1</index>
          </busyLampField>
          <busyLampField>
            <blfDirn>1234567890</blfDirn>
            <routePartition></routePartition>
            <index>2</index>
          </busyLampField>
        </busyLampFields>

but you need to trick your SOAP middleware into not including the blfDest/blfDirn fields without throwing a schema violation error...

[christophegauder2]

Thanks Dstaudt,

I find a way to correct the wsdl...