From samuel.viscapi at univ-montp2.fr Wed Sep 2 14:11:51 2015 From: samuel.viscapi at univ-montp2.fr (Samuel VISCAPI) Date: Wed, 2 Sep 2015 16:11:51 +0200 Subject: [Ekiga-list] Ekiga 4.0.1 and Renavisio In-Reply-To: <55AE46B9.2050704@univ-fcomte.fr> References: <559BE482.5040501@univ-montp2.fr> <559BED02.5040908@univ-fcomte.fr> <559D016F.7010100@univ-montp2.fr> <559D4765.9010002@univ-montp2.fr> <55A69FBE.1090902@univ-fcomte.fr> <55A7B726.9090800@univ-montp2.fr> <55A7B999.8010405@univ-fcomte.fr> <55AE2B9A.9070708@univ-montp2.fr> <55AE46B9.2050704@univ-fcomte.fr> Message-ID: <55E703A7.4020906@univ-montp2.fr> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, Just to let you know we had our first real RENAVISIO conference with Ekiga 4.0.1 today. There were 8 participants (4 audio + 4 video), and everything worked perfectly ! Many thanks to everyone involved in that great piece of software :) Cheers, Samuel Le 21/07/2015 15:18, Eugen Dedu a ?crit : > Hi Samuel, > > I propose you to compile opal 3.10.10 with libav version 8, or > with version 9 and the patch libav9 from > https://sources.debian.net/src/opal/3.10.10~dfsg2-1/debian/patches/, > or version 10 with patches libav9 and libav10. > > (For your information, the unstable code should work without > patches with ffmpeg, but not with libav. Hehe, there are several > if-s here, but hopefully in the near future everything will be > settled. Debian has just switched from libav to ffmpeg.) > > Eugen > > On 21/07/15 13:23, Samuel VISCAPI wrote: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> Hi Eugen, >> >> For now, as this is for production environment, I'd rather stay >> on the stable 4.0.1 version. But if time permits, I'd be glad to >> test the unstable branch and report here though :) >> >> On a side note, I didn't managed to compile Opal 3.10.10 with >> either libav 11.4/10.7 or ffmpeg 2.7.2. I tried to apply the >> Debian patches you told me about, but the patch command failed on >> some chunks. I tried to add these by hand, but that only led to >> more errors... Could you help me on this one please ? >> >> In the mean time, we received the new x86 based machine, an Intel >> NUC D34010WYKH, which is of course a lot more powerful than the >> tiny Raspberry Pi 2. >> >> Cheers, Samuel >> >> Le 16/07/2015 16:03, Eugen Dedu a ?crit : >>> Samuel, would it be possible to you to use ekiga unstable code >>> instead of ekiga 4.0.1? We are fixing bugs for the former, >>> while the latter is too old to fix bugs. Note that for the >>> moment you need to use ffmpeg, not libav, for the unstable code >>> of ekiga. >>> >>> On 16/07/15 15:52, Samuel VISCAPI wrote: Hi Eugen, >>> >>> Thanks for your offer, but I won't have too much free time >>> today for testing, sorry. I could be more available tomorrow >>> morning, I'll let you know. >>> >>> I found something quite interesting: even though the Raspberry >>> Pi 2 supports the NEON set of instructions, I couldn't get >>> libav-0.8.17 to compile with NEON enabled. >>> >>> I just checked with libav-11.4, and the configure script seems >>> to like NEON better :) Using these instructions could lead to >>> a significant performance boost on ARM platform, and maybe make >>> Ekiga usable on the Raspberry Pi 2. I'll give this a try ASAP >>> ! >>> >>> Ultimately, If that doesn't work, we'll have to use a beefier, >>> x86 based machine (which is already ordered). >>> >>> Cheers, Samuel >>> >>> Le 15/07/2015 20:00, Eugen Dedu a ?crit : >>>>>> Hi Samuel, >>>>>> >>>>>> We can make some tests tomorrow if you wish, I have >>>>>> access to renavisio too. Note that I will use the >>>>>> development code in order to allow to fix any issue which >>>>>> might appear. >>>>>> >>>>>> Eugen >>>>>> >>>>>> On 08/07/15 17:53, Samuel VISCAPI wrote: >>>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >>>>>>> >>>>>>> Hi all, >>>>>>> >>>>>>> I managed to compile Ekiga 4.0.1 with H.263 support, >>>>>>> with libav-0.8.17 :) With this build I could join a >>>>>>> Renavisio conference and have a short, rather sluggish >>>>>>> (~15 FPS + stuttering sound) talk with my >>>>>>> colleague...before the Raspberry PI 2 crashed ;) >>>>>>> >>>>>>> I'll try again later with some overclock and / or more >>>>>>> memory dedicated to the GPU. >>>>>>> >>>>>>> Stay tuned ! >>>>>>> >>>>>>> Cheers, Samuel >>>>>>> >>>>>>> Le 08/07/2015 12:54, Samuel VISCAPI a ?crit : >>>>>>>> Hi all, >>>>>>>> >>>>>>>> Thanks for your answers, I'll try to build Ekiga >>>>>>>> with H.263 support ASAP. By the way, is there a >>>>>>>> recommended version of libav for that purpose ? >>>>>>>> >>>>>>>> @ Eugen: I built Opal 3.10.10 from sources, do I >>>>>>>> still need to apply those Debian patches (on >>>>>>>> Raspbian/ARM) ? >>>>>>>> >>>>>>>> Cheers, Samuel >>>>>>>> >>>>>>>> Le 07/07/2015 17:15, Eugen Dedu a ?crit : >>>>>>>>> On 07/07/15 16:38, Samuel VISCAPI wrote: >>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >>>>>>>>>> >>>>>>>>>> Dear all, >>>>>>>>>> >>>>>>>>>> This is my first post to that mailing list :) >>>>>>>>>> >>>>>>>>>> I'd like to use Ekiga to participate in a >>>>>>>>>> conference hosted on Renavisio, the French >>>>>>>>>> education visioconferencing platform: >>>>>>>>>> >>>>>>>>>> https://visio.renater.fr/ >>>>>>>>>> >>>>>>>>>> I managed to join the conference room using the >>>>>>>>>> SIP protocol. I had to set DTMF mode to RFC 2833 >>>>>>>>>> in order to type in the password though. >>>>>>>>>> >>>>>>>>>> Audio is working correctly, but video is not. I >>>>>>>>>> can't see my colleague (in CC) who's connected to >>>>>>>>>> the same conference room, and he doesn't see me >>>>>>>>>> either. The webcam is a Logitech C920, which >>>>>>>>>> appears to be working just fine in the "echo >>>>>>>>>> test" room. As for my colleague, he is using >>>>>>>>>> Scopia and the H.323 protocol: >>>>>>>>>> >>>>>>>>>> http://www.avaya.com/usa/product/avaya-scopia-desktop-and-mob il >> >>>>>>>>>> e-a >>> >>>>>>>>>> >> pp >>>>>>> >>>>>>>>>> >>> l >>>>>>>> >>>>>>>>>> >>>>>>> ica >>>>>>>>>> >>>>>>>>>> >>>>>>>> tions/# >>>>>>>>>> >>>>>>>>>> By the way, I'm running Ekiga 4.0.1 compiled >>>>>>>>>> from sources on a Raspberry PI 2. I followed >>>>>>>>>> these instructions: >>>>>>>>>> >>>>>>>>>> http://wiki.ekiga.org/index.php/Compiling_Ekiga >>>>>>>>>> >>>>>>>>>> What am I doing wrong ? >>>>>>>>>> >>>>>>>>>> P.S: Damien told me it could be a video codec >>>>>>>>>> issue. So far, only theora and h261 are available >>>>>>>>>> in the "Preferences" menu. If need be, I could >>>>>>>>>> install libav/ffmpeg and libx264 then recompile >>>>>>>>>> Ekiga. >>>>>>>> >>>>>>>>> Hi Samuel, >>>>>>>> >>>>>>>>> I would relaly love to make Ekiga work with >>>>>>>>> Renavisio. I plan to test it myself, but I am >>>>>>>>> pretty busy at the moment. >>>>>>>> >>>>>>>>> I see at >>>>>>>>> https://lpsc.in2p3.fr/trac/faq/wiki/Renavisio that >>>>>>>>> the H263 codecs are needed. You need libav >>>>>>>>> (perhaps ffmpeg works too) for that. There is a >>>>>>>>> patch (or two) you need to use, see >>>>>>>>> https://sources.debian.net/src/opal/3.10.10~dfsg2-1/debian/pat ch >> >>>>>>>>> es/ > > _______________________________________________ ekiga-list mailing > list ekiga-list at gnome.org > https://mail.gnome.org/mailman/listinfo/ekiga-list > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iF4EAREIAAYFAlXnA6cACgkQqjnQbvs+kDlhhAEAl1Bv2xxftKBDMT0NNAkDXTtk Dek4D6UFO8OEGMhFqBkBAJZVeLiHMxcRNGGam+wbdRmv0uJlx6yvJpWcKw0EDLrp =/FIO -----END PGP SIGNATURE----- From eugen.dedu at univ-fcomte.fr Wed Sep 2 15:00:50 2015 From: eugen.dedu at univ-fcomte.fr (Eugen Dedu) Date: Wed, 2 Sep 2015 17:00:50 +0200 Subject: [Ekiga-list] Ekiga 4.0.1 and Renavisio In-Reply-To: <55E703A7.4020906@univ-montp2.fr> References: <559BE482.5040501@univ-montp2.fr> <559BED02.5040908@univ-fcomte.fr> <559D016F.7010100@univ-montp2.fr> <559D4765.9010002@univ-montp2.fr> <55A69FBE.1090902@univ-fcomte.fr> <55A7B726.9090800@univ-montp2.fr> <55A7B999.8010405@univ-fcomte.fr> <55AE2B9A.9070708@univ-montp2.fr> <55AE46B9.2050704@univ-fcomte.fr> <55E703A7.4020906@univ-montp2.fr> Message-ID: <55E70F22.1050909@univ-fcomte.fr> Great, glad to hear that! Eugen On 02/09/15 16:11, Samuel VISCAPI wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi all, > > Just to let you know we had our first real RENAVISIO conference with > Ekiga 4.0.1 today. > > There were 8 participants (4 audio + 4 video), and everything worked > perfectly ! > > Many thanks to everyone involved in that great piece of software :) > > Cheers, Samuel > > Le 21/07/2015 15:18, Eugen Dedu a ?crit : >> Hi Samuel, >> >> I propose you to compile opal 3.10.10 with libav version 8, or >> with version 9 and the patch libav9 from >> https://sources.debian.net/src/opal/3.10.10~dfsg2-1/debian/patches/, >> or version 10 with patches libav9 and libav10. >> >> (For your information, the unstable code should work without >> patches with ffmpeg, but not with libav. Hehe, there are several >> if-s here, but hopefully in the near future everything will be >> settled. Debian has just switched from libav to ffmpeg.) >> >> Eugen >> >> On 21/07/15 13:23, Samuel VISCAPI wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >>> >>> Hi Eugen, >>> >>> For now, as this is for production environment, I'd rather stay >>> on the stable 4.0.1 version. But if time permits, I'd be glad to >>> test the unstable branch and report here though :) >>> >>> On a side note, I didn't managed to compile Opal 3.10.10 with >>> either libav 11.4/10.7 or ffmpeg 2.7.2. I tried to apply the >>> Debian patches you told me about, but the patch command failed on >>> some chunks. I tried to add these by hand, but that only led to >>> more errors... Could you help me on this one please ? >>> >>> In the mean time, we received the new x86 based machine, an Intel >>> NUC D34010WYKH, which is of course a lot more powerful than the >>> tiny Raspberry Pi 2. >>> >>> Cheers, Samuel >>> >>> Le 16/07/2015 16:03, Eugen Dedu a ?crit : >>>> Samuel, would it be possible to you to use ekiga unstable code >>>> instead of ekiga 4.0.1? We are fixing bugs for the former, >>>> while the latter is too old to fix bugs. Note that for the >>>> moment you need to use ffmpeg, not libav, for the unstable code >>>> of ekiga. >>>> >>>> On 16/07/15 15:52, Samuel VISCAPI wrote: Hi Eugen, >>>> >>>> Thanks for your offer, but I won't have too much free time >>>> today for testing, sorry. I could be more available tomorrow >>>> morning, I'll let you know. >>>> >>>> I found something quite interesting: even though the Raspberry >>>> Pi 2 supports the NEON set of instructions, I couldn't get >>>> libav-0.8.17 to compile with NEON enabled. >>>> >>>> I just checked with libav-11.4, and the configure script seems >>>> to like NEON better :) Using these instructions could lead to >>>> a significant performance boost on ARM platform, and maybe make >>>> Ekiga usable on the Raspberry Pi 2. I'll give this a try ASAP >>>> ! >>>> >>>> Ultimately, If that doesn't work, we'll have to use a beefier, >>>> x86 based machine (which is already ordered). >>>> >>>> Cheers, Samuel >>>> >>>> Le 15/07/2015 20:00, Eugen Dedu a ?crit : >>>>>>> Hi Samuel, >>>>>>> >>>>>>> We can make some tests tomorrow if you wish, I have >>>>>>> access to renavisio too. Note that I will use the >>>>>>> development code in order to allow to fix any issue which >>>>>>> might appear. >>>>>>> >>>>>>> Eugen >>>>>>> >>>>>>> On 08/07/15 17:53, Samuel VISCAPI wrote: >>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >>>>>>>> >>>>>>>> Hi all, >>>>>>>> >>>>>>>> I managed to compile Ekiga 4.0.1 with H.263 support, >>>>>>>> with libav-0.8.17 :) With this build I could join a >>>>>>>> Renavisio conference and have a short, rather sluggish >>>>>>>> (~15 FPS + stuttering sound) talk with my >>>>>>>> colleague...before the Raspberry PI 2 crashed ;) >>>>>>>> >>>>>>>> I'll try again later with some overclock and / or more >>>>>>>> memory dedicated to the GPU. >>>>>>>> >>>>>>>> Stay tuned ! >>>>>>>> >>>>>>>> Cheers, Samuel >>>>>>>> >>>>>>>> Le 08/07/2015 12:54, Samuel VISCAPI a ?crit : >>>>>>>>> Hi all, >>>>>>>>> >>>>>>>>> Thanks for your answers, I'll try to build Ekiga >>>>>>>>> with H.263 support ASAP. By the way, is there a >>>>>>>>> recommended version of libav for that purpose ? >>>>>>>>> >>>>>>>>> @ Eugen: I built Opal 3.10.10 from sources, do I >>>>>>>>> still need to apply those Debian patches (on >>>>>>>>> Raspbian/ARM) ? >>>>>>>>> >>>>>>>>> Cheers, Samuel >>>>>>>>> >>>>>>>>> Le 07/07/2015 17:15, Eugen Dedu a ?crit : >>>>>>>>>> On 07/07/15 16:38, Samuel VISCAPI wrote: >>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >>>>>>>>>>> >>>>>>>>>>> Dear all, >>>>>>>>>>> >>>>>>>>>>> This is my first post to that mailing list :) >>>>>>>>>>> >>>>>>>>>>> I'd like to use Ekiga to participate in a >>>>>>>>>>> conference hosted on Renavisio, the French >>>>>>>>>>> education visioconferencing platform: >>>>>>>>>>> >>>>>>>>>>> https://visio.renater.fr/ >>>>>>>>>>> >>>>>>>>>>> I managed to join the conference room using the >>>>>>>>>>> SIP protocol. I had to set DTMF mode to RFC 2833 >>>>>>>>>>> in order to type in the password though. >>>>>>>>>>> >>>>>>>>>>> Audio is working correctly, but video is not. I >>>>>>>>>>> can't see my colleague (in CC) who's connected to >>>>>>>>>>> the same conference room, and he doesn't see me >>>>>>>>>>> either. The webcam is a Logitech C920, which >>>>>>>>>>> appears to be working just fine in the "echo >>>>>>>>>>> test" room. As for my colleague, he is using >>>>>>>>>>> Scopia and the H.323 protocol: >>>>>>>>>>> >>>>>>>>>>> http://www.avaya.com/usa/product/avaya-scopia-desktop-and-mob > il >>> >>>>>>>>>>> > e-a >>>> >>>>>>>>>>> >>> pp >>>>>>>> >>>>>>>>>>> >>>> l >>>>>>>>> >>>>>>>>>>> >>>>>>>> ica >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> tions/# >>>>>>>>>>> >>>>>>>>>>> By the way, I'm running Ekiga 4.0.1 compiled >>>>>>>>>>> from sources on a Raspberry PI 2. I followed >>>>>>>>>>> these instructions: >>>>>>>>>>> >>>>>>>>>>> http://wiki.ekiga.org/index.php/Compiling_Ekiga >>>>>>>>>>> >>>>>>>>>>> What am I doing wrong ? >>>>>>>>>>> >>>>>>>>>>> P.S: Damien told me it could be a video codec >>>>>>>>>>> issue. So far, only theora and h261 are available >>>>>>>>>>> in the "Preferences" menu. If need be, I could >>>>>>>>>>> install libav/ffmpeg and libx264 then recompile >>>>>>>>>>> Ekiga. >>>>>>>>> >>>>>>>>>> Hi Samuel, >>>>>>>>> >>>>>>>>>> I would relaly love to make Ekiga work with >>>>>>>>>> Renavisio. I plan to test it myself, but I am >>>>>>>>>> pretty busy at the moment. >>>>>>>>> >>>>>>>>>> I see at >>>>>>>>>> https://lpsc.in2p3.fr/trac/faq/wiki/Renavisio that >>>>>>>>>> the H263 codecs are needed. You need libav >>>>>>>>>> (perhaps ffmpeg works too) for that. There is a >>>>>>>>>> patch (or two) you need to use, see >>>>>>>>>> https://sources.debian.net/src/opal/3.10.10~dfsg2-1/debian/pat > ch >>> >>>>>>>>>> > es/ >> >> _______________________________________________ ekiga-list mailing >> list ekiga-list at gnome.org >> https://mail.gnome.org/mailman/listinfo/ekiga-list >> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.17 (GNU/Linux) > > iF4EAREIAAYFAlXnA6cACgkQqjnQbvs+kDlhhAEAl1Bv2xxftKBDMT0NNAkDXTtk > Dek4D6UFO8OEGMhFqBkBAJZVeLiHMxcRNGGam+wbdRmv0uJlx6yvJpWcKw0EDLrp > =/FIO > -----END PGP SIGNATURE----- > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > https://mail.gnome.org/mailman/listinfo/ekiga-list > From samuel.viscapi at univ-montp2.fr Thu Sep 17 12:16:49 2015 From: samuel.viscapi at univ-montp2.fr (Samuel VISCAPI) Date: Thu, 17 Sep 2015 14:16:49 +0200 Subject: [Ekiga-list] STUN issues with Ekiga 4.0.1 and RENAVISIO ? Message-ID: <55FAAF31.3040206@univ-montp2.fr> -----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----- From eugen.dedu at univ-fcomte.fr Thu Sep 17 20:59:48 2015 From: eugen.dedu at univ-fcomte.fr (Eugen Dedu) Date: Thu, 17 Sep 2015 22:59:48 +0200 Subject: [Ekiga-list] STUN issues with Ekiga 4.0.1 and RENAVISIO ? In-Reply-To: <55FAAF31.3040206@univ-montp2.fr> References: <55FAAF31.3040206@univ-montp2.fr> Message-ID: <55FB29C4.5050505@univ-fcomte.fr> 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 From samuel.viscapi at univ-montp2.fr Mon Sep 21 10:55:38 2015 From: samuel.viscapi at univ-montp2.fr (Samuel VISCAPI) Date: Mon, 21 Sep 2015 12:55:38 +0200 Subject: [Ekiga-list] STUN issues with Ekiga 4.0.1 and RENAVISIO ? In-Reply-To: <55FB29C4.5050505@univ-fcomte.fr> References: <55FAAF31.3040206@univ-montp2.fr> <55FB29C4.5050505@univ-fcomte.fr> Message-ID: <55FFE22A.7000800@univ-montp2.fr> -----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 +33 (0)4 67 14 93 32 samuel.viscapi at univ-montp2.fr GPG: FB3E9039 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iF4EAREIAAYFAlX/4ioACgkQqjnQbvs+kDkDegD/VVuCxUFcjgzP3peOIPoZyP8y Hx5CW0mNBTXQY4hU6r0BANdz2/YWDxyKrTovHOiqtTwlB+QouuVT4hiogH9t6Ysq =2lM6 -----END PGP SIGNATURE-----