[OpenSIPS-Users] engage_rtp_proxy()

[Miha]

ok tnx. I understand documentation on wrong way.

But then, what is the difference with  using rtpproxy offer, answer ?


br

mia


On 31/05/2016 14:17, Sasmita Panda wrote:
> If there is sdp in ACK and u wanted to engage rtp proxy , the  you 
> have to write it inside ACK also ... By writing for INVITE cant help 
> you to update ACK also . For 200 OK , you must write it in reply route .
>
> */Thanks & Regards/*
> /Sasmita Panda/
> /Network Testing and Software Engineer/
> /3CLogic , ph:07827611765/
>
> On Tue, May 31, 2016 at 5:35 PM, Johan De Clercq <johan at democon.be 
> <mailto:johan at democon.be>> wrote:
>
>     put it also in reply route.
>
>     2016-05-31 13:42 GMT+02:00 Miha <miha at softnet.si
>     <mailto:miha at softnet.si>>:
>
>         HI
>
>         if I use engage_rtp_proxy(), I can use it only on initial
>         INVITE and opensips should automatically rewritten also 200 OK
>         and ACK with SDP, right?
>         But when I am using this function, I can see from trace that
>         only SDP for initial invite is rewritten, 200 ok with sdp is
>         not changed. Must I do something else?
>
>         Rtpproxy is not running in bridge mode.
>
>
>         tnx
>         miha
>
>
>
>         _______________________________________________
>         Users mailing list
>         Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>         http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160531/88d78aa3/attachment-0001.htm>