|
»
»
« Return to Thread: question of using Ekiga to KEK (fwd)
Re: question of using Ekiga to KEK (fwd)
by physjg
::
Rate this Message:
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 42009/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
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 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
« Return to Thread: question of using Ekiga to KEK (fwd)
| Free embeddable forum powered by Nabble | Forum Help |
