updateConferenceBridge fails

Version 1
    This document was generated from CDN thread

    Created by: Darin Burleigh on 12-04-2013 10:09:38 AM
    I can add CFBs via AXL just fine. The remove and get methods work correctly.  And I can update the CFB with the CCM admin interface. But the update method fails with the non-descriptive error code -1. I've seen this with both CM 8.0 and 9.1. Usually I see the '-1' error when the request is incorrect, but I don't see anything wrong. This is the request that fails. I've also tried with other elements (e.g. locationName, etc.)    
    <updateConferenceBridge>
        <name>Test-cfb</name>
        <description>Test Conference Bridge2</description>
    </updateConferenceBridge>

    Subject: RE: updateConferenceBridge fails
    Replied by: David Staudt on 17-04-2013 05:02:37 PM
    On my 9.1(1) system the following seems to work:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/9.1">
       <soapenv:Header/>
       <soapenv:Body>
          <ns:updateConferenceBridge sequence="1">
             <name>CFB232094029348</name>
             <description>CFBtest1</description>
             <locationName>Phantom</locationName>
          </ns:updateConferenceBridge>
       </soapenv:Body>
    </soapenv:Envelope>
    -----------------------
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
       <soapenv:Body>
          <ns:updateConferenceBridgeResponse sequence="1" xmlns:ns="http://www.cisco.com/AXL/API/9.1">
             <return>{BE8F2D4B-FD11-CD51-754A-BE0DC6E16BE7}</return>
          </ns:updateConferenceBridgeResponse>
       </soapenv:Body>
    </soapenv:Envelope>

    The admin UI seems pretty strict about the formatting of the name, i.e. 'CFB' - perhaps your non-standard CFB name is causing a problem?  Note that the locationName has to be from one of the previously configured Locations (System/Location Info/Location).  Enabling and examining the detailed AXL logs (see FAQ) may provide some additional clue...

    Subject: RE: updateConferenceBridge fails
    Replied by: Darin Burleigh on 29-04-2013 03:08:49 PM
    I still keep getting the '-1', even with your example. I tested against  both 8.5 and 9.1. I don't see this with any other 'Update' operations.
    I know its not the location - I get a sensible error message when I use an invalid location.

    I'll try looking at the logs.
     

    Subject: RE: updateConferenceBridge fails
    Replied by: Darin Burleigh on 29-04-2013 04:25:57 PM
    The log file had:
    2013-04-29 14:45:44,300 ERROR [http-bio-443-exec-7] axlapiservice.AXLAPIServiceS
    keleton - com.cisco.www.axlapiservice.AXLAPIServiceSkeleton@575d7e
    java.lang.NullPointerException

    I figured it must be a field I was leaving out. I found that the required field is securityProfileName.
    Everything works now.
    So now I'm wondering why I need this column? The WSDL indicates that it is optional. And it appears that David Staudt doesn't need it. Strange.