CCM 6 AXL Serviciability HTTP or HTTPS?

Unanswered Question
Jan 1st, 2008

Hi,


I am having troubles trying to get data from the RisPort interface in CCM6.


As far as I understand the message should be sent to https://152.96.11.198:8443/realtimeservice/services/RisPort.


So a message should look like


Header:


POST /realtimeservice/services/RisPort HTTP/1.1

Host: AXLserver

Authorization: Basic xxxxx

Accept: text/*

Content-type: text/xml

SOAPAction: http://schemas.cisco.com/ast/soap/action/#RisPort#SelectCmDevice

Content-length: xxx



body:


<?xml version="1.0" encoding="utf-8" ?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://schemas.cisco.com/ast/soap/" xmlns:types="http://schemas.cisco.com/ast/soap/encodedTypes" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Header>

<tns:AstHeader id="id1">

<SessionId xsi:type="xsd:string">SessionId</SessionId></tns:AstHeader> </soap:Header>

<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">

<tns:SelectCmDevice>

<StateInfo xsi:type="xsd:string" />

<CmSelectionCriteria href="#id1"/></tns:SelectCmDevice><tns:CmSelectionCriteria id="id" xsi:type="tns:CmSelectionCriteria"><MaxReturnedDevices xsi:type="xsd:unsignedInt">10</MaxReturnedDevices><Class xsi:type="tns:DeviceClass">Any</Class><Model xsi:type="xsd:unsignedInt">255</Model><Status xsi:type="tns:CmDevRegStat">Registered</Status><NodeName xsi:type="xsd:string" /><SelectBy xsi:type="tns:CmSelectBy">Name</SelectBy><SelectItems xsi:type="tns:SelectItems"><SelectItem xsi:type="tns:SelectItem"><Item xsi:type="xsd:string">SEP00059A3C7800</Item></SelectItem></SelectItems></tns:CmSelectionCriteria></soap:Body></soap:Envelope>


My question is, can I just open a socket to the server on port 8443 and send the message? When trying this I get back strange characters. If I try to send it to port 8 tomcat returns web site was moved (obvious).

If I try to use the SSL mechanism (including certification) I use with the AXL interface, I get HTTP 500 error. Any help would be appreciated. Thanks.


cheers,

alej


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion