Re: [Ekiga-list] Bug prevents VPN use
On Wed, 2 Oct 2013, Damien Sandras wrote: If user B has two local interfaces (eth0: 192.x and tun: 10.x), when EkigaB will send a SIP message to userA, it will send it twice (because it can not determine how routing will work, that's the kernel responsibility) : - one SIP message to userA through tun0 with tun0 source IP address to userA IP and port - one SIP message to userA through eth0 with eth0 source IP address to user IP and port One of them should work. Your mail suggests that both messages are sent using the same interface but with different source IP and ports. That's weird. How does Ekiga assure that the packet is actually sent out eth0 with eth0 source IP? By default routing and source address selection are completely decoupled and if default route is to tun0, then all packets regardless of source address will go out tun0. One has to put policy routing in place to avoid this and assure that eth0 IP packets actually go out eth0 (and then you have to have the concept of multiple default routes that might change over time that needs to influence the policy routing settings). -- Mikael Abrahamssonemail: swm...@swm.pp.se ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] ekiga to Polycom Viewstation 1419 H.323
On Fri, 30 Aug 2013, Mikael Abrahamsson wrote: Hello. I'm trying to make Ekiga 4.0.1 on Linux Ubuntu 13.10 talk to an rather old Polycom Viewstation 1419 using H.323. I have attached a -d 4 from when I try to do this. What happens is the call is connected, audio only, I can hear sound from the ekiga Linux machine on the polycom, nothing from the polycom to the ekiga client. I can see using tcpdump on linux machine that it's sending packets, none coming back from the polycom. When I use the Polycom to connect to another Polycom (audio+video), it claims in the info menu about ongoing call, to use: Tx/Rx Clock rate: 768k Video Protocol: H.263 Video format: CIF Audio Protocol: G.722 Comm Protocol: H.323 I provice pcap packet dump files from this if it would help, but it looked like the log file logged the entire capability exchange so that might not be needed. The two machines are connected to the same IPv4 subnet on a L2 switch. This email ended up in the moderator queue. Since I don't know if file attachments are allowed, I have also put the file on my web server: http://swm.pp.se/ekiga-polycom1419.txt Thanks. -- Mikael Abrahamssonemail: swm...@swm.pp.se ___ ekiga-list mailing list ekiga-list@gnome.org https://mail.gnome.org/mailman/listinfo/ekiga-list
