<div dir="ltr">Hello,<div><br></div><div>Thanks, I'll give that a try and post back. I guess I install and run it just like mediaproxy-ng?</div><div><br></div><div>I'll also try different sip clients like zoiper etc. </div>
<div><br></div><div>One thing that occurred to me based on the fact that the sdp is faulty, as I did this test from the slides here: <a href="http://www.slideshare.net/crocodilertc/webrtc-websockets">http://www.slideshare.net/crocodilertc/webrtc-websockets</a></div>
<div>I wonder if the configuration (from page 53 in the slides) need tweaking/fixing? Here's a snippet from my config: </div><div><br></div><div><div>failure_route[UA_FAILURE] {</div><div><span class="" style="white-space:pre"> </span>if ( t_check_status("488") && sdp_content() ) {</div>
<div><span class="" style="white-space:pre">                    </span>if ( sdp_get_line_startswith("$avp(mline)", "m=") ) {</div><div><span class="" style="white-space:pre">                                  </span>if ($avp(mline) =~ "SAVPF") {</div>
<div><span class="" style="white-space:pre">                                                    </span>$avp(rtpproxy_offer_flags) = "froc-sp";</div><div><span class="" style="white-space:pre">                                                  </span>$avp(rtpproxy_answer_flags) = "froc+SP";</div>
<div><span class="" style="white-space:pre">                                    </span>} else {</div><div><span class="" style="white-space:pre">                                                   </span>$avp(rtpproxy_offer_flags) = "froc+SP";</div><div><span class="" style="white-space:pre">                                                  </span>$avp(rtpproxy_answer_flags) = "froc-sp";</div>
<div><span class="" style="white-space:pre">                                    </span>}</div><div><span class="" style="white-space:pre">                                  </span>#<a href="http://www.slideshare.net/crocodilertc/webrtc-websockets">http://www.slideshare.net/crocodilertc/webrtc-websockets</a> p.53/60</div>
<div><span class="" style="white-space:pre">                    </span>}</div><div><span class="" style="white-space:pre">                  </span>append_branch();</div><div><span class="" style="white-space:pre">                   </span>rtpproxy_offer($avp(rtpproxy_offer_flags));</div>
<div><span class="" style="white-space:pre">                    </span>t_on_reply("RTPPROXY_REPLY");</div><div><span class="" style="white-space:pre">                    </span>route(RELAY);</div><div><span class="" style="white-space:pre">      </span>}</div>
<div>}</div><div>onreply_route[RTPPROXY_REPLY] {</div><div>        if (status =~ "18[03]") {</div><div>                # mediaproxy-ng only supports SRTP/SDES</div><div>                # early media won't work so strip it out now to avoid problems</div>
<div>                change_reply_status(180, "Ringing");</div><div>                remove_body();</div><div>        } else if (status =~ "2[0-9][0-9]" && sdp_content()) {</div><div>                rtpproxy_answer($avp(rtpproxy_answer_flags));</div>
<div>        }</div><div>}</div></div><div><br></div><div><br></div><div><br></div><div>cheers,</div><div>Olli</div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-03 17:00 GMT+03:00 Richard Fuchs <span dir="ltr"><<a href="mailto:rfuchs@sipwise.com" target="_blank">rfuchs@sipwise.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
<br>
This seems to be caused by an additional media stream (second m= line)<br>
appearing in the answer SDP, which is invalid according to RFC 3264.<br>
<br>
I'd like to invite you to try the upcoming new version of mediaproxy-ng<br>
instead, which has been renamed to rtpengine:<br>
<a href="https://github.com/sipwise/rtpengine" target="_blank">https://github.com/sipwise/rtpengine</a><br>
<br>
It's still being worked on (including finalizing the name change), but<br>
it should handle those multi-stream cases much better (especially when<br>
WebRTC clients are involved), even though I can't guarantee that it will<br>
fix your problem in particular, as it's an RTC violation.<br>
<br>
cheers<br>
<div class=""><br></div><br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br></div></div>