Whoops. Yep, H.323. Fingers working faster than the brain... Yes, this setup would greatly simplify things!
-----Original Message----- From: Kurt Buff [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 30, 2008 3:27 PM To: NT System Admin Issues Subject: Re: Video Conferencing That would be H.323, I believe, and yes, you are correct. If it were me doing this (and it is, I just haven't gotten to it yet), I'd put the Polycom unit in a DMZ with it's own public IP address, and just open it up. Turn it off when not int use, and pay for the encryption license on both ends. Kurt On Tue, Sep 30, 2008 at 12:22 PM, <[EMAIL PROTECTED]> wrote: > +1 > > Unless you have a newer firewall that understands H.232 traffic, it will not > play nice with the newer Polycom stuff. > > -----Original Message----- > From: Mike French [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 30, 2008 3:14 PM > To: NT System Admin Issues > Subject: RE: Video Conferencing > > How about www.polycom.com > > Used them at a client site, had good results. Just make sure your firewall > will play nice with whatever you choose... > > ________________________________________ > From: Steve Ens [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 30, 2008 2:07 PM > To: NT System Admin Issues > Subject: Video Conferencing > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
