Hi Ovidiu,<div><br></div><div>see my comment inline.</div><div><br></div><div><br></div><div><div class="gmail_quote">2010/8/20 Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hello Carsten,<br>
<br>
If you want feedback, a new wiki page should give to users all the<br>
necessary information about this new functionality.<br>
The wiki page should provide a link to the location of the new<br>
rtpproxy code and the tarball should be removed from the git repo.<br></blockquote><div><br></div><div>I will add a Wiki-Page about this new feature next week.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Is there a chance to integrate this new functionality into the main<br>
rtpproxy project?<br></blockquote><div><br></div><div>There is no tracker like on the <a href="http://rtpproxy.org">rtpproxy.org</a> homepage. I will check next week, how i can add my patch to the project.</div><div><br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Also, this feature should be somehow standardized as rtpproxy is used<br>
by many SIP servers.<br>
There may be deployments where one instance of rtpproxy can serve<br>
simultaneously several different servers (sippy b2bua, ser, kamailio,<br>
opensips). How is this going to affect the functionality of this new<br>
feature?<br></blockquote><div><br></div><div>That should not be a problem. The functionality is acitivated using the API from rtpproxy and it is strictly implemented not to affect other implementations. E.g. sippy b2bua will use the unix-socket like now, ser, kamailio (early versions) or opensips will simply not use this function, unless (of course) adapted to do so.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Another possible scenario is having two kamailio servers using the<br>
same rtproxy: when an rtp timeout occurs, the timeout notification<br>
will it be sent to the right sever?<br></blockquote><div><br></div><div>Each server sends it's own (configurable) XML-RPC-Adress to the RTP-Proxy, so the RTP-Proxy can distinguish.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Running a version of rtpproxy from git trunk with extra functionality<br>
is not production ready. A patch to an official release would be more<br>
appealing for testing, but as I previously said, the best option would<br>
be to integrate this functionality into the main rtpproxy repo. Have<br>
you contacted the rtpproxy team about this new functionality?<br>
<br></blockquote><div><br></div><div>Not yet, but i will. </div><div><br></div><div>Carsten</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Regards,<br>
<font color="#888888">Ovidiu Sas<br>
</font><div><div></div><div class="h5"><br>
On Thu, Aug 19, 2010 at 3:33 PM, Carsten Bock <<a href="mailto:carsten@bock.info">carsten@bock.info</a>> wrote:<br>
> Hi Andrei,<br>
> You are totally correct. It is just for temporary non-local storage.<br>
> I wanted to do some more tests and i wanted to give others the possibility<br>
> to test and to give me feedback.<br>
> All changes should be fully backward compatible and the extension to the<br>
> RTP-Proxy is automatically en-/disabled using configure and autoconf.<br>
><br>
> Carsten<br>
> 2010/8/19 Andrei Pelinescu-Onciul <<a href="mailto:andrei@iptel.org">andrei@iptel.org</a>><br>
>><br>
>> On Aug 19, 2010 at 19:58, Carsten Bock <<a href="mailto:carsten@bock.info">carsten@bock.info</a>> wrote:<br>
>> > Module: sip-router<br>
>> > Branch: carstenbock/rtpproxy<br>
>> > Commit: 262e55278e8b8b0e853f00465c38e3a9d13694f0<br>
>> > URL:<br>
>> > <a href="http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=262e55278e8b8b0e853f00465c38e3a9d13694f0" target="_blank">http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=262e55278e8b8b0e853f00465c38e3a9d13694f0</a><br>
>> ><br>
>> > Author: Carsten Bock <<a href="mailto:lists@bock.info">lists@bock.info</a>><br>
>> > Committer: Carsten Bock <<a href="mailto:lists@bock.info">lists@bock.info</a>><br>
>> > Date: Thu Aug 19 19:55:01 2010 +0200<br>
>> ><br>
>> > - fixed identation<br>
>> > - added modified RTP-Proxy (rtpproxy.tar.gz, based on latest git, needs<br>
>> > some cleanup)<br>
>><br>
>> Wouldn't be better to add just a patch to the standard rtpproxy and/or<br>
>> provide a url where one could get the modified version?<br>
>> Having foreign tar.gz in the sr repository seems strange to me.<br>
>><br>
>> > (please note, that you have to have libcurl-dev and libxmlrpc-client<br>
>> > (same as for Kamailio-mi_xmlrpc) installed)<br>
>> > - some simple testing files (sample config, command line parameters for<br>
>> > pjsua (used for testing) and rtpproxy)<br>
>><br>
>> Would this module work also with the standard rtpproxy?<br>
>> Can it be compiled without the extra libs?<br>
>> If not, forking it might be a good idea (e.g. standard rtpproxy for<br>
>> easy upgrade and people that don't need the extra features and modified<br>
>> rtpproxy with more features).<br>
>><br>
>><br>
>> Andrei<br>
>><br>
>> _______________________________________________<br>
>> sr-dev mailing list<br>
>> <a href="mailto:sr-dev@lists.sip-router.org">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/cgi-bin/mailman/listinfo/sr-dev</a><br>
><br>
><br>
><br>
> --<br>
> Carsten Bock<br>
> Schomburgstr. 80<br>
> 22767 Hamburg<br>
> Germany<br>
><br>
> Mobile +49 179 2021244<br>
> Home +49 40 34927217<br>
> Fax +49 40 34927218<br>
> mailto:<a href="mailto:carsten@bock.info">carsten@bock.info</a><br>
><br>
> _______________________________________________<br>
> sr-dev mailing list<br>
> <a href="mailto:sr-dev@lists.sip-router.org">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/cgi-bin/mailman/listinfo/sr-dev</a><br>
><br>
><br>
<br>
_______________________________________________<br>
sr-dev mailing list<br>
<a href="mailto:sr-dev@lists.sip-router.org">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/cgi-bin/mailman/listinfo/sr-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Carsten Bock<br>Schomburgstr. 80<br>22767 Hamburg<br>Germany<br><br>Mobile +49 179 2021244<br>Home +49 40 34927217<br>Fax +49 40 34927218<br>mailto:<a href="mailto:carsten@bock.info">carsten@bock.info</a><br>
<br>
</div>