Eugen Dedu a écrit : > Damien Sandras wrote: >> Le dimanche 27 septembre 2009 à 12:38 +0200, yannick a écrit : >> >>> I think it is a good idea to add TCP support; atm the lack of TCP >>> signaling for SIP broke some setups (calls fail), and as a packager I do >>> not package extra codecs (non free) because of this bug. This means >>> those non free codecs are undertested (e.g. it seems latest x264 lib do >>> not compile with Ekiga anymore), and we lose some interoperability with >>> other software/hardware out of the box. >> Agreed. However, that's more an OPAL feature and it requires serious >> work on Ekiga.net to add support for TCP and NAT traversal. I'm not sure >> of the result of having 10000 active TCP connections to Ekiga.net >> either. > > TCP support is the bug number 1 in my opinion, so very important. > > TCP will be used only when the packet has more than about 1400 bytes, so > only a few clients use TCP at any given moment. >
s/1400/1300 that's how the standard define it. Should not change much your argument ;) > Moreover, I feel confident that linux can work with many TCP connections > simultaneously :o) > > Finally, note that TCP support exists already in opal, it needs testing > (Craig dixit, see attachments). > _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-devel-list