|
»
»
Sometimes Ekiga is not binding to the correct interface
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
Sometimes Ekiga is not binding to the correct interface
by Alexandre Belloni-3
::
Rate this Message:
Hi,
My setup is the following : Physically: SIP phone-----eth1-PC-eth0-----router On the PC (IP 192.168.1.86), I'm running openser in an ubuntu kvm image (IP 192.168.1.80). I'm also running ekiga (3.2.0-0ubuntu2) on this PC. The SIP phone IP address is 192.168.1.1. br0 Link encap:Ethernet HWaddr 00:10:18:35:8f:d0 inet addr:192.168.1.86 Bcast:192.168.1.255 Mask:255.255.255.0 eth0 Link encap:Ethernet HWaddr 00:21:5a:e7:2d:5f inet addr:192.168.18.109 Bcast:192.168.18.255 Mask:255.255.255.0 br0 8000.001018358fd0 no eth1 vnet0 The issue is that ekiga is binding to eth0 when I'm trying to call the sipphone. It should bind to br0. You can find debug traces here: http://piout.net/fr/ekiga.log Regards, -- Alexandre Belloni _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@... http://mail.gnome.org/mailman/listinfo/ekiga-devel-list |
|
|
|
Re: Sometimes Ekiga is not binding to the correct interface
by Damien Sandras
::
Rate this Message:
Le mercredi 14 octobre 2009 à 17:35 +0200, Alexandre Belloni a écrit :
> Hi, > > My setup is the following : > > Physically: > SIP phone-----eth1-PC-eth0-----router > > On the PC (IP 192.168.1.86), I'm running openser in an ubuntu kvm image > (IP 192.168.1.80). I'm also running ekiga (3.2.0-0ubuntu2) on this PC. > > The SIP phone IP address is 192.168.1.1. > > > br0 Link encap:Ethernet HWaddr 00:10:18:35:8f:d0 > inet addr:192.168.1.86 Bcast:192.168.1.255 Mask:255.255.255.0 > > eth0 Link encap:Ethernet HWaddr 00:21:5a:e7:2d:5f > inet addr:192.168.18.109 Bcast:192.168.18.255 Mask:255.255.255.0 > > br0 8000.001018358fd0 no eth1 > vnet0 > > > The issue is that ekiga is binding to eth0 when I'm trying to call the > sipphone. It should bind to br0. > > You can find debug traces here: > > http://piout.net/fr/ekiga.log > > Regards, > Ekiga 3 binds to all interfaces. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ Be IP : http://www.beip.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras@... _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@... http://mail.gnome.org/mailman/listinfo/ekiga-devel-list |
|
|
|
Re: Sometimes Ekiga is not binding to the correct interface
by Alexandre Belloni-3
::
Rate this Message:
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 _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@... http://mail.gnome.org/mailman/listinfo/ekiga-devel-list |
|
|
|
Re: Sometimes Ekiga is not binding to the correct interface
by Damien Sandras
::
Rate this Message:
Le jeudi 15 octobre 2009 à 10:03 +0200, Alexandre Belloni a écrit :
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. That's because the remote server accepts it. If it can't relay RTP, it should reject the INVITE request with unroutable RTP addresses.
_______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@... http://mail.gnome.org/mailman/listinfo/ekiga-devel-list |
|
|
|
Re: Sometimes Ekiga is not binding to the correct interface
by Alexandre Belloni-3
::
Rate this Message:
On Thu, Oct 15, 2009 at 10:19:01AM +0200, Damien Sandras wrote :
> That's because the remote server accepts it. If it can't relay RTP, it > should reject the INVITE request with > unroutable RTP addresses. > The RTP is not relayed (and it is not supposed to be as the 2 parties are in the same subnet). The SIP proxy (openser) doesn't care about the SDP. The invite is just forwarded as is to the sip phone. What I don't get is why would ekiga send a packet on an interface with IP that are not on the network of this interface. It really seems like a bug to me. I would really expect that a sipphone communicating on eth1 will use the ip address of eth1 in all its messages. -- Alexandre Belloni _______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@... http://mail.gnome.org/mailman/listinfo/ekiga-devel-list |
|
|
|
Re: Sometimes Ekiga is not binding to the correct interface
by Damien Sandras
::
Rate this Message:
Le jeudi 15 octobre 2009 à 10:54 +0200, Alexandre Belloni a écrit :
On Thu, Oct 15, 2009 at 10:19:01AM +0200, Damien Sandras wrote : > That's because the remote server accepts it. If it can't relay RTP, it > should reject the INVITE request with > unroutable RTP addresses. > The RTP is not relayed (and it is not supposed to be as the 2 parties are in the same subnet). The SIP proxy (openser) doesn't care about the SDP. The invite is just forwarded as is to the sip phone. What I don't get is why would ekiga send a packet on an interface with IP that are not on the network of this interface. It really seems like a bug to me. I would really expect that a sipphone communicating on eth1 will use the ip address of eth1 in all its messages. Here is how Ekiga works : - it sends the SIP PDU from each interface with that interface as origin - if one (or several) of the PDU fails to reach their destination, the interface is "sort of" marked as invalid So it should work, except if your destination endpoint is reachable from several interfaces, but the call is supposed to work only from one of them (which is a configuration problem on your side).
_______________________________________________ Ekiga-devel-list mailing list Ekiga-devel-list@... http://mail.gnome.org/mailman/listinfo/ekiga-devel-list |
| Free embeddable forum powered by Nabble | Forum Help |
