Issues with Firewalls and H.323
What makes H.323 so cumbersome to run through a firewall is its use of multiple data ports for a single call. For an H.323 call to take place it must first open an H.225 connection on TCP port 1720, using Q.931 signaling. After this has taken place, the H.245 management session is established. While this can take place on a separate channel from the H.225 setup it can also be done using H.245 tunneling, which takes the H.245 messages and embeds them in the Q.931 messages in the previously established H.225 channel.
At this point the H.245 session opens dynamically assigned ports for the
An additional problem encountered with most firewalls is the use of NAT (see “What is NAT” below for more information). Within H.323, the H.225 and H.245 signaling channels make heavy use of the embedded IP address. An example could be the following: A terminal has a private address of 10.1.1.125, which gets translated to 206.165.202.125 when it tries to place a call to an H.323 terminal with an IP address of 206.165.201.78 on the outside network. The terminal on the outside will still receive the private address within the H.225 signaling stream. Since this is a
What is the Cisco Secure PIX Firewall?
Formerly known as the PIX Firewall, the Cisco Secure PIX Firewall series is the highest- performance,
Copyright © 2001 Cisco Systems, Inc. | Page 4 of 11 |