.
> I am not sure if your configuration does what I am trying to do
> or not. You
> say the NT server has both originate and receive. If I understand
> correctly, this means the client side computers can make
> Netmeeting calls,
Yes clients can make NetMeeting calls - this is because Sygate has a built
in H.323 proxy.
> but there is no way for the outside world to call them directly. The
> outside world however can call an IP address that is owned by the
> NT Server.
> Correct so far?
That is correct.
If so, what happens to those incoming
> Netmeeting calls?
Incoming calls that are addressed to the router go to the NetMeeting running
on that box -- all other calls ( say ILS based calls for internal clients)
would go into the ozone unless placed from the internal network as those are
addressed to non routable private IP addresses ( which the clients would
have and would register in the ILS).
> How are they forwarded to the clients?
>
No NAT or firewall that I know of supports incoming calls intended for
clients behind the firewall - there is simply not enough information to
direct the call. To do that you need a gateway/gatekeeper setup where
clients register their name and IP address with the gatekeeper -- the calls
are made by calling the gateway using the registered name.
I am not sure if the Sygate software router solution would work for you
either -- it will route internal private IPs to one external IP using NAT.
It will not handle more IPs - they would have to be handled separately but
the one IP handled by Sygate could forward ports to handle web servers, ftp
servers and smtp, pop servers.
-----------------------------------------------------------------------
http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
-----------------------------------------------------------------------
