On 02/10/11 10:59, Geeziard wrote:
I am seeing the same problem on Windows with Ekiga 3.2.7. If I have the
VMware bridging networks enabled, Ekiga send the IP addresses of those along
in its register message, despite them being on a different subnet from the
outgoing package, like:
REGISTER
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
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
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
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
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
