[SR-Users] RTPEngine a=rtcp-mux

Igor Olhovskiy igorolhovskiy at gmail.com
Fri Jun 2 14:05:31 CEST 2017


Fixed.

In relay route added in

rtpengine_offer rtcp-mux-demux option.

Regards, Igor

On 2 июня 2017 г., 14:57 +0300, Richard Fuchs <rfuchs at sipwise.com>, wrote:
> On 02/06/17 07:40 AM, Igor Olhovskiy wrote:
> > Hi!
> >
> > I’m trying to make RTPEngine to work with calls Browser <-> SIP.
> > Call From SIP to Browser working perfectly, but when calling to SIP from Browser, on 200 OK (sdp) I don’t receive
> > ...
> > a=rtcp-mux
> > ...
> > lines, but it was told to RTPEngine on reply_route to add this. And this line is mandatory for me, cause I don’t control JS softphone on other side
> >
> > Reply route in a case of Browser->SIP call looks like
> >
> > reply_route[REPLY_R] {
> > …
> >   rtpengine_answer("internal external UDP/TLS/RTP/SAVPF ICE=force rtcp-mux-offer");
> > ...
> > }
> >
> > Also I’ve tried with rtcp-mux-accept but still no luck
>
> You cannot "offer" rtcp-mux an in "answer".
>
> I believe what you want is to use rtcp-mux-demux in the offer.
>
> Cheers
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20170602/785c1d96/attachment.html>


More information about the sr-users mailing list