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

[Steve Rifkin <steve410 cs jhu edu>]

Hmmm... You reference my firewall/router problems.  What specific problems do 
you think?  All the ports are forwarded as they should (per a previous e-mail of 
mine with status).  What else do you think it could be that is related to a 
router?   Can you take a look again at my router configuration that I sent you a 
bit ago (I've included it again a few lines below) and see if you see something 
that's missing from my configuration for the router/firewall?  I don't know what 
else can be set, especially with the router... the router part should be good.

My current configuration (updated).

H.245 tunneling is active.

TCP 1720  is port forwarded from router/firewall.

UDP 5000-5003  is port forwarded from router/firewall.

TCP 30000-30010 is port forwarded from router/firewall.

IP address translation is active.

The Win2k Netmeeting box has GSM activated.

MS-GSM is active in gnomemeeting.

The only thing I did not touch is the section in the H.323 Advanced prefs 
regarding H.232 Call Forwarding.  The Always forward calls to the given host, 
Forward calls to the given host if no answer, and Forward calls to the given 
host if busy are still unchecked.  The Forward calls to host section is kept 
blank.  Also, User Input Capabilities is still set to ALL.  NAT/PAT Router 
suppot is enabled with the public IP of the router.  Fast Start is disabled.

Thanks for all your help!  :)

Steve


===================

Damien wrote...

I've checked on my windows millenium and the connection is established
even if there is no common codec. My guess is that it can't establish
the H.245 channel due to your firewall/router problems, and thus codecs
can not be negotiated.






> Date: Tue, 11 Mar 2003 16:43:12 -0500 (EST)
> From: Steve Rifkin <steve410 cs jhu edu>
> Subject: Re: Problems connecting to Netmeeting machines from gnomemeeting
> To: gnomemeeting-list gnome org
> Cc: steve410 cs jhu edu

> 
> > Yes but I don't think it will help at all. I wonder if your Netmeeting
> > doesn't disable GSM for one reason or another.
> 
> GSM shows as the top codec in Netmeeting's Audio prefs on the Win2K box.  Same 
> situation as the other netmeeting machine I've tested with.
> 
> > Also check MS-GSM is enabled on your side.
> 
> Well, MS-GSM is listed in the Available Audio Codecs portion of the 
gnomemeeting 
> prefs.  Is being listed in that list enough to say that MS-GSM is "enabled" in 
> gnomemeeting?  Or must the codec be listed at the *top* or *hightlighted* in 
the 
> gnomemeeting prefs list for that specific codec to be considered enabled.  As 
it 
> turns out, MS-GSM *is* currently at the top of the Audio Codecs prefs list of 
> codecs and *is* highlighted.  Is there anything else I have to do to enable 
> MS-GSM on my side?
> 
> Steve
> 
> 
> > Also, Damien, I have a question about something you mentioned... When you 
> said:
> > 
> > > 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 
> > router, I can set the ports to be forwarded to the specific box behind the 
> > firewall.   But, I'm not sure what you mean by "only allow them".  Isn't 
that
> 
> forwarding = forward to the internal host
> allowing = accept incoming connections on those ports 
> 
> >  
> > what port forwarding does?  Only allows the ports to be active for a machine 
> > behind the firewall?  (I use port forwarding all the time for certain 
> services). 
> >  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 the 
> > codec error from Netmeeting.
> > 
> > Thanks!
> > 
> > Steve
>