Are you sure that the status of that user is different from "Do Not Disturb"? 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. 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
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=