Soap CISCO WebDialer API,AXIS引擎找不到要调用的目标服务
我正在尝试使用Cisco WebDialer API,但存在一些问题: 当我尝试发送以下SOAP请求时Soap CISCO WebDialer API,AXIS引擎找不到要调用的目标服务,soap,wsdl,cisco,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://schema
<?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:///webdialer/services/WebdialerSoapService70 通过浏览器,我收到以下消息:
AXIS error
No service is available at this URL
WebdialerSoapService
Hi there, this is an AXIS service!
Perhaps there will be a form for invoking the service here...
我的问题是怎么了?我的请求中是否有遗漏或所需服务未运行?
谢谢。好的,多亏了我的同事,我得到了答案。您需要转到以下链接:
https://SERVER:PORT/webdialer/services
您将看到所有工作服务的列表及其链接。就我而言,右链接是:
https://SERVER:PORT/webdialer/services/WebdialerSoapService
在我改变它之后,一切都开始工作了。是的,当您在浏览器中打开右链接时,您必须获得以下消息:
AXIS error
No service is available at this URL
WebdialerSoapService
Hi there, this is an AXIS service!
Perhaps there will be a form for invoking the service here...