<?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 Palo Alto Networks PA- 450 Next‑Generation Firewall to maintain uninterrupted BSNL SIP trunk services in the event of a primary internet link failure. in Next-Generation Firewall Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-networks-pa-450-next-generation-firewall-to-maintain/m-p/1245019#M6569</link>
    <description>&lt;P&gt;Please provide comprehensive and step‑by‑step instructions for configuring a Palo Alto Networks PA- 450 Next‑Generation Firewall to maintain uninterrupted BSNL SIP trunk services in the event of a primary internet link failure. The BSNL SIP Trunk Server which is on cloud having a static IP of 117.198.215.109 &amp;amp; BSNL SIP trunk is presently bound to a static public IP 116.74.149.94, which is allocated to the primary internet circuit. The requirement is to automatically reroute all BSNL SIP traffic through the secondary internet circuit having static IP 117.139.107.109 whenever the primary link becomes unavailable, while retaining the static SIP source IP of the primary line.&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jan 2026 05:11:27 GMT</pubDate>
    <dc:creator>pradip.joshi</dc:creator>
    <dc:date>2026-01-07T05:11:27Z</dc:date>
    <item>
      <title>Palo Alto Networks PA- 450 Next‑Generation Firewall to maintain uninterrupted BSNL SIP trunk services in the event of a primary internet link failure.</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-networks-pa-450-next-generation-firewall-to-maintain/m-p/1245019#M6569</link>
      <description>&lt;P&gt;Please provide comprehensive and step‑by‑step instructions for configuring a Palo Alto Networks PA- 450 Next‑Generation Firewall to maintain uninterrupted BSNL SIP trunk services in the event of a primary internet link failure. The BSNL SIP Trunk Server which is on cloud having a static IP of 117.198.215.109 &amp;amp; BSNL SIP trunk is presently bound to a static public IP 116.74.149.94, which is allocated to the primary internet circuit. The requirement is to automatically reroute all BSNL SIP traffic through the secondary internet circuit having static IP 117.139.107.109 whenever the primary link becomes unavailable, while retaining the static SIP source IP of the primary line.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 05:11:27 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-networks-pa-450-next-generation-firewall-to-maintain/m-p/1245019#M6569</guid>
      <dc:creator>pradip.joshi</dc:creator>
      <dc:date>2026-01-07T05:11:27Z</dc:date>
    </item>
    <item>
      <title>Re: Palo Alto Networks PA- 450 Next‑Generation Firewall to maintain uninterrupted BSNL SIP trunk services in the event of a primary internet link fail</title>
      <link>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-networks-pa-450-next-generation-firewall-to-maintain/m-p/1245086#M6572</link>
      <description>&lt;P&gt;For firewall to be able to keep same public IP after failing over to secondary link you need to own /24 or bigger public subnet (as /24 is smallest network you can advertise into public BGP) and you need to set up BGP peering with both ISPs and advertise out your public IP range.&lt;/P&gt;
&lt;P&gt;Without BGP peering you can't keep same public IP after failover to secondary ISP as even if ISP don't filter what source IP you send traffic into ISP 2, no traffic will be routed back to it.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2026 17:04:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/next-generation-firewall/palo-alto-networks-pa-450-next-generation-firewall-to-maintain/m-p/1245086#M6572</guid>
      <dc:creator>Raido_Rattameister</dc:creator>
      <dc:date>2026-01-07T17:04:37Z</dc:date>
    </item>
  </channel>
</rss>

