Re: [Ekiga-devel-list] Tarball generation issues

2009-01-05 Thread Damien Sandras
Le lundi 05 janvier 2009 à 12:35 +0100, Damien Sandras a écrit :
 Le lundi 05 janvier 2009 à 12:32 +0100, Peter Robinson a écrit :
I am creating the tarball for gnome development release.  The 
generation of
ekiga tarball (and its compilation) went fine, I have the tar.gz of 
ekiga
for gnome.
   
I've been playing with building this on Fedora 10 to ensure that the
release will build on Fedora rawhide. A couple of small things I've
noticed that could be fixed
  
   Oh and it also doesn't compile on Fedora 10 so that's a bit of a show
   stopper too. Errors below.
  
   It seems your opal is the old one.
  
  Its 3.4.2 which is what its asking for in configure.ac
 
 You need : PTlib v2.5.2  OPAL v3.5.2
 
 I'll update teh configure.ac script tonight.

Done.
-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: [Ekiga-devel-list] Tarball generation issues

2009-01-05 Thread Peter Robinson
Hi,

 I am creating the tarball for gnome development release.  The generation of
 ekiga tarball (and its compilation) went fine, I have the tar.gz of ekiga
 for gnome.

I've been playing with building this on Fedora 10 to ensure that the
release will build on Fedora rawhide. A couple of small things I've
noticed that could be fixed

If you do a ./configure --help you get the following:

  --enable-gstreamerEnable GStreamer support
  --enable-de  Enable KDE support
  --enable-kab  Enable KAddressBook support

I think the middle one should be --enable-kde

Also when doing the library check I get the following opal error if
the speex libs aren't installed (should it not be checking for
speex?).

checking for PTLIB... yes
checking for OPAL... configure: error: Package requirements (opal =
3.4.2) were not met:

