2009/7/23 andrei dragus <[email protected]>:
>
> Hello,
>
> Methods have been added for SDP codec manipulation in the textops module.
> Please update your module if you wish to use them.
>
> There are 4 methods:
>  codec_exists(name[,clock]); //test if a codec exists
>  codec_delete(name[,clock]); //delete a codec
>  codec_move_up(name[,clock]); //move a codec to the front of the list
>  codec_move_down(name[,clock]);//move a codec to the back of the list
>
> Each of them can take a codec name and an optional clock parameter. If the 
> clock is unspecified all of the codecs with that name will match.
>
> All of the methods will act on all streams from all sessions inside the SDP.

Hi Andrei. 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).

From some time I'm realizing that OpenSIPS is trying to behave as 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?

Regards.



-- 
Iñaki Baz Castillo
<[email protected]>

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to