<div dir="ltr"><div><div><div>I think all the items proposed in the first section would be great additions. The items in the second look more implementation specific, but I can see the uses.<br><br></div>I think that items 1a and 1b should also have the reverse options present as well. Normalize everything to long form and expand all headers. I think this would be great for interoperability as some older platforms struggle with short form (or mixed form) and consolidated headers. <br><br></div>Also, the ability to specify all the options in section 1 on a dialog direction would also be great. I.E create_dialog("sL") would compact all headers to short form for the caller side and normalize everything to long form for the callee side. create_dialog("lS") would do the opposite. The idea here is that support for a format is going to be endpoint specific, so being able to set it once at dialog creation would be helpful.<br><br></div>Regards,<br><br>Ryan Bullock<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 30, 2014 at 3:47 AM, Răzvan Crainea <span dir="ltr"><<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div><tt>Hi, Yavari!<br>
<br>
Of course, this will also impact the performance, but I don't
think it will be something considerable, since we will not
compress large amount of data.<br>
Our current tests show that for a 1024 bytes long buffer
compression/decompression time takes less than 200us for
compression and 25us for decompression on a comodity computer.
Since this will only be done on edge nodes, I don't think it has
such a big impact on the platform.<br>
<br>
Best regards,<br>
</tt><span class="">
<pre cols="72">Răzvan Crainea
OpenSIPS Solutions
<a href="http://www.opensips-solutions.com" target="_blank">www.opensips-solutions.com</a></pre></span><div><div class="h5">
On 09/30/2014 10:26 AM, H Yavari wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div style="color:#000;background-color:#fff;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:10px">
<div dir="ltr"><font><span>Hi to all,</span></font></div>
<div style="color:rgb(0,0,0);font-size:10px;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;background-color:transparent;font-style:normal" dir="ltr"><font><span>This is an amazing
idea, but I have a question about the performance, the
compression/decompression process is not any bottleneck
for the system performance? or any effect on process
power?<br>
</span></font></div>
<div style="color:rgb(0,0,0);font-size:10px;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;background-color:transparent;font-style:normal" dir="ltr"><font><br>
<span></span></font></div>
<div style="color:rgb(0,0,0);font-size:10px;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;background-color:transparent;font-style:normal" dir="ltr"><font><span>Regards,</span></font></div>
<div style="color:rgb(0,0,0);font-size:10px;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;background-color:transparent;font-style:normal" dir="ltr"><span><font>H.Yavari</font><br>
</span></div>
<div style="color:rgb(0,0,0);font-size:10px;font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;background-color:transparent;font-style:normal" dir="ltr"><span></span></div>
<div><br>
</div>
<div style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,sans-serif;font-size:10px">
<div style="font-family:HelveticaNeue,Helvetica Neue,Helvetica,Arial,Lucida Grande,Sans-Serif;font-size:12px">
<div>
<hr size="1"> <font face="Arial"> <b><span style="font-weight:bold"></span></b></font><br>
<div dir="ltr">On 03.09.2014 11:59, Saúl Ibarra Corretgé
wrote:<br clear="none">
> Hi Razvan,<br clear="none">
><br clear="none">
> On 02 Sep 2014, at 18:25, Răzvan Crainea <<a shape="rect" href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>>
wrote:<br clear="none">
><br clear="none">
>> 2)Compressing the SIP message (using gzip). The
idea is to take the SDP body and several headers that
are not used in the routing logic, compress them, apply
a base64 transformation and add to the message's body. A
use case for this is a platform that has several edge
servers (SBCs) and a few core instances - when entering
the platform the message compression should be applied
and then sent to the core servers. Inside the core
networks, the messages should be carried in the
compressed format to reduce the bandwidth. When leaving
the network, the message has to be decompressed and
forwarded to the next gateway without any compression,
since the other equipments might not understand them.<br clear="none">
>> There will be several functions exported in the
script:<br clear="none">
>><br clear="none">
>> a) compress_msg("1","Header1|Header2");
compresses the body of the message and listed headers<br clear="none">
>> b) decompress_msg(); decompress both headers
and body<br clear="none">
>><br clear="none">
>> What do you think about this approach? Is this
something you find useful? Since we don't have a final
decision for this topic, we are looking for more input
from you guys.Anybody is welcome to throw any kind of
useful feedback on this matter, so don't be shy!<br clear="none">
>><br clear="none">
><br clear="none">
> IIRC this is not standard, and Apple uses it
somewhere on their FaceTime implementation. Kamailio has
it and someone was working on a patch for PJSIP, but
other than that I’m not sure how useful it is, servers
could use TCP between them.<br clear="none">
It is not indeed, but the main idea is to first help you
with better <br clear="none">
handling traffic inside your network (which may be up to
3 or 4 OpenSIPS <br clear="none">
boxes when you have a distributed platform) ; handling
means bandwidth <br clear="none">
and processing as parsing SIP messages - like headers
(maybe 20) or body <br clear="none">
you do not care about and you just want to carry through
without a need <br clear="none">
to parse and look.<br clear="none">
<br clear="none">
And maybe in the future it will be some progress into <br clear="none">
standardization....for now I see the real need for it
(at least for me:) ).<br clear="none">
<br clear="none">
Regards,<br clear="none">
Bogdan
<div><br>
<br>
</div>
<div><br clear="none">
<br clear="none">
_______________________________________________<br clear="none">
Users mailing list<br clear="none">
<a shape="rect" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br clear="none">
<a shape="rect" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br clear="none">
</div>
</div>
<br>
<br>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>