<?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 Trunks failing in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/sip-trunks-failing/m-p/337263#M84944</link>
    <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/148197"&gt;@emrealdpaddy&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Sounds like the PAN admin may not actually be setting up a static port translation for this traffic and it's just hitting a DIPP NAT. They'll want to ensure that the source address translation type isn't interfering with the source port (IE: A Dynamic IP or Static NAT entry).&lt;/P&gt;</description>
    <pubDate>Wed, 08 Jul 2020 19:49:25 GMT</pubDate>
    <dc:creator>BPry</dc:creator>
    <dc:date>2020-07-08T19:49:25Z</dc:date>
    <item>
      <title>SIP Trunks failing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sip-trunks-failing/m-p/336823#M84892</link>
      <description>&lt;P&gt;Hi All, Im a Telephone system installer and have installed a system with SIP trunks which authenticate with the public IP (not register user name/password)&lt;/P&gt;&lt;P&gt;The SIP trunks remain working at all times for outgoing fails after a time normally about a day. the firewall is a palo alto PA220&amp;nbsp;&lt;/P&gt;&lt;P&gt;the SIP provider tells me they are trying to communicate on a port other than 5060&amp;nbsp; and as a result the incoming call fails to get through the firewall. I have asked the I.T company to allow all traffic from the SIP providers IP and he said he has. The incoming was working since last friday the 3rd July but this morning the calls are failing again and the SIP provider now say its trying to use :5164 to establish the call. Any ideas what the IT need to set to make sure it communicates on port 5060 only and not try to change the port and this can be locked down to one single IP from the SIP provider ?? thank you J&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="palo alto.png" style="width: 999px;"&gt;&lt;img src="https://live.paloaltonetworks.com/t5/image/serverpage/image-id/26628i7FC198EB5B00D225/image-size/large/is-moderation-mode/true?v=v2&amp;amp;px=999" role="button" title="palo alto.png" alt="palo alto.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 07 Jul 2020 08:17:29 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sip-trunks-failing/m-p/336823#M84892</guid>
      <dc:creator>emrealdpaddy</dc:creator>
      <dc:date>2020-07-07T08:17:29Z</dc:date>
    </item>
    <item>
      <title>Re: SIP Trunks failing</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/sip-trunks-failing/m-p/337263#M84944</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/148197"&gt;@emrealdpaddy&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;Sounds like the PAN admin may not actually be setting up a static port translation for this traffic and it's just hitting a DIPP NAT. They'll want to ensure that the source address translation type isn't interfering with the source port (IE: A Dynamic IP or Static NAT entry).&lt;/P&gt;</description>
      <pubDate>Wed, 08 Jul 2020 19:49:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/sip-trunks-failing/m-p/337263#M84944</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2020-07-08T19:49:25Z</dc:date>
    </item>
  </channel>
</rss>

