I installled the older FreePBX 13, with asterisk 13 ISO . The implication on this page is that it should work but author later eludes to Incredible PBX, so it is not that clear ,and he does not approve or answer my question.
maybe he likes to misuse the name “FreePBX” to get people over to"incrediblePBX", not sure.
after gvsip-naf install,
I have installed a trunk that I had working in Incredible PBX simply by copying and pasting the config. Tried it in pjsip_custom.conf and pjsip_custom_post.conf . “pjsip show registrations” does not show it at all.
That is up to the trademark owner and how they want to enforce the trademark. CentOS (actually RedHat) forces one to not use the CentOS name if its a fork, this wasn’t always the case but it is now. This is why we have “SangomaOS”. Otherwise we’d call it what it is, CentOS.
As for IncrediblePBX. Looking at the screenshots he keeps FreePBX in the footer so he is complying with our legal agreements in using FreePBX, which is basically if you use FreePBX you must keep Sangoma Technologies and FreePBX in the footer and also not remove the copyrights.
If the footer copyrights are removed then legal action can be pursued.
He also hasn’t changed really any code except getting rid of module signing. So he can still call it FreePBX (if he wants). This is more of a SOFT fork. He’s re-branded areas that we are fine with rebranding while still leaving the copyrights in place. Thus he is not violating anything.
An example of a HARD fork would be something like Issabel. They forked FreePBX at version 2.11. They do not provide fixes of any kind back to the FreePBX project. They have renamed all occurrences of FreePBX to Issabel. This is also legal according to the terms of the GPLv3 license. Which is the base license for FreePBX.
still working with this on FPBX ISO
These are the errors I have in the asterisk log . Maybe someone can shed some light
[2018-07-27 19:26:40] WARNING[30688] res_pjsip/config_auth.c: Unknown authentication storage type ‘oauth’ specified for auth_type
[2018-07-27 19:26:40] ERROR[30688] config_options.c: Error parsing auth_type=oauth at line 19 of /etc/asterisk/pjsip_5052222222.new.conf
[2018-07-27 19:26:40] ERROR[30688] res_sorcery_config.c: Could not create an object of type ‘auth’ with id ‘5052222222’ from configuration file ‘pjsip.conf’
[2018-07-27 19:26:40] ERROR[30688] res_pjsip/config_transport.c: Transport ‘0.0.0.0-tls’ could not be started: Address already in use
[2018-07-27 19:26:40] ERROR[30688] res_sorcery_config.c: Could not create an object of type ‘transport’ with id ‘0.0.0.0-tls’ from configuration file ‘pjsip.conf’
[2018-07-27 19:26:40] ERROR[30688] res_pjsip/config_transport.c: Transport ‘127.0.0.1-tls’ could not be started: Address already in use
[2018-07-27 19:26:40] ERROR[30688] res_sorcery_config.c: Could not create an object of type ‘transport’ with id ‘127.0.0.1-tls’ from configuration file ‘pjsip.conf’
[2018-07-27 19:26:40] ERROR[30688] res_pjsip/config_transport.c: Transport ‘198.15.100.61-tls’ could not be started: Address already in use
[2018-07-27 19:26:40] ERROR[30688] res_sorcery_config.c: Could not create an object of type ‘transport’ with id ‘XXX.XXX.XXX.XXX-tls’ from configuration file ‘pjsip.conf’
[2018-07-27 19:26:40] ERROR[30688] config_options.c: Could not find option suitable for category ‘5052222222’ named ‘outbound_registration’ at line 43 of /etc/asterisk/pjsip_5052222222.new.conf
[2018-07-27 19:26:40] ERROR[30688] res_sorcery_config.c: Could not create an object of type ‘endpoint’ with id ‘5052222222’ from configuration file ‘pjsip.conf’
[2018-07-27 19:26:40] ERROR[30688] config_options.c: Could not find option suitable for category ‘5052222222’ named ‘support_outbound’ at line 10 of /etc/asterisk/pjsip_5052222222.new.conf
[2018-07-27 19:26:40] ERROR[30688] res_sorcery_config.c: Could not create an object of type ‘registration’ with id ‘5052222222’ from configuration file ‘pjsip.conf’
from what I understand FreePBX generates transport=0.0.0.0-tls as seen in the thread here
But that does not seem to be recognized as the IncrediblPBX GVSIP - NAF has this entry that I commented out (and everything else)in pjsip_custom.conf
; [transport_tls]
; type=transport
; protocol=tls
; bind=0.0.0.0:5061
I put in pjsip_custom_post.conf and as it loads after pjsip.conf starts with continuing the [global] section
This is an IncrediblePBX issue as it uses it own version of installs for FreePBX/Asterisk. We have no clue what has been done in his code or setup processes. As well, since it’s not a “FreePBX Distro” it doesn’t have the stuff for System Admin. I’m not 100% sure that the install does the ZendGuard Loader and other installs since it is meant to run on various OS systems.
So once again it is not a solution for your desires to have GVSIP+FreePBX AND use the FreePBX System Firewall. It’s just not.