Hi.
It probably also should be noted, that the current implementation works
with a lot of different client implementations (we use Python for Nagios
and PHP for Management (both built-in XML-RPC as well as ZendFramework's
XML-RPC client)), so it cannot be that wrong.
Just my $0,02,
Carsten
2016-03-29 10:10 GMT+02:00 Daniel-Constantin Mierla <miconda(a)gmail.com>om>:
Hello,
I haven't originally implemented the rpc interface in Kamailio (which we
inherited via SER merge in 2008), but I expect to be some reason for this
behaviour, give the code is like 10 years old by now. A fault code is a
fault code, and if there was successful execution, then there was no fault.
It is why I asked to check the xmlrpc specifications, because they must
say what should be done in case of a successful execution without any data
to be returned.
If there is a problem with existing returned xml document, then of course
needs to be fixed. But adding a fault code when the specs don't say that,
it is not a fix, but breaking the specs.
Cheers,
Daniel
On 29/03/16 09:54, ycaner wrote:
Hello Daniel;
there is only rpc_send method in rpc module that dont have any code
and other parameters. it sends empty xml text. if it has parameters like
fault function , i think it will be useful.
Cheers.
<?xml version="1.0"?>
<methodResponse>
<params>
<param>
<value></value>
</param>
</params>
</methodResponse>
29.03.2016 10:32 tarihinde Daniel-Constantin Mierla-6 [via SIP Router]
yazdı:
Hello,
is this correct if there was no error? The fault node should be in case
of errors, not success. You should check the xmlrpc specs to be sure any
chance is conform with the requirements there.
Cheers,
Daniel
On 29/03/16 09:26, ycaner wrote:
hello;
i checked the rpc command and yes , you are right there isnt . i will
add a
rpc return code. it will look like if my pr is
accepted.
<?xml version="1.0"?>
<methodResponse>
<fault>
<value>
<struct>
<member>
<name>faultCode</name>
<value>
<int>200</int>
</value>
</member>
<member>
<name>faultString</name>
<value>
<string>domain is reloaded</string>
</value>
</member>
</struct>
</value>
</fault>
</methodResponse>
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/XML-RPC-reply-doesn-t-contain-any-d…
Sent from the Users mailing list archive at
Nabble.com.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
[hidden email] <http:///user/SendEmail.jtp?type=node&node=146897&i=0>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://www.asipto.com
http://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Kamailio World Conference, Berlin, May 18-20, 2016 -
<http://www.kamailioworld.com>http://www.kamailioworld.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
[hidden email] <http:///user/SendEmail.jtp?type=node&node=146897&i=1>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
------------------------------
If you reply to this email, your message will be added to the discussion
below:
http://sip-router.1086192.n5.nabble.com/XML-RPC-reply-doesn-t-contain-any-d…
To unsubscribe from XML-RPC reply doesn't contain any data, click here.
NAML
<http://sip-router.1086192.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
--
<http://www.netgsm.com.tr>
------------------------------
View this message in context: Re: XML-RPC reply doesn't contain any data
<http://sip-router.1086192.n5.nabble.com/XML-RPC-reply-doesn-t-contain-any-data-tp146894p146899.html>
Sent from the Users mailing list archive
<http://sip-router.1086192.n5.nabble.com/Users-f3.html> at
Nabble.com.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin
Mierlahttp://www.asipto.comhttp://twitter.com/#!/miconda -
http://www.linkedin.com/in/miconda
Kamailio World Conference, Berlin, May 18-20, 2016 -
http://www.kamailioworld.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Millerntorplatz 1
20359 Hamburg / Germany
mailto:carsten@ng-voice.com
Office +49 40 5247593-40
Fax +49 40 5247593-99
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben: