[GnomeMeeting-list] Re: Problems connecting to Netmeeting machines from gnomemeeting

[Steve Rifkin <steve410 cs jhu edu>]

Damien, Can you stop by and help me set up this thing?  I'll get you a beer! ;-)

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

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

In which case, then, should I activate Enable IP translation?  Is that going to 
be only useful for connecting with Netmeeting users?  If IP translation is 
disabled, I'm still able to communicate with gnomemeeting users.

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

Regarding the connection actually working once, Damien mentioned that it depends 
on how the call was initiated.  When the connection to Netmeeting did work, I 
initiated the call the same way as when it didn't.  I called up the address to 
the remote machine on gnomemeeting and clicked the Call button.

Nothing (obvious) changed between the time it worked and the rest of the time 
that it did not. 

Thanks!  Steve


Damien wrote:

Of course you need to. And forwarding is not enough. And if your router
supports H.323, then forwarding is bad ;)
 
> Yes, I had gone through the FAQ and the list of ports. I'm using a hardware 
> cable router/firewall for the linux box (gnomemeeting) and the 1720 and  
> 5000-5003 ports have been forwarded.  Not sure if I need to do the 30000-30010 
> ports. 
> 

> Remember, it *did* actually work once.  So, if the cable router wasn't 
> configured correctly, it shouldn't have worked at all?

It depends how the call is initiated.


Steve wrote:

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