Re: [GnomeMeeting-list] Setup question
- From: Rainer Dorsch <rdorsch web de>
- To: GnomeMeeting mailing list <gnomemeeting-list gnome org>
- Subject: Re: [GnomeMeeting-list] Setup question
- Date: Thu, 24 Feb 2005 22:32:13 +0100
Hi Damien,
Am Donnerstag, 24. Februar 2005 21:27 schrieb Damien Sandras:
> > Call forwarding is still not working but the debug output looks more
> > promising. It contains:
> >
> > 2005/02/24 21:07:12.510 3:05:57.063 H225 Answer:88270c0 H323
> > Party name "h323:118 145 140 124 118 152 191 172" mapped to
> > "118 145 140 124 ip$118 152 191 172:1720
> >
> > which looks like gnomemeeting is trying to forward the call which it
> > received via the gateway to the gateway (118.152.191.172), instead of may
> > laptop (118.145.140.124).
> >
> > Is that a bug or did I setup it incorrectly?
>
> That's not a bug but a feature. You have configured GnomeMeeting to go
> through a gateway, so all calls are going through the gateway, including
> those that are forwarded. If you do not want taht, then disable the
> gateway setting when you forward calls.
>
> The gateway is just a way not to have to type it in the url. So doing
> h323:5001 gateway_ip or configuring the gateway to gateway_ip and
> calling h323:5001 is just the same.
>
Ok, that sounds good. Switching forwarding off, does not work either. Maybe I
did configure the forward host incorrectly:
rdorsch paddy:~$ gconftool-2
--get /apps/gnomemeeting/protocols/h323/call_forwarding/forward_host
118.145.140.124
rdorsch paddy:~$
What I get is
2005/02/24 22:21:19.299 4:20:03.852 H225 Answer:8886c48 H225
Sending call proceeding PDU
2005/02/24 22:21:19.300 4:20:03.853 H225 Answer:8886c48 H225
Sending PDU: callProceeding
2005/02/24 22:21:19.308 4:20:03.861 H225 Answer:8886c48 H225
Sending PDU: facility
2005/02/24 22:21:19.310 4:20:03.863 H225 Answer:8886c48 H323
Clearing connection ip$[::ffff:9.152.191.172]:2675/159 reason=EndedByNoAccept
2005/02/24 22:21:19.310 4:20:03.863 H225 Answer:8886c48 H323 Call
end reason for ip$[::ffff:9.152.191.172]:2675/159 set to EndedByNoAccept
When I do 5001 118 145 140 124, I get
005/02/24 22:19:07.707 4:17:52.260 H225 Answer:87d2f40 H245
Stopping MasterSlaveDetermination: state=Idle
2005/02/24 22:19:07.708 4:17:52.261 H225 Answer:87d2f40 H245
Stopping TerminalCapabilitySet: state=Idle
2005/02/24 22:19:07.708 4:17:52.261 H225 Answer:87d2f40 H225 Set
remote application name: "Cisco IOS 12.x 181/18"
2005/02/24 22:19:07.708 4:17:52.261 H225 Answer:87d2f40 H225 Set
protocol version to 2 and implying H.245 version 3
2005/02/24 22:19:07.709 4:17:52.262 H225 Answer:87d2f40 H225
Sending call proceeding PDU
2005/02/24 22:19:07.710 4:17:52.263 H225 Answer:87d2f40 H225
Sending PDU: callProceeding
2005/02/24 22:19:07.906 4:17:52.459 H225 Answer:87d2f40 H323 Party
name "h323:5001 118 145 140 124" mapped to "5001 ip$118 145 140 124:1720
2005/02/24 22:19:07.908 4:17:52.461 H225 Answer:87d2f40 H225
Sending PDU: facility
2005/02/24 22:19:07.908 4:17:52.461 H225 Answer:87d2f40 H323
Clearing connection ip$[::ffff:118.152.191.172]:2655/157
reason=EndedByNoAccept
Nothing arrives at the debug output of the gnomemeeting running on the laptop.
Do I need to setup a gatekeeper or can I forward directly to the gnomemeeting
on the laptop?
Thanks,
Rainer
--
Rainer Dorsch
Alzentalstr. 28
D-71083 Herrenberg
07032-919495
Icq: 32550367
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]