[Sending the message twice because of attachments] - ORIGINAL - Answering a past message from Eugen Dedu <Eugen Dedu pu-pm univ-fcomte fr> I wrote: ------ quote --- Finally, I made some home.net experiments (around 8.00 p.m. GMT): Having one main PC connected to the router and a laptop with a wireless connection to the same router I was able to make a Skype call between the two: video and audio worked perfectly. I tried the same with Ekiga without success (I took so many -d 4 logs that it is now difficult for me to establish which one is the good one, but I will repeat this test and will follow up ASAP). This failure was happening in very strange circumstances: ------ unquote --- I did again the same test as said above and took the -d 4 logs on both computers so that you can hopefully understand why it is not possible to achieve from Ekiga the same result that was possible from Skype. As far as I can understand perusing the logs, the problem arise from the fact that the Laptop is 'seen' on the same internal IP assigned to the PC (xxx.xxx.xxx.111, whereas it should be xxx.xxx.xxx.102). To make the test with Ekiga I deleted the stun.ekiga.net string (using gconf-editor/apps/ekiga/general/nat) and enabled a few 'services' on the Inbound section of my Netgear DG834GT router Firewall Rules (in substitution for port forwarding, not specifically foreeen in said router). I hope this topic is of some interest. Thanks for your attention. -- [Why use Win$ozz (I say) if ... "even a fool can do that. \\?// Do something you aren't good at!" (as Henry Miller used to say)] (°|°) Regards, Ennio. )=(
Attachment:
PC_recvng-1.gz
Description: Binary data