<?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: H.323 timeou in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/h-323-timeou/m-p/3945388#M5180</link>
    <description>?</description>
    <pubDate>Tue, 22 Oct 2019 14:46:56 GMT</pubDate>
    <dc:creator>RRFS578780</dc:creator>
    <dc:date>2019-10-22T14:46:56Z</dc:date>
    <item>
      <title>H.323 timeou</title>
      <link>https://community.cisco.com/t5/network-security/h-323-timeou/m-p/3945387#M5178</link>
      <description>&lt;P&gt;After a disconnection occurred in a videoconference, troubleshooting was initiated to identify the root cause. After log analysis, we found that the call was disconnected by H.323 timeout.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However, I would like to know if you have any ASA parsing or configuration to raise an exception regarding possible H323 traffic timeout?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 17:37:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/h-323-timeou/m-p/3945387#M5178</guid>
      <dc:creator>RRFS578780</dc:creator>
      <dc:date>2020-02-21T17:37:03Z</dc:date>
    </item>
    <item>
      <title>Re: H.323 timeou</title>
      <link>https://community.cisco.com/t5/network-security/h-323-timeou/m-p/3945388#M5180</link>
      <description>?</description>
      <pubDate>Tue, 22 Oct 2019 14:46:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/h-323-timeou/m-p/3945388#M5180</guid>
      <dc:creator>RRFS578780</dc:creator>
      <dc:date>2019-10-22T14:46:56Z</dc:date>
    </item>
  </channel>
</rss>

