<?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: SIP inspection in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/sip-inspection/m-p/1490399#M740457</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have several SIP trunks at work and SIP inspection is needed if you're NATting the IP of the endpoint(s).&amp;nbsp; SIP inspection re-writes the addresses in the packet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With SIP inspection turned on try using "debug sip" while attempting a call.&amp;nbsp; Use with caution as, with all debuging, it can quickly overwhelm your screen but it ends when there is no more SIP traffic.&amp;nbsp; I found it very useful when we initially set our trunks up.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 May 2010 16:49:42 GMT</pubDate>
    <dc:creator>terrygwazdosky</dc:creator>
    <dc:date>2010-05-31T16:49:42Z</dc:date>
    <item>
      <title>SIP inspection</title>
      <link>https://community.cisco.com/t5/network-security/sip-inspection/m-p/1490397#M740397</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;We are trying to setup a SIP trunk between Avaya and Nortel through Cisco ASA. The SIP session seems to be successful and we can dial from Nortel to Avaya. The problem is that after dialing the phone rings but two ends can not hear each other. That is RTP (voice) communication is not working.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;As part of SIP, both the PBX send the IP address and port number to connect to to establish voice session.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;My assumption is that as we are NATing on ASA the TCP communication works but the original IP address and port numbers in SIP header doesn't change due to which routing breaks.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;I tried using SIP inspection on ASA and that didn't work.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Any suggestions are appreciated!!&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Thank you.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:52:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sip-inspection/m-p/1490397#M740397</guid>
      <dc:creator>pfillips11</dc:creator>
      <dc:date>2019-03-11T17:52:57Z</dc:date>
    </item>
    <item>
      <title>Re: SIP inspection</title>
      <link>https://community.cisco.com/t5/network-security/sip-inspection/m-p/1490398#M740420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would also think this is a routing issue.&lt;/P&gt;&lt;P&gt;Could you post the relevant part of your configuration?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 May 2010 14:42:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sip-inspection/m-p/1490398#M740420</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2010-05-31T14:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: SIP inspection</title>
      <link>https://community.cisco.com/t5/network-security/sip-inspection/m-p/1490399#M740457</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We have several SIP trunks at work and SIP inspection is needed if you're NATting the IP of the endpoint(s).&amp;nbsp; SIP inspection re-writes the addresses in the packet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With SIP inspection turned on try using "debug sip" while attempting a call.&amp;nbsp; Use with caution as, with all debuging, it can quickly overwhelm your screen but it ends when there is no more SIP traffic.&amp;nbsp; I found it very useful when we initially set our trunks up.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 May 2010 16:49:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/sip-inspection/m-p/1490399#M740457</guid>
      <dc:creator>terrygwazdosky</dc:creator>
      <dc:date>2010-05-31T16:49:42Z</dc:date>
    </item>
  </channel>
</rss>

