updateRemoteDestination fails to accept todAccessName but todAccess works

Version 1
    This document was generated from CDN thread

    Created by: Sascha Monteiro on 24-11-2013 05:05:57 PM
    oddly enough, the schema specifies todAccessName, but when used it throws a nullpointerexception in cucm,
    todAccess works, but is aginst the documented (9.1) schema

    Subject: RE: updateRemoteDestination fails to accept todAccessName but todAccess wor
    Replied by: Sascha Monteiro on 24-11-2013 05:32:07 PM
    hm, even though it was accepted and a correct updateRemoteDestinationResponse was returned, the database wasn't updated with the todAccess
    1<ns:updateRemoteDestination sequence="?">
    2<uuid>{4D37061A-4B65-AADC-42DF-07B5E9602351}</uuid>
    3<todAccess>TOD-RD-4d37061a-4b65-aadc-42df-07b5e9602351</todAccess>
    4</ns:updateRemoteDestination>
    5
    6<ns:updateRemoteDestinationResponse xmlns:ns="http://www.cisco.com/AXL/API/9.1" sequence="?">
    7<return>{4D37061A-4B65-AADC-42DF-07B5E9602351}</return>
    8</ns:updateRemoteDestinationResponse>