Hi Olle,<div><br></div><div>try with the XMLRPC from head and see if that works for you. I added the nested structure support to xmlrpc to dump our IMS usrloc structures and it works (lots of nests). If you have any hassles drop me a log file and I&#39;ll take a look</div>
<div><br></div><div>Cheers</div><div>Jason<br><br><div class="gmail_quote">On Fri, Jun 8, 2012 at 10:03 PM, Daniel-Constantin Mierla <span dir="ltr">&lt;<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
the lack of support for nested structures in replies of xmlrpc module should be fixed by commit:<br>
<br>
<a href="http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=fb3f37a0ba46bcb39a79a05465f512197a30da6b" target="_blank">http://git.sip-router.org/cgi-<u></u>bin/gitweb.cgi/sip-router/?a=<u></u>commit;h=<u></u>fb3f37a0ba46bcb39a79a05465f512<u></u>197a30da6b</a><br>

<br>
It is not yet backported, as I could see in the logs, but it should be.<br>
<br>
Cheers,<br>
Daniel<div class="HOEnZb"><div class="h5"><br>
<br>
On 6/8/12 4:28 PM, Olle E. Johansson wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi!<br>
<br>
When I run sercmd to test dispatcher.list I get a nice output<br>
<br>
sercmd&gt; dispatcher.list<br>
{<br>
        SET_NO: 2<br>
        SET: {<br>
                SET_ID: 1<br>
                DEST: {<br>
                        URI: sip:<a href="http://pstn1.astritech.org" target="_blank">pstn1.astritech.org</a>;<u></u>transport=udp2<br>
                        FLAGS: AX<br>
                        PRIORITY: 0<br>
                        ATTRS:<br>
                }<br>
                DEST: {<br>
                        URI: sip:<a href="http://pstn2.astritech.org" target="_blank">pstn2.astritech.org</a>;<u></u>transport=udp<br>
                        FLAGS: AX<br>
                        PRIORITY: 0<br>
                        ATTRS:<br>
                }<br>
                SET_ID: 2<br>
                DEST: {<br>
                        URI: sip:<a href="http://127.0.0.1:5080" target="_blank">127.0.0.1:5080</a><br>
                        FLAGS: AX<br>
                        PRIORITY: 200<br>
                        ATTRS:<br>
                }<br>
                DEST: {<br>
                        URI: sip:<a href="http://127.0.0.1:5084" target="_blank">127.0.0.1:5084</a><br>
                        FLAGS: AX<br>
                        PRIORITY: 50<br>
                        ATTRS:<br>
                }<br>
                DEST: {<br>
                        URI: sip:<a href="http://127.0.0.1:5082" target="_blank">127.0.0.1:5082</a><br>
                        FLAGS: IX<br>
                        PRIORITY: 10<br>
                        ATTRS:<br>
                }<br>
        }<br>
}<br>
<br>
When trying to use the same over XMLrpc I get this response<br>
<br>
HTTP/1.0 200 OK<br>
Via: SIP/2.0/TCP <a href="http://212.3.14.204:48603" target="_blank">212.3.14.204:48603</a><br>
Server: Alvondo Core - Bbtele, Sweden<br>
Content-Length: 220<br>
<br>
&lt;?xml version=&quot;1.0&quot;?&gt;<br>
&lt;methodResponse&gt;<br>
&lt;params&gt;<br>
&lt;param&gt;<br>
&lt;value&gt;&lt;struct&gt;&lt;member&gt;&lt;name&gt;<u></u>SET_NO&lt;/name&gt;&lt;value&gt;&lt;int&gt;2&lt;/<u></u>int&gt;&lt;/value&gt;&lt;/member&gt;&lt;member&gt;&lt;<u></u>name&gt;SET&lt;/name&gt;&lt;value&gt;&lt;/<u></u>struct&gt;<br>

&lt;/value&gt;<br>
&lt;/param&gt;<br>
&lt;/params&gt;<br>
&lt;/methodResponse&gt;<br>
<br>
<br>
<br>
Seems like the structure of the data in the dispacther list fails to be propagated in the xmlrpc interface. Is this possibly because of the structure of the data?<br>
<br>
The XMLRPC docs say<br>
<br>
&quot;1.3.4. Limitations<br>
<br>
SER xmlrpc modules does not implement all data types allowed in XML-RPC. As well it does not implement arrays and nested structures. &quot;<br>
<br>
Maybe we could implement a dispatcher.listflat that just publishes a flat list..<br>
<br>
<br>
/O<br>
______________________________<u></u>_________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>dev</a><br>
</blockquote>
<br></div></div><span class="HOEnZb"><font color="#888888">
-- <br>
Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a><br>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/<u></u>miconda</a><br>
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - <a href="http://asipto.com/u/katu" target="_blank">http://asipto.com/u/katu</a><br>
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - <a href="http://asipto.com/u/kpw" target="_blank">http://asipto.com/u/kpw</a></font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org" target="_blank">sr-dev@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>dev</a><br>
</div></div></blockquote></div><br></div>

<pre>This email is subject to the disclaimer of Smile Communications (PTY) Ltd. at http://www.smilecoms.com/disclaimer