We all know AXL isn't exactly as great as it's hyped to be and since we're all bound to run into the same issues, why not compile a list of what's wrong. It'll also make pressuring Cisco into fixing AXL once and for all easier.
So I'll go first:
User: the <firstname> and <lastname> element are written <firstName> and <lastName> respectively when you make a getUser despite the documentation saying otherwise. adduser and updateuser use the proper notation.
CCM Version: 4.1.3
Hmm.. why can't I edit my posts anymore?
Either way, this time it's not a false alarm:
The 4.1.3 documentation says one return element is phoneTemplate with an uuid attribute. However, in the response, there's a phoneTemplateID element without attributes instead and the uuid is given as text of the phoneTemplateID element.
In addDeviceProfile, the service then expects the proper phoneTemplate with an uuid.
Another one: The following XML is invalid, yet it is accepted:
The result is a new line 12345, forward to voicemail is set but everything below is ignored (alertingname and duration). What should happen is an error that the statement is invalid as alertingName must come after callForwardNoAnswer.
When adding/updating a HuntPilot it accepts and updates all values bar ForwardNoAns and Busy.
It returns sucess but does to make any changes to them
what about updateCallPickupGroup for updating members in CCM 4.1(3). I have experienced that if I want to update the list and don't include the currently being updated callpickupgroup it deletes itself from the list, and if I include it in the update list then I get duplicate value error. I am wondering if this is a bug. Anyone encountered this?
Adding MTPs and Conference Bridges apparently doesn't work either: http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=IP%20Communications%20and%20Video&topic=IP%20Phone%20Services%20for%20Developers&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1ddb83b7
In CCM 4.2 method "listUserByName" is not working with "*" character.
If we search for lastname = "*" CCM answers with BAD SEARCH FILTER.
My workaround is to change "*" to "* " because this filter seems to work. (But not sure...)
Note that in CCM 4.1 this method was not bugged!!!!
CCM Version 4.2
in XCallForward info the duration element can be a negative number.
When making a getLineReq in complexType GetNumPlanPattern pattern is defined as nillable="false" this should be changed.
in complexType XPhone - it's simply missing this information
modified the complexType by adding the phoneTemplateId under numberOfButtons
THERE IS NO ldapRN attribute
move userid attribute to where ldapRN is!
in AddPhoneReq there are 2 problems with XCallingSearchSpace
in the schema it requires the XCallingSearchSpace to have a name. This is not actually required (or was just causing me a bug in my java code)
in addition members can also be null.