Package speexdsp was not found in the pkg-config search path.
Perhaps you should add the directory containing `speexdsp.pc'
to the PKG_CONFIG_PATH environment variable
Package 'speexdsp', required by 'opal', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables OPAL_CFLAGS
and OPAL_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


There's also a heap of the following errors which I don't think are
fatal but probably need to be added to a todo list somewhere.

gnome-doc-utils.make:160: wildcard $(_DOC_ABS_SRCDIR: non-POSIX variable name
gnome-doc-utils.make:160: (probably a GNU make extension)
help/Makefile.am:4:   `gnome-doc-utils.make' included from here
gnome-doc-utils.make:164: if $(_DOC_OMF_IN: non-POSIX variable name
gnome-doc-utils.make:164: (probably a GNU make extension)
help/Makefile.am:4:   `gnome-doc-utils.make' included from here
gnome-doc-utils.make:164: foreach lc,C $(_DOC_REAL_LINGUAS: non-POSIX
variable name
gnome-doc-utils.make:164: (probably a GNU make extension)
help/Makefile.am:4:   `gnome-doc-utils.make' included from here
gnome-doc-utils.make:173: call db2omf_args,$@,$,'docbook': non-POSIX
variable name
gnome-doc-utils.make:173: (probably a GNU make extension)

Cheers,
Peter
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list


Re: [Ekiga-devel-list] Unnecessary files

2009-01-05 Thread Eugen Dedu

Peter Robinson wrote:

FAQ, TODO files should be removed, they are nearly empty.

Rather than removing them maybe just put a reference in them to the
FAQ and ToDo lists on the website/wiki so people can find the current
version if they're looking for it.

Isn't the presence of TODO required by autotools?


I don't believe they are required, but I think its encouraged. The
reason I mentioned referencing the wiki URL in it saves keeping things
updated in multiple locations.


Well, let's then stay as we are now, with these two files.

--
Eugen
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list


Re: [Ekiga-devel-list] Tarball generation issues

2009-01-05 Thread Peter Robinson
On Mon, Jan 5, 2009 at 10:48 AM, Peter Robinson pbrobin...@gmail.com wrote:
 Hi,

 I am creating the tarball for gnome development release.  The generation of
 ekiga tarball (and its compilation) went fine, I have the tar.gz of ekiga
 for gnome.

 I've been playing with building this on Fedora 10 to ensure that the
 release will build on Fedora rawhide. A couple of small things I've
 noticed that could be fixed

Oh and it also doesn't compile on Fedora 10 so that's a bit of a show
stopper too. Errors below.

Cheers,
Peter

/bin/sh ../../../../libtool --tag=CXX   --mode=compile g++
-DHAVE_CONFIG_H -I. -I../../../.. -I../../../../lib
-I../../../../lib/gmconf -I../../../../lib/toolbox/
-I../../../../lib/engine/ -I../../../../lib/engine/account
-I../../../../lib/engine/addressbook -I../../../../lib/engine/chat
-I../../../../lib/engine/hal -I../../../../lib/engine/presence
-I../../../../lib/engine/protocol -I../../../../lib/engine/videooutput
-I../../../../lib/engine/videoinput
-I../../../../lib/engine/audioinput
-I../../../../lib/engine/audiooutput
-I../../../../lib/engine/framework   -I/usr/include/sigc++-2.0
-I/usr/lib64/sigc++-2.0/include   -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include   -DPTRACING=1 -D_REENTRANT
-fno-exceptions -I/usr/include/opal -I/usr/kerberos/include
-DPTRACING=1 -D_REENTRANT -fno-exceptions -I/usr/kerberos/include
-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic
-DLDAP_DEPRECATED=1 -fPIC -Wall -Wextra -Winit-self -Wswitch-default
-Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal -Wshadow -MT
opal-audio.lo -MD -MP -MF .deps/opal-audio.Tpo -c -o opal-audio.lo
`test -f '../../../../lib/engine/components/opal/opal-audio.cpp' ||
echo './'`../../../../lib/engine/components/opal/opal-audio.cpp
In file included from
../../../../lib/engine/components/opal/opal-gmconf-bridge.cpp:48:
../../../../lib/engine/components/opal/sip-endpoint.h:158: error:
expected ',' or '...' before '' token
../../../../lib/engine/components/opal/sip-endpoint.h:158: error: ISO
C++ forbids declaration of 'SIPDialogNotification' with no type
make[6]: *** [opal-gmconf-bridge.lo] Error 1
make[6]: *** Waiting for unfinished jobs
 g++ -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../lib
-I../../../../lib/gmconf -I../../../../lib/toolbox/
-I../../../../lib/engine/ -I../../../../lib/engine/account
-I../../../../lib/engine/addressbook -I../../../../lib/engine/chat
-I../../../../lib/engine/hal -I../../../../lib/engine/presence
-I../../../../lib/engine/protocol -I../../../../lib/engine/videooutput
-I../../../../lib/engine/videoinput
-I../../../../lib/engine/audioinput
-I../../../../lib/engine/audiooutput
-I../../../../lib/engine/framework -I/usr/include/sigc++-2.0
-I/usr/lib64/sigc++-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -DPTRACING=1 -D_REENTRANT
-fno-exceptions -I/usr/include/opal -I/usr/kerberos/include
-DPTRACING=1 -D_REENTRANT -fno-exceptions -I/usr/kerberos/include -O2
-g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -DLDAP_DEPRECATED=1
-fPIC -Wall -Wextra -Winit-self -Wswitch-default -Wswitch-enum
-Wstrict-aliasing=2 -Wfloat-equal -Wshadow -MT opal-audio.lo -MD -MP
-MF .deps/opal-audio.Tpo -c
../../../../lib/engine/components/opal/opal-audio.cpp  -fPIC -DPIC -o
.libs/opal-audio.o
In file included from ../../../../lib/engine/components/opal/opal-main.cpp:52:
../../../../lib/engine/components/opal/sip-endpoint.h:158: error:
expected ',' or '...' before '' token
../../../../lib/engine/components/opal/sip-endpoint.h:158: error: ISO
C++ forbids declaration of 'SIPDialogNotification' with no type
make[6]: *** [opal-main.lo] Error 1
 g++ -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../lib
-I../../../../lib/gmconf -I../../../../lib/toolbox/
-I../../../../lib/engine/ -I../../../../lib/engine/account
-I../../../../lib/engine/addressbook -I../../../../lib/engine/chat
-I../../../../lib/engine/hal -I../../../../lib/engine/presence
-I../../../../lib/engine/protocol -I../../../../lib/engine/videooutput
-I../../../../lib/engine/videoinput
-I../../../../lib/engine/audioinput
-I../../../../lib/engine/audiooutput
-I../../../../lib/engine/framework -I/usr/include/sigc++-2.0
-I/usr/lib64/sigc++-2.0/include -pthread -I/usr/include/glib-2.0
-I/usr/lib64/glib-2.0/include -DPTRACING=1 -D_REENTRANT
-fno-exceptions -I/usr/include/opal -I/usr/kerberos/include
-DPTRACING=1 -D_REENTRANT -fno-exceptions -I/usr/kerberos/include -O2
-g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic -DLDAP_DEPRECATED=1
-fPIC -Wall -Wextra -Winit-self -Wswitch-default -Wswitch-enum
-Wstrict-aliasing=2 -Wfloat-equal -Wshadow -MT opal-audio.lo -MD -MP
-MF .deps/opal-audio.Tpo -c
../../../../lib/engine/components/opal/opal-audio.cpp -o opal-audio.o
/dev/null 21
mv -f .deps/opal-audio.Tpo .deps/opal-audio.Plo
make[6]: 

Re: [Ekiga-devel-list] CELT is not shown

2009-01-05 Thread Eugen Dedu

Damien Sandras wrote:

Le dimanche 04 janvier 2009 à 20:29 +0100, Eugen Dedu a écrit :

Julien Puydt wrote:

Damien Sandras a écrit :

Le dimanche 04 janvier 2009 à 15:35 +0100, Eugen Dedu a écrit :

Damien Sandras wrote:

Le samedi 03 janvier 2009 à 20:29 +0100, Eugen Dedu a écrit :

Hi,

CELT is not shown in the codec list (current trunk), is it normal? 
(G722 is shown.)



Did you compile it ?

That's weird because I only committed fixes to OPAL to allow 
building it

a few minutes ago.

Notice you have to install libcelt-dev before running configure to get
it compiled.

Really sorry, I haven't installed the libcelt-dev package... (!!)

I'm not sure if it works or not, but at least here it is listed.
I have libcelt-dev and libcelt0, version 0.4.0-1 (debian unstable), and 
opal doesn't compile :

celtcodec.c: In function ‘celt_codec_encoder’:
celtcodec.c:147: warning: passing argument 2 of ‘celt_encode’ discards 
qualifiers from pointer target type
celtcodec.c:147: warning: passing argument 4 of ‘celt_encode’ makes 
integer from pointer without a cast

celtcodec.c:147: error: too many arguments to function ‘celt_encode’
I have the same problem with the opal tarball...  Can we modify the opal 
tarball we provide on the gnome site (to fix this compilation error)?


Let's just disable celt for this release. Or you can regenerate the
tarball with the patch applied.


I preferred to regenerate the tarball with the patch 
http://www.opalvoip.org/websvn/comp.php?repname=Opalpath=%2Fcompare[]=...@21882compare[]=...@21883 
applied.  Now opal compiles with celt.


I will this one for gnome.

--
Eugen
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: [Ekiga-devel-list] Unnecessary files

2009-01-05 Thread Eugen Dedu

Eugen Dedu wrote:

Julien Puydt wrote:

Peter Robinson a écrit :

FAQ, TODO files should be removed, they are nearly empty.


Rather than removing them maybe just put a reference in them to the
FAQ and ToDo lists on the website/wiki so people can find the current
version if they're looking for it.


Isn't the presence of TODO required by autotools?


At the end of http://www.systhread.net/texts/200601autotools.php it is 
said that it is not required...


Or we can add in TODO file some major features actually missing, such as:
- TCP over SIP
- record audio and video during a conversation
- test audio and video during configuration assistant
- gstreamer support
- DCCP support


For information, I have created http://wiki.ekiga.org/index.php/ToDo 
with these items.


--
Eugen
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

[Ekiga-devel-list] ANNOUNCE - Ekiga 3.1.0 [UNSTABLE] available

2009-01-05 Thread Damien Sandras
This is the first unstable release of the next 3.2 release of Ekiga. 


* What is it ?
==

Ekiga is a free Voice over IP softphone allowing you to do free calls
over the Internet.

Ekiga is the first Open Source application to support both H.323 and
SIP, as well as audio and video. Ekiga was formerly known as
GnomeMeeting.

More information can be found at http://www.ekiga.org


* Where to get it ?
===

Ekiga is available at:
ftp://ftp.gnome.org/pub/gnome/sources/ekiga/3.1

Required librairies can be found at:
ftp://ftp.gnome.org/pub/gnome/sources/opal/3.5/
ftp://ftp.gnome.org/pub/gnome/sources/ptlib/2.5/


* What's changed ?
==

* Added support for G.722 and CELT audio wideband codecs
* Added support for SIP dialog-info notifications, it allows being
notified of  incoming calls for the phones of your colleagues with
software like Asterisk
* Added support to disable STUN detection 
* Improved LDAP support in the address book, authentication is now
possible
* Killed the gconf_test_age test, Ekiga can now finally work with badly 
installed GConf schemas
* More efficient memory handling using gmref_ptr, increases stability
* Better handling of multiple network interfaces with dynamic addition
and removal
* libgnome is not required anymore when using GTK+ 2.14
* Many code cleanups, new GObjects, ...
* Work in progress : XCAP support, Resource List support, GStreamer
audio and video capture support, ...

-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list


[Ekiga-devel-list] issue with opal 3.5.2 finding ptlib 2.5.2

2009-01-05 Thread Peter Robinson
Hi All,

I think I'm going mad. I'm trying to build the ekiga 3.1.0 build to
push to rawhide but I'm running into another build issue. Nothing else
has changed in the build env except the versions and ptlib with devel
libraries are installed. Ideas anyone?

Peter

configure: gcc version is 4.3.2
checking if gcc version is valid... yes
checking for working bit scan intrinsic... yes
configure: Opal version is 3.5.2
checking where plugins are being installed... /usr/lib64/opal-3.5.2
checking wether to build a shared library... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-redhat-linux-gnu
checking Debugging support... no
checking for PTLIB... yes
Version:  2.5.2
CFLAGS:   -DPTRACING=1 -D_REENTRANT -D_GNU_SOURCE=1 -fno-exceptions
-I/usr/kerberos/include -I/usr/include/SDL
CXXFLAGS: -felide-constructors -Wreorder
DEBUG:-L/usr/kerberos/lib64 -lpt_d -lssl -lcrypto -lz -lSDL
-lpthread -lresolv -ldl
RELEASE:  -L/usr/kerberos/lib64 -lpt -lssl -lcrypto -lz -lSDL
-lpthread -lresolv -ldl
checking ptlib version... 2.5.2
configure: error: Could not find a linkable ptlib in specified
environment to verify symbols (debug ptlib: no)
error: Bad exit status from /var/tmp/rpm-tmp.SnlcOY (%build)


RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.SnlcOY (%build)
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list


Re: [Ekiga-devel-list] issue with opal 3.5.2 finding ptlib 2.5.2

2009-01-05 Thread Craig Southeren

Damien Sandras wrote:

Hi Peter,

Le mardi 06 janvier 2009 à 05:50 +0100, Peter Robinson a écrit :

Hi All,

I think I'm going mad. I'm trying to build the ekiga 3.1.0 build to
push to rawhide but I'm running into another build issue. Nothing else
has changed in the build env except the versions and ptlib with devel
libraries are installed. Ideas anyone?


..deleted

If you build ptlib with debugging (i.e. ./configure --enable-debug), 
then you must also compile opal with debugging (i.e. ,.configure 
--enable-debug)


Also, if you do not have PTLIBDR set when compiling PTLIB and Opal, then 
you must install PTLib else Opal will not be able to find it.


  Craig


---
 Craig Southeren  Post Increment – VoIP Consulting and Software
 cra...@postincrement.com.au   www.postincrement.com.au

 Phone:  +61 243654666  ICQ: #86852844
 Fax:+61 243656905  MSN: craig_southe...@hotmail.com
 Mobile: +61 417231046  Jabber: cra...@jabber.org

 Science is the poetry of reality. Richard Dawkins
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

Re: [Ekiga-list] ekiga 3.0.1 failure

2009-01-05 Thread Damien Sandras
Le lundi 05 janvier 2009 à 19:57 +1000, Brian a écrit :
 Damien,
  It's a crash!
 
  Can you get us a backtrace next time ?
 
  See:
  http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_send_us_a_backtrace_from_a_crash
 
 Checked out the page and started ekiga with
 gdb ekiga 21 | tee gdb-ekiga.txt
 
 I then got the output below.
 So I went and checked and I do not have any debug versions.
 Now I know I can compile PTLIB and OPAL with the the debug enabled.
 However, as per previous emails I cannot compile ekiga.
 SO,
 1) Is my current gdb run worthwhile?
 2) Is it worthwhile running with just ptlib and opal with debug.
 3) Can someone supply me with a debug 32bit ekiga that will run on suse  
 11.1

