[OpenSIPS-Users] rtpengine + manual SDP manipulations

[David Villasmil]

I believe you can use this:

replace

Similar to the flags list. Controls which parts of the SDP body should be
rewritten. Contains zero or more of:

   -

   origin

   Replace the address found in the *origin* (o=) line of the SDP body.
   Corresponds to *rtpproxy* o flag.
   -

   session connection or session-connection

   Replace the address found in the *session-level connection* (c=) line of
   the SDP body. Corresponds to *rtpproxy* c flag.


Have you tried this?

Regards,

David Villasmil
email: david.villasmil.work at gmail.com
phone: +34669448337


On Sat, Jan 18, 2020 at 3:59 PM Jeff Pyle <jeff at ugnd.org> wrote:

> Hello,
>
> I'm running OpenSIPS 2.4 and rtpengine 7.0.  I have the following commands
> in my script:
>
> route[sanitize_sdp] {
>         subst_body('/^o=\S+ /o=- /');
>         subst_body('/^s=.*/s=-\r/');
> }
>
> This works fine, unless I'm also using rtpengine, in which case these
> subst_body() changes are lost.  In the past with rtpproxy this worked as
> expected.
>
> I understand the potential conflicts when manipulating the SDP using
> multiple methods at the same time.  My question is if there is a way to
> execute this type of manual manipulation in a way that's compatible with
> rtpengine, or achieve similar results within the rtpengine module itself?
> My purpose is to remove the origin and session text if possible to further
> obfuscate source network information.
>
>
> - Jeff
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20200118/44ff498f/attachment.html>