<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Also, I recommend you move to use sip.js instead of jssip. They are fairly similar but sip.js is more up to date and maintained.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 12, 2015, at 10:42 AM, Brian West <<a href="mailto:brian@freeswitch.org" class="">brian@freeswitch.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Update your FreeSWITCH, If you wish to use WebRTC you MUST use master, or at least something more recent than last July. :P </div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Feb 12, 2015 at 4:08 AM, Oleg Stolyar <span dir="ltr" class=""><<a href="mailto:olegstolyar@gmail.com" target="_blank" class="">olegstolyar@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hi guys,<div class=""><br class=""></div><div class="">Sorry for a long email.</div><div class=""><br class=""></div><div class="">I ran into this strange problem a couple of time over the last year where my Freeswitch stops receiving or sending SIP signals from and to WebRTC (JsSip) profile.</div><div class=""><br class=""></div><div class="">At the same time, SIP signals are coming through just fine on a different profile which is regular SIP.</div><div class=""><br class=""></div><div class="">It lasted for about 15 min.</div><div class=""><br class=""></div><div class="">When the problem was over, I saw a bunch of BYE signals being sent to the WebRTC users at about the same for all the calls that ended during these 15 min.</div><div class=""><br class=""></div><div class="">Also, INVITEs from these users that were sent during the 15 minutes actually got through (or at least showed in the logs) after the problem cleared.</div><div class=""><br class=""></div><div class="">I have a fairly old FS - master from July 2014 but was wondering if anyone else had this problem.</div><div class=""><div class=""><br class=""></div></div><div class="">There are no errors in the logs and I cannot reproduce this at will.</div><div class=""><br class=""></div><div class="">One possibility is that the network connection is somehow holding up these signals rather than FS. So, I was wondering when during the process of sending SIP signals over WebRTC does it get recorded in the log? Is it when the sending is successful or as soon as it's attempted? This could tell me whether FS doesn't even try to send the signal during this problem period or whether it's trying but cannot get through to the network somehow.</div><div class=""><br class=""></div><div class="">Another piece of information - calls that were connected before the problem started continued just fine and the media kept coming through.</div></div>
</blockquote></div></div></div></blockquote></div><br class=""></div></body></html>