Good, let's hope it was a windows problem. In 99.999% of the cases, if : - you hear yourself with a 5 seconds delay using the configuration assistant - you receive the video from the other side - audio channels are shown as started in the general history then it means you are correctly configured and the problem is on the other side. If you don't hear yourself with a 5 seconds delay, then you have an audio config problem. If you do, but do not receive video from the other side, and do not receive audio, it is a NAT problem. And finally, if no audio channels are started, then you have no common codec. That summarizes all possible configuration problems encountered when using GnomeMeeting :) Le sam, 03/07/2004 à 18:57 -0400, George Bell a écrit : > <snip> > > > > Correct too. You should do more tests, possibly with other users to see > > what side is problematic. My guess would really be the Netmeeting side. > > > Yes, that's probably it! A problem with the audio on the windows computer > has been found. This computer has WindowsME installed, and the microphone > on it doesn't function at all. I cannot ascertain what could have caused it > or find a solution to it. I can only guess that addware and spyware that > has plagued this machine and/or viruses have done something to it. So it > looks like the only alternative is to reformat the hardrive and reinstall > windows from scratch. Grrrrrr. > > George > -- _ Damien Sandras (o- GnomeMeeting: http://www.gnomemeeting.org/ //\ FOSDEM : http://www.fosdem.org v_/_ H.323 phone : callto:ils.seconix.com/dsandras seconix com
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=