Preview Tool

Cisco Bug: CSCvu98594 - CUCM - xsi:nil Not Working for Some updateUser Parameters

Last Modified

Sep 30, 2020

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

10.5(2.10000.5) 11.5(1.10000.6) 12.0(1.10000.10) 12.5(1.10000.22)

Description (partial)

API calls to CUCM may fail with a NullPointerException (seen in the CUCM AXL logs) if an application sends a tag with xsi:nil to CUCM rather than leaving it blank.

An element sent like this will result in a NullPointerException:

<ipccExtension xmlns:xsi="" xsi:nil="true"/>

However, <ipccExtension></ipccExtension> will work fine.  The non-working method should be an acceptable way to leave a field NULL, however, CUCM fails to process the request if it's used.

This occurs with convertUserAccount and nameDialing as well
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.