<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351970#M559558</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear charles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if u have other connections from 10.30.100.154 , u need to have access-list for them also. fixup protocol will not open any connections dynamically. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as per ur PS :   to write a access-list u need to have either source address and destination address r u have to use any. if u dont have either choice ,nothing can be done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Nataraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 30 Jan 2005 20:12:30 GMT</pubDate>
    <dc:creator>nataraj_v</dc:creator>
    <dc:date>2005-01-30T20:12:30Z</dc:date>
    <item>
      <title>PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside</title>
      <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351967#M559544</link>
      <description>&lt;P&gt;I tried to protect an IOS H323 Gateway with a PIX. The IOS gatekeeper is outside. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That's for a customer demo so I can't open a ticket.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want the pix to allow the connection to the inside gateway only if there is an ACF between the gateway and the gatekeeper. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As stated in the documentation :&lt;/P&gt;&lt;P&gt;"The PIX Firewall administrator must open an access list for the well-known H.323 port 1720 for the H.225 call signaling. However, the H.245 signaling ports are negotiated between the endpoints in the H.225 signaling. When an H.323 gatekeeper is used, the PIX Firewall opens an H.225 connection based on inspection of the ACF message."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the real network, my customer will know the IP addresses of the remote Gatekeepers but not the IP addresses of the remote Gateways. He want to accept/refuse calls on his gatekeeper.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For my lab, I use 3*2600 with IOS (tm) C2600 Software (C2600-IS3X-M), Version 12.3(10a), RELEASE SOFTWARE (fc2) and 1 Pix 515E release 6.3.4.&lt;/P&gt;&lt;P&gt;This configuration :&lt;/P&gt;&lt;P&gt; - Gateway :&lt;/P&gt;&lt;P&gt;  interface Ethernet0/0&lt;/P&gt;&lt;P&gt;   ip address 192.168.0.5 255.255.255.0&lt;/P&gt;&lt;P&gt;   h323-gateway voip interface&lt;/P&gt;&lt;P&gt;   h323-gateway voip id gk.in.com ipaddr 10.30.100.153 1719&lt;/P&gt;&lt;P&gt;   h323-gateway voip h323-id &lt;A href="mailto:gw@in.com" target="_blank"&gt;gw@in.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;   h323-gateway voip tech-prefix 1#&lt;/P&gt;&lt;P&gt;  voice-port 1/0/0&lt;/P&gt;&lt;P&gt;   cptone FR&lt;/P&gt;&lt;P&gt;  ip route 0.0.0.0 0.0.0.0 192.168.0.1&lt;/P&gt;&lt;P&gt;  dial-peer voice 10 pots&lt;/P&gt;&lt;P&gt;   destination-pattern 1234&lt;/P&gt;&lt;P&gt;   port 1/0/0&lt;/P&gt;&lt;P&gt;  dial-peer voice 11 voip&lt;/P&gt;&lt;P&gt;   destination-pattern 2T&lt;/P&gt;&lt;P&gt;   session target ras&lt;/P&gt;&lt;P&gt;  gateway&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Firewall&lt;/P&gt;&lt;P&gt;  PIX Version 6.3(4)&lt;/P&gt;&lt;P&gt;  interface ethernet0 auto&lt;/P&gt;&lt;P&gt;  interface ethernet1 auto&lt;/P&gt;&lt;P&gt;  nameif ethernet0 outside security0&lt;/P&gt;&lt;P&gt;  nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;  fixup protocol h323 h225 1720&lt;/P&gt;&lt;P&gt;  fixup protocol h323 ras 1718-1719&lt;/P&gt;&lt;P&gt;  access-list 103 permit ip host 10.30.100.153 host 10.30.100.152&lt;/P&gt;&lt;P&gt;  ip address outside 10.30.100.151 255.255.255.0 &lt;/P&gt;&lt;P&gt;  ip address inside 192.168.0.1 255.255.255.0&lt;/P&gt;&lt;P&gt;  static (inside,outside) 10.30.100.152 192.168.0.5 netmask 255.255.255.255 0 0&lt;/P&gt;&lt;P&gt;  access-group 103 in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Gatekeeper&lt;/P&gt;&lt;P&gt;  interface Ethernet0/0&lt;/P&gt;&lt;P&gt;   ip address 10.30.100.153 255.255.255.0&lt;/P&gt;&lt;P&gt;  gatekeeper&lt;/P&gt;&lt;P&gt;   zone local gk.in.com in.com&lt;/P&gt;&lt;P&gt;   zone remote gk.out.com out.com 10.30.100.154 1719&lt;/P&gt;&lt;P&gt;   zone prefix gk.out.com 2*&lt;/P&gt;&lt;P&gt;   no shutdown&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Remote Gateway/Gatekeeper :&lt;/P&gt;&lt;P&gt;  interface Ethernet0/0&lt;/P&gt;&lt;P&gt;   ip address 10.30.100.154 255.255.255.0&lt;/P&gt;&lt;P&gt;   h323-gateway voip interface&lt;/P&gt;&lt;P&gt;   h323-gateway voip id gk.out.com ipaddr 10.30.100.154 1719&lt;/P&gt;&lt;P&gt;   h323-gateway voip h323-id &lt;A href="mailto:gw@out.com" target="_blank"&gt;gw@out.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;   h323-gateway voip tech-prefix 1#&lt;/P&gt;&lt;P&gt;  voice-port 1/0/0&lt;/P&gt;&lt;P&gt;   cptone FR&lt;/P&gt;&lt;P&gt;  dial-peer voice 10 voip&lt;/P&gt;&lt;P&gt;   destination-pattern 1T&lt;/P&gt;&lt;P&gt;   session target ras&lt;/P&gt;&lt;P&gt;  dial-peer voice 11 pots&lt;/P&gt;&lt;P&gt;   destination-pattern 2345&lt;/P&gt;&lt;P&gt;   port 1/0/0&lt;/P&gt;&lt;P&gt;  gateway&lt;/P&gt;&lt;P&gt;  gatekeeper&lt;/P&gt;&lt;P&gt;   zone local gk.out.com out.com&lt;/P&gt;&lt;P&gt;   zone remote gk.in.com in.com 10.30.100.153 1719&lt;/P&gt;&lt;P&gt;   zone prefix gk.in.com 1*&lt;/P&gt;&lt;P&gt;   no shutdown&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- I could call outside but I can't receive calls.&lt;/P&gt;&lt;P&gt;- Is there a way to do it or did I misunderstand the documentation ?&lt;/P&gt;&lt;P&gt;- If this can't work with a PIX, what could be the solution ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Charles Perroquin&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:54:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351967#M559544</guid>
      <dc:creator>cperroquin</dc:creator>
      <dc:date>2020-02-21T07:54:15Z</dc:date>
    </item>
    <item>
      <title>Re: PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside</title>
      <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351968#M559549</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear charles ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;According to ur present access-list and static nat , ur pix allow return traffic from 10.30.100.153 (which is gatekeeper) to 192.168.10.5 . Make sure wether connections  r initiated from only 10.30.100.153 r some other . And i advice nt to use ip in access-list. pls try to make a object-group for services. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards.&lt;/P&gt;&lt;P&gt;Nataraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Jan 2005 19:17:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351968#M559549</guid>
      <dc:creator>nataraj_v</dc:creator>
      <dc:date>2005-01-30T19:17:19Z</dc:date>
    </item>
    <item>
      <title>Re: PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside</title>
      <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351969#M559554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Nataraj,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agree that I should modify this line :&lt;/P&gt;&lt;P&gt; access-list 103 permit ip host 10.30.100.153 host 10.30.100.152 &lt;/P&gt;&lt;P&gt;like this&lt;/P&gt;&lt;P&gt; access-list 103 permit tcp host 10.30.100.153 host 10.30.100.152 1720&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also I agree that I will have others connections from 10.30.100.154. The point is that, I believe (wrongly/truly ?) that those connections will be open dynamicaly by the "fixup protocol h323 h225 1720" command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Charles&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS: My customer can't know the IP addresses of all the gateways (managed by other providers). And I can't allow everybody to connect to the gateway.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Jan 2005 19:56:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351969#M559554</guid>
      <dc:creator>cperroquin</dc:creator>
      <dc:date>2005-01-30T19:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside</title>
      <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351970#M559558</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear charles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if u have other connections from 10.30.100.154 , u need to have access-list for them also. fixup protocol will not open any connections dynamically. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as per ur PS :   to write a access-list u need to have either source address and destination address r u have to use any. if u dont have either choice ,nothing can be done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Nataraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Jan 2005 20:12:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351970#M559558</guid>
      <dc:creator>nataraj_v</dc:creator>
      <dc:date>2005-01-30T20:12:30Z</dc:date>
    </item>
    <item>
      <title>Re: PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside</title>
      <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351971#M559561</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I quoted below the documentation of the "fixup protocol H323 H225" command:&lt;/P&gt;&lt;P&gt;"When an H.323 gatekeeper is used, the PIX Firewall opens an H.225 connection based on inspection of the ACF message."&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a008017278b.html#wp1079378" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/secursw/ps2120/products_configuration_guide_chapter09186a008017278b.html#wp1079378&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To me, it seems that the firewall should opens an H225 connection based on the ACF message. This message is between the inside gateway and the gatekeeper.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Charles&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Jan 2005 20:28:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351971#M559561</guid>
      <dc:creator>cperroquin</dc:creator>
      <dc:date>2005-01-30T20:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside</title>
      <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351972#M559563</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'd just found a workaround : putting an H323 proxy on the gatekeeper:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Gatekeeper/Proxy&lt;/P&gt;&lt;P&gt;interface Ethernet0/0&lt;/P&gt;&lt;P&gt; ip address 10.30.100.153 255.255.255.0&lt;/P&gt;&lt;P&gt; ip access-group 101 in&lt;/P&gt;&lt;P&gt; h323 interface&lt;/P&gt;&lt;P&gt; h323 h323-id &lt;A href="mailto:px@in.com"&gt;px@in.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt; h323 gatekeeper ipaddr 10.30.100.153&lt;/P&gt;&lt;P&gt; h323 t120 bypass&lt;/P&gt;&lt;P&gt;access-list 101 permit udp host 10.30.100.152 host 10.30.100.153 eq 1719&lt;/P&gt;&lt;P&gt;access-list 101 permit udp host 10.30.100.154 host 10.30.100.153 eq 1719&lt;/P&gt;&lt;P&gt;access-list 101 permit udp host 10.30.100.153 host 10.30.100.153 eq 1719&lt;/P&gt;&lt;P&gt;access-list 101 deny   udp any host 10.30.100.153 eq 1719&lt;/P&gt;&lt;P&gt;access-list 101 permit ip any any&lt;/P&gt;&lt;P&gt;gatekeeper&lt;/P&gt;&lt;P&gt; zone local gk.in.com in.com&lt;/P&gt;&lt;P&gt; zone remote gk.out.com out.com 10.30.100.154 1719&lt;/P&gt;&lt;P&gt; use-proxy gk.in.com remote-zone out.com inbound-to gateway&lt;/P&gt;&lt;P&gt; use-proxy gk.in.com remote-zone out.com outbound-from gateway&lt;/P&gt;&lt;P&gt; use-proxy gk.in.com default inbound-to gateway&lt;/P&gt;&lt;P&gt; use-proxy gk.in.com default outbound-from gateway&lt;/P&gt;&lt;P&gt; zone prefix gk.out.com 2*&lt;/P&gt;&lt;P&gt; no shutdown&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But the problem is still open (h323 proxy are CPU intense...). &lt;/P&gt;&lt;P&gt;Could it work without the h323 proxy ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Charles Perroquin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 30 Jan 2005 22:25:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351972#M559563</guid>
      <dc:creator>cperroquin</dc:creator>
      <dc:date>2005-01-30T22:25:27Z</dc:date>
    </item>
    <item>
      <title>Re: PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside</title>
      <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351973#M559566</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear charles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls look at this link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.njedge.net/documents/h323-video-pix.ppt" target="_blank"&gt;www.njedge.net/documents/h323-video-pix.ppt&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;Nataraj&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2005 03:00:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351973#M559566</guid>
      <dc:creator>nataraj_v</dc:creator>
      <dc:date>2005-01-31T03:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: PIX protecting H323 IOS Gateway with IOS Gatekeeper Outside</title>
      <link>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351974#M559569</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Charles,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Pls go through these links too , hope they may help u.pls tell me the configuration once u fixed the issue. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.njedge.net/techsection/firewall-codecs.html" target="_blank"&gt;http://www.njedge.net/techsection/firewall-codecs.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00801fc74a.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00801fc74a.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks and Regards&lt;/P&gt;&lt;P&gt;Nataraj&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Jan 2005 03:34:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-protecting-h323-ios-gateway-with-ios-gatekeeper-outside/m-p/351974#M559569</guid>
      <dc:creator>nataraj_v</dc:creator>
      <dc:date>2005-01-31T03:34:34Z</dc:date>
    </item>
  </channel>
</rss>