1) yes, but when it freezes, you have to hit ctrl-C and type the command
'thread apply all bt' like described in the wiki.
2) not yet, perhaps later if we can not identify the freeze/crash
clearly
3) I can't answer to this one
-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga 3.0.1 failure

2009-01-05 Thread Brian

Damien,

It's a crash!

Can you get us a backtrace next time ?

See:
http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_send_us_a_backtrace_from_a_crash


Checked out the page and started ekiga with
gdb ekiga 21 | tee gdb-ekiga.txt

I then got the output below.
So I went and checked and I do not have any debug versions.
Now I know I can compile PTLIB and OPAL with the the debug enabled.
However, as per previous emails I cannot compile ekiga.
SO,
1) Is my current gdb run worthwhile?
2) Is it worthwhile running with just ptlib and opal with debug.
3) Can someone supply me with a debug 32bit ekiga that will run on suse  
11.1


Thanks,
Brian


GNU gdb (GDB; openSUSE 11.1) 6.8.50.20081120-cvs
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later  
http://gnu.org/licenses/gpl.html

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i586-suse-linux.
For bug reporting instructions, please see:
http://bugs.opensuse.org/...
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/ekiga
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb548cb90 (LWP 9750)]
[New Thread 0xb544bb90 (LWP 9751)]
[New Thread 0xb540ab90 (LWP 9752)]
[New Thread 0xb53c9b90 (LWP 9753)]
[New Thread 0xb5388b90 (LWP 9754)]
[New Thread 0xb5347b90 (LWP 9755)]
[New Thread 0xb5306b90 (LWP 9756)]
[New Thread 0xb52c5b90 (LWP 9757)]
[New Thread 0xb5284b90 (LWP 9758)]
[Thread 0xb5284b90 (LWP 9758) exited]
[New Thread 0xb5243b90 (LWP 9759)]
[New Thread 0xb5284b90 (LWP 9761)]



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] More observations about Ekiga 3.

