<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 02/06/17 07:40 AM, Igor Olhovskiy
wrote:<br>
</div>
<blockquote cite="mid:3e7c816b-2b19-47a3-b58d-be2daacfcd46@Spark"
type="cite">
<title></title>
<div name="messageBodySection" style="font-size: 14px;">Hi!
<div><br>
</div>
<div>I’m trying to make RTPEngine to work with calls Browser
<-> SIP.</div>
<div>Call From SIP to Browser working perfectly, but when
calling to SIP from Browser, on 200 OK (sdp) I don’t receive </div>
<div>...</div>
<div>a=rtcp-mux<br>
</div>
<div>...</div>
<div>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</div>
<div><br>
</div>
<div>Reply route in a case of Browser->SIP call looks like</div>
<div><br>
</div>
<div>reply_route[REPLY_R] {</div>
<div>…</div>
<div> rtpengine_answer("internal external UDP/TLS/RTP/SAVPF
ICE=force rtcp-mux-offer");</div>
<div>...</div>
<div>}</div>
<div><br>
</div>
<div>Also I’ve tried with rtcp-mux-accept but still no luck</div>
</div>
</blockquote>
<br>
You cannot "offer" rtcp-mux an in "answer".<br>
<br>
I believe what you want is to use rtcp-mux-demux in the offer.<br>
<br>
Cheers<br>
</body>
</html>