[no subject]

So, I guess that the only thing left to do is try .96.1 as you suggested.  =
Yes?

Also, Damien, I have a question about something you mentioned... When you s=
aid:

> If your router natively supports H.323:
> - disable H.245 Tunneling, disable Fast Start, disable IP Translation,
> do not forward ports, only allow them

What did you mean by do not forward ports, only allow them?  On the cable=
=20
router, I can set the ports to be forwarded to the specific box behind the=
=20
firewall.   But, I'm not sure what you mean by "only allow them".  Isn't th=
at=20
what port forwarding does?  Only allows the ports to be active for a machin=
e=20
behind the firewall?  (I use port forwarding all the time for certain servi=
ces).=20
 So, I may be confusing your terms of "forwarding" and "allowing".

I should be able to try the .96.1 tonight and will report back regarding th=
e=20
codec error from Netmeeting.

Thanks!

Steve



Le mar 11/03/2003 =E0 21:23, Steve Rifkin a =E9crit :
> Damien, Can you stop by and help me set up this thing?  I'll get you a be=
er!=20
;-)
>=20

;-)

> Seriously, I guess I'm confused as to what I'll need to forward, then.  I=
've=20
got=20
> H.245 Tunneling activated at my end.  And it sounds like I need to activa=
te=20
the=20
> 30000-300010 ports.  I'm trying to find some docs (I've looked in the FAQ=
)=20
> regarding what purpose the 30000-series ports are for, but I can't seem t=
o=20
find=20
> that info.
>=20

30000-30010 are used for the H.245 Channel. If you are using the H.245
Tunneling, you don't need them, except for Netmeeting as Netmeeting
doesn't support H.245 Tunneling.

If your router natively supports H.323:
- disable H.245 Tunneling, disable Fast Start, disable IP Translation,
do not forward ports, only allow them

If your router does not support H.323:
- do what you want with H.245 Tunneling and Fast Start, forward all
ports from the FAQ (if they are cited, there is a reason;) ), enable IP
translation

> I will have to find out if my cable router natively supports H.323 (altho=
ugh,=20
I=20
> didn't see that support listed in my router's manual.  If it *is* support=
ed in=20
> the router, I will need to disable H.245 Tunneling, correct?  If it *is n=
ot*=20
> supported, I need to enable H.245, yes?

See above. H.323 support might be cited as "Netmeeting support".

>=20
> In which case, then, should I activate Enable IP translation?  Is that go=
ing=20
to=20
> be only useful for connecting with Netmeeting users?  If IP translation i=
s=20
> disabled, I'm still able to communicate with gnomemeeting users.
>=20

See above. IP translation is needed for both Netmeeting and GnomeMeeting
users.

> All this to chat with Netmeeting.  Any changes I make for access to=20
Netmeeting,=20
> I hope, do not change my ability to talk to gnomemeeting users, as that p=
art=20
is=20
> working (at least only when I initiate the call... but that's for another=
=20
> e-mail.)
>=20

No, both should work.

> Regarding the connection actually working once, Damien mentioned that it=
=20
depends=20
> on how the call was initiated.  When the connection to Netmeeting did wor=
k, I=20
> initiated the call the same way as when it didn't.  I called up the addre=
ss to=20
> the remote machine on gnomemeeting and clicked the Call button.
>=20
> Nothing (obvious) changed between the time it worked and the rest of the =
time=20
> that it did not.=20
>=20

It depends how channels are initiated. You can initiate outgoing
channels even if the call comes in.

> Thanks!  Steve
>=20
>=20
> Damien wrote:
>=20
> Of course you need to. And forwarding is not enough. And if your router
> supports H.323, then forwarding is bad ;)
> =20
> > Yes, I had gone through the FAQ and the list of ports. I'm using a hard=
ware=20
> > cable router/firewall for the linux box (gnomemeeting) and the 1720 and=
 =20
> > 5000-5003 ports have been forwarded.  Not sure if I need to do the=20
30000-30010=20
> > ports.=20
> >=20
>=20
> > Remember, it *did* actually work once.  So, if the cable router wasn't=
=20
> > configured correctly, it shouldn't have worked at all?
>=20
> It depends how the call is initiated.
>=20
>=20
> Steve wrote:
>=20
> >=20
> > Remember, it *did* actually work once.  So, if the cable router wasn't=
=20
> > configured correctly, it shouldn't have worked at all?
> >=20
> > Yes, I had gone through the FAQ and the list of ports. I'm using a hard=
ware=20
> > cable router/firewall for the linux box (gnomemeeting) and the 1720 and=
 =20
