CISCO WebDialer API,AXIS引擎无法找到要调用的目标服务

时间:2014-10-22 06:05:04

标签: soap wsdl cisco

我正在尝试使用Cisco WebDialer API,但它有一些问题:

当我尝试发送以下SOAP请求时

<?xml version="1.0" encoding="utf-8" ?> 
 <soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:urn="urn:WD70">
    <soapenv:Header/>
    <soapenv:Body>
       <urn:makeCallSoap soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
          <in0 xsi:type="urn:Credential">
             <userID xsi:type="xsd:string">user******</userID>
             <password xsi:type="xsd:string">pass*****</password>
          </in0>
          <in1 xsi:type="soapenc:string" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">1234</in1>
          <in2 xsi:type="urn:UserProfile">
             <user xsi:type="xsd:string">wd</user>
             <deviceName xsi:type="xsd:string">SEP001558C8970F</deviceName>
             <lineNumber xsi:type="xsd:string">901234565</lineNumber>
             <supportEM xsi:type="xsd:boolean">false</supportEM>
             <locale xsi:type="xsd:string">English</locale>
             <dontAutoClose xsi:type="xsd:boolean">false</dontAutoClose>
             <dontShowCallConf xsi:type="xsd:boolean">true</dontShowCallConf>
          </in2>
       </urn:makeCallSoap>
    </soapenv:Body>
 </soapenv:Envelope>

https://SERVER:PORT/webdialer/services/WebdialerSoapService70我收到以下错误:

The AXIS engine could not find a target service to invoke!  targetService is WebdialerSoapService70

当我尝试通过浏览器直接访问https:/// webdialer / services / WebdialerSoapService70时,我收到以下消息:

AXIS error
No service is available at this URL

我的问题是什么问题?我的请求中是否遗漏了某些内容,或者所需的服务未运行? 谢谢。

1 个答案:

答案 0 :(得分:0)

好的,感谢我的同事,我得到了答案。您需要转到以下链接:

https://SERVER:PORT/webdialer/services

您将看到所有工作服务的列表以及指向它们的链接。在我的情况下,右链接是:

https://SERVER:PORT/webdialer/services/WebdialerSoapService

在我改变它之后,一切都开始起作用了。是的,当您在浏览器中打开右侧链接时,您必须收到以下消息:

WebdialerSoapService
Hi there, this is an AXIS service!
Perhaps there will be a form for invoking the service here...