<?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 Using SIP-over-TLS phones behind CheckPoint firewall in General Topics</title>
    <link>https://community.checkpoint.com/t5/General-Topics/Using-SIP-over-TLS-phones-behind-CheckPoint-firewall/m-p/50069#M9855</link>
    <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;To your knowledge, is it possible to place a SIP phone behind a firewall and make it communicate with a SIP server (gateway, PBX) somewhere on Internet, while encrypting the SIP traffic by TLS (let's say, SIP control channel is over TCP)? Given that FW also works as a NAT gateway?&lt;/P&gt;&lt;P&gt;As I understand from &lt;FONT face="verdana,geneva"&gt;&lt;A href="https://sc1.checkpoint.com/documents/R80.10/WebAdminGuides/EN/CP_R80.10_VoIP_AdministrationGuide/html_frameset.htm" target="_blank" rel="noopener"&gt;VoIP Administration Guide&lt;/A&gt;&lt;/FONT&gt;, it's not possible. &lt;A href="https://help.fortinet.com/fos50hlp/54/Content/FortiOS/fortigate-voip-guide-52/ssl-tls.htm" target="_self"&gt;Unlike FortiGate&lt;/A&gt;, Checkpoint FW doesn't support TLS inspection (full man-in-the-middle) for SIP. But I may be wrong.&lt;/P&gt;&lt;P&gt;And without inspection, FW won't be able to interpret SIP signaling and open ports for outgoing or, especially, incoming RTP connections from the PBX to the phone.&lt;/P&gt;&lt;P&gt;Is my understanding correct? Has someone tried such configuration?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vladimir.&lt;/P&gt;</description>
    <pubDate>Sun, 07 Apr 2019 16:33:42 GMT</pubDate>
    <dc:creator>Vladimir_Ostrov</dc:creator>
    <dc:date>2019-04-07T16:33:42Z</dc:date>
    <item>
      <title>Using SIP-over-TLS phones behind CheckPoint firewall</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Using-SIP-over-TLS-phones-behind-CheckPoint-firewall/m-p/50069#M9855</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;To your knowledge, is it possible to place a SIP phone behind a firewall and make it communicate with a SIP server (gateway, PBX) somewhere on Internet, while encrypting the SIP traffic by TLS (let's say, SIP control channel is over TCP)? Given that FW also works as a NAT gateway?&lt;/P&gt;&lt;P&gt;As I understand from &lt;FONT face="verdana,geneva"&gt;&lt;A href="https://sc1.checkpoint.com/documents/R80.10/WebAdminGuides/EN/CP_R80.10_VoIP_AdministrationGuide/html_frameset.htm" target="_blank" rel="noopener"&gt;VoIP Administration Guide&lt;/A&gt;&lt;/FONT&gt;, it's not possible. &lt;A href="https://help.fortinet.com/fos50hlp/54/Content/FortiOS/fortigate-voip-guide-52/ssl-tls.htm" target="_self"&gt;Unlike FortiGate&lt;/A&gt;, Checkpoint FW doesn't support TLS inspection (full man-in-the-middle) for SIP. But I may be wrong.&lt;/P&gt;&lt;P&gt;And without inspection, FW won't be able to interpret SIP signaling and open ports for outgoing or, especially, incoming RTP connections from the PBX to the phone.&lt;/P&gt;&lt;P&gt;Is my understanding correct? Has someone tried such configuration?&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vladimir.&lt;/P&gt;</description>
      <pubDate>Sun, 07 Apr 2019 16:33:42 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Using-SIP-over-TLS-phones-behind-CheckPoint-firewall/m-p/50069#M9855</guid>
      <dc:creator>Vladimir_Ostrov</dc:creator>
      <dc:date>2019-04-07T16:33:42Z</dc:date>
    </item>
    <item>
      <title>Re: Using SIP-over-TLS phones behind CheckPoint firewall</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Using-SIP-over-TLS-phones-behind-CheckPoint-firewall/m-p/50101#M9863</link>
      <description>&lt;P&gt;The “&lt;A href="https://sc1.checkpoint.com/documents/R80.20_GA/WebAdminGuides/EN/CP_R80.20_VoIP_AdminGuide/html_frameset.htm?topic=documents/R80.20_GA/WebAdminGuides/EN/CP_R80.20_VoIP_AdminGuide/207829" target="_blank"&gt;Legacy Solution for SIP TLS Support&lt;/A&gt;” section describes solution, where all high ports are open for incoming traffic (so security is sacrificed for ability to use SIP signalling over TLS without inspection) – but how it’s supposed to work in NAT environment?&lt;/P&gt;&lt;P&gt;Let’s say, some phone behind the FW signalled to PBX that it’s ready to accept traffic on UDP port &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;12345&lt;/FONT&gt;&lt;/STRONG&gt; – but this signalling occurred over TLS, so it’s opaque for the FW.&lt;/P&gt;&lt;P&gt;When PBX will send RTP packets to public IP of the firewall and to port &lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;12345&lt;/FONT&gt;&lt;/STRONG&gt; – how can FW know, to which internal IP to forward these packets to?&lt;/P&gt;&lt;P&gt;The guide doesn’t explain this.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Apr 2019 08:31:56 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Using-SIP-over-TLS-phones-behind-CheckPoint-firewall/m-p/50101#M9863</guid>
      <dc:creator>Vladimir_Ostrov</dc:creator>
      <dc:date>2019-04-08T08:31:56Z</dc:date>
    </item>
    <item>
      <title>Re: Using SIP-over-TLS phones behind CheckPoint firewall</title>
      <link>https://community.checkpoint.com/t5/General-Topics/Using-SIP-over-TLS-phones-behind-CheckPoint-firewall/m-p/52873#M10530</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We got a response from CheckPoint support that such configuration isn't possible.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;CheckPoint FW can't inspect (by "lawful" MITM) SIP-over-TLS traffic, and without such inspection SIP won't work.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 08 May 2019 08:59:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/General-Topics/Using-SIP-over-TLS-phones-behind-CheckPoint-firewall/m-p/52873#M10530</guid>
      <dc:creator>Vladimir_Ostrov</dc:creator>
      <dc:date>2019-05-08T08:59:05Z</dc:date>
    </item>
  </channel>
</rss>

