Author Message
marilinacicerone
Joined: May 14, 2008
Messages: 0
Offline
Hi.

We are using a java client generated automatically from axis 1.4.
When we try to submit a provisioning request we receive from server the following error message: Procedure 'model' not present.
We receive this error for other kind of requests we submetted (i.e. Add station, List station, Add Hunt group).

Here there is an example of request we submetted.

POST /sms/SystemManagementService.php HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related, text/*
User-Agent: Axis/1.4
Host: 10.16.193.144:443
Cache-Control: no-cache
Pragma: no-cache
SOAPAction: "http://xml.avaya.com/ws/SystemManagementService/2005/04/04#soap_webservice#submitRequest"
Content-Length: 624
Authorization: Basic aW5hZHNAMTAuMTYuMTkzLjEzMDo1MDIyOmluZHNwdw==

<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<ns1:sessionID soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="1" xmlns:ns1="http://xml.avaya.com/ws/session">
</ns1:sessionID>
</soapenv:Header>
<soapenv:Body>
<model xmlns="">Station</model>
<operation xmlns="">display</operation>
<objectname xmlns=""></objectname>
<qualifier xmlns="">6793260</qualifier>
<fields xmlns=""></fields>
</soapenv:Body>
</soapenv:Envelope>

Response received from server is:

HTTP/1.1 500 Internal Service Error
Date Tue, 13 May 2008 13:54:31 GMT
Server Apache
X-Powered-By PHP/5.1.6
Content-Length 296
Connection close
Content-Type text/xml; charset=utf-8

XML received:
-----------------------------------------------
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>Procedure 'model' not present</faultstring>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
JohnBiggs
Joined: Jun 20, 2005
Messages: 1139
Location: Rural, Virginia
Offline
I can not simulate your message with my tools, but upon inspection your are not passing in a sessionID. If this is the initial request, then in my traces using the sms test tool

https://,ip-addr-of-AES>/sms/sms_test.php

I don't see the test application sending a session tag at all.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://xml.avaya.com/ws/SystemManagementService/2005/04/04" xmlns:ns2="http://xml.avaya.com/ws/session">
<SOAP-ENV:Header>
<ns2:sessionID SOAP-ENV:mustUnderstand="1" SOAP-ENV:actor="http://schemas.xmlsoap.org/soap/actor/next"/>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:submitRequest>
<model>Station</model>
<operation>display</operation>
<objectname></objectname>
<qualifier>40010</qualifier>
<fields>*</fields>
</ns1:submitRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

On a request where a session has been acquired I see the sessionID in the message:

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://xml.avaya.com/ws/SystemManagementService/2005/04/04" xmlns:ns2="http://xml.avaya.com/ws/session">
<SOAP-ENV:Header>
<ns2:sessionID SOAP-ENV:mustUnderstand="1" SOAP-ENV:actor="http://schemas.xmlsoap.org/soap/actor/next">f9f39c91227a51d0bded3fbe548a850f</ns2:sessionID>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:submitRequest>
<model>Station</model>
<operation>display</operation>
<objectname></objectname>
<qualifier>40010</qualifier>
<fields>*</fields>
</ns1:submitRequest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Hope that puts you on track....
John
HyoungjooLee2
Joined: Feb 12, 2007
Messages: 0
Offline
Hi,

The main problem is there is no <submitRequest> in your request. The <model>, <operation> .... should be subelement of <submitRequest>.

Thanks

hj
marilinacicerone
Joined: May 14, 2008
Messages: 0
Offline
Hi.
It seems that the problem comes when we generate client using Axis from SystemManagementService.wsdl.
In the client provided as example the method submitRequest is:
public ReturnType submitRequest(SubmitRequestType body);

otherwise in the code generated by us using Axis the method is:

public Result submitRequest(String model, String operation, String objectname, String qualifier, String fields)

So you can see that the input parameters and output object are different.

HyoungjooLee2
Joined: Feb 12, 2007
Messages: 0
Offline
Hi,

Which axis version are you using? The sample client code was generated by Axis 1.2 version. The generated slient stub code can be different depending on Axis version or your configuration. Even if they are diffetent, they refer the same thing.

Thanks
Go to:   
Mobile view