<HTML>
<HEAD>
<TITLE>Re: [OpenSIPS-Users] [NEW] SDP codec manipulation feature</TITLE>
</HEAD>
<BODY>
<FONT FACE="Tahoma, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:10pt'>Iñaki,<BR>
<BR>
>From a purely philosophical perspective, I have nothing to add. I don’t know.<BR>
<BR>
>From an application perspective, this is exactly what we’ve been waiting for. Even if it doesn’t function in all cases for everyone, it will function in most portions of our network where only G.711 and G.729 are used on unencrypted messaging. It’s perfect. It allows the scalability and “lightweight”-ness of a proxy while giving us very useful features we otherwise wouldn’t have. I can’t wait to test it.<BR>
<BR>
<BR>
- Jeff<BR>
<BR>
<BR>
<BR>
On 7/28/09 4:34 AM, "Iñaki Baz Castillo" <<a href="ibc@aliax.net">ibc@aliax.net</a>> wrote:<BR>
<BR>
Hi Andrei. <BR>
Please don't take me wrong, but is this a task for a proxy?
I wonder what would occur in the following cases:
- The UAC/UAS use encrypted SDP (S/MIME...).
- The UAC/UAS use multipart content (some devices do it for an INVITE).<BR>
<FONT COLOR="#0000FF"><BR>
</FONT>From some time I'm realizing that OpenSIPS is trying to behave as <BR>
a B2BUA, or it wants to manage dialogs (and it doesn't do it properly)
and now it handles the SDP (just in case the SDP comes not encrypted
in a single part body). Is it really the target of a proxy?
</SPAN></FONT>
</BODY>
</HTML>