Geoffrey Carman | I made the following call: <soapenv:Envelope xmlns:ns="http://www.cisco.com/AXL/API/8.5" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header/> <soapenv:Body> <ns:updateDeviceProfile sequence="?"> <name>EM_Profile_70001</name> <mlppIndicationStatus>Off</mlppIndicationStatus> <preemption>Default</preemption> <lines> <lineIdentifier> <index>1</index> <label>Name New Last Name1 70001</label> <display>Name New Last Name1</display> <displayAscii>Name New Last Name1</displayAscii> <missedCallLogging>true</missedCallLogging> <directoryNumber>70001</directoryNumber> <routePartitionName>PT Line 1</routePartitionName> </lineIdentifier> </lines> </ns:updateDeviceProfile> </soapenv:Body> </soapenv:Envelope>
I got a success message: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <ns:updateDeviceProfileResponse xmlns:ns="http://www.cisco.com/AXL/API/8.5"> <return>{F4B7FAD3-B68A-6126-0848-0A54981BD67C}</return> </ns:updateDeviceProfileResponse> </soapenv:Body> </soapenv:Envelope>
That is returning the DeviceProfile GUID (Based on the URL I see in the CUCM Admin UI). This correctly changed the Line 1 assignment from 70005 to 70001 on the Device Profile named EM_Profile_70001. But none of the 'demographic' info changed. Am I missing something here? I do know that I changed from using <line> to <lineIdentifier> based on info provided in another thread, which was required to succeed at addDeviceProfile.
How do the <line> and sibling <lineIdentifier> interact, in the DeviceProfile API calls? |
| Please sign in to flag this as inappropriate. |