Le vendredi 25 f�vrier 2005 � 21:32 +0100, Rainer Dorsch a �crit : > > Is that dumped into a file? I am enabling the forwarding with gconftool-2 via > a shell console. >
Unfortunately not... Can't you do a ssh -X to export the display and see in real time what's happening? My guess is that the call forwarding is not activated for some obscure reason. (It could even be a bug). > > > > What happens in the GUI when you activate call forwarding, isn't there > > an error message? > > I did not watch the GUI while enabling since I did that from remote. I did > not > see a popup error box, when I returned to the workstation, running the > gnomemeeting forwarding the call. > > When starting up gnomemeeting 1.2.1 I sometimes see > > [assert] error: 111 (Connection refused) > [assert] where: "socket.c", "sw_socket_tcp_connect", line: 720 > > This is with forwarding disabled and happens only sometimes. > That's a warning from libhowl, it can be safely ignored. The ideal is to check the general history, I will try call forwarding again tonight at home to make sure it is not broken. Perhaps another GM 1.2 user can try too and report back? > Thanks, > Rainer > -- _ Damien Sandras (o- GnomeMeeting: http://www.gnomemeeting.org/ //\ FOSDEM 2005 : http://www.fosdem.org v_/_ H.323 phone : callto:ils.seconix.com/[EMAIL PROTECTED] _______________________________________________ GnomeMeeting-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnomemeeting-list
