• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1118
  • Last Modified:

Port Forwarding for Video Conferencing.

We have a video conferencing unit that we're trying to set up.
On the firewall, we forwarded the TCP ports and UDP ports to the private I.P of the Lifesize video conferencing device.

The problem is, we can connect and see/hear the other side and they can see/hear us if we initiate the call but if the outside world initiates a call it doesnt come through and doesnt ring.

The connection is from our cable modem (which runs as a bridge) to our Cisco router and then to the firewall. The configuration seems correct since both parties can see and hear each other. I just dont know why it drops the call/connection if the outside world initiates the connection to our LifeSize video conferencing unit.

Any expedient help would be greatly appreciated since they plan on using it for a meeting tomorrow.
2 Solutions
Ernie BeekCommented:
Could it be that (in the outside ACL) you're only allowing those ports from certain IPs (the other side) and not from anywhere else?
With H323, you need an ALG (Application Layer Gateway) to translate the IP address inside the packet as well as NAT the packet.

This is because (like FTP) the node IP addresses are inside the packet as well as in the header.

What model Cisco router is it, and what version (from a "show version") IOS is it running ?
GeekahAuthor Commented:
issues resolved
used a static p from ISP

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now