<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Local/Remote install & Security/Performance tradeoffs]]></title><description><![CDATA[<p dir="auto">I'm currently using a hosted FreePBX/asterisk server located in a data center somewhere; I have no physical access, but I do have shell (root) access to the box.</p>
<p dir="auto">I've installed FOP2 on the PBX host machine and all works well. Users access FOP2 from the business location... meaning that the FOP2 web sockets are going across the internet.</p>
<p dir="auto"><strong>QUESTION #1:</strong> Is this websocket traffic encrypted??? If not by default, can it be?</p>
<p dir="auto">Also, I've realized that anybody could use our machine to make calls by just guessing extension numbers and all numeric, typically very short, passwords. This is obviously terrible security...</p>
<p dir="auto"><strong>QUESTION #2:</strong> What is the normal setup in my situation (hosted, remote PBX)? Should I have installed FOP2 on a local server? But then the Asterisk API/REST calls would all be on the internet, right? Then, the same question about encryption arises...</p>
<p dir="auto"><strong>Bottom Line:</strong> What's the most secure way to set up a FOP2 for a remote Asterisk (FreePBX) box?</p>
<p dir="auto">Thanks in advance for any advice!</p>
]]></description><link>http://localhost:4567/topic/2616/local-remote-install-security-performance-tradeoffs</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 09:54:33 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/2616.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 04 Jan 2018 02:43:33 GMT</pubDate><ttl>60</ttl></channel></rss>