| Author |
Message |
Me
Guest
|
 Posted:
Thu Feb 19, 2004 12:42 am Post subject:
Polycom NAT/LAN |
|
|
We have 8 Polycom Viewstation FX devices and can make calls locally
and externally through the firewall, but when the option "System is
Behind a NAT" is selected we can not make internal calls over IP while
external works fine. Here is the senario. Lets say you have Polycom1
and Polycom2 both with the System is Behind a NAT option selected so
external calls work. When Polycom1 calls Polycom2 internally the call
is never connected and on Polycom2's monitor you see that Polycom1 is
calling but is using the IP address 49.53.55.46. That IP is not one
of ours, internal or external. This same thing happens on all 8 of
our Polycoms when System is Behind a NAT is selected and the call is
internal. Has anyone seen the samething? |
|
| Back to top |
|
 |
Fredrik
Guest
|
| Posted:
Wed Mar 24, 2004 3:21 pm Post subject:
Re: Polycom NAT/LAN |
|
|
Hi.
Yes, is a known problem. Its a limitation of Networking.
I got a good explanation from polycom but I cant find it right now. The
problem is firewalls and router that wont pass data. Its a safety function
that is built in in all(?) routers and firewalls.
One solution is to put all systems on separate public IP addresses.
"Me" <cliff.becker@att.net> skrev i meddelandet
news:1dcf5c36.0402181142.64237915@posting.google.com...
| Quote: | We have 8 Polycom Viewstation FX devices and can make calls locally
and externally through the firewall, but when the option "System is
Behind a NAT" is selected we can not make internal calls over IP while
external works fine. Here is the senario. Lets say you have Polycom1
and Polycom2 both with the System is Behind a NAT option selected so
external calls work. When Polycom1 calls Polycom2 internally the call
is never connected and on Polycom2's monitor you see that Polycom1 is
calling but is using the IP address 49.53.55.46. That IP is not one
of ours, internal or external. This same thing happens on all 8 of
our Polycoms when System is Behind a NAT is selected and the call is
internal. Has anyone seen the samething? |
|
|
| Back to top |
|
|
blah
Guest
|
| Posted:
Sat May 29, 2004 6:50 pm Post subject:
Re: Polycom NAT/LAN |
|
|
The problem is in the H245 handshaking. If you are behind a NAT you are
communicating the far end to send audio/video to your private address, which
is not possible (private IPs are not addressable from the Internet). When
you turn on NAT support and supply the IP of the public side of the
firewall, the system will send the public IP address instead. Then it is up
to the port forwarding in the firewall to get you where you need to be.
"Fredrik" <nospam@on.com> wrote in message
news:zid8c.53348$mU6.223917@newsb.telia.net...
| Quote: | Hi.
Yes, is a known problem. Its a limitation of Networking.
I got a good explanation from polycom but I cant find it right now. The
problem is firewalls and router that wont pass data. Its a safety function
that is built in in all(?) routers and firewalls.
One solution is to put all systems on separate public IP addresses.
"Me" <cliff.becker@att.net> skrev i meddelandet
news:1dcf5c36.0402181142.64237915@posting.google.com...
We have 8 Polycom Viewstation FX devices and can make calls locally
and externally through the firewall, but when the option "System is
Behind a NAT" is selected we can not make internal calls over IP while
external works fine. Here is the senario. Lets say you have Polycom1
and Polycom2 both with the System is Behind a NAT option selected so
external calls work. When Polycom1 calls Polycom2 internally the call
is never connected and on Polycom2's monitor you see that Polycom1 is
calling but is using the IP address 49.53.55.46. That IP is not one
of ours, internal or external. This same thing happens on all 8 of
our Polycoms when System is Behind a NAT is selected and the call is
internal. Has anyone seen the samething?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in