<?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: Behaviour RTCP sessions in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218620#M63187</link>
    <description>&lt;P&gt;Set the application like you have it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Change the service field to "application-default".&amp;nbsp; Or, if you are running rtp/rtcp on non-standard ports, then list those ports here.&lt;/P&gt;</description>
    <pubDate>Wed, 20 Jun 2018 19:49:07 GMT</pubDate>
    <dc:creator>fjwcash</dc:creator>
    <dc:date>2018-06-20T19:49:07Z</dc:date>
    <item>
      <title>Behaviour RTCP sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218346#M63121</link>
      <description>&lt;P&gt;i,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are having a weird behaviour with rtcp-base and rtcp apps.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jun 2018 09:05:08 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218346#M63121</guid>
      <dc:creator>soporteseguridad</dc:creator>
      <dc:date>2018-06-21T09:05:08Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour RTCP sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218361#M63125</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/9102"&gt;@soporteseguridad&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;What does eithe security policy actually look like, could you post how you have those configured as well?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 15:09:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218361#M63125</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-06-19T15:09:57Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour RTCP sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218365#M63127</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jun 2018 09:04:45 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218365#M63127</guid>
      <dc:creator>soporteseguridad</dc:creator>
      <dc:date>2018-06-21T09:04:45Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour RTCP sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218367#M63128</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/9102"&gt;@soporteseguridad&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;I'ts because you have an application specified when specifying the service as 'any'. The first few packets in a flow are unable to be identified as rtcp or rtp-base traffic and will therefore match your Temp rule until the traffic is identified. When the application changes and goes back through the security policy it will match your 'Telefonica Hacia Sede' policy as it now has the proper app-id identified.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 19 Jun 2018 15:45:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218367#M63128</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2018-06-19T15:45:09Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour RTCP sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218467#M63144</link>
      <description>&lt;P&gt;Yes, but we dont see "incomplete" and some sessions are matching with the same values. So if we dont have a below rule with any, this traffic would be denied??? What it would be the best practices to match only in the correct rule?&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jun 2018 07:37:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218467#M63144</guid>
      <dc:creator>soporteseguridad</dc:creator>
      <dc:date>2018-06-20T07:37:23Z</dc:date>
    </item>
    <item>
      <title>Re: Behaviour RTCP sessions</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218620#M63187</link>
      <description>&lt;P&gt;Set the application like you have it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Change the service field to "application-default".&amp;nbsp; Or, if you are running rtp/rtcp on non-standard ports, then list those ports here.&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jun 2018 19:49:07 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/behaviour-rtcp-sessions/m-p/218620#M63187</guid>
      <dc:creator>fjwcash</dc:creator>
      <dc:date>2018-06-20T19:49:07Z</dc:date>
    </item>
  </channel>
</rss>

