Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Issues with RisPort - No Handler found for SelectCmDevice


I am getting "No Handler found for SelectCmDevice" when i am trying to send the following soap message :

<soap:Envelope xmlns:soap="" xmlns:soapenc="" xmlns:tns="" xmlns:types="" xmlns:xsi="" xmlns:xsd=""><soap:Header><tns:AstHeader id="id1"> <SessionId xsi:type="xsd:string">1234-20060201020721</SessionId></tns:AstHeader></soap:Header> <soap:Body soap:encodingStyle=""><tns:SelectCmDevice> <CmSelectionCriteria href="#id1"/></tns:SelectCmDevice><tns:CmSelectionCriteria id="id1" xsi:type="tns:CmSelectionCriteria"> <MaxReturnedDevices xsi:type="xsd:unsignedInt">10</MaxReturnedDevices> <Class xsi:type="tns:DeviceClass">Phone</Class> <Model xsi:type="xsd:unsignedInt">255</Model> <Status xsi:type="tns:CmDevRegStat">Any</Status> <SelectBy xsi:type="tns:CmSelectBy">Name</SelectBy> <SelectItems href="#id2"/> </tns:CmSelectionCriteria><soapenc:Array id="id2" soapenc:arrayType="tns:SelectItem[1]"> <Item href="#id3"/></soapenc:Array><tns:SelectItem id="id3" xsi:type="tns:SelectItem"> <Item xsi:type="xsd:string">SEP00054B9C1D45</Item></tns:SelectItem> </soap:Body></soap:Envelope>


I am getting response as

<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="" xmlns:SOAP-ENV=""><SOAP-ENV:Header/><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>No Handler found for SelectCmDevice</faultstring><detail><axl:Error xmlns:axl=""><axl:code>5003</axl:code><axl:message>No Handler found for SelectCmDevice</axl:message><request>SelectItem</request></axl:Error></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

Please help me out how to get rid of this issue.


Re: Issues with RisPort - No Handler found for SelectCmDevice

CCM returns a fault SOAP request with HTTP error, which usually would mean an internal HTTP server error. you might have used the wrong (AXL) URL instead of using the\realtimeservice URL...

New Member

Re: Issues with RisPort - No Handler found for SelectCmDevice


Thanks a lot for your response. Now i used \realtimeservice... URL and i am getting "no SOAPAction header" fault message. Here is my request :

POST /axl/ HTTP/1.1


Authorization: Basic Y2NtYWRtaW5pc3RyYXRvcjpub3Q0dTJj

Accept: application/soap+xml, text/*

Content-type: text/xml;charset=utf-8 ;


Content-length:1327" xmlns:soapenc="" xmlns:tns="" xmlns:types="" xmlns:xsi="" xmlns:xsd="">

1234-20060201020721"> 10 Phone 255 Any Name SEP00054E4B1D28

Please help me out to get rid of this error.

New Member

Re: Issues with RisPort - No Handler found for SelectCmDevice

Is there a soap or http header that requires the AXL service url?

New Member

Re: Issues with RisPort - No Handler found for SelectCmDevice

I see. In this case, you have to set the request-uri as the soap:address url from the Service Definitions in RisPort.wsdl, instead of /axl/, which is the Service Definition for AXLAPI.wsdl.