Le mardi 01 septembre 2009 à 00:29 +0200, Shawn Adams a écrit : > It might appear that I've been seeing a similar issue for some weeks > now, several qualifying differences: > > #1 I am not using ekiga client > > #2 I have used 2 different routers, switching routers does not help, > both have what I'd call fairly reliable SIP ALGs. > > #3 the problem seems to come and go, without my intervention -sometimes > lasting an hour or more, and then not happing for hours. > > #4 during the failure, the response does indeed come, but my sniffer is > behind the FW, thus - shows the internal IPs, and not the original > packet received by the FW public interface > > #5 icmp echos to ekiga.net show no basic connectivity issues during the > failure. I have not yet tried traceroute to see if the frames take > different paths - perhaps through some device that may be causing the issue. > > I'm going to try to get time to rig up a sniffer on the public > interface, and get good/bad comparisons, but would appear to be a server > issue *if* these are all the same issue, not sure i can manage this > anytime soon. >
When it fails (timeout), if you let the client run, will it work in the following minutes ? Or does it fail consistantly. Because the server might be overloaded at some point. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsand...@ekiga.net _______________________________________________ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
