[OpenSIPS-Users] Need some clarification in rtpengine module .

[Sasmita Panda]

How I will add a attribute in the SDP body . In the rtpengine module there
is no flag which will add a attribute directly .

If I am doing like below

add_body_part("$var(body)", "a=sdpmangled:yes\r\n");

Its not adding this attribute in the body . Is there any other option
to do this ?

*Thanks & Regards*
*Sasmita Panda*
*Senior Network Testing and Software Engineer*
*3CLogic , ph:07827611765*


On Thu, Sep 26, 2019 at 7:37 PM Bogdan-Andrei Iancu <bogdan at opensips.org>
wrote:

> Hi Sasmita,
>
> Not sure if rtpengine has a similar built-in feature (their doc is
> something that can be improved :P), but you can achieve the same from
> script level I guess (adding and testing that SDP 'a' line).
>
> Best regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   https://www.opensips-solutions.com
> OpenSIPS Summit 2019
>   https://www.opensips.org/events/Summit-2019Amsterdam/
>
> On 9/24/19 9:42 AM, Sasmita Panda wrote:
>
> Hi All,
>
> rtpengine and rtpproxy module somehow plays same role with some advance
> features in rtpengine .
>
> There is a parameter in rtpproxy module " nortpproxy_str " through which
> we can manage the involvement  of rtpproxy in the call leg .
>
> modparam("rtpproxy", "nortpproxy_str", "a=sdpmangled:yes\r\n")
>
> In rtpengine there is no such parameter having similar functionality .
> Is there any other way which will behave similarly in rtpengine .
>
> Basically what I wanted to do is , in a call having 2 different leg .
> If in one leg rtpengine is already involved ,
> I don,'t want to involved rtpengine again in the other leg .
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20190927/80ddf26a/attachment-0001.html>