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
Le 01/09/2013 19:05, *Mark Carroll* wrote:
Is it possible to use Ekiga, at least to initiate SIP calls, if it is
behind NAT that won't forward 5060?
Using gconf-editor (apps > ekiga > protocols > sip), you can set listen_port
= 5061 and place and receive SIP calls as well. :-)
_
Obvious followup, though: if the ISP does firewall UDP 5060 upstream,
then is there any hope?
-- Mark
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list
Stuart Gathman writes:
> You haven't established that the device is to blame. It could be your
> ISP blocking port 5060 (as some have infamously been know to do to
> promote their own VOIP solutions).
True. The device does support incoming 5060 for people who use the ISP's
VoIP service; I don
On 09/01/2013 01:05 PM, Mark Carroll wrote:
I am having trouble with ekiga not registering when behind a BT Home
Hub running software version 8.1.H.U (Type A), whether or not I enable
network detection in the preferences. The -d 4 log is pasted at
http://pastebin.com/bd6kAWgp
In probing the port
Still no luck, latest log in http://pastebin.com/fnmF8CY0 where I tried
configuring SIP to listen on 5050 instead: I hoped to be able to
initiate calls, but I can't even register with ekiga.net.
Basically, is it possible at all to use ekiga from behind NAT if UDP
5060 is blocked? (I have all the o
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
