question of using Ekiga to KEK (fwd)

[physjg]

Hello,

I used Ekiga 2.x with Ubuntu 8.04 to connect to KEK meeting room via H323
before and it worked ok.  Recently I upgraded to Ubuntu 9.04 and also installed
Ekiga 3.x, then that connection does not work anymore.

While I tried to connect to 30222@... or 30425@..., it
showed a message of "Connected with RADVISION MCU", but it did not really
connected to those meeting room.  However, I tried again with older Ekiga (2.x)
at another person's laptop and it does work.  So, it cannot be the gateway's
problem.

I consulted with KEK IT center and they also found Ekiga 3.x not working to
connect to their meeting room.  Could any expert from Ekiga group to
investigate it?

physjg

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

[Joseph Comfort]

I have the very same problem with SuSE 11.1 (and 11.0 before that). I have
to stick with SuSE 10.3 and the Ekiga 2.x version.  The Ekiga mailing list
is full of messages about problems with Ekiga and Ubuntu, but the problems
are broader than that.  It may be partly due to some major changes in
audio systems in the more recent OS releases, but I am sure that ekiga
has gone bad as well.

Joe Comfort

On Fri, 26 Jun 2009, physjg wrote:

> Hello,
>
> I used Ekiga 2.x with Ubuntu 8.04 to connect to KEK meeting room via H323
> before and it worked ok.  Recently I upgraded to Ubuntu 9.04 and also
> installed Ekiga 3.x, then that connection does not work anymore.
>
> While I tried to connect to 30222@... or 30425@..., it
> showed a message of "Connected with RADVISION MCU", but it did not really
> connected to those meeting room.  However, I tried again with older Ekiga
> (2.x) at another person's laptop and it does work.  So, it cannot be the
> gateway's problem.
>
> I consulted with KEK IT center and they also found Ekiga 3.x not working to
> connect to their meeting room.  Could any expert from Ekiga group to
> investigate it?
>
> physjg
>
> _______________________________________________
> ekiga-list mailing list
> ekiga-list@...
> http://mail.gnome.org/mailman/listinfo/ekiga-list
>
>

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

[Eugen Dedu]

physjg wrote:

> Hello,
>
> I used Ekiga 2.x with Ubuntu 8.04 to connect to KEK meeting room via
> H323 before and it worked ok.  Recently I upgraded to Ubuntu 9.04 and
> also installed Ekiga 3.x, then that connection does not work anymore.
>
> While I tried to connect to 30222@... or 30425@...,
> it showed a message of "Connected with RADVISION MCU", but it did not
> really connected to those meeting room.  However, I tried again with
> older Ekiga (2.x) at another person's laptop and it does work.  So, it
> cannot be the gateway's problem.
>
> I consulted with KEK IT center and they also found Ekiga 3.x not working
> to connect to their meeting room.  Could any expert from Ekiga group to
> investigate it?

Could you send us the -d 4 output?

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

[Damien Sandras]

Le jeudi 25 juin 2009 à 21:21 -0700, Joseph Comfort a écrit :
> I have the very same problem with SuSE 11.1 (and 11.0 before that). I have
> to stick with SuSE 10.3 and the Ekiga 2.x version.  The Ekiga mailing list
> is full of messages about problems with Ekiga and Ubuntu, but the problems
> are broader than that.  It may be partly due to some major changes in
> audio systems in the more recent OS releases, but I am sure that ekiga
> has gone bad as well.

Joe,

nobody is actively working on the H.323 part anymore, unfortunately.
--
 _     Damien Sandras