2009-01-05 Thread peasthope
Folk,

Palo, thanks for the information about sound devices.
When there is time on a weekend I'll try to decipher 
the code and implement the ideas in my system.

As recommended, Ekiga 3.0.1 is under trial in Debian 
Lenny here.  A few observations in case they help.

When Ekiga is started from the Desktop Menu, the tiny 
clock remains attached to the mouse pointer until 
the green Ekiga icon in the task bar is clicked.  
My interpretation is that Ekiga is not completing 
a startup process properly.

A call to sip:5...@ekiga.net works, although the 
amplitude of the echo is very small.

If a call to a PSTN number through the Diamond 
service is attempted, the echo test repeats.
The selected contact is ignored.

Do most users have Gnome?  I wonder whether this 
Xfce environment is the source of some problems?

Thanks,  ... Peter E.

-- 
http://members.shaw.ca/peasthope/
http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] More observations about Ekiga 3.

2009-01-05 Thread Damien Sandras
Le lundi 05 janvier 2009 à 12:13 -0800, peasth...@shaw.ca a écrit :
 Folk,
 
 Palo, thanks for the information about sound devices.
 When there is time on a weekend I'll try to decipher 
 the code and implement the ideas in my system.
 
 As recommended, Ekiga 3.0.1 is under trial in Debian 
 Lenny here.  A few observations in case they help.
 
 When Ekiga is started from the Desktop Menu, the tiny 
 clock remains attached to the mouse pointer until 
 the green Ekiga icon in the task bar is clicked.  
 My interpretation is that Ekiga is not completing 
 a startup process properly.
 
 A call to sip:5...@ekiga.net works, although the 
 amplitude of the echo is very small.
 
 If a call to a PSTN number through the Diamond 
 service is attempted, the echo test repeats.
 The selected contact is ignored.

