<?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: ZBFW SIP Protocol Violation - IOS 15.5(3)M7 on 2901 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/zbfw-sip-protocol-violation-ios-15-5-3-m7-on-2901/m-p/4060850#M1068924</link>
    <description>&lt;P&gt;We simply removed the "match protocol sip" and let it default to "match protocol udp" for outgoing. There are apparently quite a few problems with inspecting SIP with ZBFW&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 07 Apr 2020 14:16:55 GMT</pubDate>
    <dc:creator>Tboss99</dc:creator>
    <dc:date>2020-04-07T14:16:55Z</dc:date>
    <item>
      <title>ZBFW SIP Protocol Violation - IOS 15.5(3)M7 on 2901</title>
      <link>https://community.cisco.com/t5/network-security/zbfw-sip-protocol-violation-ios-15-5-3-m7-on-2901/m-p/3786988#M1048523</link>
      <description>&lt;P&gt;Hi Cisco IOS SMEs,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;there have been some prior posts on this subject, but they are very old and relate to much less recent IOS versions:&lt;/P&gt;&lt;P&gt;here:&amp;nbsp;&lt;A href="https://community.cisco.com/t5/firewalls/zbfw-quot-sip-protocol-violations-quot/m-p/1251998" target="_blank"&gt;https://community.cisco.com/t5/firewalls/zbfw-quot-sip-protocol-violations-quot/m-p/1251998&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am running IOS 15.5(3)M7 on 2901 ISR Router and am in process of trying to get SIP Trunk configured with CME on the router, but has issue with this and so started to test with SW sip user agent (Blink Pro). My trunk provider is using Cisco Broadworks SIP Server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As part of testing I have put SIP devices in DMZ with public IP address so as to avoid any potential NAT/SIP complications.&lt;/P&gt;&lt;P&gt;Based on reading other posts relating to getting SIP_PROTOCOL_VIOLATION reports (via log) I have configured the following set of definitions into my configuration:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;start of snippet&amp;gt;&amp;gt;&lt;/P&gt;&lt;P&gt;class-map type inspect sip match-any SIP-MESSAGE&lt;BR /&gt;match protocol-violation&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;class-map type inspect match-all SIP-FW-PROTOCOL&lt;BR /&gt;match protocol sip&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;policy-map type inspect sip SIP-ACTION&lt;BR /&gt;class type inspect sip SIP-MESSAGE&lt;BR /&gt;log&lt;BR /&gt;allow&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;policy-map type inspect POLICY-DMZ-OUT&lt;BR /&gt;class type inspect SIP-FW-PROTOCOL&lt;BR /&gt;inspect&lt;BR /&gt;service-policy sip SIP-ACTION&lt;BR /&gt;class class-default&lt;BR /&gt;drop log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;end of snippet&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So even when I have configured this I am getting the following result:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;004654: Jan 24 08:25:14.844 UTC: %AIC-4-SIP_PROTOCOL_VIOLATION: SIP protocol violation (Content length invalid / Non-SIP MSG recvd) -&lt;SPAN class="Apple-converted-space"&gt;&amp;nbsp; &lt;/SPAN&gt;dropping udp session 203.XX.XX.40:62509 45.XX.1XX.232:5060 on zone-pair ZP-DMZ-OUT class SIP-FW-PROTOCOL&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;My testing has found that the violation occurs during INVITE exchange. REGISTER completes successfully, without any SIP Protocol Violations.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;So the documented work around for protocol violations itself does not appear to be working.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Can anyone please advise.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;As the response is coming from Cisco Broadwork server, I am very&amp;nbsp;surprised that Cisco IOS FW is not handling traffic ...&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks in advance for any suggestions.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;John.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 16:41:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbfw-sip-protocol-violation-ios-15-5-3-m7-on-2901/m-p/3786988#M1048523</guid>
      <dc:creator>johnhart</dc:creator>
      <dc:date>2020-02-21T16:41:43Z</dc:date>
    </item>
    <item>
      <title>Re: ZBFW SIP Protocol Violation - IOS 15.5(3)M7 on 2901</title>
      <link>https://community.cisco.com/t5/network-security/zbfw-sip-protocol-violation-ios-15-5-3-m7-on-2901/m-p/3787832#M1048541</link>
      <description>&lt;P&gt;Hi IOS SMEs,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;can anyone please confirm expect behaviour of the work around outlined in this bug report, which is consistent with the configuration I posted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is bug link:&amp;nbsp;&lt;A title="SIP Protocol Violation work around" href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtl58680" target="_self"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCtl58680&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In the text of link it says:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;"This is an enhancement to just drop the packet in these cases and not the entire UDP session and child connections"&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My expectation of added the service-policy:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;-- snippet --&amp;gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;class-map type inspect sip match-any allow-violations&lt;/P&gt;&lt;P&gt;&amp;nbsp; match protocol-violation&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;policy-map type inspect sip allow-violations&lt;/P&gt;&lt;P&gt;&amp;nbsp; class type inspect sip allow-violations&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; allow&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;policy-map type inspect self-&amp;gt;out&lt;/P&gt;&lt;P&gt;&amp;nbsp; class type inspect self-&amp;gt;out&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; inspect&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; service-policy sip allow-violations&lt;/P&gt;&lt;P&gt;&amp;nbsp; class class-default&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; drop log&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt;-- snippet --&amp;gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;would be to not drop the packet and let it pass through.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Am I wrong in this thinking ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;John.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jan 2019 23:42:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbfw-sip-protocol-violation-ios-15-5-3-m7-on-2901/m-p/3787832#M1048541</guid>
      <dc:creator>johnhart</dc:creator>
      <dc:date>2019-01-25T23:42:04Z</dc:date>
    </item>
    <item>
      <title>Re: ZBFW SIP Protocol Violation - IOS 15.5(3)M7 on 2901</title>
      <link>https://community.cisco.com/t5/network-security/zbfw-sip-protocol-violation-ios-15-5-3-m7-on-2901/m-p/4060850#M1068924</link>
      <description>&lt;P&gt;We simply removed the "match protocol sip" and let it default to "match protocol udp" for outgoing. There are apparently quite a few problems with inspecting SIP with ZBFW&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Apr 2020 14:16:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/zbfw-sip-protocol-violation-ios-15-5-3-m7-on-2901/m-p/4060850#M1068924</guid>
      <dc:creator>Tboss99</dc:creator>
      <dc:date>2020-04-07T14:16:55Z</dc:date>
    </item>
  </channel>
</rss>

