<div dir="ltr"><div class="gmail_extra">Hi,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Parallel forking works when none of clients connect over WenSocket.</div><div class="gmail_extra"><br></div><div class="gmail_extra">
I think i should explain my scenario in a better way.</div><div class="gmail_extra"><br></div><div class="gmail_extra">when one web socket and one sip end point registered. when i make call to kamailio using ICE and webrtc RTP profile RTP/SAVPF in SDP (using some ICE attributes), then call is forked to two end points (webrtc and sip end point) and call successfully goes to webrtc client and SIP end point.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Webrtc client rings and can answer the call as well. But SIP end point returns 488 not acceptable here because of RTP profile RTP/SAVPF so it fails.</div><div class="gmail_extra">
<br></div><div class="gmail_extra">Now the question is there any way i can modify SDP RTP profile when call is forked to normal sip end point. <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks in advance.<br>
<br><br><br><div class="gmail_quote">On Sat, Dec 22, 2012 at 6:40 PM, Peter Dunkley <span dir="ltr"><<a href="mailto:peter.dunkley@crocodile-rcs.com" target="_blank">peter.dunkley@crocodile-rcs.com</a>></span> wrote:<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">configuration</blockquote></div><br><br clear="all"><div><br>
</div><div><br></div><div><br></div></div></div>