<?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 ASA SIP inspection in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179462#M358499</link>
    <description>&lt;P&gt;Hi All, &lt;/P&gt;&lt;P&gt;we are having an issue with ASA sip inspection. here is our topology: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CUCM-A --&amp;gt; ASA-A -- &amp;gt; ASA-B --&amp;gt; CUCM-B &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;phone from site A calls site B, call is connected and media is being passed. when phone in site A puts the call on hold, the call is dropped immediatly. I did packet capture from ASA-A egress interface, and it is sending its own public IP address in SDP contact when phone A puts the call on hold. is it supposed to be 0.0.0.0 when phone A puts the call on hold? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appreciate any suggestion &lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:26:35 GMT</pubDate>
    <dc:creator>alex goshtaei</dc:creator>
    <dc:date>2019-03-12T01:26:35Z</dc:date>
    <item>
      <title>ASA SIP inspection</title>
      <link>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179462#M358499</link>
      <description>&lt;P&gt;Hi All, &lt;/P&gt;&lt;P&gt;we are having an issue with ASA sip inspection. here is our topology: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CUCM-A --&amp;gt; ASA-A -- &amp;gt; ASA-B --&amp;gt; CUCM-B &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;phone from site A calls site B, call is connected and media is being passed. when phone in site A puts the call on hold, the call is dropped immediatly. I did packet capture from ASA-A egress interface, and it is sending its own public IP address in SDP contact when phone A puts the call on hold. is it supposed to be 0.0.0.0 when phone A puts the call on hold? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;appreciate any suggestion &lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:26:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179462#M358499</guid>
      <dc:creator>alex goshtaei</dc:creator>
      <dc:date>2019-03-12T01:26:35Z</dc:date>
    </item>
    <item>
      <title>ASA SIP inspection</title>
      <link>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179463#M358500</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As long as I know that behavior of setting the SDP contact as 0 has been deprecated,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the following RFC for more comments &lt;SPAN __jive_emoticon_name="grin" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/grin.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://tools.ietf.org/html/rfc5359#section-2.1"&gt;http://tools.ietf.org/html/rfc5359#section-2.1&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;P&gt;Remember to rate all of the helpfull posts&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 Apr 2013 22:25:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179463#M358500</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-04-10T22:25:12Z</dc:date>
    </item>
    <item>
      <title>ASA SIP inspection</title>
      <link>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179464#M358501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the link, but even I don't see "audio=inactive" in SDP header coming from ASA-A. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Apr 2013 18:26:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179464#M358501</guid>
      <dc:creator>alex goshtaei</dc:creator>
      <dc:date>2013-04-11T18:26:58Z</dc:date>
    </item>
    <item>
      <title>ASA SIP inspection</title>
      <link>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179465#M358502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a way you could attach the debugs and captures to this discussion&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Apr 2013 22:35:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-sip-inspection/m-p/2179465#M358502</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2013-04-11T22:35:12Z</dc:date>
    </item>
  </channel>
</rss>

