<?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 Webex H.323 from behind a firewall in Webex Administration</title>
    <link>https://community.cisco.com/t5/webex-administration/webex-h-323-from-behind-a-firewall/m-p/4112133#M1698</link>
    <description>&lt;P&gt;H.323 is advertised as working for Webex. All of our invites have a line saying "&lt;SPAN&gt;You can also dial 173.243.2.68 and enter your meeting number." This works fine&amp;nbsp;&lt;EM&gt;unless your endpoint is behind a NAT.&amp;nbsp;&lt;/EM&gt;I'm trying to use this for B2B calls for customers and partners that have older endpoints that only do H.323. Of course they are behind a NAT.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I opened a TAC case and they say it's working as designed. That they don't use an ALG or firewall fixup to change the internal IP addresses in the signaling messages.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But if I call the BlueJeans network H.323 address (&lt;SPAN&gt;199.48.152.152) it works fine. The Zoom H.323 address works as well, as does the Polycom test bridge on&amp;nbsp;140.242.250.204.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;Why is it everyone seems to understand H.323 networking better than the Webex video team?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jul 2020 21:42:38 GMT</pubDate>
    <dc:creator>jbburks</dc:creator>
    <dc:date>2020-07-01T21:42:38Z</dc:date>
    <item>
      <title>Webex H.323 from behind a firewall</title>
      <link>https://community.cisco.com/t5/webex-administration/webex-h-323-from-behind-a-firewall/m-p/4112133#M1698</link>
      <description>&lt;P&gt;H.323 is advertised as working for Webex. All of our invites have a line saying "&lt;SPAN&gt;You can also dial 173.243.2.68 and enter your meeting number." This works fine&amp;nbsp;&lt;EM&gt;unless your endpoint is behind a NAT.&amp;nbsp;&lt;/EM&gt;I'm trying to use this for B2B calls for customers and partners that have older endpoints that only do H.323. Of course they are behind a NAT.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I opened a TAC case and they say it's working as designed. That they don't use an ALG or firewall fixup to change the internal IP addresses in the signaling messages.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;But if I call the BlueJeans network H.323 address (&lt;SPAN&gt;199.48.152.152) it works fine. The Zoom H.323 address works as well, as does the Polycom test bridge on&amp;nbsp;140.242.250.204.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;SPAN&gt;Why is it everyone seems to understand H.323 networking better than the Webex video team?&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 21:42:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/webex-administration/webex-h-323-from-behind-a-firewall/m-p/4112133#M1698</guid>
      <dc:creator>jbburks</dc:creator>
      <dc:date>2020-07-01T21:42:38Z</dc:date>
    </item>
  </channel>
</rss>