(o-      
//\    Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP           : http://www.beip.be/
       FOSDEM          : http://www.fosdem.org/
       SIP Phone       : sip:dsandras@...
                       

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

[physjg]

The full output is too long so my previous mail was blocked.
This one is with the "short" version of the ekiga -d 4 output.

However, from Damien Sandras's mail. does it mean Ekiga can be out of free
H.323 software business now?

physjg


On Fri, 26 Jun 2009, Eugen Dedu wrote:

> physjg wrote:
>> Hello,
>>
>> I used Ekiga 2.x with Ubuntu 8.04 to connect to KEK meeting room via H323
>> before and it worked ok.  Recently I upgraded to Ubuntu 9.04 and also
>> installed Ekiga 3.x, then that connection does not work anymore.
>>
>> While I tried to connect to 30222@... or 30425@..., it
>> showed a message of "Connected with RADVISION MCU", but it did not really
>> connected to those meeting room.  However, I tried again with older Ekiga
>> (2.x) at another person's laptop and it does work.  So, it cannot be the
>> gateway's problem.
>>
>> I consulted with KEK IT center and they also found Ekiga 3.x not working to
>> connect to their meeting room.  Could any expert from Ekiga group to
>> investigate it?
>
> Could you send us the -d 4 output?
>
> --
> Eugen
> _______________________________________________
> ekiga-list mailing list
> ekiga-list@...
> http://mail.gnome.org/mailman/listinfo/ekiga-list
>

> ekiga -d 4

2009/06/26 15:27:02.275  0:00.086                       Version 3.2.0 by  on Unix Linux (2.6.28-13-generic-i686) with PTLib (v2.6.1) at 2009/6/26 15:27:02.274
2009/06/26 15:27:02.275  0:00.086                       Ekiga SVN revision: unknown
2009/06/26 15:27:02.279  0:00.090                       Ekiga registered on D-Bus: org.ekiga.Ekiga
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
2009/06/26 15:27:02.280  0:00.091                       PWLib File handle high water mark set: 14 Thread unblock pipe
2009/06/26 15:27:02.280  0:00.091                       PWLib Thread high water mark set: 2
2009/06/26 15:27:02.281  0:00.092                       PWLib File handle high water mark set: 16 Thread unblock pipe
2009/06/26 15:27:02.281  0:00.092                       PWLib Thread high water mark set: 3
2009/06/26 15:27:02.281  0:00.092                       PWLib File handle high water mark set: 18 Thread unblock pipe
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
2009/06/26 15:27:02.283  0:00.094                       PWLib File handle high water mark set: 20 Thread unblock pipe
2009/06/26 15:27:02.285  0:00.096                       PWLib Thread high water mark set: 4
2009/06/26 15:27:02.286  0:00.097                       HalManager_dbus Initialising HAL Manager
2009/06/26 15:27:02.292  0:00.103                       HalManager_dbus Populating device list
2009/06/26 15:27:02.445  0:00.256                       HalManager_dbus Populated device list with 14 devices
2009/06/26 15:27:02.445  0:00.256                       HalManager_dbus Populating interface list
2009/06/26 15:27:02.446  0:00.257                       HalManager_dbus Populating full interface list failed - Method "getDevices" with signature "" on interface "org.freedesktop.NetworkManager" doesn't exist

2009/06/26 15:27:02.446  0:00.257                       Detecting V4L2 devices
2009/06/26 15:27:02.447  0:00.258                       PV4L2Plugin detected device metadata at /sys/class/video4linux/
2009/06/26 15:27:02.486  0:00.297                       PWLib File handle high water mark set: 25 Thread unblock pipe
2009/06/26 15:27:02.486  0:00.297                       PWLib Thread high water mark set: 5
2009/06/26 15:27:02.486  0:00.297                       OpalMan Created manager.
2009/06/26 15:27:02.486  0:00.297                       OpalMan Registered endpoint with prefix pc
2009/06/26 15:27:02.487  0:00.298                       OpalEP Created endpoint: pc
2009/06/26 15:27:02.559  0:00.370                       PCSS Created PC sound system endpoint.
Players:
Default
HDA Intel
HDA Intel (1)
EKIGA
*.wav
Recorders:
Default
HDA Intel
HDA Intel (1)
EKIGA
*.wav

2009/06/26 15:27:02.561  0:00.372                       OPAL SetMediaFormatOrder()
2009/06/26 15:27:02.561  0:00.372                       OPAL SetMediaFormatMask()
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
2009/06/26 15:27:02.563  0:00.374                       OpalMan Registered endpoint with prefix sip
2009/06/26 15:27:02.563  0:00.374                       OpalEP Created endpoint: sip
2009/06/26 15:27:02.563  0:00.374                       PWLib File handle high water mark set: 26 PUDPSocket
2009/06/26 15:27:02.563  0:00.374                       IfaceMon Initial interface list:
127.0.0.1 [00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:01] <00-00-00-00-00-00> (lo)
140.112.102.80 [fe:80:00:00:00:00:00:00:02:02:b3:ff:fe:4d:3d:ca] <00-02-B3-4D-3D-CA> (eth2)
192.168.10.230 [fe:80:00:00:00:00:00:00:02:1b:fc:ff:fe:8c:05:d3] <00-1B-FC-8C-05-D3> (eth0)

2009/06/26 15:27:02.564  0:00.375                       PWLib File handle high water mark set: 27 Thread unblock pipe
2009/06/26 15:27:02.564  0:00.375                       PWLib Thread high water mark set: 6
2009/06/26 15:27:02.564  0:00.375                       PWLib File handle high water mark set: 29 Thread unblock pipe
2009/06/26 15:27:02.564  0:00.375                       PWLib Thread high water mark set: 7
2009/06/26 15:27:02.564  0:00.375 Network In...0xb5526b90 IfaceMon Started interface monitor thread.
2009/06/26 15:27:02.564  0:00.375                       OpalMan Registered endpoint with prefix sips
2009/06/26 15:27:02.564  0:00.375                       SIP Created endpoint.
2009/06/26 15:27:02.564  0:00.375 Network In...0xb5526b90 PWLib File handle high water mark set: 30 PUDPSocket
2009/06/26 15:27:02.565  0:00.376                       PWLib File handle high water mark set: 31 PUDPSocket
2009/06/26 15:27:02.565  0:00.376                       MonSock Created socket bundle for all interfaces.
2009/06/26 15:27:02.565  0:00.376                       PWLib File handle low water mark set: 30 PUDPSocket
2009/06/26 15:27:02.565  0:00.376                       MonSock Created bundled UDP socket 140.112.102.80:5060
2009/06/26 15:27:02.565  0:00.376                       PWLib File handle high water mark set: 32 PUDPSocket
2009/06/26 15:27:02.565  0:00.376                       MonSock Created bundled UDP socket 192.168.10.230:5060
2009/06/26 15:27:02.565  0:00.376                       PWLib File handle high water mark set: 34 Thread unblock pipe
2009/06/26 15:27:02.565  0:00.376                       PWLib Thread high water mark set: 8
2009/06/26 15:27:02.566  0:00.377 Opal Liste...0xb54a4b90 Listen Started listening thread on udp$*:5060
2009/06/26 15:27:02.566  0:00.377                       OpalMan Added route "sip:.*=pc:*"
2009/06/26 15:27:02.566  0:00.377                       OpalMan Added route "pc:.*=sip:<da>"
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
2009/06/26 15:27:02.567  0:00.378                       OpalMan Registered endpoint with prefix h323
2009/06/26 15:27:02.567  0:00.378                       OpalEP Created endpoint: h323
2009/06/26 15:27:02.567  0:00.378                       OpalMan Registered endpoint with prefix h323s
2009/06/26 15:27:02.567  0:00.378                       H323 Created endpoint.
2009/06/26 15:27:02.567  0:00.378                       PWLib File handle high water mark set: 35 PTCPSocket
2009/06/26 15:27:02.568  0:00.379                       PWLib File handle high water mark set: 37 Thread unblock pipe
2009/06/26 15:27:02.568  0:00.379                       PWLib Thread high water mark set: 9
2009/06/26 15:27:02.568  0:00.379 Opal Liste...0xb5463b90 Listen Started listening thread on tcp$*:1720
2009/06/26 15:27:02.568  0:00.379 Opal Liste...0xb5463b90 Listen Waiting on socket accept on tcp$*:1720
2009/06/26 15:27:02.568  0:00.379                       OpalMan Added route "h323:.*=pc:<db>"
2009/06/26 15:27:02.568  0:00.379                       OpalMan Added route "pc:.*=h323:<da>"
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)