> > 5000-5003 ports have been forwarded.  Not sure if I need to do the=20
30000-30010=20
> > ports.=20
> >=20
> > I've been having no problems in connecting to gnomemeeting machines.  A=
nd=20
> again,=20
> > the Netmeeting machine I was able to successfully connect to once, but =
then=20
> > never again (and without changes at my end or the remote end.)
> >=20
> > I will try .96.1 and see if that works better.  I'll let you know!  Tha=
nks=20
> much!
> >=20
> > Steve
> >=20
> >=20
> > Damien wrote:
> >=20
> > Ah, that can be a source of problem. Have you read the FAQ and are you
> > sure and certain that things are correctly configured ?
> >=20
> > =20
> > > The win2k machines have both been set for LAN network connections.
> > >=20
> > > The gnomemeeting machine is behind a cable router (with firewall), bu=
t I'm
> > > able to connect with gnomemeeting users when I initiate a call.
> > =20
> >=20
> >=20
> > >=20
> > > > Date: Tue, 11 Mar 2003 13:25:50 -0500 (EST)
> > > > From: Steve Rifkin <steve410 cs jhu edu>
> > > =20
> > > > (Damien, this is an update to what I sent via bugzilla, but, since =
it=20
has=20
> > been=20
> > > > determined it is not an actual bug, I'm writing here, as it's still=
 a=20
> > problem=20
> > > on=20
> > > > my end.)
> > > >=20
> > > > I'm running gnomemeeting .96.0 on RH 8 (Gnome environment) with Qui=
ckCam=20
> > > Express=20
> > > > webcam.
> > > >=20
> > > > I have  had several successful calls to other Gnomemeeting users.
> > > >=20
> > > > When attempting to connect to a user who is using Netmeeting 3.01=
=20
(Windows
> > > > 2000), I receive the following error about the remote site's attemp=
t to
> > > > answer my call:
> > > >=20
> > > > "could not find common codec with remote party"
> > > >=20
> > > > It was suggested that I install the MS-GSM from the gnomemeeting.or=
g=20
site=20
> > onto=20
> > > > the Win2K netmeeting box.
> > > >=20
> > > > Actually, what is on the gnomemeeting.org site (that I could find) =
was=20
the=20
> > GSM=20
> > > > codec... it didn't explicitly say MS-GSM.  But, I found it under th=
e=20
> > > > Netmeeting/GSM packages, so I figure it's the correct one.
> > > >=20
> > > > I installed it on the Win2k machine (with netmeeting shut off).  I =
then=20
> > > brought=20
> > > > netmeeting back up, and it did show the gsm codec now active.
> > > >=20
> > > > At the gnomemeeting box, I called the netmeeting remote site... it =
could=20
> > > answer=20
> > > > this time!  Success!  Well, not really.  The connection dropped aft=
er=20
> about=20
> > 2=20
> > > > minutes.  When I tried to connect again, I once again got the "coul=
d not=20
> > find=20
> > > > common codec with remote party" error.  But, I confirmed that the g=
sm=20
> codec=20
> > > was=20
> > > > still on the win2k netmeeting.
> > > >=20
> > > > I restarted netmeeting.  And I confirmed the gsm codec was still=20
> configured=20
> > > into=20
> > > > netmeeting.  Then, I restarted gnomemeeting (on the linux box), and=
=20
still,=20
> > > when=20
> > > > I connect to the win2k box, I get the same error as above.
> > > >=20
> > > > So, it worked once... but that's all.
> > > >=20
> > > > I set up another Win2k box to use the gsm codec.  It never answered=
 the=20
> > > > gnomemeeting calls at all without producing the error.
> > > >=20
> > > > Any ideas?
> > > >=20
> > > > The win2k machines have both been set for LAN network connections.
> > > >=20
> > > > The gnomemeeting machine is behind a cable router (with firewall), =
but=20
I'm=20
> > > able=20
> > > > to connect with gnomemeeting users when I initiate a call.
> > > >=20
> > > > I have video and audio on at the time of the connection attempts.
> > > > I've also had video turned off at the time of the connection attemp=
ts to
> > > > see if that made a difference.  Same error when the connection is
> > > > attempted.
> > > >=20
> > > > I have not tried connection with audio turned off.  I will have to =
do=20
that
> > > > the next time I can check.
> > > >=20
> > > > Thanks!
> > > >=20
> > > > Steve
> > > >=20
>=20