<?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 Cisco Spam Calls blocking in Automation/API Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/h-323-cisco-spam-calls-blocking/m-p/68717#M1181</link>
    <description>&lt;P&gt;Hello mkhavari,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm seeking a similar solution, but it seems a difficult thing to do. Here's my thread trying to filter on h323/h225 fields.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Custom-Signatures/h323-message-body-values/m-p/68702#U68702" target="_self"&gt;https://live.paloaltonetworks.com/t5/Custom-Signatures/h323-message-body-values/m-p/68702#U68702&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Will&lt;/P&gt;</description>
    <pubDate>Thu, 26 Nov 2015 18:18:21 GMT</pubDate>
    <dc:creator>Froning</dc:creator>
    <dc:date>2015-11-26T18:18:21Z</dc:date>
    <item>
      <title>H.323 Cisco Spam Calls blocking</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/h-323-cisco-spam-calls-blocking/m-p/65422#M1170</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying find out if anyone has successfully (without the creation of a blacklist) blocked these spam calls. I opened a support ticket with Palo Alto and they suggested that I reach out to this board for help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are constantly getting our conference systems coming off sleep mode to respond to the calls.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There are few articles floading around the web in regards to this issues like the link below&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.videonationsltd.co.uk/2015/04/h-323-cisco-spam-calls/" target="_blank"&gt;http://www.videonationsltd.co.uk/2015/04/h-323-cisco-spam-calls/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am sure this issue can be mitigated by a custom profile or signature.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Attached is a PCAP output from one of the packets. I am guessing if a custom signature can match a pattern in the PCAP output, we can block these annoying calls.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Oct 2015 22:19:13 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/h-323-cisco-spam-calls-blocking/m-p/65422#M1170</guid>
      <dc:creator>mkhavari</dc:creator>
      <dc:date>2015-10-02T22:19:13Z</dc:date>
    </item>
    <item>
      <title>Re: H.323 Cisco Spam Calls blocking</title>
      <link>https://live.paloaltonetworks.com/t5/automation-api-discussions/h-323-cisco-spam-calls-blocking/m-p/68717#M1181</link>
      <description>&lt;P&gt;Hello mkhavari,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I'm seeking a similar solution, but it seems a difficult thing to do. Here's my thread trying to filter on h323/h225 fields.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://live.paloaltonetworks.com/t5/Custom-Signatures/h323-message-body-values/m-p/68702#U68702" target="_self"&gt;https://live.paloaltonetworks.com/t5/Custom-Signatures/h323-message-body-values/m-p/68702#U68702&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Good luck!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Will&lt;/P&gt;</description>
      <pubDate>Thu, 26 Nov 2015 18:18:21 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/automation-api-discussions/h-323-cisco-spam-calls-blocking/m-p/68717#M1181</guid>
      <dc:creator>Froning</dc:creator>
      <dc:date>2015-11-26T18:18:21Z</dc:date>
    </item>
  </channel>
</rss>