(the above message repeated many many times.........)

2009/06/26 15:27:03.043  0:00.854                       Ekiga version 3.2.0
2009/06/26 15:27:03.043  0:00.854                       OPAL version 3.6.1
2009/06/26 15:27:03.043  0:00.854                       PTLIB version 2.6.1
2009/06/26 15:27:03.043  0:00.854                       GNOME support disabled
2009/06/26 15:27:03.043  0:00.854                       Accelerated rendering support enabled
2009/06/26 15:27:03.043  0:00.854                       DBUS support enabled
2009/06/26 15:27:03.043  0:00.854                       GConf support enabled
2009/06/26 15:27:03.043  0:00.854                       ESound support disabled
GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)

(the above message repeated many times again.........)

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

[Damien Sandras]

Le vendredi 26 juin 2009 à 15:35 +0800, physjg a écrit :
> The full output is too long so my previous mail was blocked.
> This one is with the "short" version of the ekiga -d 4 output.

There is no call attempt.

> However, from Damien Sandras's mail. does it mean Ekiga can be out of free
> H.323 software business now?

It is maintained, but not improved anymore.
--
 _     Damien Sandras
(o-      
//\    Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP           : http://www.beip.be/
       FOSDEM          : http://www.fosdem.org/
       SIP Phone       : sip:dsandras@...
                       

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

[Joseph Comfort]

Unfortunately, I have not found much in the way of good H323 alternatives
to Ekiga.  There are alternatives for SIP.  I'm only a user, but it seems
to me that Ekiga has gone too far out on the bleeding edge with all kinds
of frilly add-ons which depend on OS systems and packages (even compilers)
that are still in development.  Maintenance of the core functionality is
drowning.  I have not yet had a successful compilation of the latest
source.  Still, the basic issue may be in the audio stuff of the OS.

Joe Comfort

On Fri, 26 Jun 2009, Damien Sandras wrote:

> Le vendredi 26 juin 2009 à 15:35 +0800, physjg a écrit :
> > The full output is too long so my previous mail was blocked.
> > This one is with the "short" version of the ekiga -d 4 output.
>
> There is no call attempt.
>
> > However, from Damien Sandras's mail. does it mean Ekiga can be out of free
> > H.323 software business now?
>
> It is maintained, but not improved anymore.
> --
>  _     Damien Sandras
> (o-      
> //\    Ekiga Softphone : http://www.ekiga.org/
> v_/_   Be IP           : http://www.beip.be/
>        FOSDEM          : http://www.fosdem.org/
>        SIP Phone       : sip:dsandras@...
>                        
>
> _______________________________________________
> ekiga-list mailing list
> ekiga-list@...
> http://mail.gnome.org/mailman/listinfo/ekiga-list

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

[Craig Southeren]

Joseph Comfort wrote:
> Unfortunately, I have not found much in the way of good H323 alternatives
> to Ekiga.  There are alternatives for SIP.  I'm only a user, but it seems
> to me that Ekiga has gone too far out on the bleeding edge with all kinds
> of frilly add-ons which depend on OS systems and packages (even compilers)
> that are still in development.  Maintenance of the core functionality is
> drowning.  I have not yet had a successful compilation of the latest
> source.  Still, the basic issue may be in the audio stuff of the OS.

H.323 is still very actively maintained in the Opal library.

If you are having problems with H.323, please let us know on the Opal
list (see www.opalvoip.org)

    Craig
--

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

  Phone:  [phone]      ICQ: #86852844
  Fax:    [phone]      MSN: craig_southeren@...
  Mobile: [phone]      Jabber: craigs@...

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

[Joseph Comfort]

Craig,

Thank you.  I'm not sure H323 is the problem, and I will let Opal know
if I can pinpoint something there.  The symptom is that, while video
appears to be transmitted out from Ekiga, there is no video back and no
audio either way.  The -d 4 logs apparently do not show any problems.
Portions of the audio system work (e.g., I get the system sounds) but
others have become largely non-functional in some of the recent OS
releases.  I keep thinking it is something simple and all the problems
will go away.  No luck yet.

Joe

Craig Southeren wrote:
>
> H.323 is still very actively maintained in the Opal library.
>
> If you are having problems with H.323, please let us know on the Opal
> list (see www.opalvoip.org)
>
>    Craig

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

[physjg]

Hello,

Sorry, the log file from -d 4 output I sent was just the result while
launching the Ekiga, not really doing any connection action yet.  I will
try to produce it again with the information from connection attempt.  I
tried it a few times, somehow the program crashed and even my address book
was gone.

physjg


On Fri, 26 Jun 2009, Joseph Comfort wrote:

> Craig,
>
> Thank you.  I'm not sure H323 is the problem, and I will let Opal know
> if I can pinpoint something there.  The symptom is that, while video
> appears to be transmitted out from Ekiga, there is no video back and no
> audio either way.  The -d 4 logs apparently do not show any problems.
> Portions of the audio system work (e.g., I get the system sounds) but
> others have become largely non-functional in some of the recent OS
> releases.  I keep thinking it is something simple and all the problems
> will go away.  No luck yet.
>
> Joe
>
> Craig Southeren wrote:
>>
>> H.323 is still very actively maintained in the Opal library.
>>
>> If you are having problems with H.323, please let us know on the Opal
>> list (see www.opalvoip.org)
>>
>>    Craig
>
> _______________________________________________
> ekiga-list mailing list
> ekiga-list@...
> http://mail.gnome.org/mailman/listinfo/ekiga-list
>

--
====================
Jing-Ge Shiu
PhY-WSU-DESY-WSU-NTU
TEL: [phone]
FAX: [phone]

  ____  _   _  _  _  ___   ____  ___
(  _ \( )_( )( \/ )/ __) (_  _)/ __)
  )___/ ) _ (  \  / \__ \.-_)( ( (_-.
(__)  (_) (_) (__) (___/\____) \___/


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

[Eugen Dedu]

Joseph Comfort wrote:
> Unfortunately, I have not found much in the way of good H323 alternatives
> to Ekiga.  There are alternatives for SIP.  I'm only a user, but it seems
> to me that Ekiga has gone too far out on the bleeding edge with all kinds
> of frilly add-ons which depend on OS systems and packages (even compilers)
> that are still in development.  Maintenance of the core functionality is
> drowning.  I have not yet had a successful compilation of the latest
> source.  Still, the basic issue may be in the audio stuff of the OS.

I agree with you that the core functionality is the most important, and
it should work flawlessly.  The work is focused on this goal currently.
  If you look at recent commits, there are only fixes, and many fixes.
It still seems that sometimes, these fixes break other parts of the
software.  I suppose this is because SIP/H323 is very complex.

(People use ekiga, and complain, but few help...)

> Joe Comfort
>
> On Fri, 26 Jun 2009, Damien Sandras wrote:
>
>> Le vendredi 26 juin 2009 à 15:35 +0800, physjg a écrit :
>>> The full output is too long so my previous mail was blocked.
>>> This one is with the "short" version of the ekiga -d 4 output.
>> There is no call attempt.
>>
>>> However, from Damien Sandras's mail. does it mean Ekiga can be out of free
>>> H.323 software business now?
>> It is maintained, but not improved anymore.
>> --
>>  _     Damien Sandras
>> (o-      
>> //\    Ekiga Softphone : http://www.ekiga.org/
>> v_/_   Be IP           : http://www.beip.be/
>>        FOSDEM          : http://www.fosdem.org/
>>        SIP Phone       : sip:dsandras@...
>>                        
>>
>> _______________________________________________
>> ekiga-list mailing list
>> ekiga-list@...
>> http://mail.gnome.org/mailman/listinfo/ekiga-list
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> ekiga-list mailing list
>> ekiga-list@...
>> http://mail.gnome.org/mailman/listinfo/ekiga-list

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

[physjg]

Hello,

> Joseph Comfort wrote:
> ....
> (People use ekiga, and complain, but few help...)

For most of people, like me, are only users but developers.  What the best
we can contribute is to feedback our experience.  If one thinks in another
way, complain is a good thing.  Under what condition there will be no
complain ---- no one is really using it.

Attached is a piece of the ekiga -d 4 output while attempting to connect
to a meeting room at KEK.  I hope this can give the experts some clues.
The symptom is different from before.  This time I cannot make any
connection.  Before at lease I can have "Connected with RADVISION MCU".

physjg

On Sat, 27 Jun 2009, Eugen Dedu wrote:

> Joseph Comfort wrote:
>> Unfortunately, I have not found much in the way of good H323 alternatives
>> to Ekiga.  There are alternatives for SIP.  I'm only a user, but it seems
>> to me that Ekiga has gone too far out on the bleeding edge with all kinds
>> of frilly add-ons which depend on OS systems and packages (even compilers)
>> that are still in development.  Maintenance of the core functionality is
>> drowning.  I have not yet had a successful compilation of the latest
>> source.  Still, the basic issue may be in the audio stuff of the OS.
>
> I agree with you that the core functionality is the most important, and
> it should work flawlessly.  The work is focused on this goal currently.
>  If you look at recent commits, there are only fixes, and many fixes.
> It still seems that sometimes, these fixes break other parts of the
> software.  I suppose this is because SIP/H323 is very complex.
>
> (People use ekiga, and complain, but few help...)
>
>> Joe Comfort
>>
>> On Fri, 26 Jun 2009, Damien Sandras wrote:
>>
>>> Le vendredi 26 juin 2009 à 15:35 +0800, physjg a écrit :
>>>> The full output is too long so my previous mail was blocked.
>>>> This one is with the "short" version of the ekiga -d 4 output.
>>> There is no call attempt.
>>>
>>>> However, from Damien Sandras's mail. does it mean Ekiga can be out of
> free
>>>> H.323 software business now?
>>> It is maintained, but not improved anymore.
>>> --
>>>  _     Damien Sandras
>>> (o-
>>> //\    Ekiga Softphone : http://www.ekiga.org/
>>> v_/_   Be IP           : http://www.beip.be/
>>>        FOSDEM          : http://www.fosdem.org/
>>>        SIP Phone       : sip:dsandras@...
>>>
>>>
>>> _______________________________________________
>>> ekiga-list mailing list
>>> ekiga-list@...
>>> http://mail.gnome.org/mailman/listinfo/ekiga-list
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> ekiga-list mailing list
>>> ekiga-list@...
>>> http://mail.gnome.org/mailman/listinfo/ekiga-list
>
> _______________________________________________
> ekiga-list mailing list
> ekiga-list@...
> http://mail.gnome.org/mailman/listinfo/ekiga-list

2009/06/28 14:05:53.400  6:11.627                       OpalMan Set up call from pc:* to h323:30425@...
2009/06/28 14:05:53.401  6:11.628                       Call Created Call[y1b92e0d81]
2009/06/28 14:05:53.401  6:11.628                       OpalMan Set up connection to "pc:*"
2009/06/28 14:05:53.403  6:11.630                       OpalCon Created connection Call[y1b92e0d81]-EP<pc>[sf6d465192]
2009/06/28 14:05:53.403  6:11.630                       Silence Parameters set: mode=AdaptiveSilenceDetection, threshold=0, silencedb=3200, signaldb=80, period=4800
2009/06/28 14:05:53.403  6:11.630                       Silence Handler created
2009/06/28 14:05:53.404  6:11.631                       Echo Canceler Handler created
2009/06/28 14:05:53.404  6:11.631                       PCSS Created PC sound system connection: token="sf6d465192" player="EKIGA" recorder="EKIGA"
2009/06/28 14:05:53.404  6:11.631                       OpalCon SetPhase from UninitialisedPhase to SetUpPhase for Call[y1b92e0d81]-EP<pc>[sf6d465192]
2009/06/28 14:05:53.405  6:11.632                       OpalMan OnIncoming connection Call[y1b92e0d81]-EP<pc>[sf6d465192]
2009/06/28 14:05:53.405  6:11.632                       OpalCon Applying string options:


2009/06/28 14:05:53.405  6:11.632                       Call GetOtherPartyConnection Call[y1b92e0d81]-EP<pc>[sf6d465192]
2009/06/28 14:05:53.405  6:11.632                       OpalMan Searching for route "pc:physjg h323:30425@..."
2009/06/28 14:05:53.405  6:11.632                       OpalMan Set up connection to "h323:30425@..."
2009/06/28 14:05:53.405  6:11.633                       H323 Making call to: h323:30425@...
2009/06/28 14:05:53.406  6:11.633                       DNS SRV Lookup h323gk.kek.jp service _h323._tcp
2009/06/28 14:05:53.446  6:11.673                       OpalCon Created connection Call[y1b92e0d81]-EP<h323>[localhost/8175]
2009/06/28 14:05:53.447  6:11.674                       RFC2833 Handler created
2009/06/28 14:05:53.447  6:11.674                       RFC2833 Handler created
2009/06/28 14:05:53.447  6:11.674                       H460 Endpoint Attached
2009/06/28 14:05:53.447  6:11.674                       H323 Created new connection: localhost/8175
2009/06/28 14:05:53.447  6:11.674                       PCSS Outgoing call routed to h323: for Call[y1b92e0d81]-EP<pc>[sf6d465192]
2009/06/28 14:05:53.447  6:11.674   CallSetup:0xb3231b90 Call OnSetUp Call[y1b92e0d81]-EP<pc>[sf6d465192]
2009/06/28 14:05:53.448  6:11.675   CallSetup:0xb3231b90 OpalCon Applying string options:


2009/06/28 14:05:53.448  6:11.675                       OpalMan SetUpCall succeeded, call=Call[y1b92e0d81]
2009/06/28 14:05:53.451  6:11.678 H225 Caller:0xb31f0b90 H225 Started call thread
2009/06/28 14:05:53.451  6:11.678   CallSetup:0xb3231b90 OpalCon OnSetUpConnectionCall[y1b92e0d81]-EP<h323>[localhost/8175]
2009/06/28 14:05:53.451  6:11.678   CallSetup:0xb3231b90 OpalEP OnSetUpConnection Call[y1b92e0d81]-EP<h323>[localhost/8175]
2009/06/28 14:05:53.451  6:11.678 H225 Caller:0xb31f0b90 OpalCon SetPhase from UninitialisedPhase to SetUpPhase for Call[y1b92e0d81]-EP<h323>[localhost/8175]
2009/06/28 14:05:53.454  6:11.681 H225 Caller:0xb31f0b90 OpalCon SetPhase from SetUpPhase to SetUpPhase for Call[y1b92e0d81]-EP<h323>[localhost/8175]
2009/06/28 14:05:53.454  6:11.681 H225 Caller:0xb31f0b90 OpalTCP Connecting to 130.87.34.42:1720 (local port=30000)
2009/06/28 14:05:53.492  6:11.719 H225 Caller:0xb31f0b90 OpalTCP Started connection to 130.87.34.42:1720 (if=140.112.102.80:30000)
2009/06/28 14:05:53.492  6:11.719 H225 Caller:0xb31f0b90 H225 Sending Setup PDU
2009/06/28 14:05:53.492  6:11.719 H225 Caller:0xb31f0b90 OpalCon Applying string options:


2009/06/28 14:05:53.497  6:11.724 H225 Caller:0xb31f0b90 MediaFormat Removing codecs PCM-16-48kHz,PCM-16-32kHz,PCM-16-16kHz,PCM-16,G.726-16k,G.726-24k,G.726-32k,G.726-40k,GSM-06.10,GSM-AMR,LPC-10,MS-GSM,MS-IMA-ADPCM,SpeexIETFNarrow-11k,SpeexIETFNarrow-15k,SpeexIETFNarrow-18.2k,SpeexIETFNarrow-24.6k,SpeexIETFNarrow-5.95k,SpeexIETFNarrow-8k,SpeexNB,SpeexWNarrow-8k,YUV420P,RFC4175_YCbCr-4:2:0,RGB32,RGB24,RFC4175_RGB,SIP-IM,T.140,H.224/H323AnnexQ,H.224/HDLCTunneling,Linear-16-Stereo-48kHz
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 Call GetMediaFormats for Call[y1b92e0d81]-EP<h323>[localhost/8175]
theora
H.261
H.261-CIF
H.261-QCIF
SpeexIETFWide-20.6k
SpeexWB
SpeexWide-20.6k
G.711-uLaw-64k
G.711-ALaw-64k
G.722-64k

2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Could not find capability: "SpeexIETFWide-20.6k"
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Added capability: SpeexIETFWide-20.6k <1>
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Could not find capability: "SpeexWB"
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Could not find capability: "SpeexWide-20.6k"
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Added capability: SpeexWide-20.6k <2>
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Could not find capability: "G.711-uLaw-64k"
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Added capability: G.711-uLaw-64k <3>
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Could not find capability: "G.711-ALaw-64k"
2009/06/28 14:05:53.499  6:11.726 H225 Caller:0xb31f0b90 H323 Added capability: G.711-ALaw-64k <4>
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Could not find capability: "G.722-64k"
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Added capability: G.722-64k <5>
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Could not find capability: "theora"
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Could not find capability: "H.261"
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Added capability: H.261 <6>
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Could not find capability: "H.261-CIF"
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Added capability: H.261-CIF <7>
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Could not find capability: "H.261-QCIF"
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Added capability: H.261-QCIF <8>
2009/06/28 14:05:53.500  6:11.727 H225 Caller:0xb31f0b90 H323 Added capability: UserInput/hookflash <9>
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 H323 Added capability: UserInput/basicString <10>
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 H323 Added capability: UserInput/dtmf <11>
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 H323 Added capability: UserInput/RFC2833 <12>
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 H323 Found capability: UserInput/RFC2833 <12>
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 Call GetOtherPartyConnection Call[y1b92e0d81]-EP<h323>[localhost/8175]
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 H323 SetLocalCapabilities:
 Table:
   SpeexIETFWide-20.6k <1>
   SpeexWide-20.6k <2>
   G.711-uLaw-64k <3>
   G.711-ALaw-64k <4>
   G.722-64k <5>
   H.261 <6>
   H.261-CIF <7>
   H.261-QCIF <8>
   UserInput/hookflash <9>
   UserInput/basicString <10>
   UserInput/dtmf <11>
   UserInput/RFC2833 <12>
 Set:
   0:
     0:
       SpeexIETFWide-20.6k <1>
       SpeexWide-20.6k <2>
       G.711-uLaw-64k <3>
       G.711-ALaw-64k <4>
       G.722-64k <5>
     1:
       H.261 <6>
       H.261-CIF <7>
       H.261-QCIF <8>
     2:
       UserInput/hookflash <9>
     3:
       UserInput/basicString <10>
       UserInput/dtmf <11>
       UserInput/RFC2833 <12>

2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 H225 Check for Fast start by local endpoint
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 H245 Default OnSelectLogicalChannels, FastStartInitiate
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 Call IsMediaBypassPossible Call[y1b92e0d81]-EP<h323>[localhost/8175] session 1
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 OpalMan IsMediaBypassPossible: session 1
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 OpalCon IsMediaBypassPossible: default returns false
2009/06/28 14:05:53.501  6:11.728 H225 Caller:0xb31f0b90 RTP Cannot find RTP session 1
2009/06/28 14:05:53.502  6:11.729 H225 Caller:0xb31f0b90 RTP_UDP Session 1, created with NAT flag set to 0
2009/06/28 14:05:53.502  6:11.729 H225 Caller:0xb31f0b90 RTP_UDP Session 1 created: 140.112.102.80:5062-5063 ssrc=3255873038
2009/06/28 14:05:53.707  6:11.934 H225 Caller:0xb31f0b90 RTP Creating new session RTP_UDP
2009/06/28 14:05:53.707  6:11.934 H225 Caller:0xb31f0b90 Call IsMediaBypassPossible Call[y1b92e0d81]-EP<h323>[localhost/8175] session 1
2009/06/28 14:05:53.707  6:11.934 H225 Caller:0xb31f0b90 OpalMan IsMediaBypassPossible: session 1
2009/06/28 14:05:53.707  6:11.934 H225 Caller:0xb31f0b90 OpalCon IsMediaBypassPossible: default returns false
2009/06/28 14:05:53.707  6:11.934 H225 Caller:0xb31f0b90 RTP Found existing media session 1
2009/06/28 14:05:53.708  6:11.935 H225 Caller:0xb31f0b90 H323RTP Receiver created using session 1
2009/06/28 14:05:53.708  6:11.935 H225 Caller:0xb31f0b90 Call IsMediaBypassPossible Call[y1b92e0d81]-EP<h323>[localhost/8175] session 1

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