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 21:13:56 +0100
Hi Kilian,
I installed the new gnomemeeting version 1.2.0+1.2.1cvs20050220-1 from sid.
I setup call forwarding
rdorsch paddy:~$ gconftool-2
--get /apps/gnomemeeting/protocols/h323/call_forwar
ding/forward_host
118.145.140.124
rdorsch paddy:~$ gconftool-2
--get /apps/gnomemeeting/protocols/h323/call_forwar
ding/always_forward
true
rdorsch paddy:~$
and a gateway is in use:
rdorsch paddy:~$
cat .gconf/apps/gnomemeeting/protocols/h323/gateway/%gconf.xml
<?xml version="1.0"?>
<gconf>
<entry name="use_gateway" mtime="1109275384" type="bool" value="true">
</entry>
<entry name="host" mtime="1102685717" type="string">
<stringvalue>118.152.191.172</stringvalue>
</entry>
</gconf>
rdorsch paddy:~$
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?
Here is the full debug output of an incoming call:
2005/02/24 21:07:12.464 3:05:57.017 H323 Listener:83340e8 H323TCP
Started connection: host=::ffff:118.152.191.172:2064,
if=118.152.251.114:1720, handle=45
2005/02/24 21:07:12.465 3:05:57.018 H225 Answer:88270c0 H225
Started incoming call thread
2005/02/24 21:07:12.465 3:05:57.018 H225 Answer:88270c0 H225
Awaiting first PDU
2005/02/24 21:07:12.472 3:05:57.025 H225 Answer:88270c0 H225
Receiving PDU: setup
2005/02/24 21:07:12.472 3:05:57.025 H225 Answer:88270c0 H225
Incoming call, first PDU: callReference=155
2005/02/24 21:07:12.473 3:05:57.026 H225 Answer:88270c0 H323 Added
capability: iLBC-13k3{sw} <1>
2005/02/24 21:07:12.473 3:05:57.026 H225 Answer:88270c0 H323 Added
capability: MS-GSM{sw} <2>
2005/02/24 21:07:12.473 3:05:57.026 H225 Answer:88270c0 H323 Added
capability: SpeexNarrow-15k{sw} <3>
2005/02/24 21:07:12.474 3:05:57.027 H225 Answer:88270c0 H323 Added
capability: iLBC-15k2{sw} <4>
2005/02/24 21:07:12.474 3:05:57.027 H225 Answer:88270c0 H323 Added
capability: GSM-06.10{sw} <5>
2005/02/24 21:07:12.474 3:05:57.027 H225 Answer:88270c0 H323 Added
capability: SpeexNarrow-8k{sw} <6>
2005/02/24 21:07:12.475 3:05:57.028 H225 Answer:88270c0 H323 Added
capability: G.726-32k{sw} <7>
2005/02/24 21:07:12.475 3:05:57.028 H225 Answer:88270c0 H323 Added
capability: G.711-uLaw-64k <8>
2005/02/24 21:07:12.475 3:05:57.028 H225 Answer:88270c0 H323 Added
capability: G.711-ALaw-64k <9>
2005/02/24 21:07:12.476 3:05:57.029 H225 Answer:88270c0 H323 Added
capability: H.261-QCIF <10>
2005/02/24 21:07:12.476 3:05:57.029 H225 Answer:88270c0 H323 Added
capability: H.261-CIF <11>
2005/02/24 21:07:12.476 3:05:57.029 H225 Answer:88270c0 H323 Added
capability: UserInput/hookflash <12>
2005/02/24 21:07:12.477 3:05:57.030 H225 Answer:88270c0 H323 Added
capability: UserInput/basicString <13>
2005/02/24 21:07:12.477 3:05:57.030 H225 Answer:88270c0 H323 Added
capability: UserInput/dtmf <14>
2005/02/24 21:07:12.477 3:05:57.030 H225 Answer:88270c0 H323 Added
capability: UserInput/RFC2833 <15>
2005/02/24 21:07:12.478 3:05:57.031 H225 Answer:88270c0 H323 Found
capability: iLBC-13k3{sw} <1>
2005/02/24 21:07:12.478 3:05:57.031 H225 Answer:88270c0 H323 Found
capability: MS-GSM{sw} <2>
2005/02/24 21:07:12.478 3:05:57.031 H225 Answer:88270c0 H323 Found
capability: SpeexNarrow-15k{sw} <3>
2005/02/24 21:07:12.479 3:05:57.032 H225 Answer:88270c0 H323 Found
capability: iLBC-15k2{sw} <4>
2005/02/24 21:07:12.479 3:05:57.032 H225 Answer:88270c0 H323 Found
capability: GSM-06.10{sw} <5>
2005/02/24 21:07:12.479 3:05:57.032 H225 Answer:88270c0 H323 Found
capability: SpeexNarrow-8k{sw} <6>
2005/02/24 21:07:12.480 3:05:57.033 H225 Answer:88270c0 H323 Found
capability: G.726-32k{sw} <7>
2005/02/24 21:07:12.480 3:05:57.033 H225 Answer:88270c0 H323 Found
capability: G.711-uLaw-64k <8>
2005/02/24 21:07:12.480 3:05:57.034 H225 Answer:88270c0 H323 Found
capability: G.711-ALaw-64k <9>
2005/02/24 21:07:12.481 3:05:57.034 H225 Answer:88270c0 H323 Found
capability: H.261-QCIF <10>
2005/02/24 21:07:12.481 3:05:57.034 H225 Answer:88270c0 H323 Found
capability: H.261-CIF <11>
2005/02/24 21:07:12.481 3:05:57.034 H225 Answer:88270c0 H323 Found
capability: UserInput/hookflash <12>
2005/02/24 21:07:12.482 3:05:57.035 H225 Answer:88270c0 H323 Found
capability: UserInput/basicString <13>
2005/02/24 21:07:12.482 3:05:57.035 H225 Answer:88270c0 H323 Found
capability: UserInput/dtmf <14>
2005/02/24 21:07:12.482 3:05:57.036 H225 Answer:88270c0 H323 Found
capability: UserInput/RFC2833 <15>
2005/02/24 21:07:12.483 3:05:57.036 H225 Answer:88270c0 RFC2833
Handler created
2005/02/24 21:07:12.483 3:05:57.036 H225 Answer:88270c0 H323
Created new connection: ip$[::ffff:118.152.191.172]:2064/155
2005/02/24 21:07:12.484 3:05:57.037 H225 Answer:88270c0 H225
Handling PDU: Setup callRef=155
2005/02/24 21:07:12.484 3:05:57.037 H225 Answer:88270c0 H245
Stopping MasterSlaveDetermination: state=Idle
2005/02/24 21:07:12.484 3:05:57.037 H225 Answer:88270c0 H245
Stopping TerminalCapabilitySet: state=Idle
2005/02/24 21:07:12.485 3:05:57.038 H225 Answer:88270c0 H225 Set
remote application name: "Cisco IOS 12.x 181/18"
2005/02/24 21:07:12.485 3:05:57.038 H225 Answer:88270c0 H225 Set
protocol version to 2 and implying H.245 version 3
2005/02/24 21:07:12.486 3:05:57.039 H225 Answer:88270c0 H225
Sending call proceeding PDU
2005/02/24 21:07:12.487 3:05:57.040 H225 Answer:88270c0 H225
Sending PDU: callProceeding
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
2005/02/24 21:07:12.512 3:05:57.065 H225 Answer:88270c0 H225
Sending PDU: facility
2005/02/24 21:07:12.512 3:05:57.066 H225 Answer:88270c0 H323
Clearing connection ip$[::ffff:118.152.191.172]:2064/155
reason=EndedByNoAccept
2005/02/24 21:07:12.513 3:05:57.066 H225 Answer:88270c0 H323 Call
end reason for ip$[::ffff:118.152.191.172]:2064/155 set to EndedByNoAccept
2005/02/24 21:07:12.513 3:05:57.067 H225 Answer:88270c0 H225
Sending release complete PDU: callRef=155
2005/02/24 21:07:12.515 3:05:57.068 H225 Answer:88270c0 H225
Sending PDU: releaseComplete
2005/02/24 21:07:12.515 3:05:57.068 H323 Cleaner H323
Cleaning up connections
2005/02/24 21:07:12.516 3:05:57.069 H225 Answer:88270c0 H225
Application not accepting calls
2005/02/24 21:07:12.516 3:05:57.069 H225 Answer:88270c0 H323
Clearing connection ip$[::ffff:118.152.191.172]:2064/155
reason=EndedByTransportFail
2005/02/24 21:07:12.516 3:05:57.070 H225 Answer:88270c0 H225 Signal
channel stopped on first PDU.
2005/02/24 21:07:12.517 3:05:57.070 H323 Cleaner H323
Connection ip$[::ffff:118.152.191.172]:2064/155 closing:
connectionState=NoConnectionActive
2005/02/24 21:07:12.518 3:05:57.071 H323 Cleaner H245
Stopping MasterSlaveDetermination: state=Idle
2005/02/24 21:07:12.518 3:05:57.071 H323 Cleaner H245
Stopping TerminalCapabilitySet: state=Idle
2005/02/24 21:07:12.518 3:05:57.071 H323 Cleaner H323
H323Transport::Close
2005/02/24 21:07:12.519 3:05:57.072 H323 Cleaner H323
H323Transport::CleanUpOnTermination for H225 Answer:88270c0
2005/02/24 21:07:12.519 3:05:57.072 H323 Cleaner H323
Connection ip$[::ffff:118.152.191.172]:2064/155 terminated.
2005/02/24 21:07:12.564 3:05:57.117 H323 Cleaner H323
Connection ip$[::ffff:118.152.191.172]:2064/155 deleted.
2005/02/24 21:07:12.564 3:05:57.118 H323 Cleaner H323
Cleaning up connections
Thanks,
Rainer
Am Sonntag, 13. Februar 2005 03:27 schrieb Kilian Krause:
> Hi Rainer,
>
> > Hmm...but being called over IPv6 is not a problem at all. The problem
> > comes up, when I am trying to forward these calls. Does that still make
> > sense for you?
>
> as long as IPv4 notation-compatibility notation in IPv6 is used, there
> will be problems. Thus if your forwarding is to an ipv4 host, yes.
>
> > > The GnomeMeeting 1.2.1 with fixed OpenH323 will be ready for GNOME 2.10
> > > so this should happen rather soon (before end of Feb).
> >
> > I am confused about the openh323. On www.openh323.org I find the latest
> > version is 1.12.2
> >
> > On the Debian server I see versions 1.13.2, 1.14.2, and 1.15.2
> >
> > What version I should watch out for?
>
> For now it's tagged pwlib 1.8.4 and openh323 1.15.3. Yet that IPv6 bug
> isn't fixed so far and still needs to be adressed. If you seriously need
> this to work or would like to test the cutting edge GnomeMeeting CVS, i
> can hand you cvs snapshot debs. Maybe i'll also find some time these
> days to get the autobuilder script back online.
--
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]