[Ekiga-list] SVN
Hello, where can I get pwlib(1.11.4) and opal(2.3.2) on subversion? ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
Le lundi 19 février 2007 à 23:31 +0100, Jure Petrovic a écrit : > > I have empty methods inside g729codec.cxx, so file compiles > on command line. How can I get this linked to > libopal library? (I don't care if they're empty for now) > > It should generate a plugin (with OPAL CVS) in plugins/pwlib/, but I guess, only if the voiceage library is present (there is a README). -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] weird Ekiga behaviour, bug?
Le mardi 20 février 2007 à 00:47 +, John Leach a écrit : > On Tue, 2007-02-20 at 01:18 +0100, Jan Schampera wrote: > > On Mon, 19 Feb 2007 21:56:03 + > > John Leach <[EMAIL PROTECTED]> wrote: > > > > > I've come across a strange problem that affects Ekiga. It usually > > > works well, but once in a while my calls are so choppy as to be > > > completely unusable. The strange behaviour is that if I start > > > another process that is CPU intensive, Ekiga works fine! > > > > > > So, I experience choppy calls, then run: > > > > > > # dd if=/dev/zero of=/dev/null bs=1M > > > > > > and the choppiness completely disappears. Kill dd and it reappears. > > > > > > I tend to get choppy calls for a whole session. Restarting Ekiga > > > doesn't help. > > > > > > I'm using Ubuntu Edgy on an i386 Sony Vaio laptop. I use suspend to > > > ram a lot, if that's any clue. > > > > > > So, I'm not sure if this is even a Ekiga bug. Any ideas anyone? > > > > That's the second time I hear such a report: choppy sound goes away on > > high CPU load (first report was on IRC). > > > > In your special case: Maybe the CPU is throttled? > > acpi (via proc) tells me throttling is turned off. It does very much > sound like a CPU problem, and not Ekiga. Though maybe the report will > help others with the same problem. > > I'm going to try arrange to test it with the upcoming Feisty Ubuntu > release as that has a newer kernel. I'll get back with any results. > Try this : arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 16000 -f S16_LE - and this : arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 8000 -f S16_LE - do you notice the same problem ? (it is basically an echo test) -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers?
Le lundi 19 février 2007 à 16:32 -0800, JCA a écrit : > > Have you tried with Ekiga 2.0.5 ? > >pwlib 1.10.4, configured with > > ./configure --prefix=/usr --enable-plugins --disable-oss --enable-v4l2 > > refuses to compile on my Slackware 11.0 box: > > make[3]: Entering directory `/home/IJK/pwlib-1.10.4/plugins/vidinput_v4l2' > mkdir -p ../pwlib/device/videoinput > g++ -DP_USE_PRAGMA -D_REENTRANT -Wall -fPIC -DPIC > -I/home/IJK/pwlib-1.10.4/include \ > vidinput_names.cxx \ > -I. -shared vidinput_v4l2.cxx -o > ../pwlib/device/videoinput/v4l2_pwplugin.so > In file included from vidinput_v4l2.cxx:145: > vidinput_v4l2.h:157: error: field `videoCapability' has incomplete type > vidinput_v4l2.h:158: error: field `videoStreamParm' has incomplete type > vidinput_v4l2.cxx:219: error: `V4L2_PIX_FMT_GREY' was not declared in this > scope > > etc. Mandriva ? I know that there are patches hanging around to patch kernel headers for that bug, but I am not aware of the exact location... > >Also, I noticed that the configure file for 2.0.5 strongly > recommends not to disable Gnome support: > > --disable-gnomeRemove GNOME support. Don't do this, it > removes essential features > >Which are those essential features? There are none if I remember correctly. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] SVN
Le mardi 20 février 2007 à 09:24 +0100, Jure Petrovic a écrit : > Hello, > > where can I get pwlib(1.11.4) and opal(2.3.2) > on subversion? > It is on CVS, http://www.sf.net/projects/openh323 -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
Opal CVS is not a problem. I read your article about .so plugins. What about OPAL release? Do I have to edit Makefile manually? > It should generate a plugin (with OPAL CVS) in plugins/pwlib/, but I > guess, only if the voiceage library is present (there is a README). ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] stable windows version? Re: Let's spread Ekiga : volunteers ?
> > 7) WORD OF MOUTH I would like to recommend ekiga to my sister so that I can phone with her, but do not know how stable it is on Windows. Should she (advanced user but with no time to fiddle around) give it a try or better wait? (I think a stable and easy installable windows port is very much needed to spread ekiga. Sorry, that I cannot help.) jens ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
Le mardi 20 février 2007 à 10:00 +0100, Jure Petrovic a écrit : > Opal CVS is not a problem. I read your article about .so > plugins. > > What about OPAL release? Do I have to edit Makefile manually? > I think so, but I'm sorry, I have never done that, so I can guide you to a precise way of doing things. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers?
On Mon, Feb 19, 2007 at 04:32:05PM -0800, JCA wrote: > refuses to compile on my Slackware 11.0 box: > > vidinput_v4l2.h:157: error: field `videoCapability' has incomplete type > vidinput_v4l2.h:158: error: field `videoStreamParm' has incomplete type > vidinput_v4l2.cxx:219: error: `V4L2_PIX_FMT_GREY' was not declared in this > scope V4L2 plugins use Linux kernel header. So you must have a recent Linux kernel header in /usr/include/linux to build pwlib. By default Slackware comes with a 2.4 kernel so it can't be used. Try to install the 2.6.17.13, if it's help. Quote from the website: <> Luc ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
> I think so, but I'm sorry, I have never done that, so I can guide you > to > a precise way of doing things. Don't worry. I am back on CVS :) configure: error: Sorry but the recommended OPAL version is 2.3.2 I have libopal 2.3.2 !! From www.ekiga.org, cvs snapshots ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
Le mardi 20 février 2007 à 11:08 +0100, Jure Petrovic a écrit : > > I think so, but I'm sorry, I have never done that, so I can guide you > > to > > a precise way of doing things. > > Don't worry. I am back on CVS :) > > configure: error: Sorry but the recommended OPAL version is 2.3.2 > > I have libopal 2.3.2 !! From www.ekiga.org, cvs snapshots > If it tells you you do not have 2.3.2, then you do not have 2.3.2 installed where it is looking for... -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] stable windows version? Re: Let's spread Ekiga : volunteers ?
Le mardi 20 février 2007 à 10:11 +0100, Jens Nachtigall a écrit : > > > 7) WORD OF MOUTH > > I would like to recommend ekiga to my sister so that I can phone with her, > but > do not know how stable it is on Windows. Should she (advanced user but with > no time to fiddle around) give it a try or better wait? > > (I think a stable and easy installable windows port is very much needed to > spread ekiga. Sorry, that I cannot help.) I think it is stable, but not easy to install yet. My colleague is working on an installer. -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] CVS version compiles ok, but problems connecting
running the latest snapshots (as of today) of pwlib, opal, and Ekiga from a terminal It comes up ok, but when I try to call out, I get this error: [EMAIL PROTECTED] ~]$ ekiga patch.cxx(301) Patch Added sink from PCM-16 Clock Rate = 8000 Frame Time = 8 Max Bit Rate = 64000 Max Frame Size = 16 Needs Jitter = 1 Rx Frames Per Packet = 240 Tx Frames Per Packet = 30 to G.711-uLaw-64k Clock Rate = 8000 Frame Time = 8 Max Bit Rate = 64000 Max Frame Size = 8 Needs Jitter = 1 Rx Frames Per Packet = 240 Tx Frames Per Packet = 30 patch.cxx(301) Patch Added sink from G.711-uLaw-64k Clock Rate = 8000 Frame Time = 8 Max Bit Rate = 64000 Max Frame Size = 8 Needs Jitter = 1 Rx Frames Per Packet = 240 Tx Frames Per Packet = 30 to PCM-16 Clock Rate = 8000 Frame Time = 8 Max Bit Rate = 128000 Max Frame Size = 16 Needs Jitter = 1 Rx Frames Per Packet = 240 Tx Frames Per Packet = 30 patch.cxx(301) Patch Added sink from YUV420P Adaptive Packet Delay = 1 Clock Rate = 9 Dynamic Video Quality = 1 Encoding Quality = 6 Frame Height = 144 Frame Time = 1500 Frame Width = 176 Max Bit Rate = 621700 Target Bit Rate = 64000 to H.261 Adaptive Packet Delay = 1 Clock Rate = 9 Dynamic Video Quality = 1 Encoding Quality = 6 Frame Height = 144 Frame Time = 1500 Frame Width = 176 Max Bit Rate = 621700 Target Bit Rate = 64000 h323_cifMPI = 4 h323_qcifMPI = 2 patch.cxx(301) Patch Added sink from H.261 Adaptive Packet Delay = 1 Clock Rate = 9 Dynamic Video Quality = 1 Encoding Quality = 6 Frame Height = 144 Frame Time = 1500 Frame Width = 176 Max Bit Rate = 621700 Target Bit Rate = 64000Xlib: unexpected async reply (sequence 0x1e62)! Multiple segmentation faults occurred; can't display error dialog h323_cifMPI = 4 h323_qcifMPI = 2 to YUV420P Adaptive Packet Delay = 1 Clock Rate = 9 Dynamic Video Quality = 1 Encoding Quality = 6 Frame Height = 144 Frame Time = 3600 Frame Width = 176 Max Bit Rate = 30412800 Target Bit Rate = 64000 Xlib: unexpected async reply (sequence 0x1e62)! Multiple segmentation faults occurred; can't display error dialog [EMAIL PROTECTED] ~]$ ** (bug-buddy:21176): WARNING **: Couldn't load icon for Open Folder ** (bug-buddy:21176): WARNING **: Couldn't load icon for Zapping TV Viewer ptrace: No such process. /home/george/20876: No such file or directory. No stack. Then Ekiga crashes. Fedora Core 6 Linux Ekiga Rocks!! One program so many ways to connect! sip: [EMAIL PROTECTED] (or [EMAIL PROTECTED]) H323: gk.voxgratia.net:1719 geboyd53 SipBroker: *673-617808 -or- *011-1617808 (alias 617808) e164: +13606660349 or +882 398265 (linked to ekiga) Voipbuster: geboyd53 (chat), 13606660349 (telephone) Forward: 781549 Voxalot: 106153 Gizmo: 17476918163 ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
Le mardi 20 février 2007 à 04:14 -0800, George Boyd a écrit : > running the latest snapshots (as of today) of pwlib, opal, and Ekiga > from a terminal It comes up ok, but when I try to call out, I get this > error: > > [EMAIL PROTECTED] ~]$ ekiga >patch.cxx(301) Patch Added sink > from PCM-16 > Clock Rate = 8000 > Frame Time = 8 > Max Bit Rate = 64000 > Max Frame Size = 16 > Needs Jitter = 1 > Rx Frames Per Packet = 240 > Tx Frames Per Packet = 30 > to G.711-uLaw-64k > Clock Rate = 8000 > Frame Time = 8 > Max Bit Rate = 64000 > Max Frame Size = 8 > Needs Jitter = 1 > Rx Frames Per Packet = 240 > Tx Frames Per Packet = 30 > >patch.cxx(301) Patch Added sink > from G.711-uLaw-64k > Clock Rate = 8000 > Frame Time = 8 > Max Bit Rate = 64000 > Max Frame Size = 8 > Needs Jitter = 1 > Rx Frames Per Packet = 240 > Tx Frames Per Packet = 30 > to PCM-16 > Clock Rate = 8000 > Frame Time = 8 > Max Bit Rate = 128000 > Max Frame Size = 16 > Needs Jitter = 1 > Rx Frames Per Packet = 240 > Tx Frames Per Packet = 30 > >patch.cxx(301) Patch Added sink > from YUV420P > Adaptive Packet Delay = 1 > Clock Rate = 9 > Dynamic Video Quality = 1 > Encoding Quality = 6 > Frame Height = 144 > Frame Time = 1500 > Frame Width = 176 > Max Bit Rate = 621700 > Target Bit Rate = 64000 > to H.261 > Adaptive Packet Delay = 1 > Clock Rate = 9 > Dynamic Video Quality = 1 > Encoding Quality = 6 > Frame Height = 144 > Frame Time = 1500 > Frame Width = 176 > Max Bit Rate = 621700 > Target Bit Rate = 64000 > h323_cifMPI = 4 > h323_qcifMPI = 2 > >patch.cxx(301) Patch Added sink > from H.261 > Adaptive Packet Delay = 1 > Clock Rate = 9 > Dynamic Video Quality = 1 > Encoding Quality = 6 > Frame Height = 144 > Frame Time = 1500 > Frame Width = 176 > Max Bit Rate = 621700 > Target Bit Rate = 64000Xlib: unexpected async reply (sequence > 0x1e62)! > Multiple segmentation faults occurred; can't display error dialog > h323_cifMPI = 4 > h323_qcifMPI = 2 > to YUV420P > Adaptive Packet Delay = 1 > Clock Rate = 9 > Dynamic Video Quality = 1 > Encoding Quality = 6 > Frame Height = 144 > Frame Time = 3600 > Frame Width = 176 > Max Bit Rate = 30412800 > Target Bit Rate = 64000 > > Xlib: unexpected async reply (sequence 0x1e62)! > Multiple segmentation faults occurred; can't display error dialog > [EMAIL PROTECTED] ~]$ > ** (bug-buddy:21176): WARNING **: Couldn't load icon for Open Folder > > ** (bug-buddy:21176): WARNING **: Couldn't load icon for Zapping TV > Viewer > ptrace: No such process. > /home/george/20876: No such file or directory. > No stack. > > Then Ekiga crashes. Perhaps CVS is broken ? Can you try gdb ekiga type 'run' and when it crashes, type 'threads apply all bt' -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Video Plugins
Hi, ist there yet a way to get video codec plugins to work? For some time there is the respective GUI control but the only available codec is H261 (QCIF I suppose) Do I have to - have ffmpeg present and configured (how?) - recompile Ekiga with some ---config options - wait :-) Thanks for answering Conrad ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Video Plugins
Le mardi 20 février 2007 à 16:04 +0100, Conrad Beckert a écrit : > Hi, > > ist there yet a way to get video codec plugins to work? For some time > there is the respective GUI control but the only available codec is H261 > (QCIF I suppose) > > Do I have to > - have ffmpeg present and configured (how?) > - recompile Ekiga with some ---config options > - wait :-) > wait ? or investigate by yourself :-) -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
On Tue, 2007-02-20 at 11:14 +0100, Damien Sandras wrote: > If it tells you you do not have 2.3.2, then you do not have 2.3.2 > installed where it is looking for... Ok, that happens if you have 2 opal(s) installed. Compiled ok, but now it crashes on connection established with the following error: 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP Could not find SDP media description for Video 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP Could not find SDP media description for Image Xlib: unexpected async reply (sequence 0x11518)! No help if I disable that "Enable video" checkbox. Jure ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
When I run gdb ekiga, it doesn't crash, it stops (but doesn't disappear
like it does just running "ekiga") where it errors. If I run ekiga on it
own, at the point it crashes I get a window that pops up saying "No
Pointer Reference" then it kills itself.
(gdb) run
Starting program: /usr/bin/ekiga
[Thread debugging using libthread_db enabled]
[New Thread -1208731936 (LWP 31376)]
[New Thread -1210831984 (LWP 31438)]
[New Thread -1211098224 (LWP 31439)]
[New Thread -1289057392 (LWP 31468)]
[New Thread -1299547248 (LWP 31469)]
[New Thread -1310037104 (LWP 31470)]
[New Thread -1320526960 (LWP 31471)]
[New Thread -1331016816 (LWP 31472)]
[New Thread -1341506672 (LWP 31473)]
[New Thread -1352410224 (LWP 31476)]
[New Thread -1362900080 (LWP 31479)]
[Thread -1310037104 (LWP 31470) exited]
[Thread -1320526960 (LWP 31471) exited]
[Thread -1331016816 (LWP 31472) exited]
[Thread -1289057392 (LWP 31468) exited]
[Thread -1341506672 (LWP 31473) exited]
[Thread -1299547248 (LWP 31469) exited]
[New Thread -1310409840 (LWP 31516)]
[New Thread -1310676080 (LWP 31517)]
[New Thread -1310942320 (LWP 31518)]
[New Thread -1299547248 (LWP 31519)]
[New Thread -1341506672 (LWP 31520)]
[New Thread -1289057392 (LWP 31521)]
[Thread -1299547248 (LWP 31519) exited]
[Thread -1341506672 (LWP 31520) exited]
[Thread -1289057392 (LWP 31521) exited]
[New Thread -1311470704 (LWP 31525)]
[New Thread -1311736944 (LWP 31526)]
[New Thread -1312003184 (LWP 31527)]
[New Thread -1312269424 (LWP 31528)]
[New Thread -1312535664 (LWP 31529)]
[New Thread -1312801904 (LWP 31531)]
[New Thread -1313068144 (LWP 31532)]
[New Thread -1313334384 (LWP 31533)]
[New Thread -1313600624 (LWP 31535)]
[New Thread -1313866864 (LWP 31537)]
[New Thread -1314133104 (LWP 31538)]
[New Thread -1314399344 (LWP 31539)]
[New Thread -1314665584 (LWP 31540)]
[New Thread -1314931824 (LWP 31542)]
[New Thread -1315198064 (LWP 31543)]
[New Thread -1315464304 (LWP 31544)]
[New Thread -1315730544 (LWP 31545)]
[New Thread -1315996784 (LWP 31548)]
[New Thread -1316263024 (LWP 31549)]
[New Thread -1316529264 (LWP 31550)]
[Thread -1310942320 (LWP 31518) exited]
[New Thread -1310942320 (LWP 31556)]
[New Thread -1316795504 (LWP 31557)]
[Thread -1310942320 (LWP 31556) exited]
[New Thread -1310942320 (LWP 31558)]
patch.cxx(301) Patch Added sink
from PCM-16
Clock Rate = 8000
Frame Time = 8
Max Bit Rate = 64000
Max Frame Size = 16
Needs Jitter = 1
Rx Frames Per Packet = 240
Tx Frames Per Packet = 30
to G.711-uLaw-64k
Clock Rate = 8000
Frame Time = 8
Max Bit Rate = 64000
Max Frame Size = 8
Needs Jitter = 1
Rx Frames Per Packet = 240
Tx Frames Per Packet = 30
patch.cxx(301) Patch Added sink
from G.711-uLaw-64k
Clock Rate = 8000
Frame Time = 8
Max Bit Rate = 64000
Max Frame Size = 8
Needs Jitter = 1
Rx Frames Per Packet = 240
Tx Frames Per Packet = 30
to PCM-16
Clock Rate = 8000
Frame Time = 8
Max Bit Rate = 128000
Max Frame Size = 16
Needs Jitter = 1
Rx Frames Per Packet = 240
Tx Frames Per Packet = 30
[New Thread -1318327408 (LWP 31652)]
patch.cxx(301) Patch Added sink
from YUV420P
Adaptive Packet Delay = 1
Clock Rate = 9
Dynamic Video Quality = 1
Encoding Quality = 2
Frame Height = 144
Frame Time = 1500
Frame Width = 176
Max Bit Rate = 621700
Target Bit Rate = 64000
to H.261
Adaptive Packet Delay = 1
Clock Rate = 9
Dynamic Video Quality = 1
Encoding Quality = 2
Frame Height = 144
Frame Time = 1500
Frame Width = 176
Max Bit Rate = 621700
Target Bit Rate = 64000
h323_cifMPI = 4
h323_qcifMPI = 2
patch.cxx(301) Patch Added sink
from H.261
Adaptive Packet Delay = 1
Clock Rate = 9
Dynamic Video Quality = 1
Encoding Quality = 2
Frame Height = 144
Frame Time = 1500
Frame Width = 176
Max Bit Rate = 621700
Target Bit Rate = 64000
h323_cifMPI = 4
h323_qcifMPI = 2
to YUV420P
Adaptive Packet Delay = 1
Clock Rate = 9
Dynamic Video Quality = 1
Encoding Quality = 2
Frame Height = 144
Frame Time = 3600
Frame Width = 176
Max Bit Rate = 30412800
Target Bit Rate = 64000
[New Thread -1318593648 (LWP 31674)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1318593648 (LWP 31674)]
0x024887a8 in RTP_UDP::WriteData () at /usr/include/ptclib/http.h:494
494 {
(gdb)
Fedora Core 6 Linux
Ekiga Rocks!! One program so many ways to connect!
sip: [EMAIL PROTECTED] (or [EMAIL
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
On Tue, 2007-02-20 at 10:53 -0800, George Boyd wrote: > When I run gdb ekiga, it doesn't crash, it just stops (but doesn't disappear > like it does just running "ekiga"). If I run ekiga on it's > own, at the point it crashes I get a window that pops up saying "No > Pointer Reference" then it kills itself. > I guess what I'm trying to say is that running it under gdb, ekiga doesn't kill itself so I can't run "threads apply all bt". When I do, it's still running in gdb and it comes back with "(gdb) threads apply all bt Undefined command: "threads". Try "help". If I force quit ekiga, gdb says it's still running. The problem occurs whenever I try to call out. George ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
Le mardi 20 février 2007 à 11:12 -0800, George Boyd a écrit : > On Tue, 2007-02-20 at 10:53 -0800, George Boyd wrote: > > When I run gdb ekiga, it doesn't crash, it just stops (but doesn't disappear > > like it does just running "ekiga"). If I run ekiga on it's > > own, at the point it crashes I get a window that pops up saying "No > > Pointer Reference" then it kills itself. > > > > I guess what I'm trying to say is that running it under gdb, ekiga > doesn't kill itself so I can't run "threads apply all bt". When I do, > it's still running in gdb and it comes back with > > "(gdb) threads apply all bt > Undefined command: "threads". Try "help". > > If I force quit ekiga, gdb says it's still running. > > The problem occurs whenever I try to call out. > the command is thread apply all bt (sorry). Make sure that your compilation and setup are ok because the crash you are reporting is very weird... Damien ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
Le mardi 20 février 2007 à 18:39 +0100, Jure Petrovic a écrit : > On Tue, 2007-02-20 at 11:14 +0100, Damien Sandras wrote: > > If it tells you you do not have 2.3.2, then you do not have 2.3.2 > > installed where it is looking for... > > Ok, that happens if you have 2 opal(s) installed. > Compiled ok, but now it crashes on connection established > with the following error: > > 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP > Could not find SDP media description for Video > 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP > Could not find SDP media description for Image > > Xlib: unexpected async reply (sequence 0x11518)! > > > No help if I disable that "Enable video" checkbox. Given that George is also encountering a crash, I would think Craig recently broke something. Can you do the same operation than George (see other e-mails sent today) to see if it is the same crash ? -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
On Tue, 2007-02-20 at 20:22 +0100, Damien Sandras wrote: > Make sure that your compilation and setup are ok because the crash you > are reporting is very weird... > > Damien My version (2.1.0) from HEAD also crashes with null pointer reference, when connection gets established! If I run it from console, it prints out on stdout: 007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP Could not find SDP media description for Video 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP Could not find SDP media description for Image Xlib: unexpected async reply (sequence 0x11518)! ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
On Tue, 2007-02-20 at 20:23 +0100, Damien Sandras wrote:
> Given that George is also encountering a crash, I would think Craig
> recently broke something.
>
> Can you do the same operation than George (see other e-mails sent
> today)
> to see if it is the same crash ?
Avec plaisir :-)
This is a 286-line trace, so I will attach a txt file.
In case mailing list does not support attachments,
I am sending it to you, too
Jure
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /usr/local/bin/ekiga
[Thread debugging using libthread_db enabled]
[New Thread -1208527136 (LWP 18758)]
It appears that you do not have ekiga.server installed in a valid location.
Factory mode disabled.
[New Thread -1210627184 (LWP 18761)]
[New Thread -1210893424 (LWP 18762)]
[New Thread -1235297392 (LWP 18763)]
[New Thread -1245787248 (LWP 18764)]
[New Thread -1256277104 (LWP 18765)]
[New Thread -1266766960 (LWP 18767)]
[Thread -1245787248 (LWP 18764) exited]
[Thread -1235297392 (LWP 18763) exited]
[New Thread -1267405936 (LWP 18769)]
[New Thread -1267672176 (LWP 18770)]
[New Thread -1267938416 (LWP 18771)]
[New Thread -1245787248 (LWP 18772)]
[New Thread -1235297392 (LWP 18773)]
[New Thread -1269826672 (LWP 18774)]
[New Thread -1268204656 (LWP 18775)]
[New Thread -1268470896 (LWP 18778)]
[Thread -1267938416 (LWP 18771) exited]
[Thread -1235297392 (LWP 18773) exited]
[Thread -1245787248 (LWP 18772) exited]
[Thread -1269826672 (LWP 18774) exited]
[New Thread -1267938416 (LWP 18780)]
[New Thread -1280316528 (LWP 18781)]
[Thread -1267938416 (LWP 18780) exited]
[New Thread -1267938416 (LWP 18782)]
patch.cxx(301) Patch Added sink
from PCM-16
Clock Rate = 8000
Frame Time = 8
Max Bit Rate = 13200
Max Frame Size = 16
Needs Jitter = 1
Rx Frames Per Packet = 1
Tx Frames Per Packet = 1
to GSM-06.10
Clock Rate = 8000
Frame Time = 160
Max Bit Rate = 13200
Max Frame Size = 33
Needs Jitter = 1
Rx Frames Per Packet = 1
Tx Frames Per Packet = 1
patch.cxx(301) Patch Added sink
from GSM-06.10
Clock Rate = 8000
Frame Time = 160
Max Bit Rate = 13200
Max Frame Size = 33
Needs Jitter = 1
Rx Frames Per Packet = 1
Tx Frames Per Packet = 1
to PCM-16
Clock Rate = 8000
Frame Time = 8
Max Bit Rate = 128000
Max Frame Size = 16
Needs Jitter = 1
Rx Frames Per Packet = 240
Tx Frames Per Packet = 30
[New Thread -1280779376 (LWP 18783)]
[New Thread -1281045616 (LWP 18784)]
[New Thread -1281311856 (LWP 18785)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1280779376 (LWP 18783)]
0x010f4bb8 in RTP_UDP::WriteData () at /usr/local/include/ptclib/http.h:494
494 {
(gdb) thread apply all bt
Thread 21 (Thread -1281311856 (LWP 18785)):
#0 0x007a6402 in __kernel_vsyscall () at /usr/local/include/ptclib/http.h:494
#1 0x00c4998e in __lll_mutex_lock_wait () at
/usr/local/include/ptclib/http.h:494
#2 0x00c4421a in _L_mutex_lock_2031 () at /usr/local/include/ptclib/http.h:494
#3 0x00c434d7 in start_thread () at /usr/local/include/ptclib/http.h:494
#4 0x00b9d26e in clone () at /usr/local/include/ptclib/http.h:494
Thread 20 (Thread -1281045616 (LWP 18784)):
#0 0x00c428b1 in __nptl_create_event () at /usr/local/include/ptclib/http.h:494
#1 0x00c43e97 in pthread_create@@GLIBC_2.1 () at
/usr/local/include/ptclib/http.h:494
#2 0x00a23a33 in PThread::Restart () at /usr/local/include/ptclib/http.h:494
#3 0x00a23d0c in PThread::Suspend () at /usr/local/include/ptclib/http.h:494
#4 0x00a2264d in PThread::Resume () at /usr/local/include/ptclib/http.h:494
#5 0x00a33458 in PSimpleThread::PSimpleThread () at
/usr/local/include/ptclib/http.h:494
#6 0x00a3349b in PThread::Create () at /usr/local/include/ptclib/http.h:494
#7 0x010f887d in OpalJitterBuffer::Resume () at
/usr/local/include/ptclib/http.h:494
#8 0x010f2838 in RTP_Session::SetJitterBufferSize () at
/usr/local/include/ptclib/http.h:494
#9 0x010dab07 in OpalRTPMediaStream::EnableJitterBuffer () at
/usr/local/include/ptclib/http.h:494
#10 0x010dfa07 in OpalMediaPatch::Main () at
/usr/local/include/ptclib/http.h:494
#11 0x010dfe3e in OpalMediaPatch::Thread::Main () at
/usr/local/include/ptclib/http.h:494
#12 0x00a23678 in PThread::PX_ThreadStart () at
/usr/local/include/ptclib/http.h:494
#13 0x00c433db in start_thread () at /usr/local/include/ptclib/http.h:494
#14 0x00b9d26e in clone () at /usr/local/include/ptclib/http.h:494
Thread 19 (Thread -1280779376 (LWP 18783)):
#0 0x010f4bb8 in RTP_UDP::WriteData () at /usr/local/include/ptclib/http.h:494
#1 0x010dc5ac in OpalRTPMediaStream::WritePacket () at
/usr/local/include/ptclib/http.h:494
#2 0x010df05e in OpalMediaPatch::Sink::WriteFrame () at
/usr/local/include/ptclib/http.h
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
> the command is thread apply all bt (sorry). > I should have known that :) Here's the output: (gdb) thread apply all bt Thread 52 (Thread -1299080304 (LWP 1938)): #0 0x00131402 in __kernel_vsyscall () at /usr/include/ptclib/http.h:494 #1 0x004be729 in ioctl () at /usr/include/ptclib/http.h:494 #2 0x00efdfec in PVideoInputDevice_V4L2::GetFrameDataNoDelay () at /usr/include/ptclib/http.h:494 #3 0x00efe11e in PVideoInputDevice_V4L2::GetFrameData () at /usr/include/ptclib/http.h:494 #4 0x024708de in OpalVideoMediaStream::ReadData () at /usr/include/ptclib/http.h:494 #5 0x0246f2d5 in OpalMediaStream::ReadPacket () at /usr/include/ptclib/http.h:494 #6 0x0247365e in OpalMediaPatch::Main () at /usr/include/ptclib/http.h:494 #7 0x02473a2e in OpalMediaPatch::Thread::Main () at /usr/include/ptclib/http.h:494 #8 0x02bff83c in PThread::PX_ThreadStart () at /usr/include/ptclib/http.h:494 #9 0x0056c3db in start_thread () at /usr/include/ptclib/http.h:494 #10 0x004c626e in clone () at /usr/include/ptclib/http.h:494 Thread 51 (Thread -1298814064 (LWP 1937)): #0 0x00131402 in __kernel_vsyscall () at /usr/include/ptclib/http.h:494 #1 0x00572aa1 in __lll_mutex_unlock_wake () at /usr/include/ptclib/http.h:494 #2 0x0056f7d9 in _L_mutex_unlock_101 () at /usr/include/ptclib/http.h:494 ---Type to continue, or q to quit--- #3 0x0056f440 in __pthread_mutex_unlock_usercnt () at /usr/include/ptclib/http.h:494 #4 0x0056f7d0 in pthread_mutex_unlock () at /usr/include/ptclib/http.h:494 #5 0x0095d1ca in g_source_attach () at /usr/include/ptclib/http.h:494 #6 0x0095d2bc in g_idle_add_full () at /usr/include/ptclib/http.h:494 #7 0x02c23a30 in PAssertFunc () at /usr/include/ptclib/http.h:494 #8 0x02c16d58 in PAbstractList::Append () at /usr/include/ptclib/http.h:494 #9 0x02c0b3b6 in PSocket::SelectList::operator+= () at /usr/include/ptclib/http.h:494 #10 0x02c076d3 in PSocket::Select () at /usr/include/ptclib/http.h:494 #11 0x02487d60 in RTP_UDP::ReadData () at /usr/include/ptclib/http.h:494 #12 0x0248c176 in RTP_JitterBuffer::OnReadPacket () at /usr/include/ptclib/http.h:494 #13 0x0248e588 in OpalJitterBuffer::OnRead () at /usr/include/ptclib/http.h:494 #14 0x0248e9ef in OpalJitterBuffer::JitterThreadMain () at /usr/include/ptclib/http.h:494 #15 0x0248ea96 in OpalJitterBuffer::JitterThreadMain_PNotifier::Call () at /usr/include/ptclib/http.h:494 #16 0x02c0e28c in PSimpleThread::Main () at /usr/include/ptclib/http.h:494 #17 0x02bff83c in PThread::PX_ThreadStart () at /usr/include/ptclib/http.h:494 #18 0x0056c3db in start_thread () at /usr/include/ptclib/http.h:494 #19 0x004c626e in clone () at /usr/include/ptclib/http.h:494 ---Type to continue, or q to quit--- Thread 50 (Thread -1298547824 (LWP 1936)): #0 0x00131402 in __kernel_vsyscall () at /usr/include/ptclib/http.h:494 #1 0x004bf0d1 in select () at /usr/include/ptclib/http.h:494 #2 0x02c015d2 in PThread::Sleep () at /usr/include/ptclib/http.h:494 #3 0x024736cc in OpalMediaPatch::Main () at /usr/include/ptclib/http.h:494 #4 0x02473a2e in OpalMediaPatch::Thread::Main () at /usr/include/ptclib/http.h:494 #5 0x02bff83c in PThread::PX_ThreadStart () at /usr/include/ptclib/http.h:494 #6 0x0056c3db in start_thread () at /usr/include/ptclib/http.h:494 #7 0x004c626e in clone () at /usr/include/ptclib/http.h:494 Every time it asks ---Type to continue, or q to quit--- If I type enter, it just repeats itself. Fedora Core 6 Linux Ekiga Rocks!! One program so many ways to connect! sip: [EMAIL PROTECTED] (or [EMAIL PROTECTED]) H323: gk.voxgratia.net:1719 geboyd53 SipBroker: *673-617808 -or- *011-1617808 (alias 617808) e164: +13606660349 or +882 398265 (linked to ekiga) Voipbuster: geboyd53 (chat), 13606660349 (telephone) Forward: 781549 Voxalot: 106153 Gizmo: 17476918163 ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
It's the similar crash as in the other list thread that currently is discussed (what a good english sentence...). J. -- Once you've got the perfect hammer, everything looks like a nail. ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
On Tue, 20 Feb 2007 20:23:58 +0100 Damien Sandras <[EMAIL PROTECTED]> wrote: > Le mardi 20 février 2007 à 18:39 +0100, Jure Petrovic a écrit : > > On Tue, 2007-02-20 at 11:14 +0100, Damien Sandras wrote: > > > If it tells you you do not have 2.3.2, then you do not have 2.3.2 > > > installed where it is looking for... > > > > Ok, that happens if you have 2 opal(s) installed. > > Compiled ok, but now it crashes on connection established > > with the following error: > > > > 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP > > Could not find SDP media description for Video > > 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP > > Could not find SDP media description for Image > > > > Xlib: unexpected async reply (sequence 0x11518)! > > > > > > No help if I disable that "Enable video" checkbox. > > Given that George is also encountering a crash, I would think Craig > recently broke something. > > Can you do the same operation than George (see other e-mails sent today) > to see if it is the same crash ? The only changes I made were to prevent error conditions causing crashes, and should not actually change existing functionality. I'll check SIP with video today using simpleopal and let you know how it goes. The two log mesages above indicate that the SDP does not contain any video or image (fax) entries. Without seeing the SDP I can't tell if this is true. Craig --- Craig Southeren Post Increment VoIP Consulting and Software [EMAIL PROTECTED] www.postincrement.com.au Phone: +61 243654666 ICQ: #86852844 Fax:+61 243656905 MSN: [EMAIL PROTECTED] Mobile: +61 417231046 Jabber: [EMAIL PROTECTED] "It takes a man to suffer ignorance and smile. Be yourself, no matter what they say." Sting ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Let's spread Ekiga : volunteers ?
Le mercredi 21 février 2007 à 08:06 +1100, Craig Southeren a écrit : > On Tue, 20 Feb 2007 20:23:58 +0100 > Damien Sandras <[EMAIL PROTECTED]> wrote: > > > Le mardi 20 février 2007 à 18:39 +0100, Jure Petrovic a écrit : > > > On Tue, 2007-02-20 at 11:14 +0100, Damien Sandras wrote: > > > > If it tells you you do not have 2.3.2, then you do not have 2.3.2 > > > > installed where it is looking for... > > > > > > Ok, that happens if you have 2 opal(s) installed. > > > Compiled ok, but now it crashes on connection established > > > with the following error: > > > > > > 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP > > > Could not find SDP media description for Video > > > 2007/02/20 18:36:37.052 1:57.200 SIP Handle...er:969c848 SIP > > > Could not find SDP media description for Image > > > > > > Xlib: unexpected async reply (sequence 0x11518)! > > > > > > > > > No help if I disable that "Enable video" checkbox. > > > > Given that George is also encountering a crash, I would think Craig > > recently broke something. > > > > Can you do the same operation than George (see other e-mails sent today) > > to see if it is the same crash ? > > The only changes I made were to prevent error conditions causing > crashes, and should not actually change existing functionality. > > I'll check SIP with video today using simpleopal and let you know how it > goes. > > The two log mesages above indicate that the SDP does not contain any > video or image (fax) entries. Without seeing the SDP I can't tell if > this is true. If you check the backtrace on the mailing list, you will see that it crashes in the rtp stack. I do not have much time to have a look at this (FOSDEM is approaching), so I'll leave this into your hands :-) -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
On Tue, 20 Feb 2007 12:17:07 -0800 George Boyd <[EMAIL PROTECTED]> wrote: > > > the command is thread apply all bt (sorry). > > > I should have known that :) > > Here's the output: ...deleted This backtrace showed me exactly where I had made my mistake :( I've checked in a fix for the problem into the OPAL CVS My apologies to all for the time wasted Craig --- Craig Southeren Post Increment VoIP Consulting and Software [EMAIL PROTECTED] www.postincrement.com.au Phone: +61 243654666 ICQ: #86852844 Fax:+61 243656905 MSN: [EMAIL PROTECTED] Mobile: +61 417231046 Jabber: [EMAIL PROTECTED] "It takes a man to suffer ignorance and smile. Be yourself, no matter what they say." Sting ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] CVS version compiles ok, but problems connecting
Le mercredi 21 février 2007 à 08:38 +1100, Craig Southeren a écrit : > On Tue, 20 Feb 2007 12:17:07 -0800 > George Boyd <[EMAIL PROTECTED]> wrote: > > > > > > the command is thread apply all bt (sorry). > > > > > I should have known that :) > > > > Here's the output: > > ...deleted > > This backtrace showed me exactly where I had made my mistake :( > > I've checked in a fix for the problem into the OPAL CVS > > My apologies to all for the time wasted > No time has been wasted, it is software development :) Thanks for the fix ! Damien ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Ekiga does not play sound when other applications already play sound, even with ALSA
Thanks a lot, the link indeed contained the information I needed. Turned out I had to use the "default" device instead of "nVidia NForce 2". Thanks again! I wouldn't have figured this out myself. Jan Schampera schreef: > On Thu, 8 Feb 2007 01:13:56 +0100 (CET) > [EMAIL PROTECTED] wrote: > >> I'm using Ekiga for internet telephony. Everything works perfectly >> well, except that Ekiga refuses to play any sounds when another >> application is playing sound. This way, I won't be able to hear >> incoming calls when I'm playing music. >> >> Other applications (e.g. Skype) do NOT have this problem. I am using >> the ALSA drivers. >> >> Is this intended behaviour of Ekiga, or am I doing anything wrong? >> >> Thanks for your help. >> >> If anybody could answer any of the above questions I would be >> thankful! I AM already using ALSA instead of OSS. > > This is not the intended behaviour for the ALSA backend, definitely. > Maybe > http://wiki.ekiga.org/index.php/Getting_several_applications_using_the_sound_card_at_the_same_time_%3F > helps you. > > Regards, > Jan > ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Problem receiving calls... and a solution.
Hi all, First of all, thank you for the nice work bringing Ekiga to the world. It's one of the best softphones out there, and it's free! I've run into a problem trying to set up Ekiga and luckily was able to fix it. As I didn't find a (specific) mention of it in the FAQ and it seems to me to be fairly common, I'm sending it to you in hope of helping someone else. Maybe it should go to the FAQ? Here is the problem: I've got a simple setup, Linux (Fedora 6), no NAT, a direct connection to the net, but I've got a strict firewall (iptables, stateful). Concerning UDP, only ESTABLISHED,RELATED packets are allowed in, all packets are allowed out. Pretty simple, pretty common, I suppose. The problem is, with this setup Ekiga (as configured by the wizard, with STUN) only receives calls just after connecting to ekiga.net (or any other SIP provider). I can make calls, but if I let Ekiga running after some time I can't receive any calls. Here is the cause: Ekiga (probably following SIP) registers with a service using UDP and the service (probably following SIP) expects to find Ekiga at the port it sent the registration (I guess :)). Well, in Linux with IP iptables, this port is only accessible for 180 seconds after the registration. After this time, the firewall will block the packets coming from the SIP service, as it considers the "session" to be over. Here is the solution: There are two ways of coping with that. If you can control your host (root), you can set the UDP iptables timeout to one hour: # echo 3600 > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream The FAQ hints at this buried in the script of section 6.2, but it points to the wrong variable ip_conntrack_udp_timeout instead of ip_conntrack_udp_timeout_stream. See http://ipsysctl-tutorial.frozentux.net/ipsysctl-tutorial.html#AEN730 for more details. You can use the sysctl utility to set kernel variables more easily. If you don't have control of your host, you can configure each account to refresh the registration every 180 seconds. That's it. Hope I've got it right and that it is useful. :) Abraços, Gustavo ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
Re: [Ekiga-list] Problem receiving calls... and a solution.
Le jeudi 01 février 2007 à 09:13 -0200, Gustavo Maciel Dias Vieira a écrit : > Hi all, > > First of all, thank you for the nice work bringing Ekiga to the world. > It's one of the best softphones out there, and it's free! > Thanks and sorry for the delay, your email was held in the queue. > I've run into a problem trying to set up Ekiga and luckily was able to > fix it. As I didn't find a (specific) mention of it in the FAQ and it > seems to me to be fairly common, I'm sending it to you in hope of > helping someone else. Maybe it should go to the FAQ? > > Here is the problem: I've got a simple setup, Linux (Fedora 6), no NAT, > a direct connection to the net, but I've got a strict firewall > (iptables, stateful). Concerning UDP, only ESTABLISHED,RELATED packets > are allowed in, all packets are allowed out. Pretty simple, pretty > common, I suppose. The problem is, with this setup Ekiga (as configured > by the wizard, with STUN) only receives calls just after connecting to > ekiga.net (or any other SIP provider). I can make calls, but if I let > Ekiga running after some time I can't receive any calls. > > Here is the cause: Ekiga (probably following SIP) registers with a > service using UDP and the service (probably following SIP) expects to > find Ekiga at the port it sent the registration (I guess :)). Well, in > Linux with IP iptables, this port is only accessible for 180 seconds > after the registration. After this time, the firewall will block the > packets coming from the SIP service, as it considers the "session" to be > over. > > Here is the solution: There are two ways of coping with that. If you can > control your host (root), you can set the UDP iptables timeout to one > hour: > # echo 3600 > /proc/sys/net/ipv4/netfilter/ip_conntrack_udp_timeout_stream > The FAQ hints at this buried in the script of section 6.2, but it points > to the wrong variable ip_conntrack_udp_timeout instead of > ip_conntrack_udp_timeout_stream. See > http://ipsysctl-tutorial.frozentux.net/ipsysctl-tutorial.html#AEN730 for > more details. You can use the sysctl utility to set kernel variables > more easily. If you don't have control of your host, you can configure > each account to refresh the registration every 180 seconds. > > That's it. Hope I've got it right and that it is useful. :) What is the difference between udp_timeout and udp_timeout_stream ? Also, do you know that Ekiga is supposed to send a packet every 30 seconds to the SIP host in order to refresh the binding ? Is it possible for you to sniff the trafic and see why it does not happen ? Thanks ! -- _ Damien Sandras (o- //\Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
[Ekiga-list] Registration failed: timeout with Ekiga 2.1
Hi, I can't connect to my ekiga.net and sipphone accounts. It used to work yesterday and really nothing changed on my system since then. The error I'm getting is "Registration failed: timeout". Oddly enough I can connect to another account on messagenet.it. Can anybody tell me what's going on? ekiga -d 4 says 2007/02/20 17:07:32.206 0:24.863 HousekeeperSIP Transaction 9 SUBSCRIBE timeout, making retry 3 2007/02/20 17:07:32.206 0:24.863 HousekeeperSIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:[EMAIL PROTECTED] SIP/2.0 CSeq: 9 SUBSCRIBE Via: SIP/2.0/UDP 160.36.56.237:5062 ;branch=z9hG4bKa6761a6c-9cbf-db11-85da-0015580bfcb9;rport User-Agent: Ekiga/2.1.0-20070217-01 From: ;tag=426c1a6c-9cbf-db11-85da-0015580bfcb9 Call-ID: [EMAIL PROTECTED] To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/02/20 17:07:34.686 0:27.343 HousekeeperSIP Set state Terminated_Timeout for transaction 8 REGISTER 2007/02/20 17:07:34.706 0:27.363 HousekeeperSIP Set state Terminated_Timeout for transaction 9 SUBSCRIBE Thanks Alfredo - Alfredo Buttari, Innovative Computing Laboratory, UTK Computer Science Dept. 1122 Volunteer Blvd. Knoxville, TN 37996 Tel: 001-865-974-9989 URL: http://www.ce.uniroma2.it/~buttari ___ ekiga-list mailing list ekiga-list@gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list
