Re: [GnomeMeeting-list] A handshake problem?

[Damien Sandras <dsandras seconix com>]

On Sat, Jan 05, 2002 at 07:25:04PM -0700, Chris Worley wrote:
> Clueless user is stuck... hopefully someone can bail him out... 
> 
> I've been using gnomemeeting successfully for a long time.  I recently
> upgraded to SuSE 7.3 (both machines I'm trying to connect), and can't
> get gnomemeeting working again.  SuSE ships with gnomemeeting 0.10, but
> I upgraded to 0.12.2 (both machines) when SuSE's version didn't work;
> but, that exhibits the same problem.  
> 
> Both machines are on a LAN, w/no firewall in-between, although one of
> the machines (...1) is a firewall/gateway to the Internet; but it's not
> getting in the way (I've checked -- no packets are being dropped by the
> firewall on the lan side). 
> 
> It looks like the gnomemeeting machine having problems (...254) is
> hanging during the initial connection handshake, when they're supposed
> to negotiate the protocols.  This machine has a working video card (the
> ...1 machine doesn't -- it has an Iomega Buz which has never worked with
> gnomemeeting [another story entirely]) and "video preview" shows that
> it's getting the video data.  It's a very slow machine -- a 150Mhz
> Pentium w/ 40MB RAM.  Maybe I should refer to it as "swap city" rather
> than "...254" ;)  
> 
> ...254 is using an ALS4000 sound card, ...1 is using an AWE64 SB (I'm
> not sure if gnomemeeting on either is sensing audio correctly,
> especially in version 0.12.2).  Both machines are using oss drivers,
> which SuSE auto installed (and they seem to work for other
> applications). I used to use the Forefront oss drivers (but, SuSE's
> installation was so good at figuring out the right drivers, so I didn't
> bother installing Forefront).  Both machines are running KDE (meaning
> sound goes through artsd), but most of GNOME is installed on both. 
> Sound seemed fine (I had no reason to think it was the problem) in
> version 0.10, but 0.12.2 didn't have the audio devices preset in the
> "settings" window (and I don't know what to put in for "recording" dsp
> and mixer, so I just repeated /dev/dsp and /dev/mixer for the recording
> devices).  Also, with "video preview" turned on, I'd think I'd hear the
> video's audio too, but I don't. 
> 
> Both machines were tested with the same versions of gnomemeeting. 
> 
> In version 0.10, ...1, after connecting, shows remote user info; while
> ...254 doesn't... it stays in the "calling" state.  Here's ...1's
> output: 
> 
> 17:17:14 :  Reinitialize the capabilities 
> 17:17:14 :  Added MS-GSM capability 
> 17:17:14 :  Added G.711-uLaw capability 
> 17:17:14 :  Added G.711-ALaw capability 
> 17:17:14 :  Added GSM-06.10 capability 
> 17:17:14 :  Added LPC10 capability 
> 17:17:14 :  Added H.261 QCIF capability 
> 17:17:14 :  Added H.261 CIF capability 
> 17:17:14 :  Listener started 
> 17:21:17 :  Call from : Jon Worley [192.168.0.254] 
> 17:21:35 :  Answering incoming call 
> 17:21:37 :  Started New Logical Channel... 
> 17:21:37 :  Sending MS-GSM{sw} 
> 17:21:37 :  Fast start disabled 
> 17:21:37 :  H245 Tunnelling disabled 
> 17:21:37 :  Connected with Jon Worley [192.168.0.254] using gnomemeeting
> 0.10.1 9:0:61 
> 
> ...254 shows that it connected but doesn't show the "user info" or the
> agreed protocols.  It still says "calling...". 
> 
> Hit disconnect on ...1, it's okay: 
> 
> 17:24:58 :  Stopping current call 
> 17:24:59 :  Call completed 
> 
> but .254's gnomemeeting seems hung trying to disconnect.  Try to
> reconnect from ...1 (while ...254 is still trying to disconnect), it
> quickly deconnects: 
> 
> 18:08:21 :  Call 2: calling 192.168.0.254 
> 18:08:21 :  Call completed 
> 
> And, ...254 is still hung in a disconnecting state,  If I kill
> gnomemeeting, it's hard to restart... the port being left open (v0.12.2
> seems to handle this "restart after hard kill" situation better). 
> 
> Version 0.12.2 only differs in that ...254, during connection, starts
> it's timer ticking as if it's connected, but it still acts like it
> didn't get thru the initial handshake. 
> 
> The output on ...1 for version 0.12.2 looks like: 
> 
> Incoming Call 
> 18:56:26 :  Started New Logical Channel... 
> 18:56:26 :  Sending G.711-uLaw-64k{sw} 
> 18:56:26 :  Enabled silence detection for G.711-uLaw-64k{sw} 
> 18:56:26 :  Fast start disabled 
> 18:56:26 :  H.245 Tunnelling disabled 
> 18:56:26 :  Connected with Jon Worley [192.168.0.254] using gnomemeeting
> 0.12.2 9:0:61 
> 
> While ...254 still says "calling..." (even though it's connection timer
> has started). 
> 
> I've mucked with all the settings: "auto answer", "H.245 tunnelling",
> "Fast Start" on and off, and different port and codec settings.  I've
> started the call from both sides, with no difference in operation. 
> 
> All I can think is that this is related to the slow speed of the ...254
> machine. 
> 
> Any ideas? 


I can see 2 possible problems :
* artsd is blocking the soundcard (I don't think so)
* you encountered the PWLib bug (I think it is the problem)

You said that there were no detected devices for sound in GnomeMeeting.
Is that right ?
No sound devices are usable. It comes from a bug in PWLib that doesn't
detect the soundcards correctly on some configurations. I mailed
Equivalence about that 2 weeks ago, but they are still on holiday.

You have 2 solutions : wait for the next release or recompile with my 
little patch...

Hope it helps,

> 
> Thanks, 
> 
> Chris 
> 
> 
> _______________________________________________
> Gnomemeeting-list mailing list
> Gnomemeeting-list gnome org
> http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
> 

-- 
 _	Damien Sandras
(o-	GnomeMeeting - H.323 Video-Conferencing application -
//\		web:  http://www.gnomemeeting.org/
v_/_	FOSDEM 2002  - Free Software and Open Source Developers Meeting -
		web:  http://www.fosdem.org/