Hello,<br><br> as Daniel correctly pointed me out I need to clarify my statements on the seas branch commits.<br><br>the commits were not actually 'back'ported, but 'forward'ported since they were old commits from openser/kamailio and opensips. Then for the licensing and IP of those changes, the t_uac_cancel was a commit I did myself in the past, so it has BSD license. for the dlg_add_extra commit, it was done by Andrei Pisau on behalf of VozTelecom who agree to license it as BSD, so no problems to integrate those on tm.<br>
<br>Elias<br><br><div class="gmail_quote">On Wed, Feb 3, 2010 at 1:09 AM, Elias Baixas <span dir="ltr"><<a href="mailto:elias.baixas@voztele.com" target="_blank">elias.baixas@voztele.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Ok, i've just created ebaixas/fixing_seas, take a look if you will, and lets prepare a merge of my changes into the master.<br><br>some things I am unsure about my modifications to tm are:<br><br>-backported dlg_add_extra from opensips, which lets me copy [local,remote] Display Name into struct dlg/loc_dname,rem_dname<br>
(I just thought that I didn't remember to add the piece of code to free that shared mem from dlg when the dialog is destroyed. TODO)<br><br>-backported t_uac_cancel from opensips, which lets me cancel a branch, but also adding some new headers to the CANCEL (the uac cancel function in ser doesn't let adding new headers, and this is needed for AppServer)<br>
<br>-backported build_uac_cancel needed for t_uac_cancel<br><br>-in t_reply_with_body changed arguments of type char* to str* and the functions using this accordingly (I think :P )<br><br>everything else are changes in seas module itself.<br>
<br>those changes include some important fixes to seas that break the binary-protocol compatibility with the application server. This are needed changes that are not yet published to the public WeSIP/seas-JAIN release. I have uploaded an updated seas-jain compatible with the new protocol to <a href="http://www.baixas.net/seas-jain.jar" target="_blank">http://www.baixas.net/seas-jain.jar</a>, get it if you need.<br>
<br>at the moment the seas module just compiles with the master sip-router. remains to see if it actually works. this is work I plan to do on the next months, at the moment I can't guarantee everything works as it did/should.<br>
<br>best regards,<br><font color="#888888"><br>Elias</font><div><div></div><div><br><br><div class="gmail_quote">On Tue, Feb 2, 2010 at 9:51 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<div><div></div><div><br>
<br>
On 2/2/10 9:26 PM, Jan Janak wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
On 02-02 19:36, Elias Baixas wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello all,<br>
<br>
I have been working on the seas module to make it work on sip-router. I<br>
have my own git branch locally, but I'd like to share it on the sip-router<br>
public git so that others can take a look and finally push it to the<br>
master branch.<br>
<br>
it needs some transaction-module changes, so it needs good review from<br>
other more tm-knowledgable coders before it can be finally merged.<br>
<br>
where do I need to send my public ssh key to get commit access to the<br>
sip-router git ?<br>
<br>
</blockquote>
That's great, I actually also started working on making the seas module<br>
compile, so if you want you can send the patches to me and I'd be happy to review and commit the changes to tm and other places.<br>
<br>
I'd be also happy to do some testing becase I was going to use it this week.<br>
<br>
Regarding the ssh, you can send it to either Daniel or myself and we'll give<br>
you access.<br>
<br>
</blockquote></div></div>
ssh access should be up, hopefully I haven't forgot anything and just works now :-)<br>
<br>
Cheers,<br><font color="#888888">
Daniel<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>