<?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: FWSM/PIX and POLYCOM in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-pix-and-polycom/m-p/571875#M526084</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 believe, on PIX you are NATing the internal polycom to some public/other IP. and the ACL rules and NAT statements are not applied as per that&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Incase, you want the foreign polycom to access internal poly with its original IP, then you need to setup "nat 0" or identity NAT .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It might be possible that in netscreen, these conditions are already met and hence working. kindly check this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;aashish C&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 29 Mar 2006 07:47:34 GMT</pubDate>
    <dc:creator>aashish.c</dc:creator>
    <dc:date>2006-03-29T07:47:34Z</dc:date>
    <item>
      <title>FWSM/PIX and POLYCOM</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-pix-and-polycom/m-p/571874#M526083</link>
      <description>&lt;P&gt;Just now I have setup POLYCOM Viewstation H323 behind a PIX and in a "DMZ" under the FWSM ... it seems the Calling has started at the foreign POLYCOM, but the call cannot complete connecting.  I have noted at the foreign POLYCOM that has picked up a Calling partner of the internal (before NAT) address, which i wonder if that causes the problem !! but WHY ? ... note : my Netscreens have no such problem !!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Raymond.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:48:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-pix-and-polycom/m-p/571874#M526083</guid>
      <dc:creator>raymond.leung</dc:creator>
      <dc:date>2020-02-21T08:48:01Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM/PIX and POLYCOM</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-pix-and-polycom/m-p/571875#M526084</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 believe, on PIX you are NATing the internal polycom to some public/other IP. and the ACL rules and NAT statements are not applied as per that&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Incase, you want the foreign polycom to access internal poly with its original IP, then you need to setup "nat 0" or identity NAT .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It might be possible that in netscreen, these conditions are already met and hence working. kindly check this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;aashish C&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 29 Mar 2006 07:47:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-pix-and-polycom/m-p/571875#M526084</guid>
      <dc:creator>aashish.c</dc:creator>
      <dc:date>2006-03-29T07:47:34Z</dc:date>
    </item>
  </channel>
</rss>

