NEW iPBX 2027 Product Lineup

[wardmundy]

Incredible PBX 2027 Solutions - Out of the Box​

• Incredible PBX 2027 for Linux Containers LXC
• Incredible PBX 2027 for Mac UTM
• Incredible PBX 2027 for Proxmox
• Incredible PBX 2027 for VirtualBox
• Incredible PBX 2027 for VMware
• Incredible PBX 2027 for Windows11 WSL
• Incredible PBX 2027-U for CrownCloud
• Incredible PBX 2027 for Raspberry Pi
• Incredible PBX 2027 for Debian 11
• Incredible PBX 2027 for Ubuntu 22.04
• Incredible PBX 2027 for Rocky 8 & AlmaLinux 8

 

[dhoppy]

Is a "go public" version still in the works for IPBX 2027?

 

[wardmundy]

Is a "go public" version still in the works for IPBX 2027?

Not yet available. Sorry. Still assessing consequences of recent FreePBX compromise. OpenVPN is safest course for remote users.

 

[Samot]

Not yet available. Sorry. Still assessing consequences of recent FreePBX compromise. OpenVPN is safest course for remote users.

The bug in the OSS code has been addressed, the other reported issues are within commercial modules which aren't used in IPBX.

 

[dicko]

The elephant in the room has always been listening on UDP/5060, until this is addressed then it won't be a safe "public" voip server. If anyone has experienced a compromised server requiring a TLS certificate un-associated with the FreePBX GUI, please let me know.

 

[wardmundy]

The elephant in the room has always been listening on UDP/5060, until this is addressed then it won't be a safe "public" voip server. If anyone has experienced a compromised server requiring a TLS certificate un-associated with the FreePBX GUI, please let me know.

Our PUBLIC implementations require (hopefully obscured) FQDN access to SIP resources. That appears to be holding... knocking on wood.

But TLS and/or OpenVPN would be even better.