I tried the SDK4.1's example for the JSP axl call method (GroupMWI.jsp) but it doesn't seem to work. (I recompiled the CiscoIPPhoneSDK.jar to use the correct AXL path (https://cmserver:8443/axl/) but the example doesn't work. Here is my SOAP:XML call:
<SOAP-ENV:Body> <axl:getLine xmlns:axl="http://www.cisco.com/AXL/1.0\" xsi:schemaLocation="http://www.cisco.com/AXL/1.0 http://ccmserver/schema/axlsoap.xsd" sequence="1234"> <pattern>30036</pattern><routePartitionId>0335750A-7AEF-23F8-74EC-0858D114D6C7</routePartitionId><routeFilterId></routeFilterId>
</axl:getLine> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
According to the GroupMWI.jsp example, the POST is correct but it doesn't return the element <mwiStatus>. Anybody know how to correct this?
What is the response you get from the server?
Is 30036 s valid DN and is there a partition with pkid = 0335750A-7AEF-23F8-74EC-0858D114D6C7?
30036 is a valid DN in the partition, in fact, it's my extension. the pkid is also in the table. What else may I try to remedy the problem?
That seems rather telling to me.. could it be that your extension isn't in the partition you specified?
Run the axl command executeSQLQuery with the following query:
select dnorpattern, fkroutepartition from numplan where dnorpattern = '30036'
and post the result
This is what I get back
hmm... now that is weird.. they do look correct (I checked the first block and the last few digits). I think now it's time to turn on AXL debug logging, do the whole thing again, then look at the AXL traces using RTMT and look at entries that happen after you send the command from the client.
I've seen the AXL error not reflect what is really going wrong before.. looking at the server logs then cleared up the issue.
my hunch is that the example is not correct. The JSP code does this:
Then it parses out the partition id: NodeList partitionList = axlResultDoc.getElementsByTagName("routePartition");
What is returns isn't the pkid when I manually POST it to axl.
Then it sends out another axl request:
Does this seem right?