<?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: Shun Automatically Turned-on for Cisco Call Manager in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/shun-automatically-turned-on-for-cisco-call-manager/m-p/1325962#M785541</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ray,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check if the ASA has threat detection with shun option enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not then probably you have an IPS that has the ASA configured and identified the CCM as an attached and went in and shunned it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or a user logged into the ASA and shunned the CM (which I doubt).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 17 Nov 2009 14:47:57 GMT</pubDate>
    <dc:creator>Panos Kampanakis</dc:creator>
    <dc:date>2009-11-17T14:47:57Z</dc:date>
    <item>
      <title>Shun Automatically Turned-on for Cisco Call Manager</title>
      <link>https://community.cisco.com/t5/network-security/shun-automatically-turned-on-for-cisco-call-manager/m-p/1325961#M785535</link>
      <description>&lt;P&gt;Hello Experts, we have cisco ASA 5505 running for our branch office and STS tunnel is configured for remote site. The cisco call manager is placed on remote site. Yesterday, we experienced that all conference calls were got it disconnected automatically and no reply messages were recieving while doing ping to call manager server. I logged into the firewall and saw that the shun automatically turned-on for CCM server and when I manually turned-off then cisco IP phone were got it up. Can anyone explain why it was turned-on for CCM Server.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 16:40:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shun-automatically-turned-on-for-cisco-call-manager/m-p/1325961#M785535</guid>
      <dc:creator>ray_stone</dc:creator>
      <dc:date>2019-03-11T16:40:28Z</dc:date>
    </item>
    <item>
      <title>Re: Shun Automatically Turned-on for Cisco Call Manager</title>
      <link>https://community.cisco.com/t5/network-security/shun-automatically-turned-on-for-cisco-call-manager/m-p/1325962#M785541</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ray,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check if the ASA has threat detection with shun option enabled.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If not then probably you have an IPS that has the ASA configured and identified the CCM as an attached and went in and shunned it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Or a user logged into the ASA and shunned the CM (which I doubt).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 17 Nov 2009 14:47:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/shun-automatically-turned-on-for-cisco-call-manager/m-p/1325962#M785541</guid>
      <dc:creator>Panos Kampanakis</dc:creator>
      <dc:date>2009-11-17T14:47:57Z</dc:date>
    </item>
  </channel>
</rss>

