![freepbx server freepbx server](https://i1.wp.com/techridez.com/wp-content/uploads/2020/08/Outline_OwnVPNServer.png)
Choose “Add New Chan_PJSIP Extension” and click Submit.This will let you add the extensions for your phones.
![freepbx server freepbx server](https://net.cloudinfrastructureservices.co.uk/wp-content/uploads/2021/08/asterisknow-freepbx-asterisk.png)
You must separately configure the phones themselves to connect to your PBX, either by configuring the phones manually, or by using the Endpoint Manager Module. Note that this module only configures FreePBX and Asterisk.
FREEPBX SERVER PASSWORD
In this module, you’ll create an extension number and set a password for each extension and set-up voicemail (if desired).
![freepbx server freepbx server](https://www.liventerprise.com/pics/tools/FreePBX.jpg)
NOTICE: chan_sip.c:29722 sip_poke_noanswer: Peer '283' is now UNREACHABLE! Last qualify: 1004 NOTICE: chan_sip.c:29722 sip_poke_noanswer: Peer '293' is now UNREACHABLE! Last qualify: 14 NOTICE: chan_sip.c:29722 sip_poke_noanswer: Peer '292' is now UNREACHABLE! Last qualify: 1010 NOTICE: chan_sip.c:23715 handle_response_peerpoke: Peer '253' is now Reachable. NOTICE: chan_sip.c:23715 handle_response_peerpoke: Peer '249' is now Reachable. NOTICE: chan_sip.c:23715 handle_response_peerpoke: Peer '229' is now Reachable. NOTICE: chan_sip.c:23715 handle_response_peerpoke: Peer '242' is now Reachable. NOTICE: chan_sip.c:23715 handle_response_peerpoke: Peer '284' is now Reachable. My freepbx logs are non stop showing phones/peers becoming lagged, unreachable and then reachable again but only for the peers on VLAN200. GATEWAY=192.168.2.16 <-NOTE: This is our SIP TrunkĮTH0.200 = VLAN200 (Inside same building as LAN)ĮTH0.250 = VLAN205 (Outside building connected via IPSec Tunnel) Also, Network Manager is not installed on the server. VLAN205 is in a separate building (connected via IPSec Tunnel). VLAN200 is inside the same building as the LAN.
FREEPBX SERVER FREE
The phones are on their own vlan as I don't have enough free IP's to keep them on the same internal IP schema. I'm having a routing issue I can't figure out. I have a freepbx based (XorCom) server running on CentOS 6.7