Re: [GnomeMeeting-list] Codec closes immediately after establishing connection

[Mario Juric <mjuric astro princeton edu>]

Damien Sandras wrote:
> Hi,

Hi and thank you for the quick reply.

> Are you sure you have the exact same problem with gnomemeeting to
> gnomemeeting calls?
>
> That seems weird to me. Can you please mail the debug output (level 3,
> ie gnomemeeting -d 3) on the gnomemeeting side?
> If it doesn't give much information, we can try to have a look at the
> output of the other gnomemeeting. One of them is closing the codec for a
> good reason, we have to determine why.

The level 3 outputs are at:

	http://majuric.org/gm/

The RedHat9 machine causing problems is called 'qonos', the Fedora1 box 
with working gnomemeeting is 'caladan', while the WinXP laptop is 
'vulcan'. qonos<->vulcan connection is through a common physical cable, 
while qonos<->caladan connection is through a VPN.

Three files are:
	gm.qonos-caladan.3.log - log of gnomemeeting on qonos, while talking to 
caladan (Fedora1)
	gm.caladan-qonos.3.log - log of gnomemeeting on caladan, while talking 
to qonos
	gm.qonos-vulcan.3.log - log of gnomemeeting on qonos, while talking to 
vulcan (WinXP)

From qonos' output it seems something becomes wrong with gnomemeeting's 
socket descriptor:

2004/03/22 10:20:00.841	  1:21.943	      LogChanRx:834a280	RTP	Jitter 
buffer created: size=101 delay=160-4000/160 (20ms) obj=0x83454f8
2004/03/22 10:20:00.848	  1:21.950	     RTP Jitter:83454f8	RTP	Jitter 
RTP receive thread started: 0x83454f8
2004/03/22 10:20:00.849	  1:21.951	     RTP Jitter:83454f8	RTP_UDP 
Session 1, Select error: Bad file descriptor
2004/03/22 10:20:00.851	  1:21.952	     RTP Jitter:83454f8	RTP	Jitter 
RTP receive thread ended
2004/03/22 10:20:00.880	  1:21.982	      LogChanRx:834a280	H323RTP 
Receive G.711-uLaw-64k thread ended
2004/03/22 10:20:00.937	  1:22.039	           H245:833e240	H245 
Receiving PDU: response openLogicalChannelAck
2004/03/22 10:20:00.938	  1:22.040	           H245:833e240	H245	Received 
open channel ack: T-101, state=AwaitingEstablishment
2004/03/22 10:20:00.939	  1:22.041	           H245:833e240	H323RTP 
OnReceiveOpenAck
2004/03/22 10:20:00.940	  1:22.042	           H245:833e240	RTP_UDP 
SetRemoteSocketInfo: session=1 control channel, 
new=140.180.162.174:49475, local=140.180.162.204:5006-5007, 
remote=140.180.162.174:49474-49475
2004/03/22 10:20:00.942	  1:22.043	           H245:833e240	RTP_UDP 
SetRemoteSocketInfo: session=1 data channel, new=140.180.162.174:49474, 
local=140.180.162.204:5006-5007, remote=140.180.162.174:49474-49475
2004/03/22 10:20:00.944	  1:22.045	           H245:833e240	H323 
InternalEstablishedConnectionCheck: 
connectionState=EstablishedConnection fastStartState=FastStartDisabled
2004/03/22 10:20:00.946	  1:22.048	      LogChanTx:834a540	H323RTP 
Transmit MS-GSM thread started: rate=320 time=40ms size=1*65=65
2004/03/22 10:20:00.990	  1:22.093	      LogChanTx:834a540	H323RTP 
Transmit start of talk burst: 320
2004/03/22 10:20:00.993	  1:22.095	      LogChanTx:834a540	RTP_UDP 
Session 1, Write error on data port (9): Bad file descriptor
2004/03/22 10:20:00.994	  1:22.096	      LogChanTx:834a540	H245	Closing 
channel: T-101, state=Established
2004/03/22 10:20:00.996	  1:22.098	      LogChanTx:834a540	H245	Sending 
PDU: request closeLogicalChannel
2004/03/22 10:20:00.998	  1:22.099	      LogChanTx:834a540	H323RTP 
Transmit MS-GSM thread ended

This appears both when talking to other gnomemeeting and to netmeeting.

Regards,
--
Mario Juric,
Graduate Student, Astrophysical Sciences, Princeton University
Web   :  http://astro.princeton.edu/~mjuric
Phone :  +1 609 258 7936        PGP: ~mjuric/crypto/public.key