To answer the other question, I did not try pinging the host while the problems were occurring, but I was able to call back in with no problem only a few seconds after I got dropped (less than 20), so if it is a network issue it would have to have been very brief.
--StephenOn Mon, May 4, 2009 at 10:52 PM, Stephen Crosby <stevecrozz@gmail.com> wrote:
Network problem is what I'm still thinking. Take a look at this log snippet:
http://pastebin.freeswitch.org/8813
I'm CALLER_A, and you can see me calling back in on line 8 after I got dropped. But that was only seconds prior. There really seems to be nothing in the log at the time the calls were dropped.
--StephenOn Mon, May 4, 2009 at 10:27 PM, Jason White <jason@jasonjgw.net> wrote:
Stephen Crosby <stevecrozz@gmail.com> wrote:My suspicion is that it's a network problem unrelated to FreeSWITCH.
> We had our first big issues with our freeswitch system today. During at
> least 2 conferences, audio became jittery and there were three occasions
> where everyone was dropped from a conference. Even so, conference recording
> was not interrupted, and the freeswitch debug log doesn't show anything
> unusual.
Did you try pinging the host while the problems were occurring?
What did FreeSWITCH report in the log as the reason for terminating the calls
to the conference?
_______________________________________________
Freeswitch-users mailing list
Freeswitch-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org