A bit weird. you are probably not doing the right thing.

 Do most users have Gnome?  I wonder whether this 
 Xfce environment is the source of some problems?
 

Certainly not.
-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] ANNOUNCE - Ekiga 3.1.0 [UNSTABLE] available

2009-01-05 Thread Damien Sandras
This is the first unstable release of the next 3.2 release of Ekiga. 


* What is it ?
==

Ekiga is a free Voice over IP softphone allowing you to do free calls
over the Internet.

Ekiga is the first Open Source application to support both H.323 and
SIP, as well as audio and video. Ekiga was formerly known as
GnomeMeeting.

More information can be found at http://www.ekiga.org


* Where to get it ?
===

Ekiga is available at:
ftp://ftp.gnome.org/pub/gnome/sources/ekiga/3.1

Required librairies can be found at:
ftp://ftp.gnome.org/pub/gnome/sources/opal/3.5/
ftp://ftp.gnome.org/pub/gnome/sources/ptlib/2.5/


* What's changed ?
==

* Added support for G.722 and CELT audio wideband codecs
* Added support for SIP dialog-info notifications, it allows being
notified of  incoming calls for the phones of your colleagues with
software like Asterisk
* Added support to disable STUN detection 
* Improved LDAP support in the address book, authentication is now
possible
* Killed the gconf_test_age test, Ekiga can now finally work with badly 
installed GConf schemas
* More efficient memory handling using gmref_ptr, increases stability
* Better handling of multiple network interfaces with dynamic addition
and removal
* libgnome is not required anymore when using GTK+ 2.14
* Many code cleanups, new GObjects, ...
* Work in progress : XCAP support, Resource List support, GStreamer
audio and video capture support, ...

