Re: [Ekiga-devel-list] Sometimes Ekiga is not binding to the correct interface



On Wed, Oct 14, 2009 at 07:45:49PM +0200, Damien Sandras wrote :
> Ekiga 3 binds to all interfaces.
> 

Yeah ok but it is not sending its RTP on the correct one. You can see in
the traces that it is binding to 192.168.18.109 instead of 192.168.1.86.

2009/10/14 14:02:45.591	  0:08.722	   CallSetup:0xb39a0b90	OpalUDP
Setting interface to 192.168.18.109%eth0

2009/10/14 14:02:45.591	  0:08.722	   CallSetup:0xb39a0b90	SIP
Transaction timers set: retry=0.500, completion=1:00.000

2009/10/14 14:02:45.591	  0:08.722	   CallSetup:0xb39a0b90	OpalCon
OnSetUpConnectionCall[j5b3316471]-EP<sip>[5c242127-27b7-de11-93d0-00215ae72d5f]

2009/10/14 14:02:45.591	  0:08.722	   CallSetup:0xb39a0b90	OpalEP
OnSetUpConnection
Call[j5b3316471]-EP<sip>[5c242127-27b7-de11-93d0-00215ae72d5f]

2009/10/14 14:02:45.591	  0:08.722	   CallSetup:0xb39a0b90	PWLib
Ended thread 0xa279708 CallSetup:0xb39a0b90

2009/10/14 14:02:45.592	  0:08.723	Opal Liste...0xb52beb90	OpalUDP
Binding to interface: 192.168.18.109:5060

Then, the sip phone will either reject the call because it can't route
any packets to 192.168.18.109 or simply not have audio.

-- 
Alexandre Belloni


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]