SOLVED extensions couldn't be registered

Status
Not open for further replies.
OLO

OLO

New Member
May 5, 2017
28
1
3
Installed fusionpbx on RPI3, create some extensions, but no one could be registered by either cisco ip phone or softphone like zoiper. Don't know what reason, also couldn't find the answer from internet.
 
Last edited:
And with you providing so little information no one here will be able to help you either ;)
 
Sorry I don't know what I should give because I know a little about fusionpbx/freeswitch although having used elastix/freepbx more than ten yeas

My extension setting as below, can't find anything wrong, tried to register it via ip phone and zoiper, but always failed

upload_2017-5-30_11-0-51.png
 
Last edited:
EasyBB said:
Try with Yate Client with SIP debug on. See what error message you get.
Click to expand...

Thanks!

frustrated, try yate with freepbx extension, no problem at all, but still not successful with fusionpbx extension, debug always shows "timeout"
 
In the linux gui try:
Code: 
service fail2ban stop
I imagine you have got yourself banned if it is timing out.
 
Finally works after re-install system. Don't know what reason causes it, perhaps I used wrong instruction, the below instruction is correct.

apt-get update && apt-get upgrade -y --force-yes
apt-get install -y --force-yes ca-certificates
apt-get install -y --force-yes git
cd /usr/src
git clone https://github.com/fusionpbx/fusionpbx-install.sh.git
chmod 755 -R /usr/src/fusionpbx-install.sh
cd /usr/src/fusionpbx-install.sh/debian
./install.sh --use-switch-package-unofficial-arm
 
Last edited:
strange! all extensions can't register with server after reboot. also "service fail2ban stop", but nothing happened.

Log as below:

FreeSWITCH Started
Max Sessions [1000]
Session Rate [30]
SQL [Enabled]
2017-10-20 23:48:20.490553 [NOTICE] sofia_reg.c:448 Registering 1fad83f7-e77b-44c8-8ae1-606c488a2102
2017-10-20 23:48:20.490553 [ERR] sofia_reg.c:2447 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration with status Service Unavailable [503]. failure #2
2017-10-20 23:48:21.490560 [WARNING] sofia_reg.c:505 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration [503], setting retry to 30 seconds.
2017-10-20 23:48:52.610544 [NOTICE] sofia_reg.c:448 Registering 1fad83f7-e77b-44c8-8ae1-606c488a2102
2017-10-20 23:48:52.630540 [ERR] sofia_reg.c:2447 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration with status Service Unavailable [503]. failure #3
2017-10-20 23:48:53.610547 [WARNING] sofia_reg.c:505 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration [503], setting retry to 30 seconds.
2017-10-20 23:49:24.750558 [NOTICE] sofia_reg.c:448 Registering 1fad83f7-e77b-44c8-8ae1-606c488a2102
2017-10-20 23:49:24.750558 [ERR] sofia_reg.c:2447 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration with status Service Unavailable [503]. failure #4
2017-10-20 23:49:25.750540 [WARNING] sofia_reg.c:505 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration [503], setting retry to 30 seconds.
2017-10-20 23:49:56.850536 [NOTICE] sofia_reg.c:448 Registering 1fad83f7-e77b-44c8-8ae1-606c488a2102
2017-10-20 23:49:56.850536 [ERR] sofia_reg.c:2447 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration with status Service Unavailable [503]. failure #5
2017-10-20 23:49:57.850526 [WARNING] sofia_reg.c:505 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration [503], setting retry to 30 seconds.
2017-10-20 23:50:28.910541 [NOTICE] sofia_reg.c:448 Registering 1fad83f7-e77b-44c8-8ae1-606c488a2102
2017-10-20 23:50:28.990523 [ERR] sofia_reg.c:2447 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration with status Service Unavailable [503]. failure #6
2017-10-20 23:50:29.910536 [WARNING] sofia_reg.c:505 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration [503], setting retry to 30 seconds.
2017-10-20 23:51:00.970532 [NOTICE] sofia_reg.c:448 Registering 1fad83f7-e77b-44c8-8ae1-606c488a2102
2017-10-20 23:51:00.990555 [ERR] sofia_reg.c:2447 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration with status Service Unavailable [503]. failure #7
2017-10-20 23:51:01.990531 [WARNING] sofia_reg.c:505 1fad83f7-e77b-44c8-8ae1-606c488a2102 Failed Registration [503], setting retry to 30 seconds.
2017-10-20 23:51:32.050524 [NOTICE] sofia_reg.c:448 Registering 1fad83f7-e77b-44c8-8ae1-606c488a2102
 
Last edited:
I don't know what negative affects the arm switch may or may not have but it is no longer necessary to use it, the instructions on the fusionpbx home page should work just fine now.
 
Once rebooted, try restarting freeswitch again, perhaps freeswitch started before all the other services where ready.
 
DigitalDaz said:
I don't know what negative affects the arm switch may or may not have but it is no longer necessary to use it, the instructions on the fusionpbx home page should work just fine now.
Click to expand...

I have tried many times by instruction on http://wiki.fusionpbx.com/index.php?title=Raspberry_Pi_Script , but always got below:

Makefile:563: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/usr/src/freeswitch/src'
Makefile:3132: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/usr/src/freeswitch'
Makefile:1402: recipe for target 'all' failed
make: *** [all] Error 2
ERROR: FreeSWITCH Build Failure.
 
DigitalDaz said:
Once rebooted, try restarting freeswitch again, perhaps freeswitch started before all the other services where ready.
Click to expand...

after reboot, and "freeswitch" , then system show below :

Cannot lock pid file /var/run/freeswitch/freeswitch.pid.
 
What do you mean by after reboot and freeswitch?

You are not typing freeswitch on the command line are you?
 
DigitalDaz said:
What do you mean by after reboot and freeswitch?

You are not typing freeswitch on the command line are you?
Click to expand...

I did use the instruction on https://www.fusionpbx.com/download.php, installation successful, everything works well, but once reboot, encountered same: extensions and gateway failed to register .

afterwards I login in as root via ssh, and type " freeswitch", then got:

Cannot lock pid file /var/run/freeswitch/freeswitch.pid.
 
Freeswitch should already be running.

If not you start / restart with:
Code: 
systemctl restart freeswitch
or
Code: 
systemctl start freeswitch

Simply trying to run freeswitch as your logged in user will try and do it with the wrong permissions
 
OLO said:
I did use the instruction on https://www.fusionpbx.com/download.php, installation successful, everything works well, but once reboot, encountered same: extensions and gateway failed to register .

afterwards I login in as root via ssh, and type " freeswitch", then got:

Cannot lock pid file /var/run/freeswitch/freeswitch.pid.
Click to expand...
DigitalDaz said:
Freeswitch should already be running.

If not you start / restart with:
Code: 
systemctl restart freeswitch
or
Code: 
systemctl start freeswitch

Simply trying to run freeswitch as your logged in user will try and do it with the wrong permissions
Click to expand...

It works. my fusionpbx recovered! Thanks a lot, DigitalDaz!
 
Last edited:
Status
Not open for further replies.
Top Bottom