GNOME Bugzilla – Bug 591253
Ekiga misdetect network interface when using virtualization
Last modified: 2009-09-20 16:16:12 UTC
Please describe the problem: Hi, Downstream bug: https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/371527 Have several interfaces because virtualization is being used (2 additional ifaces created by VMware, and another one by VirtualBox). Ekiga chooses the wrong interfaces, without an option to force the right one (eth0). No registration is possible. ProblemType: Bug Architecture: amd64 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/ekiga NonfreeKernelModules: nvidia Package: ekiga 3.2.0-0ubuntu1 ../.. Yes, indeed, when I shutdown virbr0 then ekiga works properly. Attaching the debug log. -d 4: http://launchpadlibrarian.net/30082942/log.txt.gz IMHO, Relevant part: 2009/08/09 18:31:03.734 0:07.067 subscriber:0xb3190b90 SIP Sending PDU (655 bytes) to: rem=udp$193.28.87.126:5060,local=udp$94.27.64.202:5060,if=192.168.1.4%ath0 REGISTER sip:193.28.87.126 SIP/2.0 ../.. 2009/08/09 18:31:03.735 0:07.068 subscriber:0xb3190b90 OpalUDP Setting interface to 192.168.1.4%ath0 2009/08/09 18:31:03.735 0:07.068 subscriber:0xb3190b90 SIP Transaction timers set: retry=0.500, completion=6.000 2009/08/09 18:31:03.736 0:07.069 subscriber:0xb3190b90 OpalUDP Writing to interface 1 - "192.168.122.1%virbr0" 2009/08/09 18:31:03.739 0:07.072 subscriber:0xb3190b90 OpalMan Listener interfaces: associated transport=udp$192.168.122.1:5060 udp$94.27.64.202:5060,udp$192.168.1.4:5060,udp$192.168.122.1:5060 From the Ekiga point of view, it seems ath0 and virbr0 share the same IP: udp$192.168.1.4:5060 , thus the confusion... Best regards, Yannick Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Isn't duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=587504 or http://bugzilla.gnome.org/show_bug.cgi?id=568140 ?
Your bug has been fixed Yannick. However, it won't work with Asterisk because Asterisk does not support fully the RFC when it comes to forking.
Hu, this bug has nothing to do with Asterisk. Are you sure you closed the right bug?
Yes.
Are the two bugs at comment #1 fixed too?
I commented in both bug reports.