Hi, Please stick to english, we are not the only ones to read this.
Thank you for your answer, still i'm not sure what the issue is. Your issue seems related to NAT configuration using Ekiga. It seems Twinkle (?) can handle that better than Ekiga, right? Why exactly? Was ekiga failing handling the NAT or was ekiga audio bad? Is twinkle handling NAT with a feature ekiga do not provide? A nice way to handle NAT in case of SIP with several clients behind it, is using port triggering if your router supports it: http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#Symmetric_NAT:_Dynamic_navigation_of_NAT_routers Best regards, Yannick -- 1st call after launch of ekiga works perfectly, but after it's impossible to call, I had to close ekiga and restart it... https://bugs.launchpad.net/bugs/378403 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
