TIPS Public Facing patch for Raspberry Pi 2021?

[infinitive]

Hi, am trying to see if its possible to do a public facing setup on the Raspberry Pi IPBX 2020 currently.
I tried the latest 2021 public facing patch unsure if it would work on the Raspberry Pi IPBX build as it states its for 2021 on Debian but it gave this error:
"GO-PUBLIC install requires Incredible PBX platform. Exiting..."

I knew it would be iffy it would work as is like this but is there some other way to get this public facing patch applied to the IPBX 2020 build for the Raspberry Pi?
Dynamic IP's changing often can really be annoying trying to maintain extensions staying online while using smartphones with the IP's changing often so this would be perfect if doable vs resorting to using a VPN on said smartphones.

Also a bit off topic but maybe related enough to ask here, is there a 2021 IPBX version for the Raspberry PI planned on being released in the future? I saw recently a post about this here https://nerdvittles.com/moving-from-incredible-pbx-2020-to-2021-on-the-raspberry-pi/ and it mentioned in another thread that people have been using this without much/any issues so I'll be doing this tonight and testing the public patch afterwards crossing fingers it works, will update the thread on progress for this.

Thanks for any input and /or help on these questions, the time volunteered and put into all this is much appreciated!

 

[infinitive]

Was very pleased to see the raspberry pi get that IPBX 2021 update support and I've since installed the raspberry pi 2020 to 2021 upgrade script & restarted the raspberry pi since & attempted to run the 2021 public facing patch but it resulted in the same error as when I tried before on IPBX 2020 for the raspberry pi.

"GO-PUBLIC install requires Incredible PBX platform. Exiting..."

I tried searching around for anyone else attempting this on the raspberry pi to see if any information might be out there to help make this possible but couldn't find anything.
Does anyone know of a way to make this work and if not does anyone know if the raspberry pi will get an update script to make this work in the future?

Even if I have to manually go through and do what the script would normally do automatically for this setup I wouldn't mind putting that extra work in to get this working I just would need a bit of guidance from someone kind enough to explain on what and where to edit / change to make this work.

 

[rob92]

If you are sure fail2ban is working and all your SIP passwords are secure... all you need to do is edit your iptables config and open up port 5060, 5061 for TCP & UDP. Port 10000-20000 UDP should already be open for anyone for RTP traffic but if it's not you will need to open those too if you have issues with no or one way audio.

 

[hawk#1]

you should also read the tutorial on Nerdvittles. https://nerdvittles.com/morphing-incredible-pbx-into-a-public-facing-cloud-pbx/. the tutorial was written by Ward, the person that generously provides us with all the IncrediblePBX features, installations, scripts etc. You may find the information useful since you will need to do more than just open up ports as the person suggests in the post above. Hope you find the tutorial helpful and you may find others there to be informative also

 

[infinitive]

Thank you both for your posts which directed me to that new article/tutorial put out by the great Ward himself, he's truly too kind with sharing his knowledge and I really appreciate it.

I'm going to take a crack at this again this week on the Raspberry, if I'm successful or not I'll update the thread about it for others to know. Just from looking over the tutorial, it looks like I'm going to be successful this go with this information & I'm very excited about that!

 

[rob92]

Since you are on Raspberry Pi make a full disk image of the SD card. If anything goes wrong you can also revert back.

Also since you are on Raspberry Pi presumably you are behind NAT which besides tending to be problematic also requires further configuration of your router. Setting up with VPN might be best, especially if you are using a phone such as Yealink or Sangoma that has built in VPN client.

 

[hawk#1]

Thank you both for your posts which directed me to that new article/tutorial put out by the great Ward himself, he's truly too kind with sharing his knowledge and I really appreciate it.

I'm going to take a crack at this again this week on the Raspberry, if I'm successful or not I'll update the thread about it for others to know. Just from looking over the tutorial, it looks like I'm going to be successful this go with this information & I'm very excited about that!

Lots of tutorials on Nerdvittles. May I suggest you upgrade to IPBX 2021 for raspbian before you try to go public facing. Make a good disk copy (image) after upgrading to 2021 also if you haven't done so already, so you can quickly get back to a normal (non public) but working pbx real quick just in case something goes wrong (better safe than sorry). Hope you have success getting your IPBX public facing.

 

[wardmundy]

Really, really, really not designed for any platform that is not directly on the public Internet with a static IP address. That's why you're getting an error attempting to use it with a RasPi which we are assuming doesn't meet these requirements. Spend the $10/year on a cloud-based server if you want to go PUBLIC.

 

[hawk#1]

@wardmundy
your experience is way beyond mine, what tipped you off that he is not using a static ip?

 

[infinitive]

I think the presumption here is that Raspberry PI's, in general will be mostly all running from home and on a non-static IP as that is the most common type of internet connection for homes and for most I'm sure this is the case. But In my case I paid extra for a block of static IP's from my ISP and have 1 that I dedicated for this Raspberry Pi.

 

[hawk#1]

I think the presumption here is that Raspberry PI's, in general will be mostly all running from home and on a non-static IP as that is the most common type of internet connection for homes and for most I'm sure this is the case. But In my case I paid extra for a block of static IP's from my ISP and have 1 that I dedicated for this Raspberry Pi.

I was trying to figure out what I might have missed that indicated a non static IP. I wish people would realize that numerous people who use a Raspberry Pi, actually use static IP's also. I also have paid for static ip's from my isp and dedicated one for my Raspberry PI.