Free PBX Setup Notes
This will be an ongoing log as I reinstate FreePBX in the lab. First thing to note upon installation of the OS is that the network IPV4 is disabled. You will need to access the following file:
nano /etc/sysconfig/network-scripts/ifcfg-eth0
(add these lines)
BOOTPROTO=static
ONBOOT=yes
IPADDR= <Your IP Address>
GATEWAY= <Your Default Gateway Address>
NETMASK= <Your Network Subnet Mask>
to enable the IPV4 pick up the dhcp service.
Still need to enable local SIP lines and build out transport.
Good video on FreePBX
https://www.youtube.com/watch?v=p3al27mMCAA
We are having trouble registering devices on the PBX however a website reminded me to check firewalls:
https://www.zoiper.com/en/support/home/article/19/Error%20408%20Request%20Timeout
The netgear router we are using has one built in. I had to use port forwarding to get around it. Now the first phone has registered.
First call placed on Dallas PBX between 1010 and 1563.
Exchange is good in Dallas no go on Ft. Worth box (not pulling IP).
Voicemail setup and functional for extension 1010 good test using * key to access.
Free PBX does need access to the internet to access certain modules.
------------------------------------------------------------------
Calls are limited and various phones are unable to register looking into ports:
Suggested disable data on androids and Iphones trying to connect to PBX on local Wifi.
****RESOLVED: Connection issues with multiple android phones. Disable mobile data on phones attempting to connect. Some phones are better than others at choosing the appropriate network for our lab. Older androids seem to choose the mobile data over a WiFi spot without internet access.*****
The Dallas Adtran Router is up! Once Ft. Worth is complete we can build out the T1 between them B8ZS/ESF!
The T1 is up between Dallas and Ft. Worth! Had to use a T1 crossover cable to get the 2 Adtrans to talk over the T1 directly.
I have now provisioned the Adtran Routers and can ping across the Networks! I have a breakdown of what I had to understand to make it work properly. I'll post it soon!
Ok I have to post my mistakes here too (no matter how obvious). I added additional network interface cards to the PBX. The server does not automatically activate them (ifconfig eth1 up) this causes the system to see them on boot but not show them on ifconfig retrieval. Remember to activate them manually.
The PBX needs to be activated to use the system admin console at a cost. For our lab we will be using this without the sysadmin console module.
nano /etc/sysconfig/network-scripts/ifcfg-eth0
(add these lines)
BOOTPROTO=static
ONBOOT=yes
IPADDR= <Your IP Address>
GATEWAY= <Your Default Gateway Address>
NETMASK= <Your Network Subnet Mask>
to enable the IPV4 pick up the dhcp service.
Still need to enable local SIP lines and build out transport.
Good video on FreePBX
https://www.youtube.com/watch?v=p3al27mMCAA
We are having trouble registering devices on the PBX however a website reminded me to check firewalls:
https://www.zoiper.com/en/support/home/article/19/Error%20408%20Request%20Timeout
The netgear router we are using has one built in. I had to use port forwarding to get around it. Now the first phone has registered.
First call placed on Dallas PBX between 1010 and 1563.
Exchange is good in Dallas no go on Ft. Worth box (not pulling IP).
Voicemail setup and functional for extension 1010 good test using * key to access.
Free PBX does need access to the internet to access certain modules.
------------------------------------------------------------------
Calls are limited and various phones are unable to register looking into ports:
Suggested disable data on androids and Iphones trying to connect to PBX on local Wifi.
****RESOLVED: Connection issues with multiple android phones. Disable mobile data on phones attempting to connect. Some phones are better than others at choosing the appropriate network for our lab. Older androids seem to choose the mobile data over a WiFi spot without internet access.*****
The Dallas Adtran Router is up! Once Ft. Worth is complete we can build out the T1 between them B8ZS/ESF!
The T1 is up between Dallas and Ft. Worth! Had to use a T1 crossover cable to get the 2 Adtrans to talk over the T1 directly.
I have now provisioned the Adtran Routers and can ping across the Networks! I have a breakdown of what I had to understand to make it work properly. I'll post it soon!
Ok I have to post my mistakes here too (no matter how obvious). I added additional network interface cards to the PBX. The server does not automatically activate them (ifconfig eth1 up) this causes the system to see them on boot but not show them on ifconfig retrieval. Remember to activate them manually.
The PBX needs to be activated to use the system admin console at a cost. For our lab we will be using this without the sysadmin console module.
Now working to get the Eth traffic onto the T1 to travel between locations.
Link on how to make recordings for the PBX:
ReplyDeletehttps://youtu.be/mc5pHaWf3Cc?t=5m42s
Connections are sluggish on the PBX. We suspect the Netgear Router is slowing them down. I am implementing the following:
ReplyDeletehttp://smallbusiness.chron.com/turn-off-spi-netgear-router-52558.html
to see if packets will now move faster across the router.
The Ft.Worth Box is now up and running pushed out to DMZ to help with load for testing.
ReplyDelete