<div dir="ltr">One clarification:<div><br></div><div>I understand that the delay may be caused by handshaking and testing different ICE candidate pairs but it seems to happen even when the correct candidate from the WebRTC client (the <span style="color:rgb(0,0,0);font-size:1em">srflx one) </span>has the highest priority in the SDP.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 12, 2014 at 2:57 PM, Oleg Stolyar <span dir="ltr"><<a href="mailto:olegstolyar@gmail.com" target="_blank">olegstolyar@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi guys,<div><br></div><div>does anyone know what is causing media delay after the call is connected in this case?</div>
<div><br></div><div>Usually delays in WebRTC are caused by ICE candidate gathering and I am seeing that on my client (JsSip demo). However there is another delay in getting media after the call is connected. </div>
<div><br></div><div>I found an old Jira ticket where Anthony mentioned that on FS demo servers there is a 2.5 sec delay in answering but I could not find info on what is causing this delay. </div><div><br></div><div>It seems to me that FS does not need to gather ICE candidates since it can (and does) take the only candidate from the ext-rtp-ip variable.</div>
<div><br></div><div>So, why the delay?</div><div><br></div><div>Thank you</div><span class="HOEnZb"><font color="#888888"><div>Oleg</div></font></span></div>
</blockquote></div><br></div>