Cisco Bug: CSCvv49103 - updatePhone API With Empty VendorConfig Writes Incorrect deviceXML to Database
Oct 08, 2020
- Cisco Unified Communications Manager (CallManager)
Known Affected Releases
10.5(2.10000.5) 11.5(1.10000.6) 11.5(1.18900.98) 11.5(1.21000.34) 12.0(1.10000.10) 12.5(1.10000.22)
Symptom: This is breakage due to this fix that went into SU8. CSCvs29317 XMLNS Added to XML Data in UpdatePhone API When Single Vendor Config Option Provided The issue is caused because they are sending an empty vendor config tag in the updatePhone request: <vendorConfig></vendorConfig> Because of the fix for CSCvs29317, if the vendor config tag is empty, for some reason we are mistakenly updating the deviceXML in the database to the text ‘<xml-fragment>’: execute procedure dbWriteDeviceXML('8473de53-e13b-51f9-ee0d-24feae9e7aaf','<xml-fragment>') Because this an incomplete XML tag (there is an open with no close) that is causing the error in the getPhone API when we try and retrieve the deviceXML from the database: 2020-08-18 14:12:55,426 DEBUG [http-bio-443-exec-20] axlapiservice.Handler - execute function dbReadDeviceXML('8473de53-e13b-51f9-ee0d-24feae9e7aaf') 2020-08-18 14:12:55,433 DEBUG [http-bio-443-exec-20] axlapiservice.Handler - com.cisco.www.axlapiservice.GetPhoneHandler@1c53c43 org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 31; The element type "xml-fragment" must be terminated by the matching end-tag "</xml-fragment>". Conditions: Customer uses CUCDM or some other front end tool for multiple cluster management through AXL calls. Customer is using CUCM 188.8.131.5200.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases