There is a problem here, you don't have any rules for the RTP port range. Without that, most calls with fails with no audio and no video being transmitted. I suggest you continue investigating because it hides another problem. The remote user is busy problem could come from the H.245 port range not being forwarded. Le ven, 14/05/2004 à 14:46 -0600, Doug Beattie a écrit : > Thanks to all. I went onto IRC and received help there. > > I don't know why, but I didn't require all the iptable rules from FAQ > 7.1.3 to get things working. > > Should anyone need to know what to use on a debian stable 2.4.18-bf2.4 > kernel I only used: > -------------------------------------------------------------------------- > #!/bin/bash > # where the iptables binary resides (see "type -p iptables") > IPTABLES=/sbin/iptables > # > # = your public Internet-Device > OUT_DEV=eth0 > # > # = your internal Internet-Device > IN_DEV=eth1 > # > # = Host to which the incoming H323 is being forwarded > IN_HOST=192.168.<octet3>.<octet4> # put in your last 2 octets here > # > #TCP_LISTENING_PORT - H.323 port > # H323 Port > TCP_LISTENING_PORT=1720 > # > #TCP_PORT_RANGE - H245, if no tunneling is made > TCP_PORT_RANGE=30000:30010 > # > $IPTABLES -t nat -I PREROUTING 1 -i $OUT_DEV -p tcp --dport > $TCP_LISTENING_PORT -j DNAT --to-dest $IN_HOST > $IPTABLES -I FORWARD 1 -p tcp -i $OUT_DEV --dport $TCP_LISTENING_PORT -d > $IN_HOST -j ACCEPT > # > # activate masquerading on public interface > $IPTABLES -t nat -A POSTROUTING -o $OUT_DEV -j MASQUERADE > # > $IPTABLES -t nat -I PREROUTING 1 -i $OUT_DEV -p tcp --dport > $TCP_PORT_RANGE -j DNAT --to-dest $IN_HOST > $IPTABLES -I FORWARD 1 -p tcp -i $OUT_DEV --dport $TCP_PORT_RANGE -d > $IN_HOST -j ACCEPT > # > -------------------------------------------------------------------------- > On Fri, May 14, 2004 at 09:43:05AM -0600, Doug Beattie wrote: > > Damien: > > > > Re: > > On Fri, May 14, 2004 at 05:34:45PM +0200, Damien Sandras wrote: > > > Are you sure that the status of that user is different from "Do Not > > > Disturb"? > > > > He has clicked on the "Call" button and under it the "Available" option > > is clicked as enabled. > > > > Another of his friends can call him without any problems. > > > > > > > > If that user has placed his GM in "Do not disturb", all calls are > > > automatically rejected. The same happens when you call users who are > > > already in a call. > > > > > > > Where else should I/he check to make sure the problems is not on the > > other end? > > > > Is there something I can look for with ethereal to see if packets are > > getting out and returned as a busy? > > > > Thanks for your reply. I look forward to hearing back again. > > > > Doug > > > > > > > > Le ven, 14/05/2004 ? 09:31 -0600, Doug Beattie a ?crit : > > > > Hello. I am new to this list and Gnomemeeting so I apologize if this > > > > question has been answered before. I have read through the FAQ and > > > > did not find an answer to my problem. > > > > > > > > I have GnomeMeeting 1.0.1 (from the new SuSE 9.1 release) and am able > > > > to have a friend of mine connect to me without problem. I can talk, > > > > post messages, and even transmit video to him. > > > > > > > > The problem I am having is that every time I try to connect to my > > > > friend, or anyone from the ils.seconix.com list, I get a "Remote user is > > > > busy" message as soon as I execute the call to the person. > > > > > > > > I searched "The mail.gnome.org Archives" for the term "busy" without > > > > finding any results. > > > > > > > > The system running GnomeMeeting sits behind a debian gateway/router on a > > > > 192.168.x.x subnet. The debian gateway/router system is connected with > > > > a static IP directly to the internet via a DSL modem. > > > > > > > > I set up the following rules for iptables on the debian system: > > > > (Based on the date from the FAQ sections 7.1.2 and 7.1.3. "What > > > > iptables rules could I use for GNU/Linux?") > > > > ------------------------------------------------------------------------------ > > > > #!/bin/bash > > > > # > > > > # Set up general H.323 port for TCP > > > > iptables -t nat -I PREROUTING -p tcp --dport 1720 -j DNAT --to > > > > 192.168.13.13:1720 > > > > iptables -I FORWARD -p tcp -d 192.168.13.13 --dport 1720 -j ACCEPT > > > > iptables -I FORWARD -p tcp -s 192.168.13.13 --sport 1720 -j ACCEPT > > > > # > > > > # Set up H.245 TCP port range 30000:30010 > > > > iptables -t nat -I PREROUTING -p tcp --dport 30000:30010 -j DNAT --to > > > > 192.168.13.13:30000:30010 > > > > iptables -I FORWARD -p tcp -d 192.168.13.13 --dport 30000:30010 -j > > > > ACCEPT > > > > iptables -I FORWARD -p tcp -s 192.168.13.13 --sport 30000:30010 -j > > > > ACCEPT > > > > # > > > > # > > > > # Set up RTP port range 5000:5007 (2 audio, 2 video - RTP and RTCP) > > > > iptables -t nat -I PREROUTING -p tcp --dport 5000:5007 -j DNAT --to > > > > 192.168.13.13:5000:5007 > > > > iptables -I FORWARD -p tcp -d 192.168.13.13 --dport 5000:5007 -j ACCEPT > > > > iptables -I FORWARD -p tcp -s 192.168.13.13 --sport 5000:5007 -j ACCEPT > > > > # > > > > # > > > > # Set up Gate Keeper port range 5010:5013 > > > > iptables -t nat -I PREROUTING -p tcp --dport 5010:5013 -j DNAT --to > > > > 192.168.13.13:5010:5013 > > > > iptables -I FORWARD -p tcp -d 192.168.13.13 --dport 5010:5013 -j ACCEPT > > > > iptables -I FORWARD -p tcp -s 192.168.13.13 --sport 5010:5013 -j ACCEPT > > > > # > > > > # > > > > # Set up SIP port range 5060:5080 > > > > iptables -t nat -I PREROUTING -p tcp --dport 5060:5080 -j DNAT --to > > > > 192.168.13.13:5060:5080 > > > > iptables -I FORWARD -p tcp -d 192.168.13.13 --dport 5060:5080 -j ACCEPT > > > > iptables -I FORWARD -p tcp -s 192.168.13.13 --sport 5060:5080 -j ACCEPT > > > > # > > > > ------------------------------------------------------------------------------ > > > > > > > > Does anyone know why I would be getting the "Remote user is busy" > > > > condition when the remote use is known to be available? > > > > > > > > Thanks for any help you may offer me. > > > > > > > > Doug > > > > -- > > > > _______________________________________________ > > > > GnomeMeeting-list mailing list > > > > GnomeMeeting-list gnome org > > > > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list > > > > > > > > > _______________________________________________ > > > GnomeMeeting-list mailing list > > > GnomeMeeting-list gnome org > > > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list > > > > > > -- > > _______________________________________________ > > GnomeMeeting-list mailing list > > GnomeMeeting-list gnome org > > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list > > -- > _______________________________________________ > GnomeMeeting-list mailing list > GnomeMeeting-list gnome org > http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=