AXL 12.0 List Users API if not functioning as expected

[nilluru]

We have been using AXL listUsers api to retrieve users from Cisco ACE call manager clusters. Recently we started seeing the duplicate entries of users (12-40 entries for each user depends on the no.of users on the cluster). I am not sure if there are any recent schema changes resulted cartesian results sent to the callers.

We are using AXL 12.0 library. Can someone please take a look and update what caused this to fail?

[npetrele]

What version(s) of call manager are you using?  I don't know if there's an issue with using AXL 12.0 with earlier versions of call manager, but it's not something I would recommend. I'd advise you to use an AXL version that matches your call manager version.

If there's a problem with AXL or call manager, you can open a support case here:

https://developer.cisco.com/site/support/

[dstaudt]

Looks like this defect https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvv98281

Symptom:
AXL API returns duplicate entries during SQL query of end users.

Conditions:
This will happen for any endusers with the following criteria:
1. The enduser has a primary extension defined in the End User page.
2. The primary extension is assigned to a partition and that partition is assigned to multiple Calling Search Spaces.

Workaround:
Remove the end user's primary extension.

The defect appears resolved in CUCM 12.5(1.14900.18) - customers should be able to request an 'engineering special' release with the fix from TAC. A possible workaround from the AXL side would be to use <executeSqlQuery> against the 'endusers' table, but that could involve extra joins and other complications depending on what data you needed from <listUsers>