-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] Re (2): More observations about Ekiga 3.

2009-01-05 Thread peasthope
Damien  others,

 A bit weird. you are probably not doing the right thing.

Agreed  agreed.

Let's forget the test calls for now.  The clock is on the 
mouse pointer for about 45 seconds.  How long does 
registration of an ekiga account and a Diamond 
account normally require?  If one of these services 
happens to be down, Ekiga waits to a timeout?

Incidentally, Ekiga 2 displayed the number of accounts 
successfully registered.  I don't see this number on 
Ekiga 3.

Regards,... Peter E.

-- 
http://members.shaw.ca/peasthope/
http://carnot.yi.org/ = http://carnot.pathology.ubc.ca/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Re (2): More observations about Ekiga 3.

2009-01-05 Thread Damien Sandras
Le lundi 05 janvier 2009 à 13:29 -0800, peasth...@shaw.ca a écrit :
 Damien  others,
 
  A bit weird. you are probably not doing the right thing.
 
 Agreed  agreed.
 
 Let's forget the test calls for now.  The clock is on the 
 mouse pointer for about 45 seconds.  How long does 
 registration of an ekiga account and a Diamond 
 account normally require?  If one of these services 
 happens to be down, Ekiga waits to a timeout?

Yes, you can check if it is registered or not by looking at the accounts
window (Edit menu).

Now that I think about it, I can confirm that the mouse pointer that you
notice after having started Ekiga is not influenced by Ekiga at all. It
is supposed to show the busy state (the clock) during a GNOME program
launch, but it is also supposed to end right after, without any
interaction of the program itself.

So it is not influenced by the account registration.

 
 Incidentally, Ekiga 2 displayed the number of accounts 
 successfully registered.  I don't see this number on 
 Ekiga 3.

Yes, we dropped that information.
-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list