STUN issues with Ekiga 4.0.1 and RENAVISIO ?

[Samuel VISCAPI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi all,

One of my colleague is having issues with his Ekiga setup.

We are running the same version of Ekiga (4.0.1) on similar machines
(Ubuntu 14.04 x86-64). The only difference is that he's using KDE,
while I'm using Unity.

We are on the same physical network, with ports range already opened
for Ekiga.

While I can dial in the SIP number of a RENAVISIO conference and reach
the bridge without any problem (as I told you before in a previous
e-mail), it just doesn't work on his side... He still get the same
error message about Ekiga not being able to configure the network
automatically...

Here is an excerpt of his logfile (ekiga -d 4), where one could see
some STUN related errors:

2015/09/17 13:42:47.465  0:00.913 Ekiga version 4.0.1
2015/09/17 13:42:47.465  0:00.913 PTLIB version 2.10.10
2015/09/17 13:42:47.465  0:00.913 OPAL version 3.10.10
2015/09/17 13:42:47.465  0:00.913 Accelerated rendering support enabled
2015/09/17 13:42:47.465  0:00.913 DBUS support enabled
2015/09/17 13:42:47.465  0:00.913 GConf support enabled
2015/09/17 13:42:48.696  0:02.143 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:49.161  0:02.608 StunDetect...a965e31700 STUN No
response to STUN server 217.10.68.152:3478
2015/09/17 13:42:49.161  0:02.608 StunDetect...a965e31700 PWLib
Closing channel, fd=45
2015/09/17 13:42:49.161  0:02.608 StunDetect...a965e31700 PWLib
Closing channel, fd=46
2015/09/17 13:42:49.161  0:02.609 StunDetect...a965e31700 OPAL STUN
server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1
2015/09/17 13:42:49.161  0:02.609 StunDetect...a965e31700 PWLib File
handle low water mark set: 45 PTextFile
2015/09/17 13:42:49.162  0:02.609 StunDetect...a965e31700 PTLib
Thread ended: name="StunDetector:0x7fa965e31700", real=2.405,
kernel=0.000 (0%), user=0.000 (0%), both=0.000 (0%)
2015/09/17 13:42:49.696  0:03.144 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:50.697  0:04.144 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:51.697  0:05.144 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:52.698  0:06.145 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:53.698  0:07.145 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:54.698  0:08.146 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:55.699  0:09.146 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:56.699  0:10.147 Opal Garba...a965f35700 SIP Garbage
collection: transactions=0, connections=0
2015/09/17 13:42:56.753  0:10.200 Housekeepe...a99018a700 Ekiga
Stopped STUN detector
2015/09/17 13:42:56.753  0:10.200 Housekeepe...a99018a700 PTLib
Destroyed thread 0xe0e6a0 StunDetector:0x7fa965e31700(id = 0)
2015/09/17 13:42:56.753  0:10.200 Housekeepe...a99018a700 PTLib
MONITOR: timers=1, expiries=2
2015/09/17 13:42:56.753  0:10.200 Housekeepe...a99018a700 SIP NAT
Binding refresh started.
2015/09/17 13:42:56.753  0:10.201 Housekeepe...a99018a700 SIP NAT
Binding refresh finished.

What are we doing wrong ?

Any help would be greatly appreciated :)

Cheers, Samuel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iF4EAREIAAYFAlX6rzEACgkQqjnQbvs+kDl3MQEAmFH2LZFVkfcKLxsowQLXE3DA
zKyk11mgFq2jxZDXKgkA/0nYXDi/sYsx5USy1GDOjH0GdsT1DzKGpyH8EaXD1MQu
=FLzE
-----END PGP SIGNATURE-----
_______________________________________________
ekiga-list mailing list
[hidden email]
https://mail.gnome.org/mailman/listinfo/ekiga-list

[Eugen Dedu-2]

On 17/09/15 14:16, Samuel VISCAPI wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi all,
>
> One of my colleague is having issues with his Ekiga setup.
>
> We are running the same version of Ekiga (4.0.1) on similar machines
> (Ubuntu 14.04 x86-64). The only difference is that he's using KDE,
> while I'm using Unity.
>
> We are on the same physical network, with ports range already opened
> for Ekiga.
>
> While I can dial in the SIP number of a RENAVISIO conference and reach
> the bridge without any problem (as I told you before in a previous
> e-mail), it just doesn't work on his side... He still get the same
> error message about Ekiga not being able to configure the network
> automatically...

