Guest

Preview Tool

Cisco Bug: CSCvj13354 - minOccurrs incorrect for XRemoteDestination remoteDestinationProfileName and dualModeDeviceName

Last Modified

May 08, 2018

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

11.5(1.10000.1) 12.0(1.10000.1)

Description (partial)

Symptom:
SOAP Fault indicates "At a time you can associate Remote Destination Profile either with Remote device or dual mode device"

Conditions:
Attempting to add or update a Remote Destination Profile. Issue is schema defines remoteDestinationProfileName and dualModeDeviceName with a minOccurs of 1, but only one of these two should be defined, not both.

Related Community Discussions

minOccurs settings for remoteDestinationProfileName and dualModeDeviceName in XRemoteDestination
Hi Cisco folks, The schema definition for XRemoteDestination includes the follows: <xsd:element maxOccurs= "1" minOccurs= "1" name= "remoteDestinationProfileName" nillable= "true" type= "axlapi:XFkType" > and <xsd:element maxOccurs= "1" minOccurs= "1" name= "dualModeDeviceName" nillable= "true" type= "axlapi:XFkType" /> This is annotated as such: <xsd:annotation>   <xsd:documentation> If you are giving value to dualModeDeviceName then you can't give value to remoteDestinationProfileName,viceversa ...
Latest activity: Apr 24, 2018
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)
  • 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.