Re: [GnomeMeeting-list] Codec closes immediately after establishing connection
- From: Mario Juric <mjuric astro princeton edu>
- To: gnomemeeting-list gnome org
- Subject: Re: [GnomeMeeting-list] Codec closes immediately after establishing connection
- Date: Mon, 22 Mar 2004 14:45:13 -0500
Damien Sandras wrote:
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
This seems there is nothing that can be done about it. It is a local
problem. Are you using some kind of firewall?
No, but thanks for the suggestion because that got me thinking. Maybe
there was something that was blocking the required ports. And when I
checked, sure enough, gnomemeeting tries to use the same ports as does
OpenVPN:
2004/03/22 14:34:26.968 6:10.741 H225 Answer:8341f18 RTP_UDP
SetRemoteSocketInfo: session=1 data channel, new=128.112.24.88:5002,
local=140.180.162.204:5000-5001, remote=128.112.24.88:5002-5003
OpenVPN uses port 5000 as default, and port above 5000 for each client
connection. I shut down OpenVPN and the connection went through smoothly.
Is it possible to instruct GM to use other ports (preferrably, high
above in the 5-digits range)? I have a fairly extensive OpenVPN
installation, and the port numbers are hardcoded in every user's config
file (which would have to be changed manually). I see Netmeeting uses
ports in ~49000 range for the h323 connection. Is there a way to make
gnomemeeting use similar ports (it's not a problem for me to recompile
it, if that's what it takes).
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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]