From dog at bluezoo.org Wed Mar 7 21:45:04 2012 From: dog at bluezoo.org (Chris Burdess) Date: Wed, 7 Mar 2012 21:45:04 +0000 Subject: [Ekiga-list] Ekiga application font Message-ID: <20120307214503.GA2946@deerhound.local> Hi There doesn't seem to be any way to configure the font and font size used by the Ekiga application. It doesn't use the application font and size defined for Gnome (which can be set in gnome-tweak-tool), as other Gnome applications do. Is there any way to get around this? -- Chris Burdess From dpsilvaengcomp at gmail.com Thu Mar 8 12:16:59 2012 From: dpsilvaengcomp at gmail.com (Diego Silva) Date: Thu, 8 Mar 2012 09:16:59 -0300 Subject: [Ekiga-list] Video file as ekiga output Message-ID: Mailing list, Has anyone used a video streaming instead of webcams on ekiga? I would like to use ekiga and Video4Linux Loopback Device. Someone was successful trying it? How do? Thanks, Diego Silva. -- Diego dos Passos Silva Engenheiro da Computa??o Mestre em Ci?ncia da Computa??o - Redes de Computadores Doutorando em Ciencia da Computa??o - Cin-UFPE Phone: 55 81 9792-0576 -------------- next part -------------- An HTML attachment was scrubbed... URL: From william-t2 at live.com Thu Mar 8 21:31:28 2012 From: william-t2 at live.com (william howell) Date: Thu, 8 Mar 2012 16:31:28 -0500 Subject: [Ekiga-list] Video file as ekiga output In-Reply-To: References: Message-ID: What are you attempting to do? Are you trying to do like a web training function or just want to stream a movie through your softphone? Thanks, Amphibian Date: Thu, 8 Mar 2012 09:16:59 -0300 From: dpsilvaengcomp at gmail.com To: ekiga-list at gnome.org Subject: [Ekiga-list] Video file as ekiga output Mailing list, Has anyone used a video streaming instead of webcams on ekiga? I would like to use ekiga and Video4Linux Loopback Device. Someone was successful trying it? How do? Thanks, Diego Silva. -- Diego dos Passos Silva Engenheiro da Computa??o Mestre em Ci?ncia da Computa??o - Redes de Computadores Doutorando em Ciencia da Computa??o - Cin-UFPE Phone: 55 81 9792-0576 _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Fri Mar 9 08:58:13 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Fri, 09 Mar 2012 09:58:13 +0100 Subject: [Ekiga-list] Ekiga application font In-Reply-To: <20120307214503.GA2946@deerhound.local> References: <20120307214503.GA2946@deerhound.local> Message-ID: <4F59C625.3020606@pu-pm.univ-fcomte.fr> On 07/03/12 22:45, Chris Burdess wrote: > Hi > > There doesn't seem to be any way to configure the font and font size used by > the Ekiga application. It doesn't use the application font and size defined > for Gnome (which can be set in gnome-tweak-tool), as other Gnome applications > do. Is there any way to get around this? What text do you speak about? Menus, dialog boxes, text in local contacts etc.? -- Eugen From dog at bluezoo.org Fri Mar 9 20:51:40 2012 From: dog at bluezoo.org (Chris Burdess) Date: Fri, 9 Mar 2012 20:51:40 +0000 Subject: [Ekiga-list] Ekiga application font In-Reply-To: <4F59C625.3020606@pu-pm.univ-fcomte.fr> References: <20120307214503.GA2946@deerhound.local> <4F59C625.3020606@pu-pm.univ-fcomte.fr> Message-ID: <20120309205140.GA17228@deerhound.local> Eugen Dedu wrote: > On 07/03/12 22:45, Chris Burdess wrote: > >There doesn't seem to be any way to configure the font and font size used by > >the Ekiga application. It doesn't use the application font and size defined > >for Gnome (which can be set in gnome-tweak-tool), as other Gnome applications > >do. Is there any way to get around this? > > What text do you speak about? Menus, dialog boxes, text in local > contacts etc.? Yes, all of the above. See e.g. http://bluezoo.org/ss1.png -- Chris Burdess From dave.koelmeyer at davekoelmeyer.co.nz Sun Mar 11 10:39:48 2012 From: dave.koelmeyer at davekoelmeyer.co.nz (Dave Koelmeyer) Date: Sun, 11 Mar 2012 23:39:48 +1300 Subject: [Ekiga-list] Ekiga 3.2.7 on Windows 7 Enterprise 64 bit fails to exit cleanly Message-ID: <4F5C80F4.1010306@davekoelmeyer.co.nz> Hi All, Just filed a bug here for completeness: https://bugzilla.gnome.org/show_bug.cgi?id=671818 Cheers, -- Dave Koelmeyer http://www.davekoelmeyer.co.nz From dave.koelmeyer at davekoelmeyer.co.nz Mon Mar 12 08:29:13 2012 From: dave.koelmeyer at davekoelmeyer.co.nz (Dave Koelmeyer) Date: Mon, 12 Mar 2012 21:29:13 +1300 Subject: [Ekiga-list] Areas of "frozen" video are observed in Ekiga 3.2.7 on Windows 7 Enterprise 64 bit Message-ID: <4F5DB3D9.2070501@davekoelmeyer.co.nz> Hi All, I have opened a bug report for this issue here: https://bugzilla.gnome.org/show_bug.cgi?id=671868 Cheers, -- Dave Koelmeyer http://www.davekoelmeyer.co.nz From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Mar 12 09:36:47 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 12 Mar 2012 10:36:47 +0100 Subject: [Ekiga-list] Ekiga application font In-Reply-To: <20120309205140.GA17228@deerhound.local> References: <20120307214503.GA2946@deerhound.local> <4F59C625.3020606@pu-pm.univ-fcomte.fr> <20120309205140.GA17228@deerhound.local> Message-ID: <4F5DC3AF.9050309@pu-pm.univ-fcomte.fr> On 09/03/12 21:51, Chris Burdess wrote: > Eugen Dedu wrote: >> On 07/03/12 22:45, Chris Burdess wrote: >>> There doesn't seem to be any way to configure the font and font size used by >>> the Ekiga application. It doesn't use the application font and size defined >>> for Gnome (which can be set in gnome-tweak-tool), as other Gnome applications >>> do. Is there any way to get around this? >> >> What text do you speak about? Menus, dialog boxes, text in local >> contacts etc.? > > Yes, all of the above. > > See e.g. http://bluezoo.org/ss1.png I fear that the problem is with your machine or your distribution, since here changing font in gnome-tweal-tool changes menu and roster (and others) accordingly. -- Eugen From dog at bluezoo.org Mon Mar 12 10:28:05 2012 From: dog at bluezoo.org (Chris Burdess) Date: Mon, 12 Mar 2012 10:28:05 +0000 Subject: [Ekiga-list] Ekiga application font In-Reply-To: <4F5DC3AF.9050309@pu-pm.univ-fcomte.fr> References: <20120307214503.GA2946@deerhound.local> <4F59C625.3020606@pu-pm.univ-fcomte.fr> <20120309205140.GA17228@deerhound.local> <4F5DC3AF.9050309@pu-pm.univ-fcomte.fr> Message-ID: <20120312102805.GA15423@deerhound.local> Eugen Dedu wrote: > On 09/03/12 21:51, Chris Burdess wrote: > >Eugen Dedu wrote: > >>On 07/03/12 22:45, Chris Burdess wrote: > >>>There doesn't seem to be any way to configure the font and font size used by > >>>the Ekiga application. It doesn't use the application font and size defined > >>>for Gnome (which can be set in gnome-tweak-tool), as other Gnome applications > >>>do. Is there any way to get around this? > >> > >>What text do you speak about? Menus, dialog boxes, text in local > >>contacts etc.? > > > >Yes, all of the above. > > > >See e.g. http://bluezoo.org/ss1.png > > I fear that the problem is with your machine or your distribution, > since here changing font in gnome-tweal-tool changes menu and roster > (and others) accordingly. I found the problem. It seems that Ekiga reads .gtkrc-2.0 even when running under Gnome 3. -- Chris Burdess From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Mar 12 10:31:15 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 12 Mar 2012 11:31:15 +0100 Subject: [Ekiga-list] Ekiga application font In-Reply-To: <20120312102805.GA15423@deerhound.local> References: <20120307214503.GA2946@deerhound.local> <4F59C625.3020606@pu-pm.univ-fcomte.fr> <20120309205140.GA17228@deerhound.local> <4F5DC3AF.9050309@pu-pm.univ-fcomte.fr> <20120312102805.GA15423@deerhound.local> Message-ID: <4F5DD073.1060600@pu-pm.univ-fcomte.fr> On 12/03/12 11:28, Chris Burdess wrote: > Eugen Dedu wrote: >> On 09/03/12 21:51, Chris Burdess wrote: >>> Eugen Dedu wrote: >>>> On 07/03/12 22:45, Chris Burdess wrote: >>>>> There doesn't seem to be any way to configure the font and font size used by >>>>> the Ekiga application. It doesn't use the application font and size defined >>>>> for Gnome (which can be set in gnome-tweak-tool), as other Gnome applications >>>>> do. Is there any way to get around this? >>>> >>>> What text do you speak about? Menus, dialog boxes, text in local >>>> contacts etc.? >>> >>> Yes, all of the above. >>> >>> See e.g. http://bluezoo.org/ss1.png >> >> I fear that the problem is with your machine or your distribution, >> since here changing font in gnome-tweal-tool changes menu and roster >> (and others) accordingly. > > I found the problem. It seems that Ekiga reads .gtkrc-2.0 even when running > under Gnome 3. Good! This is because it is still based on gtk 2. -- Eugen From niki at cplus.ru Fri Mar 16 07:11:38 2012 From: niki at cplus.ru (=?UTF-8?B?ItCd0LjQutC+0LvQsNC5INCTLiDQn9C10YLRgNC+0LIi?=) Date: Fri, 16 Mar 2012 11:11:38 +0400 Subject: [Ekiga-list] trouble with HD web cam logtech B990 Message-ID: <4F62E7AA.9010703@cplus.ru> Hi guys! I have a some problem with "HD Web Cam Logitech B990". May be you know about my problem)? In debug mode I see following: $ ekiga -d 1 > 2012/03/15 18:56:50.296 > 0:00.030 Version 3.2.7 by on > Unix Linux (2.6.32-5-686-i686) with PTLib (v2.6.7) at 2012/3/15 > 18:56:50.296 > 2012/03/15 18:56:50.296 0:00.030 Ekiga > git revision: unknown > 2012/03/15 18:56:50.300 0:00.034 > HalManager_dbus Populating full device list failed - The name > org.freedesktop.Hal was not provided by any .service files > 2012/03/15 18:56:50.300 0:00.034 > HalManager_dbus Populating full interface list failed - Method > "getDevices" with signature "" on interface > "org.freedesktop.NetworkManager" doesn't exist > > 2012/03/15 18:56:50.335 0:00.069 > Detecting V4L2 devices > 2012/03/15 18:57:15.944 0:25.678 Ekiga > version 3.2.7 > 2012/03/15 18:57:15.944 0:25.678 OPAL > version 3.6.8 > 2012/03/15 18:57:15.944 0:25.678 PTLIB > version 2.6.7 > 2012/03/15 18:57:15.944 0:25.678 GNOME > support disabled > 2012/03/15 18:57:15.944 0:25.678 > Accelerated rendering support enabled > 2012/03/15 18:57:15.944 0:25.678 DBUS > support enabled > 2012/03/15 18:57:15.944 0:25.678 GConf > support enabled > 2012/03/15 18:57:15.944 0:25.678 ESound > support disabled > 2012/03/15 18:57:19.592 0:29.326 > Detecting V4L2 devices > 2012/03/15 18:57:19.608 0:29.342 > PVidInDev Open() videoFd:-1 > 2012/03/15 18:57:19.608 0:29.342 > PVidInDev Close() videoFd:-1 started:0 > 2012/03/15 18:57:19.608 0:29.342 > Detecting V4L2 devices > 2012/03/15 18:57:19.619 0:29.353 > PVidInDev Open() devName:/dev/video0 videoFd:-1 > 2012/03/15 18:57:19.628 0:29.362 > VideoInputDevice S_STD failed : ???????????? ???????? > libv4l2: error converting / decoding frame data: v4l-convert: error > parsing JPEG header: Bogus jpeg format > 2012/03/15 18:57:20.324 0:30.058 VideoPrevi...0xb4e39b70 > PVidInDev QBUF failed : ???????????? ???????? > 2012/03/15 18:57:20.324 0:30.058 VideoPrevi...0xb4e39b70 > GMVideoInputManager_ptlib Expected a frame of 115200 bytes but > got 9352 bytes > 2012/03/15 18:57:20.326 0:30.060 GMVideoOut...0xb4db7b70 > XVideo XQueryShmExtension success > 2012/03/15 18:57:20.327 0:30.061 GMVideoOut...0xb4db7b70 > XVideo Using SHM extension > 2012/03/15 18:57:20.327 0:30.061 GMVideoOut...0xb4db7b70 > X11 Unknown X Event 19 received > libv4l2: error converting / decoding frame data: v4l-convert: error > parsing JPEG header: Bogus jpeg format $ uname -a > Linux test 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 GNU/Linux (latest Debian Dsktop 32bit) $ lsusb > Bus 001 Device 004: ID 046d:0828 Logitech, Inc. HD Webcam B990 $ sudo lsmod | grep pwc $(nothing) -------------- next part -------------- An HTML attachment was scrubbed... URL: From dima at minignu.minidns.net Mon Mar 19 13:31:12 2012 From: dima at minignu.minidns.net (Dima) Date: Mon, 19 Mar 2012 15:31:12 +0200 Subject: [Ekiga-list] Source snapshots for DEB-SRC In-Reply-To: <4F145659.9060007@pu-pm.univ-fcomte.fr> Message-ID: <87ipi0pvj3.fsf@minignu.minidns.net> >> Hi. >> I would like to try the snapshots for Debian/SID, however no snapshots are for PowerPC. Do Ekiga developers have some kind of 'deb-src' compatible repository, thus I could fullfill the dependencies and build the snapshots from source for my machine (powerpc) with apt-get. > I create snapshots for amd64 and i386. > > Here is my script to generate snapshots. See the comments at the > beginning to create the directories. Afterwards use ./build to build a > snapshot. Feel free to use it for your needs. Hi, Eugen. In the build script you have the following lines echo "Copying debian files in $i and updating the date in debian files..." cp -a ../debian/snapshots/$i/debian . sed -i "s/20080418/$date/g" debian/changelog sed -i "s/Sun, 18 Apr 2008 00:00:00 +0200/`date -R`/g" debian/changelog where, I believe, under `../debian' sit rules for `debuild'. Can you please post those files, or send link if they are somewhere on the web. Thanks, regards, Dima. From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon Mar 19 14:28:47 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 19 Mar 2012 15:28:47 +0100 Subject: [Ekiga-list] Source snapshots for DEB-SRC In-Reply-To: <87ipi0pvj3.fsf@minignu.minidns.net> References: <87ipi0pvj3.fsf@minignu.minidns.net> Message-ID: <4F67429F.4000002@pu-pm.univ-fcomte.fr> On 19/03/12 14:31, Dima wrote: >>> Hi. >>> I would like to try the snapshots for Debian/SID, however no snapshots are for PowerPC. Do Ekiga developers have some kind of 'deb-src' compatible repository, thus I could fullfill the dependencies and build the snapshots from source for my machine (powerpc) with apt-get. > >> I create snapshots for amd64 and i386. >> >> Here is my script to generate snapshots. See the comments at the >> beginning to create the directories. Afterwards use ./build to build a >> snapshot. Feel free to use it for your needs. > Hi, Eugen. > > In the build script you have the following lines > > echo "Copying debian files in $i and updating the date in debian > files..." > cp -a ../debian/snapshots/$i/debian . > sed -i "s/20080418/$date/g" debian/changelog > sed -i "s/Sun, 18 Apr 2008 00:00:00 +0200/`date -R`/g" > debian/changelog > > where, I believe, under `../debian' sit rules for `debuild'. Can you please > post those files, or send link if they are somewhere on the web. Oh yes, here they are. -- Eugen -------------- next part -------------- A non-text attachment was scrubbed... Name: debian.tar.xz Type: application/octet-stream Size: 28164 bytes Desc: not available URL: From dima at minignu.minidns.net Tue Mar 20 08:57:57 2012 From: dima at minignu.minidns.net (Dima) Date: Tue, 20 Mar 2012 10:57:57 +0200 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F145832.5040202@pu-pm.univ-fcomte.fr> Message-ID: <87pqc7ps2y.fsf@minignu.minidns.net> On 10/01/12 00:17, Dima Sorkin wrote: >> Hi. >> Ekiga 3.2.7 at Debian/SID (powerpc). >> >> When I call 500 at ekiga dot net, I hear silence, >> and in fact, the numbers at the bottom of a window show that >> no audio is received from the ekiga.net server. Video is ok, >> after 20 sec my cam is echoed to me back. >> >> On the other hand, when I use the 520 at ekiga dot net, >> it returns call to me, and then audio is just fine. >> Other audio echo services (4444 at sip2sip dot info) work fine. >> >> With Twinkle on the same machine the audio echo from 500 at ekiga is fine. >> >> What can be the reason that with Ekiga I get no audio echo from 500 ? > > This is surely a bug. Could you use in debian the ekiga version from > experimental and tell if the problem persists? > > -- > Eugen Hi, Eugen. I have built ekiga-snapshot using your script. Exactly the same phenomena persists. It is Debian Sid on PowerPC-32bit (iBook G4). Maybe its endianness matters ?! On x86*, regular version of Ekiga (3.2.7) does not have this buggy behavior. If this case seems interesting and more data is needed, I can provide it. Thanks, Dima. From geo.cherchetout at laposte.net Tue Mar 20 09:46:54 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Tue, 20 Mar 2012 10:46:54 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <20120109231740.3148D7A066@minignu.minidns.net> References: <20120109231740.3148D7A066@minignu.minidns.net> Message-ID: <4F68520E.70007@laposte.net> Le 10/01/2012 00:17, *Dima Sorkin* a ?crit fort ? propos : > Hi. Ekiga 3.2.7 at Debian/SID (powerpc). > > When I call 500 at ekiga dot net, I hear silence, and in fact, the > numbers at the bottom of a window show that no audio is received from the > ekiga.net server. Video is ok, after 20 sec my cam is echoed to me back. > > On the other hand, when I use the 520 at ekiga dot net, it returns call > to me, and then audio is just fine. Other audio echo services (4444 at > sip2sip dot info) work fine. > > With Twinkle on the same machine the audio echo from 500 at ekiga is > fine. Using Linphone, I notice the opposite behaviour : Good audio and video echo on 500 and neither sound nor video on 520. Using ekiga 3.2.7, wich is the current available version on Mageia, 500 is perfect echoing audio and video (PCMA - H261) and 520 doesn't recall me. From dima at minignu.minidns.net Tue Mar 20 10:20:42 2012 From: dima at minignu.minidns.net (Dima) Date: Tue, 20 Mar 2012 12:20:42 +0200 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F68520E.70007@laposte.net> Message-ID: <87mx7bpo91.fsf@minignu.minidns.net> > Geo Cherchetout wrote: > Using Linphone, I notice the opposite behaviour : Good audio and video echo > on 500 and neither sound nor video on 520. > > Using ekiga 3.2.7, wich is the current available version on Mageia, 500 is > perfect echoing audio and video (PCMA - H261) and 520 doesn't recall me. Is port 5060 open? (or it does not matter?) If not, it is possible that 520 just can't reach you behind router or so. By http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually http://wiki.ekiga.org/index.php/Internet_ports_used_by_Ekiga Thanks, Dima. From geo.cherchetout at laposte.net Tue Mar 20 10:30:03 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Tue, 20 Mar 2012 11:30:03 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <87mx7bpo91.fsf@minignu.minidns.net> References: <87mx7bpo91.fsf@minignu.minidns.net> Message-ID: <4F685C2B.2030006@laposte.net> Le 20/03/2012 11:20, *Dima* a ?crit fort ? propos : > Is port 5060 open? (or it does not matter?) If not, > it is possible that 520 just can't reach you behind router or so. Ports 5060 to 5070 are open and Stun is activated (stunserver.org for ekiga and for linphone). Using Linphone, 520 recalls me and the communication is established. From geo.cherchetout at laposte.net Tue Mar 20 10:37:27 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Tue, 20 Mar 2012 11:37:27 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F685C2B.2030006@laposte.net> References: <87mx7bpo91.fsf@minignu.minidns.net> <4F685C2B.2030006@laposte.net> Message-ID: <4F685DE7.9080502@laposte.net> Le 20/03/2012 11:30, *geo cherchetout* a ?crit : > Ports 5060 to 5070 are open and Stun is activated (stunserver.org for ekiga > and for linphone). Using Linphone, 520 recalls me and the communication is > established. (And SIP ALG is desabled on my Speedtouch adsl modem-router. And I use 5061 port.) From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Mar 20 11:11:15 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 20 Mar 2012 12:11:15 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F68520E.70007@laposte.net> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> Message-ID: <4F6865D3.4000801@pu-pm.univ-fcomte.fr> On 20/03/12 10:46, geo cherchetout wrote: > Le 10/01/2012 00:17, *Dima Sorkin* a ?crit fort ? propos : >> Hi. Ekiga 3.2.7 at Debian/SID (powerpc). >> >> When I call 500 at ekiga dot net, I hear silence, and in fact, the >> numbers at the bottom of a window show that no audio is received from the >> ekiga.net server. Video is ok, after 20 sec my cam is echoed to me back. >> >> On the other hand, when I use the 520 at ekiga dot net, it returns call >> to me, and then audio is just fine. Other audio echo services (4444 at >> sip2sip dot info) work fine. >> >> With Twinkle on the same machine the audio echo from 500 at ekiga is >> fine. > > Using Linphone, I notice the opposite behaviour : Good audio and video > echo on 500 and neither sound nor video on 520. > > Using ekiga 3.2.7, wich is the current available version on Mageia, 500 > is perfect echoing audio and video (PCMA - H261) and 520 doesn't recall me. geo, please provide -d 4 log when calling 500 and 520. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Mar 20 11:13:20 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 20 Mar 2012 12:13:20 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <87pqc7ps2y.fsf@minignu.minidns.net> References: <87pqc7ps2y.fsf@minignu.minidns.net> Message-ID: <4F686650.8070800@pu-pm.univ-fcomte.fr> On 20/03/12 09:57, Dima wrote: > On 10/01/12 00:17, Dima Sorkin wrote: >>> Hi. >>> Ekiga 3.2.7 at Debian/SID (powerpc). >>> >>> When I call 500 at ekiga dot net, I hear silence, >>> and in fact, the numbers at the bottom of a window show that >>> no audio is received from the ekiga.net server. Video is ok, >>> after 20 sec my cam is echoed to me back. >>> >>> On the other hand, when I use the 520 at ekiga dot net, >>> it returns call to me, and then audio is just fine. >>> Other audio echo services (4444 at sip2sip dot info) work fine. >>> >>> With Twinkle on the same machine the audio echo from 500 at ekiga is fine. >>> >>> What can be the reason that with Ekiga I get no audio echo from 500 ? >> >> This is surely a bug. Could you use in debian the ekiga version from >> experimental and tell if the problem persists? > > Hi, Eugen. > > I have built ekiga-snapshot using your script. Exactly the same phenomena > persists. It is Debian Sid on PowerPC-32bit (iBook G4). Maybe its > endianness matters ?! It seems yes. In the past, I used a macbook too. Please provide a log when calling 500 and does not work. It never works, is that right? Or sometimes yes, sometimes not? > On x86*, regular version of Ekiga (3.2.7) does not have this buggy > behavior. -- Eugen From dima at minignu.minidns.net Tue Mar 20 11:20:47 2012 From: dima at minignu.minidns.net (Dima) Date: Tue, 20 Mar 2012 13:20:47 +0200 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F686650.8070800@pu-pm.univ-fcomte.fr> Message-ID: <87k42fplgw.fsf@minignu.minidns.net> >>>> Hi. >>>> Ekiga 3.2.7 at Debian/SID (powerpc). >>>> >>>> When I call 500 at ekiga dot net, I hear silence, >>>> and in fact, the numbers at the bottom of a window show that >>>> no audio is received from the ekiga.net server. Video is ok, >>>> after 20 sec my cam is echoed to me back. >>>> >>>> On the other hand, when I use the 520 at ekiga dot net, >>>> it returns call to me, and then audio is just fine. >>>> Other audio echo services (4444 at sip2sip dot info) work fine. >>>> >>>> With Twinkle on the same machine the audio echo from 500 at ekiga is fine. >>>> >>>> What can be the reason that with Ekiga I get no audio echo from 500 ? >>> >>> This is surely a bug. Could you use in debian the ekiga version from >>> experimental and tell if the problem persists? >> >> Hi, Eugen. >> >> I have built ekiga-snapshot using your script. Exactly the same phenomena >> persists. It is Debian Sid on PowerPC-32bit (iBook G4). Maybe its >> endianness matters ?! > > It seems yes. In the past, I used a macbook too. > > Please provide a log when calling 500 and does not work. It never > works, is that right? Or sometimes yes, sometimes not? I will provide a log at night (currently I have no access). The behaviour is consistent, i.e. it is always as I described above. Creating log is `ekiga-snapshot -d 4 2> log' ? Thanks, Dima. From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue Mar 20 12:31:40 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 20 Mar 2012 13:31:40 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <87k42fplgw.fsf@minignu.minidns.net> References: <87k42fplgw.fsf@minignu.minidns.net> Message-ID: <4F6878AC.40402@pu-pm.univ-fcomte.fr> On 20/03/12 12:20, Dima wrote: > >>>>> Hi. >>>>> Ekiga 3.2.7 at Debian/SID (powerpc). >>>>> >>>>> When I call 500 at ekiga dot net, I hear silence, >>>>> and in fact, the numbers at the bottom of a window show that >>>>> no audio is received from the ekiga.net server. Video is ok, >>>>> after 20 sec my cam is echoed to me back. >>>>> >>>>> On the other hand, when I use the 520 at ekiga dot net, >>>>> it returns call to me, and then audio is just fine. >>>>> Other audio echo services (4444 at sip2sip dot info) work fine. >>>>> >>>>> With Twinkle on the same machine the audio echo from 500 at ekiga is fine. >>>>> >>>>> What can be the reason that with Ekiga I get no audio echo from 500 ? >>>> >>>> This is surely a bug. Could you use in debian the ekiga version from >>>> experimental and tell if the problem persists? >>> >>> Hi, Eugen. >>> >>> I have built ekiga-snapshot using your script. Exactly the same phenomena >>> persists. It is Debian Sid on PowerPC-32bit (iBook G4). Maybe its >>> endianness matters ?! >> >> It seems yes. In the past, I used a macbook too. >> >> Please provide a log when calling 500 and does not work. It never >> works, is that right? Or sometimes yes, sometimes not? > > I will provide a log at night (currently I have no access). > The behaviour is consistent, i.e. it is always as I described above. > > Creating log is `ekiga-snapshot -d 4 2> log' ? Yes. -- Eugen From dima at minignu.minidns.net Wed Mar 21 00:45:44 2012 From: dima at minignu.minidns.net (Dima) Date: Wed, 21 Mar 2012 02:45:44 +0200 Subject: [Ekiga-list] Ekiga + encryption Message-ID: <874ntin5mv.fsf@minignu.minidns.net> Hi, Does Ekiga encrypt audio and video streams in a conversation? If yes - probably the subject of encryption is a complex one - i.e. which certificates are envolved e.t.c. - where can I find more information on the encryption fundamentals in Ekiga? If not - what is the easiest way to use some external means in order to keep conversations encrypted ? Thanks, Dima. From dima at minignu.minidns.net Wed Mar 21 00:50:08 2012 From: dima at minignu.minidns.net (Dima) Date: Wed, 21 Mar 2012 02:50:08 +0200 Subject: [Ekiga-list] Ekiga with no ports forwarded to it Message-ID: <871uomn5fj.fsf@minignu.minidns.net> Hi. What is the right way to configure Ekiga for operation on a laptop that primarily uses public WiFi for internet connection? Surely no ports will be forwarded for it and it will probably sit behind NAT... Any material to read? Thanks, Dima. From stuart at gathman.org Wed Mar 21 04:51:31 2012 From: stuart at gathman.org (Stuart Gathman) Date: Wed, 21 Mar 2012 00:51:31 -0400 Subject: [Ekiga-list] Ekiga with no ports forwarded to it In-Reply-To: <871uomn5fj.fsf@minignu.minidns.net> References: <871uomn5fj.fsf@minignu.minidns.net> Message-ID: <4F695E53.2090800@gathman.org> Long ago, Nostradamus foresaw that on 03/20/2012 08:50 PM, Dima would write: > What is the right way to configure Ekiga for operation on a laptop that > primarily uses public WiFi for internet connection? > > Surely no ports will be forwarded for it and it will probably sit behind > NAT... > You will not be able to receive direct VOIP calls. However, it will work with a POTS service such as diamondcard (Ekiga Callout) or other VOIP telephone service. diamondcard also offers VPN service, which will encrypt your calls (between you and their servers). I have family members on openvpn, which then lets you make direct VOIP calls to other members on the VPN via their private IP. This also encrypts the calls. IP6 would also solve the NAT problems, and I have IP6 everywhere. But the last time I checked, Ekiga did not work with IP6. It would also work with a SIP proxy service - an asterisk server somewhere on a direct IP - to make and receive VOIP calls. If you don't want to undertake the (daunting) task of operating asterisk on a home server, you can buy an embedded box for less than $1000 (more $$$ for more "lines") that provides sip proxy, telco interface, etc, etc. You still need an unnatted IP for your sip proxy. From geo.cherchetout at laposte.net Wed Mar 21 09:15:43 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Wed, 21 Mar 2012 10:15:43 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F6865D3.4000801@pu-pm.univ-fcomte.fr> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> Message-ID: <4F699C3F.5080500@laposte.net> Le 20/03/2012 12:11, *Eugen Dedu* a ?crit fort ? propos : >> Using Linphone, I notice the opposite behaviour : Good audio and video >> echo on 500 and neither sound nor video on 520. >> >> Using ekiga 3.2.7, wich is the current available version on Mageia, 500 >> is perfect echoing audio and video (PCMA - H261) and 520 doesn't recall me. > > geo, please provide -d 4 log when calling 500 and 520. They are in your private mail box. From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 15:06:48 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 16:06:48 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F699C3F.5080500@laposte.net> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> Message-ID: <4F69EE88.8040606@pu-pm.univ-fcomte.fr> On 21/03/12 10:15, geo cherchetout wrote: > Le 20/03/2012 12:11, *Eugen Dedu* a ?crit fort ? propos : > >>> Using Linphone, I notice the opposite behaviour : Good audio and video >>> echo on 500 and neither sound nor video on 520. >>> >>> Using ekiga 3.2.7, wich is the current available version on Mageia, 500 >>> is perfect echoing audio and video (PCMA - H261) and 520 doesn't >>> recall me. >> >> geo, please provide -d 4 log when calling 500 and 520. > > They are in your private mail box. What does "gconftool -g /apps/ekiga/protocols/ports/udp_port_range" show on the machine where it does not work? -- Eugen From geo.cherchetout at laposte.net Wed Mar 21 15:22:19 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Wed, 21 Mar 2012 16:22:19 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F69EE88.8040606@pu-pm.univ-fcomte.fr> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> <4F69EE88.8040606@pu-pm.univ-fcomte.fr> Message-ID: <4F69F22B.3030204@laposte.net> Le 21/03/2012 16:06, *Eugen Dedu* a ?crit fort ? propos : > gconftool -g /apps/ekiga/protocols/ports/udp_port_range 5060:5100 From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 15:30:28 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 16:30:28 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F69F22B.3030204@laposte.net> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> <4F69EE88.8040606@pu-pm.univ-fcomte.fr> <4F69F22B.3030204@laposte.net> Message-ID: <4F69F414.1010008@pu-pm.univ-fcomte.fr> On 21/03/12 16:22, geo cherchetout wrote: > Le 21/03/2012 16:06, *Eugen Dedu* a ?crit fort ? propos : >> gconftool -g /apps/ekiga/protocols/ports/udp_port_range > > 5060:5100 Could you increase these values to 5060:65000 for example and retry? Also, check off all g726* audio codecs. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 15:32:13 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 16:32:13 +0100 Subject: [Ekiga-list] Ekiga + encryption In-Reply-To: <874ntin5mv.fsf@minignu.minidns.net> References: <874ntin5mv.fsf@minignu.minidns.net> Message-ID: <4F69F47D.7040708@pu-pm.univ-fcomte.fr> On 21/03/12 01:45, Dima wrote: > Hi, > Does Ekiga encrypt audio and video streams in a conversation? No. > If yes - probably the subject of encryption is a complex one - > i.e. which certificates are envolved e.t.c. - where can I find more > information on the encryption fundamentals in Ekiga? > > If not - what is the easiest way to use some external means in order to > keep conversations encrypted ? I do not know, but if I remember correctly there were 1 or 2 threads on this subject and they provided a solution using some external machine (not remember exactly how). -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 15:34:52 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 16:34:52 +0100 Subject: [Ekiga-list] Ekiga with no ports forwarded to it In-Reply-To: <871uomn5fj.fsf@minignu.minidns.net> References: <871uomn5fj.fsf@minignu.minidns.net> Message-ID: <4F69F51C.3090606@pu-pm.univ-fcomte.fr> On 21/03/12 01:50, Dima wrote: > Hi. > > What is the right way to configure Ekiga for operation on a laptop that > primarily uses public WiFi for internet connection? > > Surely no ports will be forwarded for it and it will probably sit behind > NAT... It should work, except if you are behind symmetric nat (or a completely blocked one). > Any material to read? http://wiki.ekiga.org/index.php/Understanding_NAT/firewall_issues_with_SIP_clients_%28eg_ekiga%29 -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 15:39:22 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 16:39:22 +0100 Subject: [Ekiga-list] trouble with HD web cam logtech B990 In-Reply-To: <4F62E7AA.9010703@cplus.ru> References: <4F62E7AA.9010703@cplus.ru> Message-ID: <4F69F62A.4080606@pu-pm.univ-fcomte.fr> On 16/03/12 08:11, "??????? ?. ??????" wrote: > Hi guys! > > I have a some problem with "HD Web Cam Logitech B990". May be you know > about my problem)? > > In debug mode I see following: > > $ ekiga -d 1 > >> 2012/03/15 18:56:50.296 0:00.030 Version 3.2.7 by on Unix Linux >> (2.6.32-5-686-i686) with PTLib (v2.6.7) at 2012/3/15 18:56:50.296 >> 2012/03/15 18:56:50.296 0:00.030 Ekiga git revision: unknown >> 2012/03/15 18:56:50.300 0:00.034 HalManager_dbus Populating full >> device list failed - The name org.freedesktop.Hal was not provided by >> any .service files >> 2012/03/15 18:56:50.300 0:00.034 HalManager_dbus Populating full >> interface list failed - Method "getDevices" with signature "" on >> interface "org.freedesktop.NetworkManager" doesn't exist >> >> 2012/03/15 18:56:50.335 0:00.069 Detecting V4L2 devices >> 2012/03/15 18:57:15.944 0:25.678 Ekiga version 3.2.7 >> 2012/03/15 18:57:15.944 0:25.678 OPAL version 3.6.8 >> 2012/03/15 18:57:15.944 0:25.678 PTLIB version 2.6.7 >> 2012/03/15 18:57:15.944 0:25.678 GNOME support disabled >> 2012/03/15 18:57:15.944 0:25.678 Accelerated rendering support enabled >> 2012/03/15 18:57:15.944 0:25.678 DBUS support enabled >> 2012/03/15 18:57:15.944 0:25.678 GConf support enabled >> 2012/03/15 18:57:15.944 0:25.678 ESound support disabled >> 2012/03/15 18:57:19.592 0:29.326 Detecting V4L2 devices >> 2012/03/15 18:57:19.608 0:29.342 PVidInDev Open() videoFd:-1 >> 2012/03/15 18:57:19.608 0:29.342 PVidInDev Close() videoFd:-1 started:0 >> 2012/03/15 18:57:19.608 0:29.342 Detecting V4L2 devices >> 2012/03/15 18:57:19.619 0:29.353 PVidInDev Open() devName:/dev/video0 >> videoFd:-1 >> 2012/03/15 18:57:19.628 0:29.362 VideoInputDevice S_STD failed : >> ???????????? ???????? >> libv4l2: error converting / decoding frame data: v4l-convert: error >> parsing JPEG header: Bogus jpeg format >> 2012/03/15 18:57:20.324 0:30.058 VideoPrevi...0xb4e39b70 PVidInDev >> QBUF failed : ???????????? ???????? >> 2012/03/15 18:57:20.324 0:30.058 VideoPrevi...0xb4e39b70 >> GMVideoInputManager_ptlib Expected a frame of 115200 bytes but got >> 9352 bytes >> 2012/03/15 18:57:20.326 0:30.060 GMVideoOut...0xb4db7b70 XVideo >> XQueryShmExtension success >> 2012/03/15 18:57:20.327 0:30.061 GMVideoOut...0xb4db7b70 XVideo Using >> SHM extension >> 2012/03/15 18:57:20.327 0:30.061 GMVideoOut...0xb4db7b70 X11 Unknown X >> Event 19 received >> libv4l2: error converting / decoding frame data: v4l-convert: error >> parsing JPEG header: Bogus jpeg format Well, I have never seen this error. But the error is there: "v4l-convert: error parsing JPEG header: Bogus jpeg format". Try looking in Internet on this error. The error on S_STD is harmless. > $ uname -a >> Linux test 2.6.32-5-686 #1 SMP Mon Jan 16 16:04:25 UTC 2012 i686 >> GNU/Linux > (latest Debian Dsktop 32bit) > > $ lsusb >> Bus 001 Device 004: ID 046d:0828 Logitech, Inc. HD Webcam B990 > $ sudo lsmod | grep pwc > $(nothing) -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 15:43:16 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 16:43:16 +0100 Subject: [Ekiga-list] Fw: Add a menu entry of "ekiga -d 4" output In-Reply-To: <20120202100846.48f14847@acer> References: <20120113123110.71cbf8f2@acer> <20120113182934.440eda4e@acer> <4F11FF2E.4050802@davekoelmeyer.co.nz> <20120202100846.48f14847@acer> Message-ID: <4F69F714.70509@pu-pm.univ-fcomte.fr> On 02/02/12 09:08, Genghis Khan wrote: > On Sun, 15 Jan 2012 11:18:22 +1300 > Dave Koelmeyer wrote: > >> On 01/14/12 05:29 AM, Genghis Khan wrote: >>> On Fri, 13 Jan 2012 12:31:10 +0200 >>> Genghis Khan wrote: >>> >>>> Add a menu item in the Help menu which will say "Auto-build a >>>> report" "Analise and send" or "anything else", which will prompt >>>> the user to a dialog which will explain shortly what is this >>>> feature, what does it do and so on... and it will tell to the user >>>> that Ekiga is going to restart itself and will generate a debug >>>> file and there will be a link to the Users Mailing List or to both >>>> Users (Help) and Devel (Development) Mailing Lists. >>>> >>>> Any thoughts? >> >> Well, I couldn't implement such a feature, but sounds good to me. >> > Should this be realized into a script? (as a separate command) > $ ekiga-debug > > The script will display a box with instructions in the following manner: > > ----------------------------------------------------------- > | | > | ----------- ---------------------------------------- | > | | | |Welcome to the Debugging Tool of Ekiga| | > | | Icon of | | | | > | | Ekiga | | TEXT | | > | | | | TEXT | | > | ----------- | ... | | > | | | | > | | | | > | | | | > | | | | > | | | | > | | | | > | | | | > | | | | > | | | | > | | | | > | | | | > | ---------------------------------------- | > |-------------------------------------------------------- | > | ? Advanced View | Cancel | Back | Forward | | > ----------------------------------------------------------- > > Maybe better to make it look like the Configuration Assistant. > > > Instructions like. > > $ ekiga-debug > Error: Ekiga is running. Close Ekiga and try again. > > On the Welcome dialog: > Close Ekiga > Run the command (ekiga-debug) > Repeat the steps that caused to the problem. > Exit Ekiga > > > Or maybe even something like this: > > (Dialog has started) > (The user is clicking on Next, while Ekiga is still running) > Message: Ekiga is running, would you like to close it? (yes/no) > > (Closing Ekiga ... ... ...) > > Ekiga doesn't seem to be closing, would you like to terminate the > process Ekiga? (yes/no) > > (Killing Ekiga...) > > etc. > > > The script will compress the output (text) in whatever archiving format > available (7z, gzip, tar, zip). > > The output will contain the version of Ekiga and date: > Ekiga-3.3.2_YYYY-MM-DD.tar.gz > > > A message of where the file was saved to. > > Enabling ? Advanced View will show the log writing in action in an > embedded terminal within the dialog. > $ tail -f Ekiga-3.3.2_YYYY-MM-DD.log > > Maybe some grep actions? or whatever on your mind. Sorry to answer so late. Your idea about informing users is good. There are several cases where user is not guided to find out the error or help him. Using a shell script is not a good idea, since it will not work on Windows. I have to think more on it, I put it on my TODO list. -- Eugen From geo.cherchetout at laposte.net Wed Mar 21 16:13:06 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Wed, 21 Mar 2012 17:13:06 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F69F414.1010008@pu-pm.univ-fcomte.fr> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> <4F69EE88.8040606@pu-pm.univ-fcomte.fr> <4F69F22B.3030204@laposte.net> <4F69F414.1010008@pu-pm.univ-fcomte.fr> Message-ID: <4F69FE12.10809@laposte.net> Le 21/03/2012 16:30, *Eugen Dedu* a ?crit fort ? propos : >> 5060:5100 > > Could you increase these values to 5060:65000 for example and retry? Done. > Also, check off all g726* audio codecs. Not any g726 audio codec whas enabled. Only PCMA, PCMU, Speex and iLBC are. sip:500 at ekiga.net works perfectly. sip:520 at ekiga.net : A communication with PCMA-H261 codecs seems to be established and doesn't automatically finishes. During this communication, the video displayed is local video and I hear no sound. From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 16:19:03 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 17:19:03 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F69FE12.10809@laposte.net> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> <4F69EE88.8040606@pu-pm.univ-fcomte.fr> <4F69F22B.3030204@laposte.net> <4F69F414.1010008@pu-pm.univ-fcomte.fr> <4F69FE12.10809@laposte.net> Message-ID: <4F69FF77.20805@pu-pm.univ-fcomte.fr> On 21/03/12 17:13, geo cherchetout wrote: > Le 21/03/2012 16:30, *Eugen Dedu* a ?crit fort ? propos : > >>> 5060:5100 >> >> Could you increase these values to 5060:65000 for example and retry? > > Done. > >> Also, check off all g726* audio codecs. > > Not any g726 audio codec whas enabled. Only PCMA, PCMU, Speex and iLBC are. You are right, sorry. Please check off h263 and mp4v-es video codecs and try again. In fact, I noticed two strange things in your log: - your packet is greater than about 1500 bytes, yet it is still received by ekiga.net. You are connected via a cable (Ethernet), not wi-fi, is that right? - you do not use 5060 port, but another one, however here it works with another port too, maybe it would be useful to bind to the classical 5060 port (/apps/ekiga/protocols/sip/listen_port) > sip:500 at ekiga.net works perfectly. > > sip:520 at ekiga.net : A communication with PCMA-H261 codecs seems to be > established and doesn't automatically finishes. THAT is the problem, I do not know why you do not receive the BYE message from 520. Here it works... -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 16:32:25 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 17:32:25 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F69FF77.20805@pu-pm.univ-fcomte.fr> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> <4F69EE88.8040606@pu-pm.univ-fcomte.fr> <4F69F22B.3030204@laposte.net> <4F69F414.1010008@pu-pm.univ-fcomte.fr> <4F69FE12.10809@laposte.net> <4F69FF77.20805@pu-pm.univ-fcomte.fr> Message-ID: <4F6A0299.7020707@pu-pm.univ-fcomte.fr> On 21/03/12 17:19, Eugen Dedu wrote: > On 21/03/12 17:13, geo cherchetout wrote: >> Le 21/03/2012 16:30, *Eugen Dedu* a ?crit fort ? propos : >> >>>> 5060:5100 >>> >>> Could you increase these values to 5060:65000 for example and retry? >> >> Done. >> >>> Also, check off all g726* audio codecs. >> >> Not any g726 audio codec whas enabled. Only PCMA, PCMU, Speex and iLBC >> are. > > You are right, sorry. Please check off h263 and mp4v-es video codecs and > try again. > > In fact, I noticed two strange things in your log: > - your packet is greater than about 1500 bytes, yet it is still received > by ekiga.net. You are connected via a cable (Ethernet), not wi-fi, is > that right? > - you do not use 5060 port, but another one, however here it works with > another port too, maybe it would be useful to bind to the classical 5060 > port (/apps/ekiga/protocols/sip/listen_port) And especially this one: 2012/03/20 17:52:12.955 0:29.348 CallSetup:0x56873700 STUN Could not get a pair of adjacent port numbers from NAT which means that it did not succeed to bind to two adjacent ports, which is very very strange... >> sip:500 at ekiga.net works perfectly. >> >> sip:520 at ekiga.net : A communication with PCMA-H261 codecs seems to be >> established and doesn't automatically finishes. > > THAT is the problem, I do not know why you do not receive the BYE > message from 520. Here it works... -- Eugen From geo.cherchetout at laposte.net Wed Mar 21 16:35:12 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Wed, 21 Mar 2012 17:35:12 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F69F414.1010008@pu-pm.univ-fcomte.fr> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> <4F69EE88.8040606@pu-pm.univ-fcomte.fr> <4F69F22B.3030204@laposte.net> <4F69F414.1010008@pu-pm.univ-fcomte.fr> Message-ID: <4F6A0340.4030206@laposte.net> Le 21/03/2012 16:30, *Eugen Dedu* a ?crit fort ? propos : > Could you increase these values to 5060:65000 for example and retry? > > Also, check off all g726* audio codecs. New: When my ekiga is listening on port 5061, every thing works. sip:520 at ekiga.net calls me back and I hear my voice. (Video is local.) (Sometimes I have to unplug/replug my webcam.) Sorry, I thought I whas always listening on 5061 but I did listen on 5060 these last days. (New installation whith Mageia.) It is better for me listening on 5061 because 5060 is used by an ATA included in my modem. Thank you for your help. :-) From geo.cherchetout at laposte.net Wed Mar 21 16:43:42 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Wed, 21 Mar 2012 17:43:42 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F6A0340.4030206@laposte.net> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> <4F69EE88.8040606@pu-pm.univ-fcomte.fr> <4F69F22B.3030204@laposte.net> <4F69F414.1010008@pu-pm.univ-fcomte.fr> <4F6A0340.4030206@laposte.net> Message-ID: <4F6A053E.9080207@laposte.net> Le 21/03/2012 17:35, *geo cherchetout* a ?crit : > sip:520 at ekiga.net calls me back and I hear my voice. (Video is local.) Hum, *sometimes* only it calls me back after a three seconds initial communication. More frequently, the initial communication never ends... From geo.cherchetout at laposte.net Wed Mar 21 16:49:57 2012 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Wed, 21 Mar 2012 17:49:57 +0100 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F69FF77.20805@pu-pm.univ-fcomte.fr> References: <20120109231740.3148D7A066@minignu.minidns.net> <4F68520E.70007@laposte.net> <4F6865D3.4000801@pu-pm.univ-fcomte.fr> <4F699C3F.5080500@laposte.net> <4F69EE88.8040606@pu-pm.univ-fcomte.fr> <4F69F22B.3030204@laposte.net> <4F69F414.1010008@pu-pm.univ-fcomte.fr> <4F69FE12.10809@laposte.net> <4F69FF77.20805@pu-pm.univ-fcomte.fr> Message-ID: <4F6A06B5.3080408@laposte.net> Le 21/03/2012 17:19, *Eugen Dedu* a ?crit fort ? propos : > You are right, sorry. Please check off h263 and mp4v-es video codecs > and try again. Done but I don't see any better behaviour. From jbuhl_nospam at gmx.net Wed Mar 21 18:07:26 2012 From: jbuhl_nospam at gmx.net (josh) Date: Wed, 21 Mar 2012 19:07:26 +0100 Subject: [Ekiga-list] could not register sip... Message-ID: <4F6A18DE.2020807@gmx.net> Hi, ekiga cannot register my sip address. I have manually configured port forwarding on my router according to the wiki. I forward: ports 5000-5100 udp (sip) ports 3478-3479 udp (stun) port 1720 tcp (h323) yes, I did my duty and searched the forum for this topic and scanned through about twenty or more of the hits for "could not register sip". unfortunately, it seems there is no panacea for this error. I also grep'ed the debug output for "REGISTER" and tried to figure it out, but I am not familiar enough with the ekiga debug output to figure out what exactly isn't working. Many thanks in advance if somebody can help me figure out why it isn't working. my ekiga -d 4 2>/tmp/output.txt output follows. cheers, -j -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: output.txt URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 19:23:09 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 20:23:09 +0100 Subject: [Ekiga-list] could not register sip... In-Reply-To: <4F6A18DE.2020807@gmx.net> References: <4F6A18DE.2020807@gmx.net> Message-ID: <4F6A2A9D.2010409@pu-pm.univ-fcomte.fr> On 21/03/12 19:07, josh wrote: > Hi, > > ekiga cannot register my sip address. > > I have manually configured port forwarding on my router according to the > wiki. I forward: > > ports 5000-5100 udp (sip) > ports 3478-3479 udp (stun) > port 1720 tcp (h323) > > yes, I did my duty and searched the forum for this topic and scanned > through about twenty or more of the hits for "could not register sip". > unfortunately, it seems there is no panacea for this error. I also > grep'ed the debug output for "REGISTER" and tried to figure it out, but > I am not familiar enough with the ekiga debug output to figure out what > exactly isn't working. > > Many thanks in advance if somebody can help me figure out why it isn't > working. > > my ekiga -d 4 2>/tmp/output.txt output follows. Do you have an ekiga.net (or other) account?? If yes, then send us the full log, it seems you truncated it. -- Eugen From jbuhl_nospam at gmx.net Wed Mar 21 20:08:54 2012 From: jbuhl_nospam at gmx.net (joshbuhl) Date: Wed, 21 Mar 2012 13:08:54 -0700 (PDT) Subject: [Ekiga-list] could not register sip... In-Reply-To: <4F6A2A9D.2010409@pu-pm.univ-fcomte.fr> References: <4F6A18DE.2020807@gmx.net> <4F6A2A9D.2010409@pu-pm.univ-fcomte.fr> Message-ID: <1332360534145-4493584.post@n4.nabble.com> HI Eugen, thanks for replying. >Do you have an ekiga.net (or other) account?? If yes, then send us the >full log, it seems you truncated it. yes, I have an ekiga.net account. I did truncate the output. The reason is that with the full log my post was larger than 40kb and after three days of awaiting moderator approval, I cancelled the post and resubmitted with a truncated log...it looked to me like the log just kept repeating itself, but I'll be happy to submit a full log if a mod will approve the post... cheers, -j -- View this message in context: http://ekiga.1756082.n4.nabble.com/could-not-register-sip-tp4493203p4493584.html Sent from the Ekiga General mailing list archive at Nabble.com. From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 21 20:47:42 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 21 Mar 2012 21:47:42 +0100 Subject: [Ekiga-list] could not register sip... In-Reply-To: <1332360534145-4493584.post@n4.nabble.com> References: <4F6A18DE.2020807@gmx.net> <4F6A2A9D.2010409@pu-pm.univ-fcomte.fr> <1332360534145-4493584.post@n4.nabble.com> Message-ID: <4F6A3E6E.7020204@pu-pm.univ-fcomte.fr> On 21/03/12 21:08, joshbuhl wrote: > HI Eugen, > > thanks for replying. > >> Do you have an ekiga.net (or other) account?? If yes, then send us the >> full log, it seems you truncated it. > > yes, I have an ekiga.net account. I did truncate the output. The reason is > that with the full log my post was larger than 40kb and after three days of > awaiting moderator approval, I cancelled the post and resubmitted with a > truncated log...it looked to me like the log just kept repeating itself, but > I'll be happy to submit a full log if a mod will approve the post... We need the full log, see http://wiki.ekiga.org/index.php/Debugging_Ekiga#Sending_the_data_to_us for information on how to send it. I have just added a paragraph about moderator approval... -- Eugen From dima at minignu.minidns.net Wed Mar 21 21:40:24 2012 From: dima at minignu.minidns.net (Dima) Date: Wed, 21 Mar 2012 23:40:24 +0200 Subject: [Ekiga-list] Difference between 500 and 520 echoes In-Reply-To: <4F6878AC.40402@pu-pm.univ-fcomte.fr> Message-ID: <87ehsl8wfr.fsf@minignu.minidns.net> >>>>>> Hi. >>>>>> Ekiga 3.2.7 at Debian/SID (powerpc). >>>>>> >>>>>> When I call 500 at ekiga dot net, I hear silence, >>>>>> and in fact, the numbers at the bottom of a window show that >>>>>> no audio is received from the ekiga.net server. Video is ok, >>>>>> after 20 sec my cam is echoed to me back. >>>>>> >>>>>> On the other hand, when I use the 520 at ekiga dot net, >>>>>> it returns call to me, and then audio is just fine. >>>>>> Other audio echo services (4444 at sip2sip dot info) work fine. >>>>>> >>>>>> With Twinkle on the same machine the audio echo from 500 at ekiga is fine. >>>>>> >>>>>> What can be the reason that with Ekiga I get no audio echo from 500 ? >>>>> >>>>> This is surely a bug. Could you use in debian the ekiga version from >>>>> experimental and tell if the problem persists? >>>> >>>> Hi, Eugen. >>>> >>>> I have built ekiga-snapshot using your script. Exactly the same phenomena >>>> persists. It is Debian Sid on PowerPC-32bit (iBook G4). Maybe its >>>> endianness matters ?! >>> >>> It seems yes. In the past, I used a macbook too. >>> >>> Please provide a log when calling 500 and does not work. It never >>> works, is that right? Or sometimes yes, sometimes not? >> >> I will provide a log at night (currently I have no access). >> The behaviour is consistent, i.e. it is always as I described above. >> >> Creating log is `ekiga-snapshot -d 4 2> log' ? > > Yes. Hi. My results are different from what did I initially reported (the location of the machine changed?). But nevertheless, here they are This time I was sitting behind a router (another GNU/Linux box). EKIGA-SNAPSHOT (20 Mar 2012) and Ekiga3.2.7 behave similarily ALL DEBUG LOGS ARE FOR EKIGA-SNAPSHOT 1. When port forwarding is set as needed http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually both 500 and 520 work. Debug logs for 500 were created. 2. When no port forwarding is done, the results surprised me: 500 has video echo, but no audio echo (logs created). 520 succeeds to call back (how?) and audio echo works! (logs created) Debug logs can be downloaded from http://minignu.minidns.net/ppc32_ekiga_dbg_logs.tar.xz Thanks, Dima. From Markus.Elfring at web.de Thu Mar 22 20:56:02 2012 From: Markus.Elfring at web.de (Markus Elfring) Date: Thu, 22 Mar 2012 21:56:02 +0100 Subject: [Ekiga-list] Difficulties with parallel operation of SIP/H.323 applications? Message-ID: <4F6B91E2.3080509@web.de> Hello! I have found a few details for the question "Which programs don't work with Ekiga?" http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Which_programs_don.27t_work_with_Ekiga_.3F A few applications are not interoperable so far because there are limitations in the exchange of communication addresses. I would like to check if there are also more unpleasant technical challenges in the use case for the parallel operation of telephony applications. Is there any fine-tuning needed on the system setting which program will be configured as the default VoIP application? Does an Ekiga installation block the use of other tools like Skype or MSN eventually? Regards, Markus From jbuhl_nospam at gmx.net Sat Mar 24 13:05:40 2012 From: jbuhl_nospam at gmx.net (josh) Date: Sat, 24 Mar 2012 14:05:40 +0100 Subject: [Ekiga-list] could not register sip... Message-ID: <4F6DC6A4.8000702@gmx.net> Hi Eugen, thanks for your assistance. I wanted to generate a full log like you suggested, so I started ekiga like this: $ ekiga -d 4 2>/tmp/output.txt I let it fire up, waited til I saw the error message, tried connecting to the echo service and then clicked close in the menu. The gui disappeared, but an hour later there was still output being generated into output.txt. It doesn't ever stop until I kill it. How much of that log do you need? Attaching an amount that gives less than 40kb zipped (I have a 3Mb log...) -j >We need the full log, see >http://wiki.ekiga.org/index.php/Debugging_Ekiga#Sending_the_data_to_us >for information on how to send it. I have just added a paragraph >about >moderator approval... -------------- next part -------------- A non-text attachment was scrubbed... Name: output.txt.gz Type: application/x-gzip Size: 27546 bytes Desc: not available URL: From listbox at snap.net.nz Mon Mar 26 09:28:58 2012 From: listbox at snap.net.nz (listbox) Date: Mon, 26 Mar 2012 22:28:58 +1300 Subject: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready.) Message-ID: <20120326222858.70a1f3f1@snap.net.nz> Hi all, Over the past year I've had four or five goes at getting Ekiga to work (on a couple of distros). No matter the configuration, I can't get a successful echo test. I can connect to the echo test, and I can hear the voice describing the test, but as soon as she finishes the A:8.0/8.0 indicator at the bottom of the window changes to A:8.0/0.0. I cannot successfully echo and, in time, I am told that I have closed the connection. I'm guessing the crux is "RTP_UDP Session 1, Data port on remote not ready," which leads to, "RTP_UDP Session 1, Data 10 seconds of transmit fails - informing connection," and finally, "RTPCon Clearing call as all RTP session are failing." I know I'm not alone: I've seen other users with this RTP_UDP error, but as far as I can tell no one has figured out why this is happening. Thoughts are welcome. Thanks! Debug level two output follows: 2012/03/26 21:56:16.394 0:00.012 ThreadID:0x7c3728c0 Ekiga version 3.3.2 2012/03/26 21:56:16.394 0:00.012 ThreadID:0x7c3728c0 Ekiga git revision: unknown 2012/03/26 21:56:16.394 0:00.012 ThreadID:0x7c3728c0 Debug level: 2 2012/03/26 21:56:16.407 0:00.025 OpalPlugin Not adding H.323 capability for plugin codec H.263 as this has been specifically disabled 2012/03/26 21:56:16.412 0:00.030 OpalPlugin Plugin Codec DLL mpeg4_ffmpeg_ptplugin contains no codec definitions 2012/03/26 21:56:16.426 0:00.044 PTLib No permission to set priority level 4 2012/03/26 21:56:16.426 0:00.044 PTLib No permission to set priority level 4 2012/03/26 21:56:16.428 0:00.046 PTLib No permission to set priority level 4 2012/03/26 21:56:16.429 0:00.047 HalManager_dbus Populating full device list failed - The name org.freedesktop.Hal was not provided by any .service files 2012/03/26 21:56:16.429 0:00.047 HalManager_dbus Populating full interface list failed - The name org.freedesktop.NetworkManager was not provided by any .service files 2012/03/26 21:56:16.430 0:00.047 Detecting V4L2 devices 2012/03/26 21:56:16.430 0:00.047 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/26 21:56:16.442 0:00.060 Detecting V4L2 devices 2012/03/26 21:56:16.442 0:00.060 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/26 21:56:16.476 0:00.093 PTLib No permission to set priority level 4 2012/03/26 21:56:16.476 0:00.094 PTLib No permission to set priority level 4 2012/03/26 21:56:41.540 0:25.157 Detecting V4L2 devices 2012/03/26 21:56:41.540 0:25.158 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/26 21:56:41.553 0:25.171 Detecting V4L2 devices 2012/03/26 21:56:41.553 0:25.171 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/26 21:56:41.565 0:25.183 Detecting V4L2 devices 2012/03/26 21:56:41.565 0:25.183 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/26 21:56:41.691 0:25.308 Detecting V4L2 devices 2012/03/26 21:56:41.691 0:25.308 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/26 21:56:41.703 0:25.320 Detecting V4L2 devices 2012/03/26 21:56:41.703 0:25.320 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/26 21:56:41.757 0:25.375 Ekiga version 3.3.2 2012/03/26 21:56:41.757 0:25.375 OPAL version 3.10.2 2012/03/26 21:56:41.757 0:25.375 PTLIB version 2.10.2 2012/03/26 21:56:41.757 0:25.375 Accelerated rendering support enabled 2012/03/26 21:56:41.757 0:25.375 DBUS support enabled 2012/03/26 21:56:41.757 0:25.375 GConf support enabled 2012/03/26 21:56:42.695 0:26.313 Opal Liste...0x68186700 Listen UDP read error. 2012/03/26 21:56:43.015 0:26.633 PTLib No permission to set priority level 4 2012/03/26 21:56:43.343 0:26.961 SIPPres SRV lookup for '_pres._sip.ekiga.net' failed 2012/03/26 21:56:43.996 0:27.614 Opal Liste...0x68186700 PTLib No permission to set priority level 3 2012/03/26 21:56:44.007 0:27.624 Pool:0x68104700 SIPPres 'sip:REDACTED at ekiga.net' error subscribing to presence of 'sip:500 at ekiga.net' 2012/03/26 21:56:44.887 0:28.505 Pool:0x68104700 SIPPres 'sip:REDACTED at ekiga.net' error subscribing to presence of 'sip:501 at ekiga.net' 2012/03/26 21:56:45.888 0:29.506 Pool:0x68104700 SIPPres 'sip:REDACTED at ekiga.net' error subscribing to presence of 'sip:520 at ekiga.net' 2012/03/26 21:56:55.829 0:39.447 CallSetup:0x40064700 RTP_UDP SetOption(8,1048576) failed, even though it said it succeeded! 2012/03/26 21:56:55.830 0:39.447 CallSetup:0x40064700 RTP_UDP SetOption(8,524288) failed, even though it said it succeeded! 2012/03/26 21:56:55.830 0:39.447 CallSetup:0x40064700 RTP_UDP SetOption(8,262144) failed, even though it said it succeeded! 2012/03/26 21:56:55.830 0:39.447 CallSetup:0x40064700 MediaFormat Validation of merge for media option "Packetization Mode" failed. 2012/03/26 21:56:56.145 0:39.762 Opal Liste...0x68186700 PTLib No permission to set priority level 3 2012/03/26 21:56:56.146 0:39.764 Pool:0x40064700 MediaFormat Validation of merge for media option "Packetization Mode" failed. 2012/03/26 21:56:56.150 0:39.767 Pool:0x40064700 SIP PDU is likely too large (1592 bytes) for UDP datagram. 2012/03/26 21:56:56.472 0:40.090 Pool:0x40064700 SDP Unknown media attribute silenceSupp 2012/03/26 21:56:56.476 0:40.094 Pool:0x40064700 RTP_UDP Session 1, sending empty datagrams to open local Port Restricted NAT 2012/03/26 21:56:56.487 0:40.104 Pool:0x40064700 PTLib No permission to set priority level 3 2012/03/26 21:56:56.495 0:40.113 Pool:0x40064700 PTLib No permission to set priority level 3 2012/03/26 21:56:56.496 0:40.113 Pool:0x40064700 RTP_UDP Session 2, sending empty datagrams to open local Port Restricted NAT 2012/03/26 21:56:56.498 0:40.115 Pool:0x40064700 PTLib No permission to set priority level 3 2012/03/26 21:56:56.499 0:40.117 Pool:0x40064700 Detecting V4L2 devices 2012/03/26 21:56:56.499 0:40.117 Pool:0x40064700 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/26 21:56:56.512 0:40.130 Pool:0x40064700 PTLib No permission to set priority level 3 2012/03/26 21:56:56.524 0:40.141 GMVideoOut...0x7c2e8700 XVideo XQueryShmExtension success 2012/03/26 21:56:56.524 0:40.142 GMVideoOut...0x7c2e8700 XVideo Using SHM extension 2012/03/26 21:56:56.525 0:40.143 GMVideoOut...0x7c2e8700 X11 Unknown X Event 19 received 2012/03/26 21:56:56.660 0:40.278 GMVideoOut...0x7c2e8700 XVideo XQueryShmExtension success 2012/03/26 21:56:56.660 0:40.278 GMVideoOut...0x7c2e8700 XVideo Using SHM extension 2012/03/26 21:56:56.660 0:40.278 GMVideoOut...0x7c2e8700 X11 Unknown X Event 19 received 2012/03/26 21:57:00.474 0:44.091 Pool:0x40064700 SIP Cannot find transaction z9hG4bK5842d94e-8f75-e111-9c52-20cf30ac0d5d for response PDU "2 INVITE <200>" 2012/03/26 21:57:04.476 0:48.093 Pool:0x40064700 SIP Cannot find transaction z9hG4bK5842d94e-8f75-e111-9c52-20cf30ac0d5d for response PDU "2 INVITE <200>" 2012/03/26 21:57:08.473 0:52.091 Pool:0x40064700 SIP Cannot find transaction z9hG4bK5842d94e-8f75-e111-9c52-20cf30ac0d5d for response PDU "2 INVITE <200>" 2012/03/26 21:57:12.474 0:56.092 Pool:0x40064700 SIP Cannot find transaction z9hG4bK5842d94e-8f75-e111-9c52-20cf30ac0d5d for response PDU "2 INVITE <200>" 2012/03/26 21:57:16.161 0:59.779 GMVideoOut...0x7c2e8700 XVideo XQueryShmExtension success 2012/03/26 21:57:16.161 0:59.779 GMVideoOut...0x7c2e8700 XVideo Using SHM extension 2012/03/26 21:57:16.162 0:59.779 GMVideoOut...0x7c2e8700 XVideo XQueryShmExtension success 2012/03/26 21:57:16.162 0:59.780 GMVideoOut...0x7c2e8700 XVideo Using SHM extension 2012/03/26 21:57:16.162 0:59.780 GMVideoOut...0x7c2e8700 X11 Unknown X Event 19 received 2012/03/26 21:57:16.162 0:59.780 GMVideoOut...0x7c2e8700 X11 Unknown X Event 19 received 2012/03/26 21:57:16.504 1:00.122 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:16.508 1:00.126 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:16.534 1:00.151 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. 2012/03/26 21:57:16.551 1:00.168 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:16.551 1:00.169 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:16.590 1:00.208 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:17.519 1:01.136 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. 2012/03/26 21:57:18.504 1:02.122 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. 2012/03/26 21:57:19.536 1:03.153 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:20.515 1:04.133 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:21.540 1:05.157 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:22.521 1:06.138 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:23.505 1:07.123 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:24.524 1:08.141 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. 2012/03/26 21:57:25.511 1:09.128 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. 2012/03/26 21:57:26.532 1:10.149 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:26.532 1:10.149 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:27.513 1:11.130 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:27.513 1:11.130 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:28.536 1:12.154 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. 2012/03/26 21:57:28.536 1:12.154 Media Patch:0x3b279700 RTP_UDP Session 2, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:28.536 1:12.154 Media Patch:0x3b279700 RTPCon Clearing call as all RTP session are failing 2012/03/26 21:57:29.519 1:13.136 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:29.519 1:13.136 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:29.519 1:13.136 RTP Jitter:0x3b35c700 RTPCon Clearing call as all RTP session are failing 2012/03/26 21:57:30.508 1:14.125 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. 2012/03/26 21:57:30.508 1:14.125 Media Patch:0x3b279700 RTP_UDP Session 2, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:30.508 1:14.125 Media Patch:0x3b279700 RTPCon Clearing call as all RTP session are failing 2012/03/26 21:57:31.524 1:15.141 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:31.524 1:15.141 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:31.524 1:15.141 RTP Jitter:0x3b35c700 RTPCon Clearing call as all RTP session are failing 2012/03/26 21:57:32.505 1:16.122 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:32.505 1:16.122 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:32.505 1:16.122 RTP Jitter:0x3b35c700 RTPCon Clearing call as all RTP session are failing 2012/03/26 21:57:33.528 1:17.146 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:33.528 1:17.146 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:33.528 1:17.146 RTP Jitter:0x3b35c700 RTPCon Clearing call as all RTP session are failing 2012/03/26 21:57:34.509 1:18.127 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 21:57:34.509 1:18.127 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails - informing connection 2012/03/26 21:57:34.509 1:18.127 RTP Jitter:0x3b35c700 RTPCon Clearing call as all RTP session are failing 2012/03/26 21:57:34.537 1:18.155 Housekeeper:0x7c225700 SIP Transaction 3 BYE sip:500 at 192.168.1.201:5060 failed, unknown handler, ID: 56ea394d-8f75-e111-9c52-20cf30ac0d5d at thishost 2012/03/26 21:57:34.559 1:18.177 Media Patch:0x3b238700 RTP_UDP Session 2, data port on remote not ready 1 time From stuckybyler2 at yahoo.es Mon Mar 26 12:50:45 2012 From: stuckybyler2 at yahoo.es (Carola y Pablo) Date: Mon, 26 Mar 2012 07:50:45 -0500 Subject: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready.) In-Reply-To: <20120326222858.70a1f3f1@snap.net.nz> References: <20120326222858.70a1f3f1@snap.net.nz> Message-ID: <1332766245.2209.2.camel@casa-laptop-ubuntu> When I use echo test with 500 at ekiga.net, it shows it is connected, but I hear nothing.When I try it with 501, Ekiga immediately shuts down. ANy connection? Paul El lun, 26-03-2012 a las 22:28 +1300, listbox escribi?: > Hi all, > > Over the past year I've had four or five goes at getting Ekiga to work > (on a couple of distros). No matter the configuration, I can't get > a successful echo test. > > I can connect to the echo test, and I can hear the voice describing the > test, but as soon as she finishes the A:8.0/8.0 indicator at the bottom > of the window changes to A:8.0/0.0. I cannot successfully echo and, in > time, I am told that I have closed the connection. > > I'm guessing the crux is "RTP_UDP Session 1, Data port on remote not > ready," which leads to, "RTP_UDP Session 1, Data 10 seconds of transmit > fails - informing connection," and finally, "RTPCon Clearing call as > all RTP session are failing." > > I know I'm not alone: I've seen other users with this RTP_UDP error, > but as far as I can tell no one has figured out why this is happening. > Thoughts are welcome. Thanks! > > Debug level two output follows: > > 2012/03/26 21:56:16.394 0:00.012 ThreadID:0x7c3728c0 Ekiga > version 3.3.2 2012/03/26 21:56:16.394 0:00.012 > ThreadID:0x7c3728c0 Ekiga git revision: unknown 2012/03/26 > 21:56:16.394 0:00.012 ThreadID:0x7c3728c0 Debug level: 2 > 2012/03/26 21:56:16.407 0:00.025 > OpalPlugin Not adding H.323 capability for plugin codec H.263 as > this has been specifically disabled 2012/03/26 21:56:16.412 > 0:00.030 OpalPlugin Plugin Codec DLL > mpeg4_ffmpeg_ptplugin contains no codec definitions 2012/03/26 > 21:56:16.426 0:00.044 PTLib No > permission to set priority level 4 2012/03/26 21:56:16.426 > 0:00.044 PTLib No permission to set > priority level 4 2012/03/26 21:56:16.428 > 0:00.046 PTLib No permission to set > priority level 4 2012/03/26 21:56:16.429 > 0:00.047 HalManager_dbus Populating full > device list failed - The name org.freedesktop.Hal was not provided by > any .service files 2012/03/26 21:56:16.429 > 0:00.047 HalManager_dbus Populating full > interface list failed - The name org.freedesktop.NetworkManager was not > provided by any .service files 2012/03/26 21:56:16.430 > 0:00.047 Detecting V4L2 devices 2012/03/26 > 21:56:16.430 0:00.047 PV4L2Plugin > detected device metadata at /sys/class/video4linux/ 2012/03/26 > 21:56:16.442 0:00.060 Detecting V4L2 > devices 2012/03/26 21:56:16.442 0:00.060 > PV4L2Plugin detected device metadata at /sys/class/video4linux/ > 2012/03/26 21:56:16.476 0:00.093 PTLib > No permission to set priority level 4 2012/03/26 21:56:16.476 > 0:00.094 PTLib No permission to set > priority level 4 2012/03/26 21:56:41.540 > 0:25.157 Detecting V4L2 devices 2012/03/26 > 21:56:41.540 0:25.158 PV4L2Plugin > detected device metadata at /sys/class/video4linux/ 2012/03/26 > 21:56:41.553 0:25.171 Detecting V4L2 > devices 2012/03/26 21:56:41.553 0:25.171 > PV4L2Plugin detected device metadata at /sys/class/video4linux/ > 2012/03/26 21:56:41.565 0:25.183 > Detecting V4L2 devices 2012/03/26 21:56:41.565 > 0:25.183 PV4L2Plugin detected device > metadata at /sys/class/video4linux/ 2012/03/26 21:56:41.691 > 0:25.308 Detecting V4L2 devices 2012/03/26 > 21:56:41.691 0:25.308 PV4L2Plugin > detected device metadata at /sys/class/video4linux/ 2012/03/26 > 21:56:41.703 0:25.320 Detecting V4L2 > devices 2012/03/26 21:56:41.703 0:25.320 > PV4L2Plugin detected device metadata at /sys/class/video4linux/ > 2012/03/26 21:56:41.757 0:25.375 Ekiga > version 3.3.2 2012/03/26 21:56:41.757 > 0:25.375 OPAL version 3.10.2 2012/03/26 > 21:56:41.757 0:25.375 PTLIB version > 2.10.2 2012/03/26 21:56:41.757 0:25.375 > Accelerated rendering support enabled 2012/03/26 21:56:41.757 > 0:25.375 DBUS support enabled 2012/03/26 > 21:56:41.757 0:25.375 GConf support > enabled 2012/03/26 21:56:42.695 0:26.313 Opal Liste...0x68186700 > Listen UDP read error. 2012/03/26 21:56:43.015 > 0:26.633 PTLib No permission to set > priority level 4 2012/03/26 21:56:43.343 > 0:26.961 SIPPres SRV lookup for > '_pres._sip.ekiga.net' failed 2012/03/26 21:56:43.996 0:27.614 > Opal Liste...0x68186700 PTLib No permission to set priority level 3 > 2012/03/26 21:56:44.007 0:27.624 Pool:0x68104700 SIPPres > 'sip:REDACTED at ekiga.net' error subscribing to presence of > 'sip:500 at ekiga.net' 2012/03/26 21:56:44.887 0:28.505 > Pool:0x68104700 SIPPres 'sip:REDACTED at ekiga.net' error subscribing to > presence of 'sip:501 at ekiga.net' 2012/03/26 21:56:45.888 > 0:29.506 Pool:0x68104700 SIPPres 'sip:REDACTED at ekiga.net' > error subscribing to presence of 'sip:520 at ekiga.net' 2012/03/26 > 21:56:55.829 0:39.447 CallSetup:0x40064700 RTP_UDP > SetOption(8,1048576) failed, even though it said it succeeded! > 2012/03/26 21:56:55.830 0:39.447 CallSetup:0x40064700 RTP_UDP > SetOption(8,524288) failed, even though it said it succeeded! > 2012/03/26 21:56:55.830 0:39.447 CallSetup:0x40064700 RTP_UDP > SetOption(8,262144) failed, even though it said it succeeded! > 2012/03/26 21:56:55.830 0:39.447 CallSetup:0x40064700 > MediaFormat Validation of merge for media option "Packetization > Mode" failed. 2012/03/26 21:56:56.145 0:39.762 Opal > Liste...0x68186700 PTLib No permission to set priority level 3 > 2012/03/26 21:56:56.146 0:39.764 Pool:0x40064700 > MediaFormat Validation of merge for media option "Packetization > Mode" failed. 2012/03/26 21:56:56.150 0:39.767 > Pool:0x40064700 SIP PDU is likely too large (1592 bytes) for UDP > datagram. 2012/03/26 21:56:56.472 0:40.090 > Pool:0x40064700 SDP Unknown media attribute silenceSupp 2012/03/26 > 21:56:56.476 0:40.094 Pool:0x40064700 RTP_UDP Session 1, > sending empty datagrams to open local Port Restricted NAT 2012/03/26 > 21:56:56.487 0:40.104 Pool:0x40064700 PTLib No > permission to set priority level 3 2012/03/26 21:56:56.495 > 0:40.113 Pool:0x40064700 PTLib No permission to set > priority level 3 2012/03/26 21:56:56.496 0:40.113 > Pool:0x40064700 RTP_UDP Session 2, sending empty datagrams to open > local Port Restricted NAT 2012/03/26 21:56:56.498 > 0:40.115 Pool:0x40064700 PTLib No permission to set > priority level 3 2012/03/26 21:56:56.499 0:40.117 > Pool:0x40064700 Detecting V4L2 devices 2012/03/26 21:56:56.499 > 0:40.117 Pool:0x40064700 PV4L2Plugin detected device > metadata at /sys/class/video4linux/ 2012/03/26 21:56:56.512 > 0:40.130 Pool:0x40064700 PTLib No permission to set > priority level 3 2012/03/26 21:56:56.524 0:40.141 > GMVideoOut...0x7c2e8700 XVideo XQueryShmExtension success 2012/03/26 > 21:56:56.524 0:40.142 GMVideoOut...0x7c2e8700 XVideo Using SHM > extension 2012/03/26 21:56:56.525 0:40.143 > GMVideoOut...0x7c2e8700 X11 Unknown X Event 19 received 2012/03/26 > 21:56:56.660 0:40.278 GMVideoOut...0x7c2e8700 XVideo > XQueryShmExtension success 2012/03/26 21:56:56.660 0:40.278 > GMVideoOut...0x7c2e8700 XVideo Using SHM extension 2012/03/26 > 21:56:56.660 0:40.278 GMVideoOut...0x7c2e8700 X11 Unknown X > Event 19 received 2012/03/26 21:57:00.474 0:44.091 > Pool:0x40064700 SIP Cannot find transaction > z9hG4bK5842d94e-8f75-e111-9c52-20cf30ac0d5d for response PDU "2 INVITE > <200>" 2012/03/26 21:57:04.476 0:48.093 Pool:0x40064700 > SIP Cannot find transaction > z9hG4bK5842d94e-8f75-e111-9c52-20cf30ac0d5d for response PDU "2 INVITE > <200>" 2012/03/26 21:57:08.473 0:52.091 Pool:0x40064700 > SIP Cannot find transaction > z9hG4bK5842d94e-8f75-e111-9c52-20cf30ac0d5d for response PDU "2 INVITE > <200>" 2012/03/26 21:57:12.474 0:56.092 Pool:0x40064700 > SIP Cannot find transaction > z9hG4bK5842d94e-8f75-e111-9c52-20cf30ac0d5d for response PDU "2 INVITE > <200>" 2012/03/26 21:57:16.161 0:59.779 GMVideoOut...0x7c2e8700 > XVideo XQueryShmExtension success 2012/03/26 21:57:16.161 > 0:59.779 GMVideoOut...0x7c2e8700 XVideo Using SHM extension > 2012/03/26 21:57:16.162 0:59.779 GMVideoOut...0x7c2e8700 XVideo > XQueryShmExtension success 2012/03/26 21:57:16.162 0:59.780 > GMVideoOut...0x7c2e8700 XVideo Using SHM extension 2012/03/26 > 21:57:16.162 0:59.780 GMVideoOut...0x7c2e8700 X11 Unknown X > Event 19 received 2012/03/26 21:57:16.162 0:59.780 > GMVideoOut...0x7c2e8700 X11 Unknown X Event 19 received 2012/03/26 > 21:57:16.504 1:00.122 RTP Jitter:0x3b35c700 RTP_UDP Session 1, > Data port on remote not ready. 2012/03/26 21:57:16.508 > 1:00.126 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on > remote not ready. 2012/03/26 21:57:16.534 1:00.151 Media > Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. > 2012/03/26 21:57:16.551 1:00.168 RTP Jitter:0x3b35c700 RTP_UDP > Session 1, Data port on remote not ready. 2012/03/26 21:57:16.551 > 1:00.169 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on > remote not ready. 2012/03/26 21:57:16.590 1:00.208 RTP > Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. > 2012/03/26 21:57:17.519 1:01.136 Media Patch:0x3b279700 RTP_UDP > Session 2, Data port on remote not ready. 2012/03/26 21:57:18.504 > 1:02.122 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on > remote not ready. 2012/03/26 21:57:19.536 1:03.153 RTP > Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. > 2012/03/26 21:57:20.515 1:04.133 RTP Jitter:0x3b35c700 RTP_UDP > Session 1, Data port on remote not ready. 2012/03/26 21:57:21.540 > 1:05.157 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on > remote not ready. 2012/03/26 21:57:22.521 1:06.138 RTP > Jitter:0x3b35c700 RTP_UDP Session 1, Data port on remote not ready. > 2012/03/26 21:57:23.505 1:07.123 RTP Jitter:0x3b35c700 RTP_UDP > Session 1, Data port on remote not ready. 2012/03/26 21:57:24.524 > 1:08.141 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on > remote not ready. 2012/03/26 21:57:25.511 1:09.128 Media > Patch:0x3b279700 RTP_UDP Session 2, Data port on remote not ready. > 2012/03/26 21:57:26.532 1:10.149 RTP Jitter:0x3b35c700 RTP_UDP > Session 1, Data port on remote not ready. 2012/03/26 21:57:26.532 > 1:10.149 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 > seconds of transmit fails - informing connection 2012/03/26 > 21:57:27.513 1:11.130 RTP Jitter:0x3b35c700 RTP_UDP Session 1, > Data port on remote not ready. 2012/03/26 21:57:27.513 > 1:11.130 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 > seconds of transmit fails - informing connection 2012/03/26 > 21:57:28.536 1:12.154 Media Patch:0x3b279700 RTP_UDP Session 2, > Data port on remote not ready. 2012/03/26 21:57:28.536 1:12.154 > Media Patch:0x3b279700 RTP_UDP Session 2, Data 10 seconds of transmit > fails - informing connection 2012/03/26 21:57:28.536 1:12.154 > Media Patch:0x3b279700 RTPCon Clearing call as all RTP session are > failing 2012/03/26 21:57:29.519 1:13.136 RTP Jitter:0x3b35c700 > RTP_UDP Session 1, Data port on remote not ready. 2012/03/26 > 21:57:29.519 1:13.136 RTP Jitter:0x3b35c700 RTP_UDP Session 1, > Data 10 seconds of transmit fails - informing connection 2012/03/26 > 21:57:29.519 1:13.136 RTP Jitter:0x3b35c700 RTPCon Clearing > call as all RTP session are failing 2012/03/26 21:57:30.508 > 1:14.125 Media Patch:0x3b279700 RTP_UDP Session 2, Data port on > remote not ready. 2012/03/26 21:57:30.508 1:14.125 Media > Patch:0x3b279700 RTP_UDP Session 2, Data 10 seconds of transmit fails - > informing connection 2012/03/26 21:57:30.508 1:14.125 Media > Patch:0x3b279700 RTPCon Clearing call as all RTP session are failing > 2012/03/26 21:57:31.524 1:15.141 RTP Jitter:0x3b35c700 RTP_UDP > Session 1, Data port on remote not ready. 2012/03/26 21:57:31.524 > 1:15.141 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 > seconds of transmit fails - informing connection 2012/03/26 > 21:57:31.524 1:15.141 RTP Jitter:0x3b35c700 RTPCon Clearing > call as all RTP session are failing 2012/03/26 21:57:32.505 > 1:16.122 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on > remote not ready. 2012/03/26 21:57:32.505 1:16.122 RTP > Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails > - informing connection 2012/03/26 21:57:32.505 1:16.122 RTP > Jitter:0x3b35c700 RTPCon Clearing call as all RTP session are failing > 2012/03/26 21:57:33.528 1:17.146 RTP Jitter:0x3b35c700 RTP_UDP > Session 1, Data port on remote not ready. 2012/03/26 21:57:33.528 > 1:17.146 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 > seconds of transmit fails - informing connection 2012/03/26 > 21:57:33.528 1:17.146 RTP Jitter:0x3b35c700 RTPCon Clearing > call as all RTP session are failing 2012/03/26 21:57:34.509 > 1:18.127 RTP Jitter:0x3b35c700 RTP_UDP Session 1, Data port on > remote not ready. 2012/03/26 21:57:34.509 1:18.127 RTP > Jitter:0x3b35c700 RTP_UDP Session 1, Data 10 seconds of transmit fails > - informing connection 2012/03/26 21:57:34.509 1:18.127 RTP > Jitter:0x3b35c700 RTPCon Clearing call as all RTP session are failing > 2012/03/26 21:57:34.537 1:18.155 Housekeeper:0x7c225700 SIP > Transaction 3 BYE sip:500 at 192.168.1.201:5060 failed, unknown handler, > ID: 56ea394d-8f75-e111-9c52-20cf30ac0d5d at thishost 2012/03/26 > 21:57:34.559 1:18.177 Media Patch:0x3b238700 RTP_UDP Session 2, > data port on remote not ready 1 time > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From dave.koelmeyer at davekoelmeyer.co.nz Mon Mar 26 23:02:21 2012 From: dave.koelmeyer at davekoelmeyer.co.nz (Dave Koelmeyer) Date: Tue, 27 Mar 2012 12:02:21 +1300 Subject: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready.) In-Reply-To: <1332766245.2209.2.camel@casa-laptop-ubuntu> References: <20120326222858.70a1f3f1@snap.net.nz> <1332766245.2209.2.camel@casa-laptop-ubuntu> Message-ID: On Tue, Mar 27, 2012 at 1:50 AM, Carola y Pablo wrote: > When I use echo test with 500 at ekiga.net, it shows it is connected, but I > hear nothing.When I try it with 501, Ekiga immediately shuts down. ANy > connection? > > FWIW the Echo Test service appears fine from here. Cheers, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From kresander at yahoo.com Tue Mar 27 06:24:07 2012 From: kresander at yahoo.com (Ken Resander) Date: Mon, 26 Mar 2012 23:24:07 -0700 (PDT) Subject: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready.) In-Reply-To: Message-ID: <1332829447.23689.YahooMailClassic@web39405.mail.mud.yahoo.com> Try sip:music at iptel.org - it plays music. If still no sound, check the sound is working, e.g. by connecting to test function within Skype. Regards Ken --- On Tue, 27/3/12, Dave Koelmeyer wrote: From: Dave Koelmeyer Subject: Re: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready.) To: "Ekiga mailing list" Date: Tuesday, 27 March, 2012, 7:02 AM On Tue, Mar 27, 2012 at 1:50 AM, Carola y Pablo wrote: When I use echo test with 500 at ekiga.net, it shows it is connected, but I hear nothing.When I try it with 501, Ekiga immediately shuts down. ?ANy connection? FWIW the Echo Test service appears fine from here. Cheers, Dave -----Inline Attachment Follows----- _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From baijupattera at gmail.com Wed Mar 28 16:21:38 2012 From: baijupattera at gmail.com (baiju pv) Date: Wed, 28 Mar 2012 16:21:38 +0000 Subject: [Ekiga-list] Could not connect SIP with 3.3.2 In-Reply-To: References: Message-ID: On Wed, Mar 28, 2012 at 4:20 PM, baiju pv wrote: > Hi, > > I installed the new version of Ekiga 3.3.2 in Ubuntu 11.10 and 12.04 > beta.I added a SIP account but it does not connect but says "could not > connect.Remote party host is offline".The same SIP account working well > with Ekiga 3.2.7 in Ubuntu 11.04.Can anybody help me to clear the issue? > The debug output file of Ekiga has attached.Thank you. > > baijupattera > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed Mar 28 19:08:16 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 28 Mar 2012 21:08:16 +0200 Subject: [Ekiga-list] Could not connect SIP with 3.3.2 In-Reply-To: References: Message-ID: <4F7361A0.3090906@pu-pm.univ-fcomte.fr> On 28/03/12 18:21, baiju pv wrote: > On Wed, Mar 28, 2012 at 4:20 PM, baiju pv wrote: > >> Hi, >> >> I installed the new version of Ekiga 3.3.2 in Ubuntu 11.10 and 12.04 >> beta.I added a SIP account but it does not connect but says "could not >> connect.Remote party host is offline".The same SIP account working well >> with Ekiga 3.2.7 in Ubuntu 11.04.Can anybody help me to clear the issue? >> The debug output file of Ekiga has attached.Thank you. Please attach both outputs (with 3.2.7 and 3.3.2). For information, there was a fix for such an issue right after 3.3.2 if I remember correctly. -- Eugen From jbuhl_nospam at gmx.net Fri Mar 30 08:20:53 2012 From: jbuhl_nospam at gmx.net (joshbuhl) Date: Fri, 30 Mar 2012 01:20:53 -0700 (PDT) Subject: [Ekiga-list] could not register sip... In-Reply-To: <4F6DC6A4.8000702@gmx.net> References: <4F6A18DE.2020807@gmx.net> <4F6DC6A4.8000702@gmx.net> Message-ID: <1333095653655-4518374.post@n4.nabble.com> Hi, well, I did post a zipped log of maximum length. Is there anybody who could have a look at it? Thanks! cheers, -j -- View this message in context: http://ekiga.1756082.n4.nabble.com/could-not-register-sip-tp4493203p4518374.html Sent from the Ekiga General mailing list archive at Nabble.com. From Eugen.Dedu at pu-pm.univ-fcomte.fr Fri Mar 30 19:01:19 2012 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Fri, 30 Mar 2012 21:01:19 +0200 Subject: [Ekiga-list] could not register sip... In-Reply-To: <4F6DC6A4.8000702@gmx.net> References: <4F6DC6A4.8000702@gmx.net> Message-ID: <4F7602FF.5070908@pu-pm.univ-fcomte.fr> On 24/03/12 14:05, josh wrote: > Hi Eugen, > > thanks for your assistance. I wanted to generate a full log like you > suggested, so I started ekiga like this: > > $ ekiga -d 4 2>/tmp/output.txt > > > I let it fire up, waited til I saw the error message, tried connecting > to the echo service and then clicked close in the menu. The gui > disappeared, but an hour later there was still output being generated > into output.txt. It doesn't ever stop until I kill it. You cannot register because no answer to REGISTER requests arrives to your machine; however STUN works, since it replies "Cone NAT". This is surely because of a firewall. (Do not remove useful lines when replying to e-mails.) > I have manually configured port forwarding on my router according to the > wiki. I forward: > > ports 5000-5100 udp (sip) > ports 3478-3479 udp (stun) > port 1720 tcp (h323) Since you say you have done the above, the only explanation I have is that the firewall blocking your packets is *before* your router, by the Internet provider, do you have information about that? Also, are you sure that you configured well the ports on your router? > How much of that log do you need? Attaching an amount that gives less > than 40kb zipped (I have a 3Mb log...) > > -j > > >> We need the full log, see >> http://wiki.ekiga.org/index.php/Debugging_Ekiga#Sending_the_data_to_us >> for information on how to send it. I have just added a paragraph>about >> moderator approval... -- Eugen From jbuhl_nospam at gmx.net Fri Mar 30 20:37:01 2012 From: jbuhl_nospam at gmx.net (joshbuhl) Date: Fri, 30 Mar 2012 13:37:01 -0700 (PDT) Subject: [Ekiga-list] could not register sip... In-Reply-To: <4F7602FF.5070908@pu-pm.univ-fcomte.fr> References: <4F6A18DE.2020807@gmx.net> <4F6DC6A4.8000702@gmx.net> <4F7602FF.5070908@pu-pm.univ-fcomte.fr> Message-ID: <1333139821619-4520294.post@n4.nabble.com> Hi Eugen, thanks for replying and taking the time to have a look at my log. I'm not aware of any paket filtering by my isp, but that doesn't mean anything. I will inquire. On which of the ports should the register replies be coming? cheers, -j p.s. I'm not really sure what you meant by the parenthetical about not removing useful lines... -- View this message in context: http://ekiga.1756082.n4.nabble.com/could-not-register-sip-tp4493203p4520294.html Sent from the Ekiga General mailing list archive at Nabble.com. From listbox at snap.net.nz Sat Mar 31 02:27:09 2012 From: listbox at snap.net.nz (listbox) Date: Sat, 31 Mar 2012 15:27:09 +1300 Subject: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready.) Message-ID: <20120331152709.2f41e327@snap.net.nz> Hi Paul, Our problems sound a little different, so there's no connection that I'm aware of here. Have a look at your alsamixer settings; some of the problems whereby people hear nothing at all are resolved by unmuting a setting there. Good luck! R >When I use echo test with 500 at ekiga.net, it shows it is connected, but >I hear nothing.When I try it with 501, Ekiga immediately shuts down. >ANy connection? > >Paul From listbox at snap.net.nz Sat Mar 31 02:30:32 2012 From: listbox at snap.net.nz (listbox) Date: Sat, 31 Mar 2012 15:30:32 +1300 Subject: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready.) Message-ID: <20120331153032.67c5b3da@snap.net.nz> Thanks Dave, At least we know that the problem is with my network, my ISP or an intervening network. Since I've tried numerous firewalls (including fully open) and multiple routers, it's starting to look more and more like the ISP, whom I'll probably contact in the near future. Regards, R >FWIW the Echo Test service appears fine from here. > >Cheers, >Dave From listbox at snap.net.nz Sat Mar 31 02:43:38 2012 From: listbox at snap.net.nz (listbox) Date: Sat, 31 Mar 2012 15:43:38 +1300 Subject: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready. Message-ID: <20120331154338.0d0a365a@snap.net.nz> Hey Ken, Now that was interesting. I hear the music, until the call duration hits 00:31, then I'm disconnected. This time it is the remote user who disconnected the call. So it looks like the connection to that service is fine although the debug returns still show plenty of RTP_UDP issues. I'd be interested in trying another echo service, if anyone is aware of one. Thanks, R Debug output for the connection to sip:music at iptel.org follows: 2012/03/31 15:34:40.625 0:00.012 ThreadID:0xcc968c0 Ekiga version 3.3.2 2012/03/31 15:34:40.625 0:00.012 ThreadID:0xcc968c0 Ekiga git revision: unknown 2012/03/31 15:34:40.625 0:00.012 ThreadID:0xcc968c0 Debug level: 2 2012/03/31 15:34:40.638 0:00.024 OpalPlugin Not adding H.323 capability for plugin codec H.263 as this has been specifically disabled 2012/03/31 15:34:40.643 0:00.030 OpalPlugin Plugin Codec DLL mpeg4_ffmpeg_ptplugin contains no codec definitions 2012/03/31 15:34:40.657 0:00.043 PTLib No permission to set priority level 4 2012/03/31 15:34:40.657 0:00.043 PTLib No permission to set priority level 4 2012/03/31 15:34:40.658 0:00.045 PTLib No permission to set priority level 4 2012/03/31 15:34:40.659 0:00.046 HalManager_dbus Populating full device list failed - The name org.freedesktop.Hal was not provided by any .service files 2012/03/31 15:34:40.660 0:00.046 HalManager_dbus Populating full interface list failed - The name org.freedesktop.NetworkManager was not provided by any .service files 2012/03/31 15:34:40.660 0:00.047 Detecting V4L2 devices 2012/03/31 15:34:40.660 0:00.047 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/31 15:34:40.672 0:00.059 Detecting V4L2 devices 2012/03/31 15:34:40.673 0:00.059 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/31 15:34:40.705 0:00.092 PTLib No permission to set priority level 4 2012/03/31 15:34:40.706 0:00.092 PTLib No permission to set priority level 4 2012/03/31 15:35:05.765 0:25.152 Detecting V4L2 devices 2012/03/31 15:35:05.765 0:25.152 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/31 15:35:05.778 0:25.165 Detecting V4L2 devices 2012/03/31 15:35:05.778 0:25.165 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/31 15:35:05.790 0:25.176 Detecting V4L2 devices 2012/03/31 15:35:05.790 0:25.176 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/31 15:35:05.909 0:25.296 Detecting V4L2 devices 2012/03/31 15:35:05.910 0:25.296 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/31 15:35:05.921 0:25.308 Detecting V4L2 devices 2012/03/31 15:35:05.921 0:25.308 PV4L2Plugin detected device metadata at /sys/class/video4linux/ 2012/03/31 15:35:05.972 0:25.359 Ekiga version 3.3.2 2012/03/31 15:35:05.972 0:25.359 OPAL version 3.10.2 2012/03/31 15:35:05.972 0:25.359 PTLIB version 2.10.2 2012/03/31 15:35:05.972 0:25.359 Accelerated rendering support enabled 2012/03/31 15:35:05.972 0:25.359 DBUS support enabled 2012/03/31 15:35:05.972 0:25.359 GConf support enabled 2012/03/31 15:35:07.696 0:27.082 Opal Liste...0xf8aaa700 Listen UDP read error. 2012/03/31 15:35:08.020 0:27.407 PTLib No permission to set priority level 4 2012/03/31 15:35:08.342 0:27.729 SIPPres SRV lookup for '_pres._sip.ekiga.net' failed 2012/03/31 15:35:09.017 0:28.404 Opal Liste...0xf8aaa700 PTLib No permission to set priority level 3 2012/03/31 15:35:09.031 0:28.418 Pool:0xf8a28700 SIPPres 'sip:REDACTED' error subscribing to presence of 'sip:500 at ekiga.net' 2012/03/31 15:35:09.699 0:29.085 Pool:0xf8a28700 SIPPres 'sip:REDACTED' error subscribing to presence of 'sip:501 at ekiga.net' 2012/03/31 15:35:10.703 0:30.089 Pool:0xf8a28700 SIPPres 'sip:REDACTED' error subscribing to presence of 'sip:520 at ekiga.net' 2012/03/31 15:35:23.519 0:42.905 CallSetup:0xd00ef700 RTP_UDP SetOption(8,1048576) failed, even though it said it succeeded! 2012/03/31 15:35:23.519 0:42.905 CallSetup:0xd00ef700 RTP_UDP SetOption(8,524288) failed, even though it said it succeeded! 2012/03/31 15:35:23.519 0:42.905 CallSetup:0xd00ef700 RTP_UDP SetOption(8,262144) failed, even though it said it succeeded! 2012/03/31 15:35:23.519 0:42.906 CallSetup:0xd00ef700 MediaFormat Validation of merge for media option "Packetization Mode" failed. 2012/03/31 15:35:23.862 0:43.249 Opal Liste...0xf8aaa700 PTLib No permission to set priority level 3 2012/03/31 15:35:23.867 0:43.254 Pool:0xd00ef700 RTP_UDP Session 1, sending empty datagrams to open local Port Restricted NAT 2012/03/31 15:35:23.878 0:43.264 Pool:0xd00ef700 PTLib No permission to set priority level 3 2012/03/31 15:35:23.886 0:43.273 Pool:0xd00ef700 PTLib No permission to set priority level 3 2012/03/31 15:35:23.886 0:43.273 Pool:0xd00ef700 SIP Received disabled/missing media description for video 2012/03/31 15:35:24.190 0:43.577 RTP Jitter:0xd00ae700 RTP_UDP Session 1, Control port on remote not ready. 2012/03/31 15:35:27.356 0:46.743 Pool:0xd00ef700 SIP Cannot find transaction z9hG4bKa84567d4-4779-e111-8512-20cf30ac0d5d for response PDU "1 INVITE <200>" 2012/03/31 15:35:31.356 0:50.743 Pool:0xd00ef700 SIP Cannot find transaction z9hG4bKa84567d4-4779-e111-8512-20cf30ac0d5d for response PDU "1 INVITE <200>" 2012/03/31 15:35:32.250 0:51.636 RTP Jitter:0xd00ae700 RTP Session 1, ssrc=263837581, 1 packet(s) missing at 44828 2012/03/31 15:35:33.416 0:52.803 RTP Jitter:0xd00ae700 RTP_UDP Session 1, Control port on remote not ready. 2012/03/31 15:35:34.962 0:54.349 RTP Jitter:0xd00ae700 RTP Session 1, ssrc=263837581, 2 packet(s) missing at 44961 2012/03/31 15:35:35.357 0:54.744 Pool:0xd00ef700 SIP Cannot find transaction z9hG4bKa84567d4-4779-e111-8512-20cf30ac0d5d for response PDU "1 INVITE <200>" 2012/03/31 15:35:39.355 0:58.742 Pool:0xd00ef700 SIP Cannot find transaction z9hG4bKa84567d4-4779-e111-8512-20cf30ac0d5d for response PDU "1 INVITE <200>" 2012/03/31 15:35:43.355 1:02.742 Pool:0xd00ef700 SIP Cannot find transaction z9hG4bKa84567d4-4779-e111-8512-20cf30ac0d5d for response PDU "1 INVITE <200>" 2012/03/31 15:35:47.355 1:06.742 Pool:0xd00ef700 SIP Cannot find transaction z9hG4bKa84567d4-4779-e111-8512-20cf30ac0d5d for response PDU "1 INVITE <200>" 2012/03/31 15:35:48.849 1:08.235 RTP Jitter:0xd00ae700 RTP_UDP Session 1, Control port on remote not ready. 2012/03/31 15:35:49.984 1:09.370 RTP Jitter:0xd00ae700 RTP Session 1, ssrc=263837581, 2 packet(s) missing at 45712 2012/03/31 15:35:51.355 1:10.742 Pool:0xd00ef700 SIP Cannot find transaction z9hG4bKa84567d4-4779-e111-8512-20cf30ac0d5d for response PDU "1 INVITE <200>" 2012/03/31 15:35:55.357 1:14.743 Pool:0xd00ef700 SIP Cannot find transaction z9hG4bKa84567d4-4779-e111-8512-20cf30ac0d5d for response PDU "1 INVITE <200>" 2012/03/31 15:37:37.764 2:57.151 Housekeeper:0xcb49700 SIP Starting PUBLISH for binding refresh 2012/03/31 15:37:39.023 2:58.410 Housekeeper:0xcb49700 SIP Starting SUBSCRIBE for binding refresh >Try sip:music at iptel.org - it plays music. >If still no sound, check the sound is working, e.g. by connecting to >test function within Skype. > >Regards >Ken From listbox at snap.net.nz Sat Mar 31 03:18:27 2012 From: listbox at snap.net.nz (listbox) Date: Sat, 31 Mar 2012 16:18:27 +1300 Subject: [Ekiga-list] Problem with Echo Test (RTP_UDP ... Data port on remote not ready. Message-ID: <20120331161827.3b43d8cd@snap.net.nz> So, I found myself a few more echo tests and, lo and behold, echo at iptel.org works fine for me. No problems, beautiful echo, for thirty-two seconds until the remote host disconnects me. Two questions: 1) Any idea why echo at ekiga.net fails where echo at iptel.org succeeds? 2) Can someone who has no problems with echo at ekiga.net try echo at iptel.org and see if they're disconnected after thirty seconds? I'd like to see whether the duration of this echo test is fixed for everyone at thirty-two seconds, or whether I have a specific problem that is pushing me off echo at iptel.org and music at iptel.org at 32s. Thanks all, R >Hey Ken, > >Now that was interesting. I hear the music, until the call duration >hits 00:31, then I'm disconnected. This time it is the remote user who >disconnected the call. So it looks like the connection to that service >is fine although the debug returns still show plenty of RTP_UDP >issues. > >I'd be interested in trying another echo service, if anyone is aware of >one. > >Thanks, >R