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

Mon Sep 30 06:50:05 EDT 2019

I am using below revision of rtpengine .
git-master-3102357

I have to update the rtpengine code to use this flag ?

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

On Mon, Sep 30, 2019 at 4:15 PM Sasmita Panda <spanda at 3clogic.com> wrote:

> Hi ,
>
> I have gone through the document , but not done with the changes yet .
>
> I have tried to run rtpengine with the flag "loop-protect" , according to
> the explanation , rtpengine has to insert the attribute "a=rtpengine:..."
> in the SDP . But this is not happening with me .
>
> Now I am suspecting , did you mean I have ti insert that attribute through
> opensips in the SDP body while sending command to the rtpenigne ?  May be I
> am asking a stupid question but I am stuck here .
> Nothing working for me . Please do help .
>
>
>
> *Thanks & Regards*
> *Sasmita Panda*
> *Senior Network Testing and Software Engineer*
> *3CLogic , ph:07827611765*
>
>
> On Fri, Sep 27, 2019 at 5:05 PM Giovanni Maruzzelli <gmaruzz at gmail.com>
> wrote:
>
>> there is documentation available:
>>
>> https://github.com/sipwise/rtpengine
>>
>> "
>> loop protect
>>
>> Inserts a custom attribute (a=rtpengine:...) into the outgoing SDP to
>> prevent *rtpengine* processing and rewriting the same SDP multiple
>> times. This is useful if your setup involves signalling loops and need to
>> make sure that *rtpengine* doesn't start looping media packets back to
>> itself. When this flag is present and *rtpengine* sees a matching
>> attribute already present in the SDP, it will leave the SDP untouched and
>> not process the message.
>> "
>>
>> On Fri, Sep 27, 2019 at 1:12 PM Sasmita Panda <spanda at 3clogic.com> wrote:
>>
>>> I am actually not getting how to do this .
>>>
>>> Somehow add_body_part changing the Content-Type header .
>>>
>>> Before adding this function :
>>> Content-Type: application/sdp
>>>
>>> After adding this function .
>>> Content-Type: multipart/mixed;boundary=OSS-unique-boundary-42
>>>
>>> --OSS-unique-boundary-42
>>> Content-Type: application/sdp
>>>
>>> This is get added .
>>>
>>> Whats the use of this . I think rather than this , I can add any custom
>>> header and compare that custom header before sending command to rtpengine .
>>> Will that work ?
>>>
>>>
>>> *Thanks & Regards*
>>> *Sasmita Panda*
>>> *Senior Network Testing and Software Engineer*
>>> *3CLogic , ph:07827611765*
>>>
>>>
>>> On Fri, Sep 27, 2019 at 1:26 PM Callum Guy <callum.guy at x-on.co.uk>
>>> wrote:
>>>
>>>> I think your syntax is wrong?
>>>>
>>>>
>>>> https://opensips.org/html/docs/modules/3.0.x/sipmsgops.html#func_add_body_part
>>>>
>>>>
>>>> On Fri, 27 Sep 2019 at 08:36, Sasmita Panda <spanda at 3clogic.com> wrote:
>>>>
>>>>> 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
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>
>>>>
>>>> *0333 332 0000  |  www.x-on.co.uk <http://www.x-on.co.uk>  |   **
>>>> <https://www.linkedin.com/company/x-on>   <https://www.facebook.com/XonTel>
>>>>   <https://twitter.com/xonuk> *
>>>>
>>>> X-on is a trading name of Storacall Technology Ltd a limited company
>>>> registered in England and Wales.
>>>> Registered Office : Avaland House, 110 London Road, Apsley, Hemel
>>>> Hempstead, Herts, HP3 9SD. Company Registration No. 2578478.
>>>> The information in this e-mail is confidential and for use by the
>>>> addressee(s) only. If you are not the intended recipient, please notify
>>>> X-on immediately on +44(0)333 332 0000 and delete the
>>>> message from your computer. If you are not a named addressee you must
>>>> not use, disclose, disseminate, distribute, copy, print or reply to this
>>>> email. Views or opinions expressed by an individual
>>>> within this email may not necessarily reflect the views of X-on or its
>>>> associated companies. Although X-on routinely screens for viruses,
>>>> addressees should scan this email and any attachments
>>>> for viruses. X-on makes no representation or warranty as to the absence
>>>> of viruses in this email or any attachments.
>>>>
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.opensips.org
>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>
>>
>> --
>> Sincerely,
>>
>> Giovanni Maruzzelli
>> OpenTelecom.IT
>> cell: +39 347 266 56 18
>>
>> _______________________________________________
>> 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/20190930/a9acab86/attachment.html>