Re: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1
- From: John Talbut <jt dpets co uk>
- To: Ekiga mailing list <ekiga-list gnome org>
- Subject: Re: [Ekiga-list] STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1
- Date: Fri, 03 Apr 2015 16:10:35 +0100
On 03/04/15 15:38, Eugen Dedu wrote:
On 03/04/15 16:14, John Talbut wrote:
I am getting the "Ekiga did not manage to configure your network
settings automatically" message. I have followed the instructions and
checked my router settings, which seem correct (I think I have used
Ekiga before without this problem).
Using the command: ekiga -d 4 2>&1 | grep STUN
I get:
2015/04/03 15:02:04.701 0:02.756
Ekiga Started STUN detector
2015/04/03 15:02:07.171 0:05.226 StunDetector:0xad47db40
STUN No response to STUN server 77.72.174.167:3478
2015/04/03 15:02:07.172 0:05.226 StunDetector:0xad47db40
OPAL STUN server "stun.ekiga.net" replies Blocked, external IP
127.0.0.1
2015/04/03 15:02:08.556 0:06.610 Housekeeper:0xad8dab40
Ekiga Stopped STUN detector
2015/04/03 15:02:11.091 0:09.146 subscriber:0xaac14b40
STUN STUN server 77.72.174.167:3478 unexpectedly went offline getting
external address.
If the STUN server is replying to 127.0.0.1 then I imagine that the
router would block it since this is just a loopback address.
Right.
The problem is "No response to STUN server". This means it cannot
contact it. Why? Possible answers:
- you are not connected to Internet (I suppose this is not your case,
right?)
- there is a firewall which blocks those packets
STUN uses ports 3478 to 3479 (perhaps the following ones too), does a
machine block these ports?
Thanks Eugen
I had checked and have rechecked my router and ports 3478 - 3479 are
allowed. Also I can successfully ping and run traceroute to 77.72.174.167.
John
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]