Do you have this message too (on Unity machine)?

> Here is an excerpt of his logfile (ekiga -d 4), where one could see
> some STUN related errors:
>
> 2015/09/17 13:42:49.161  0:02.608 StunDetect...a965e31700 STUN No
> response to STUN server 217.10.68.152:3478
> 2015/09/17 13:42:49.161  0:02.608 StunDetect...a965e31700 PWLib
> Closing channel, fd=45
> 2015/09/17 13:42:49.161  0:02.608 StunDetect...a965e31700 PWLib
> Closing channel, fd=46
> 2015/09/17 13:42:49.161  0:02.609 StunDetect...a965e31700 OPAL STUN
> server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1

The above two errors mean that on his machine there is surely a firewall
which blocks packets to/from STUN server.  You could check this with
wireshark for instance, look at STUN lines.  Are you sure there is no
such firewall?

Cheers,
--
Eugen
_______________________________________________
ekiga-list mailing list
[hidden email]
https://mail.gnome.org/mailman/listinfo/ekiga-list

[Samuel VISCAPI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Eugen,

No, I don't have the same error message on my machine. I used to have
it though, but that was before we configured our network to fit
Ekiga's requirements.

And I don't know whether there's a firewall installed on his computer.
I'll check that ASAP using Wireshark :)

Cheers, and thanks for your help !

Sam

Le 17/09/2015 22:59, Eugen Dedu a écrit :

> On 17/09/15 14:16, Samuel VISCAPI wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
>>
>> Hi all,
>>
>> One of my colleague is having issues with his Ekiga setup.
>>
>> We are running the same version of Ekiga (4.0.1) on similar
>> machines (Ubuntu 14.04 x86-64). The only difference is that he's
>> using KDE, while I'm using Unity.
>>
>> We are on the same physical network, with ports range already
>> opened for Ekiga.
>>
>> While I can dial in the SIP number of a RENAVISIO conference and
>> reach the bridge without any problem (as I told you before in a
>> previous e-mail), it just doesn't work on his side... He still
>> get the same error message about Ekiga not being able to
>> configure the network automatically...
>
> Do you have this message too (on Unity machine)?
>
>> Here is an excerpt of his logfile (ekiga -d 4), where one could
>> see some STUN related errors:
>>
>> 2015/09/17 13:42:49.161      0:02.608    StunDetect...a965e31700
>>  STUN    No response to STUN server 217.10.68.152:3478 2015/09/17
>> 13:42:49.161      0:02.608    StunDetect...a965e31700    PWLib
>> Closing channel, fd=45 2015/09/17 13:42:49.161      0:02.608
>> StunDetect...a965e31700    PWLib Closing channel, fd=46
>> 2015/09/17 13:42:49.161      0:02.609    StunDetect...a965e31700
>>  OPAL    STUN server "stun.ekiga.net" replies Blocked, external
>> IP 127.0.0.1
>
> The above two errors mean that on his machine there is surely a
> firewall which blocks packets to/from STUN server.  You could check
> this with wireshark for instance, look at STUN lines.  Are you sure
> there is no such firewall?
>
> Cheers,

- --
Samuel VISCAPI
LUPM - UMR 5299
Université de Montpellier - Campus Triolet
Place Eugène Bataillon - 34095 Montpellier cedex 5
Bât. 13, bureau 5, 1er étage
[phone]
[hidden email]
GPG: FB3E9039
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)

iF4EAREIAAYFAlX/4ioACgkQqjnQbvs+kDkDegD/VVuCxUFcjgzP3peOIPoZyP8y
Hx5CW0mNBTXQY4hU6r0BANdz2/YWDxyKrTovHOiqtTwlB+QouuVT4hiogH9t6Ysq
=2lM6
-----END PGP SIGNATURE-----
_______________________________________________
ekiga-list mailing list
[hidden email]
https://mail.gnome.org/mailman/listinfo/ekiga-list