AXL for CUCM 9.1 - listPhone "DevicePoolName" filter not working?

[Daniel Krenzel]

I'm calling "listPhone" with filter 'abc%' for devicePoolName and it returns all phones including ones for which the device pool name doesn't match. I can filter by "name" without any issues. Is it broken or am I missing something?

[Daniel Krenzel]

I'm using python suds but here's the raw XML going out:

<?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.cisco.com/AXL/API/9.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP-ENV:Header/>

  <ns0:Body>

  <ns1:listPhone>

    <searchCriteria>

      <devicePoolName>bc%</devicePoolName>

    </searchCriteria>

    <returnedTags>

      <name></name>

    </returnedTags>

  </ns1:listPhone></ns0:Body></SOAP-ENV:Envelope>

[dstaudt]

This appears to be working OK on my 10.5 system:

<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:listPhone>
        <searchCriteria>
            <devicePoolName>abc1%</devicePoolName>
        </searchCriteria>
        <returnedTags>
            <name/>
            <devicePoolName/>
        </returnedTags>
      </ns:listPhone>
  </soapenv:Body>
</soapenv:Envelope>
-------------------------------------
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Body>
      <ns:listPhoneResponse xmlns:ns="http://www.cisco.com/AXL/API/9.1">
        <return>
            <phone uuid="{1B7A5861-A2DE-65B9-46C7-47D6C06703A4}">
              <name>BOTDSTAUDT</name>
              <devicePoolName uuid="{ED0A1AC1-1656-D869-DD30-AADDDB87434A}">abc1</devicePoolName>
            </phone>
        </return>
      </ns:listPhoneResponse>
  </soapenv:Body>
</soapenv:Envelope>

If you are running on CUCM 9.1 and still experiencing the problem, I would recommend opening a DevNet Developer Support ticket so we can investigate via the detailed AXL logs and escalate with engineering if needed: Cisco DevNet: DevNet Developer Support