Re: [Ekiga-list] usability

2013-09-05 Thread fred k
Thanks Yannick, very informative Yannick wrote(excerpts): I assume he was referring to a SIP proxy, ... can solve the NAT issue. ...we could improve the ekiga tools for supporting NAT with an ICE... ...I doubt IPV6 will solve this issue... fred ___ e

Re: [Ekiga-list] usability

2013-09-05 Thread Yannick
Le jeudi 05 septembre 2013 à 14:21 +0900, fred k a écrit : > > ... you do *not* have [to] do/know all that if you use a > commercial... > I have a question. When you use commercial SIP provider, do you mean > your voice/video/data goes through a server at the SIP provider before > reaching called p

Re: [Ekiga-list] usability

2013-09-04 Thread fred k
Hi That Guy and all gals and guys, Let me discern technical issues and non-tech ones. Plus a question regarding "SIP provider" at the bottom. That Guy wrote: $kype will continue to have a long LONG life of spying ahead. I agree but this is not a technical issue here. ...the chances that th

Re: [Ekiga-list] usability

2013-09-04 Thread Stuart Gathman
On 09/04/2013 10:46 AM, That Guy wrote: snip WOW! OK I don't feel so dumb anymore and it is clear to me why none of these have caught on and why people still use $kype. If this is what you've got to do/understand to get an FOSS VoIP client up and running I'm guessing that $kype will continue

[Ekiga-list] usability

2013-09-04 Thread That Guy
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 snip >> You either hard code the LAN ip address to forward your SIP traffic, >> or you have to configure your router to dynamically configure the >> required ports to the LAN ip address which opens port 3478 or 3479, if >> possible. >> >> I am pret