Activity for Gernot
-
Gernot posted a comment on discussion General Discussion
Thanks a lot for letting me know! Sounds great that FreePBX finally runs on PHP 7.3. I will try out these instructions soon and will come back with the results here.
-
Thank you for pointing out the error in the documentation. I removed the incorrect sentence and referred to the more complete documentation on wiki.debian.org instead. I'd rather keep this documentation more general covering all different email providers, as there are many resources on the web anyway if users want to go further into details.
-
Unfortunately all the Raspbian Buster based images (including the 06-10-2019 image) no longer support the Pi 1 platform. If FreePBX 15 could run on PHP 7.3 it would have been possible to support all the Pi versions again, but PHP 7.3 support is not there yet so I took a compromise and shipped with PHP 7.0 in the end, for which I had to drop Pi 1 support. And I also didn't want the super-old PHP 5.6 any longer on a new image. Eventually Pi 1 support might return again in the future, but I cannot promise...
-
I checked this again with the latest 11-11-2019 image (see downloads page) and it works perfectly fine, for both chan_pjsip and chan_sip extensions. The workaround presented above is for an old image and not necessary any more.
-
I checked this again in the latest 11-11-2019 image (see downloads page) and it works perfectly fine, for both chan_pjsip and chan_sip extensions. The workaround presented above is for an old image and not necessary any more.
-
You can also find the details here: http://www.raspberry-asterisk.org/documentation/running-raspbx-from-an-external-usb-hdd-or-thumb-drive/
-
It's available as well now. The latest build Asterisk 16.6.1, which I just uploaded now has the Opus codec included.
-
Please try to install UCP from the edge track: fwconsole ma --edge upgradeall fwconsole ma --edge downloadinstall ucp fwconsole reload
-
Please run these commands on the console: apt-get install unixodbc fwconsole restart Only the beta version 22-09-2019 has this problem, I've fixed it already in the 06-10-2019 version. Somehow the unixodbc slipped through on the first build unfortunately.... Then concerning the edge track, I also noticed many issues of FreePBX 15 beta were resolved already but only the edge track has the fixes, they were not pushed to the stable track. I'm not sure if using the edge track by default is a good idea,...
-
Please try to set "Enable Module Signature Checking" to no in advanced settings, as described here: https://issues.freepbx.org/browse/FREEPBX-20559 Please let us know if this solves your problem.
-
Thank you very much for testing and reporting everything here. The raspbx-backup command is still there and works as usual. I did a small enhancement to this script so it detects the root partion size properly for the Buster image, where the root partition is specified by PARTUUID. Get the updated script as usual with: raspbx-upgrade I've tested the script again on Buster and it worked perfectly fine for me. Let me know if you still have issues with it.
-
I must apologize for the late reply on this. Chan_dongle is finally available for Asterisk 16 as well on the Stretch based images. Install with raspbx-upgrade install-dongle On the new Buster based image I provided everything for Asterisk 16 including chan_dongle, then backported everything to Stretch. So it's all there for Asterisk 16 on both versions.
-
The UCP module can be installed from the command line with these steps: fwconsole ma --edge upgradeall fwconsole ma --edge downloadinstall ucp fwconsole reload Concerning the "Apply Config" button not working, it has been reported before: https://issues.freepbx.org/browse/FREEPBX-20559 Alternatively use this console command instead of "Apply Config" which does the same: fwconsole reload Or set "Enable Module Signature Checking" to no in Advanced Settings, as the bug report above suggests.
-
The first image supporting the Pi 4 is finally available: http://www.raspberry-asterisk.org/downloads/beta-image/ Please try it and report any issues you might find here. I decided to move ahead and complete this image with PHP 7.0 instead of PHP 7.3, as it is still unclear when 7.3 support will be available.
-
Concerning the current status of RasPBX on the Pi 4: I've started to create a new image based on Raspbian Buster some time ago. It is almost finished, but FreePBX 15 does not run on PHP 7.3 which ships with Raspbian Buster. Theoretically we could use an older PHP version but they either reached EOL already or support will cease soon. So I decided to wait until the compatibility issues with PHP 7.3 have been sorted out. The current status can be seen here: https://issues.freepbx.org/browse/FREEPB...
-
It is unfortunately not possible to upgrade the Jessie based to the Stretch based image. Many changes had to be made in the Stretch image, and there are no automated scripts available to perform these changes in a running environment. Setting up the new image from scratch is the only option.
-
Yes this is true, I did not yet provide a package named asterisk16-chandongle. Therefore, it is currently necessary to use Asterisk 13 when chan-dongle is needed. But I am working on a new image based on Raspbian Buster, which will ship with Asterisk 16 and all the features we had previously. I will post again here in the forums once this image is ready.
-
It is usually firmware and kernel that is too old on those older images. You could try to take a newer image first, copy the contents of its FAT32 partition (which is mounted to /boot) to the older image. This usually makes the image boot. Then run all the upgrades afterwards.
-
It says the Pi 4 requires Raspbian 10 Buster, therefore it looks like a new image is required. there is no timetable on this yet.
-
I've successfully built and uploaded Asterisk 16. Install it with apt-get update apt-get remove asterisk13 apt-get install asterisk16 Please let me know your feedback, if it works fine or there are any problems. Thanks.
-
Unfortunately the whole process is still not fully automated, it is mostly manual work to build and test the image. Also building the Asterisk is not fully automated on my end.
-
The installation instructions can be found here: https://wiki.freepbx.org/display/FOP/Installing+FreePBX+14+on+Debian+8.8 If you only want Asterisk 16 it should be sufficient to take an existing RasPBX image, uninstall Asterisk 13 with apt-get remove asterisk13 and then follow the instructions above from "Install and Configure Asterisk" until and excluding "Install and Configure FreePBX". Maybe it works for you, but I cannot promise because every new version required some additional tweaks here and...
-
It's not yet in the repository, but I will have a look at it soon and then come back to you here.
-
Did you install the UCP (User Control Panel) module? If yes, you could try to uninstall it and reboot your Pi. The UCP module needs the node server running in the background on the Pi.
-
Yes exactly. If the versions are incompatible the module fails to load.
-
Thank you for your suggestion. I've added this to install-fail2ban, the new script is available through the regular updates.
-
There is only one patch included in the RasPBX build of Asterisk: https://sourceforge.net/p/raspbx/discussion/tutorials/thread/855b8b02/ I try to stay away from adding patches to the main build usually, because it is just too risky. But it is true that modules like chan_dongle or others have to be recompiled once in a while whenever the base Asterisk is built. There is a version check between Asterisk and the modules. Most of the time they are compatible, but sometimes modules have to be rebuilt...
-
Yes exactly. First of all to occupy less space on SD cards, and then all the modules would require regular updates, keeping your SD card busy with unnecessary writes.
-
The SwithPi module has been tested before by other users, see their report here: https://sourceforge.net/p/raspbx/discussion/general/thread/79cc8e84/ So far the SwitchPi team has neither released their hardware drivers with an open source licence, nor did they publish installation instructions along with their drivers. They only offer a modified version of RasPBX as a complete bundle. But maybe the situation changes one day...
-
Did you try to revert back to an older version of Asterisk? Maybe the problem is related to the latest version. Backups of old versions can be found in /var/cache/apt/archives/. Install these with dpkg -i <packagename>
-
Did you try to revert back to an older version of Asterisk? Maybe the problem is related to the latest version. Backups of old versions can be found in /var/cache/apt/archives/. Install these with dpkg -i <packagename></packagename>
-
Finally, with the help of Walter's amazing instructions, the Opus codec has found it's way into the RasPBX Asterisk build. With version 13.23.0 the codec_opus_opensource.so module is included in the asterisk13 package. Users get it automatically when upgrading a Stretch based image. When building the module I've also applied the experimental PLC patch to Asterisk. According to some user comments this patch might have undesired effects on other codecs. In case anyone has problems please report them...
-
It is basically possible to save the complete configuration using the Backup and Restore module and then restore it on another system. But as far as I know it only works as long as FreePBX versions are the same between the backup and restore machines. Also see this post: https://community.freepbx.org/t/backup-config-and-restore-on-new-server/43844 But eventually it might be possible to first upgrade FreePBX from 2.11 to 14, backup the configuration from there and then restore it on the new install...
-
It should basically also work on plain Raspbian, but eventually the script makes some hard-coded assumptions on partition sizes which might not fit for all Raspbian versions. So just go ahead and try it out, and of course you are welcome to adapt and modify the script to your requirements.
-
You can ignore this error message. The module bcm2708-rng is only required on the old Pi 1. Pi2 and later are not using this module (and also don't need it). The script has been made to work on all Pi models, but unfortunately shows the error message on newer versions.
-
The Pi 3B+ need the latest kernel and drivers, which is why the old images refuse booting. You have to first boot the older image on a Pi 1 or 2, update the image and then insert the card into the Pi 3B+.
-
Thanks for letting us know! The new version is finally on the repository.
-
Asterisk 13.22.0 is available, you can install it manually with: cd /tmp wget http://repo.raspbx.org/download/jessie/asterisk13_13.22.0-1_armhf.deb dpkg -i asterisk13_13.22.0-1_armhf.deb apt-get -f install fwconsole restart Please let me know if it works for you, then I will upload it to the repository.
-
I still could not find out why exactly some people have problems with the new version. it would be great if someone could help finding out more. It is possible to manually install the new version with: cd /tmp wget http://repo.raspbx.org/download/jessie/asterisk13_13.21.0-1_armhf.deb dpkg -i asterisk13_13.21.0-1_armhf.deb apt-get -f install fwconsole restart If you want to go back, reinstall the old version with: wget http://repo.raspbx.org/download/jessie/asterisk13_13.17.1-1_armhf.deb dpkg -i asterisk13_13.17.1-1_armhf.deb...
-
I've removed the new version and uploaded 13.17.1 again. However, anybody who already installed it will not get downgraded automatically. I still can't tell why the new version does not work. Eventually one has to reboot the Pi after installing it.
-
I'm verry sorry you had so much trouble with your setup. But I'm not sure if the new 13.21.0 version from the repository is really broken. It works nicely for me, phones are registering and calls work. But I wanted to mention that, just in case you should really get a broken package through an update, the previous versions are still there cached in /var/cache/apt/archives/. You can install these with dpkg -i <packagename>
-
Dnsmasq is also a DNS cache for Asterisk. Whenever the outside connection drops Asterisk runs into problems because it can no longer resolve DNS queries. This is where Dnsmasq jumps in. But if this is no concern for you, you can just deinstall the whole package.
-
Tftp is enabled by default for the FreePBX endpoint manager module, which uploads firmware and config files to /tftpboot for phones to download them through tftp. If you are not going to use the endpoint manager then you can safely disable tftp in dnsmasq.conf.
-
This is because you are using a Jessie based image and unfortunately I have not been able to update the Jessie version of Asterisk for some time now due to problems with the build environment. But I plan to have this fixed again and then finally update Asterisk for the Jessie images. I'll let you know as soon as a new version is uploaded.
-
Please try this new image: http://www.raspberry-asterisk.org/download/raspbx-04-04-2018.zip.torrent It is only available through torrent for today, and currently uploading. Please let me know if it finally works on your PI3+. If everything is fine I'll publish it on the website.
-
I will update the image soon to add support for the Pi 3+. As soon as it is available I'll come back here.
-
The silk codec is unfortunately no longer available with Asterisk 13, it only shipped with Asterisk 11 on older images.
-
The Asterisk Phonebook is a FreePBX module, you can install it from Module Admin in FreePBX.
-
Maybe you just selected the wrong editor when editing the crontab for the first time. Just call select-editor And choose your editor, maybe you want to use nano. Then run crontab -e again.
-
It seems like a simple thing, but somehow since Debian Stretch there does not seem to be a simple way to restart networking anymore, see https://www.reddit.com/r/debian/comments/7nw98g/seriously_restarting_network_interfaces/
-
The "Mail Queue" check on the dashboard has recently been added to FreePBX. To fix this issue edit the file /etc/exim4/exim4.conf.template and add the line queue_list_requires_admin = false To the section MAIN CONFIGURATION SETTINGS Then call update-exim4.conf Let me know if this fixes your problem.
-
The bugfix is uploaded, from now on raspbx-upgrade always calls apt-get dist-upgrade on each run. The script updates itself by calling raspbx-upgrade Thanks again for reporting this bug.
-
You are right, this is in fact a bug in raspbx-upgrade. When I wrote this script initially I wanted it to not update all the Raspbian packages every time it is being called, because most of the updates are not crtitical anyway and it only puts unecessary IO load on the SD card. So I decided it should only update all the packages whenever there is a new Asterisk version available. But with Rasbian Jessie the behavior already changed to update every time when it is being called. Unfortunately it is...
-
It is a standard process of the FreePBX startup scripts to change the permissions of all files. I recommend to put your files into a different directory than /etc/asterisk, maybe directly in /etc/alarm.
-
I have been using the fwconsole ma upgradeall command myself many times without problems on the latest stretch builds. Are you working with a Pi 3? I have been using Pi 1 and Pi 2 mainly, maybe it makes a difference.
-
It is not compiled it, because it has a conflict with voicemail file storage. The package you are referring to is from the Raspbian repositories and does not fit unfortunately.
-
Just follow the documentation: http://www.raspberry-asterisk.org/faq/#chansccp You have to disable chan_skinny otherwise chan_sccp won't load. Edit /etc/asterisk/modules.conf and add noload = chan_skinny.so Reload Asterisk and enter module show like chan_sccp on the Asterisk console. It should show a successfully loaded chan_sccp.
-
I've deleted the Star Communication outbound route from my test setup and it worked perfectly fine as expected, all calls were successfully routed through the other trunks after this. Maybe you did not click the red "Apply Config" button after deleting the outbound route? So far I cannot see any issue in the base image, it works fine when configured properly.
-
I've checked this, but the only explanation I have is you did not configure the outbound routes correctly. You have to configure at least one additional outbound route, e.g. with the "." as match pattern, and configure an additional trunk and use this as the destination trunk in your new route. The call to 1727xxxxxxx then uses your new route and trunk. In your case it looks like the call to 1727xxxxxxx tries the Star Communication testing trunk and then fails, because the outbound route was not...
-
Ok I see! I'll check this out soon and report back here.
-
Did you try to call a number 1727xxxxxxx, starting with 1727? This is not a toll-free number and is rejected by the star communication sip proxy. Could this be the reason for your problem? I have tested the trunk setup several times and it worked fine for me. However, I had to complete the basic Asterisk SIP setup first, configuring the public IP of my router there. If this is not the reson for your issues please explain in more details, I'm not sure if I understood exactly what changes you made...
-
This question should be asked at the FreePBX forums. If it does not work by just restoring the backup from the older version, you might need to boot the older image with FreePBX 13, restore your backup there, then upgrade to FreePBX 14 using the FreePBX upgrade module, then saving the backup again.
-
This question has been asked before: https://sourceforge.net/p/raspbx/discussion/general/thread/f44bba78/ You can have 2 dongles by first using the install-dongle script to set up the first dongle, then add the second one manually to /etc/asterisk/dongle.conf. Please have a look at the chan_dongle documentation on how to configure several dongles.
-
I assume you are using a Raspbian Jessie based RasPBX build, because the latest Stretch based version (raspbx-10-10-2017) already has nodejs installed. When I built this image I found the repository version was too old for FreePBX, therefore I also had to install from nodesource.com. Maybe you want to consider upgrading.
-
I forgot to mention that the kB_read and kB_wrtn numbers in iostat refer to the total amount of data since system statup. You should divide these numbers by the uptime days, to get the amount of data read/written per day. I have a test system here which writes to the card about 600MB / day. It would be good to see your numbers in comparison.
-
If you look into the repo, it has 13.14.1 on the stable Stretch branch. 13.17.2 is on the testing branch. It looks like the stable branch is not updated so often. Could we just take it from the testing branch without running into trouble?
-
I assume you are using the Chan_PJSIP stack? Can you try with Chan_SIP instead to see if this has the same problem?
-
To analyze this further you could run the top command and watch the IO-waiting percentage, which is the wa number in the %Cpu(s) line. Also watch the cpu usage of process named mmcqd/0 which manages the SD card. It is normal these numbers go up a little e.g. when opening the dash board, but they should be 0 or very low when the system is idle. If the IO-waiting number is very high often then this is mostly a hardware problem, unless you really have a lot of traffic through the SD card. How much read/write...
-
It is unfortunately not possible to upgrade a live RasPBX from Jessie to Stretch. The raspbx-upgrade command will keep Asterisk and all other programs on your system up to date, but it cannot move you to Stretch. There were many changes that had to be made to the image with the Stretch release, all this is not available as an automated process. You can save your FreePBX settings with the Backup and Restore module, then restore them on your new setup.
-
Did you configure at least one trunk that registers with a host on the internet? Because in this case the registration would be continuously renewed, keeping port 5060 on your router open in order to allow incoming calls. Your router usually allows connections to this port from other IPs, too. This could be a possible explanation for your observations.
-
You could try to reinstall Asterisk 13 with apt-get purge asterisk13 apt-get install asterisk13 Then press the red Apply button in FreePBX.
-
This is most likely a problem with your card. Please try a different one and also make sure it is correctly inserted.
-
The issue has been resolved, and there is a new image available on the download page. If you don't want to reinstall everything again, you can easily patch your image by replacing the contents of /etc/systemd/system/mkzram.service with: [Unit] Description=Enable compressed swap in memory using zram [Service] RemainAfterExit=yes ExecStart=/usr/sbin/zramstart ExecStop=/usr/sbin/zramstop Type=oneshot [Install] WantedBy=multi-user.target Then call systemctl disable mkzram.service systemctl enable mk...
-
Thank you for reporting this issue. Are eth0 and the services finally starting reliably after rebooting the image a few times, or is it a problem that appears once in a while on every boot of this image? I think I also saw this once but then the problem disappeared. I have added a known issue on the download page, and will report back here as soon as there is a fix.
-
The commands are all there: raspbx*CLI> core show help dongle dongle callwaiting -- Enable/Disable Call-Waiting on the dongle dongle cmd -- Send commands to port for debugging dongle discovery -- Discovery devices and create config dongle pdu -- Send PDU of SMS from the dongle dongle reload -- Reload dongle dongle remove -- Remove dongle dongle reset -- Reset dongle now dongle restart -- Restart dongle dongle show device settings -- Show Dongle device settings dongle show device state -- Show Dongle...
-
I've tested the Star communication trunk again with the latest beta image dated 18-09-2017 and it works fine. I had to configure the public IP in Asterisk SIP settings and I also forwarded SIP and RTP ports 5060 and 10000-20000 on my router. Other than that no further action was required.
-
The first beta image with FreePBX 14 is out, see: http://www.raspberry-asterisk.org/downloads/ I'm linking the download page here because I expect this image to go out of beta soon. It is a complete reinstall based on Raspbian Stretch with FreePBX 14 and Asterisk 13. Let me know your results here in the forums once you tried it, I'm looking forward to read your feedback!
-
Yes the config files in /etc/asterisk are still there but you can delete them and copy the files from /usr/share/asterisk/configs/, see http://www.raspberry-asterisk.org/faq/#configfiles Disabled FreePBX just means the config files are no longer overwritten by FreePBX.
-
I have just updated the asterisk13-chandongle package, using the latest code from https://github.com/wdoekes/asterisk-chan-dongle It shows Version 1.1, Revision 43gh=47cg
-
I am sorry for that. I have updated the asterisk13-chandongle package, it works again with the latest Asterisk version. Install it with apt-get update && apt-get dist-upgrade chan_dongle revision is Version 1.1, Revision 43gh=47cg, from https://github.com/wdoekes/asterisk-chan-dongle
-
Yes the described vulnerability is also contained in Asterisk shipped with RasPBX. The fixes have been published by Digium on August 31st, I will upload updated versions of Asterisk 11 and 13 by tomorrow. The iptables rule from the Nerdvittles article above does not apply to RasPBX, as it is a rule specific to the Nerdvittles releases. Nonetheless it is possible to eliminate or at least reduce exposure to this bug, by following these steps: If your RasPBX is behind a router with a private IP (which...
-
Please try to run fwconsole start and watch the output. Are you using an old Pi 1 model? We had issues in the past with fwconsole chown taking too long on the Pi 1.
-
Asterisk is started through systemd using the file /etc/systemd/system/freepbx.service. You could try to add After=network-online.target to the Unit section of this file, causing Asterisk to wait for network service before starting. If this does not help, a simple pause could be introduced by adding ExecStartPre=/bin/sleep 30 to the Service section.
-
Maybe you want to try a different tool to flash the image to your card, such as dd on Linux. We had issues in the past with Win32DiskImager failing to copy the image properly on some Windows machines, see also https://sourceforge.net/p/raspbx/discussion/bugreports/thread/029e42a2/#8f8c
-
The download server is finally back online.
-
Unfortunately I cannot provide an upgrade option for the whole image to the latest Raspbian version. But eventually it is possible to upgrade only FreePBX, in case the FreePBX developer team provides an upgrade module. Please check out the FreePBX website and forums concerning this.
-
Unfortunately the download server is currently down and I could not get it back up till now. Please use the Torrent download option for the time being.
-
I am still waiting for an official release of a new Raspbian based on Debian Stretch. Once we have this available a new image will be made based on Stretch, including the latest Asterisk and FreePBX stable LTS versions.
-
Did you follow this guide to disable FreePBX? http://www.raspberry-asterisk.org/faq/#asteriskonly Did you try to only disable FreePBX, but keep Apache enabled? In this case the sms webpage should still be there. Once you set up everything with FreePBX enabled you should still be able to use the sms feature with everything even after disabling FreePBX. Nonetheless, I'm not sure if you really gain much by disabling FreePBX, it won't change much on your power budget. Most of the power will be required...
-
I tried to follow this guide to find out if fstrim is really doing anything on my Pi: https://linuxnorth.wordpress.com/2014/03/18/trim-your-ssd-down-to-size/ Unfortunately the hdparm –read-sector command does not work on the Pi, but instead I used dd as a replacement. So hdparm –fibmap tempfile showed my file starts at sector 724992, then I've used dd skip=724992 if=/dev/mmcblk0 count=1 of=outf2 to read the first 512 bytes directly from disk. I could verify this is exactly the content of the tempfile....
-
In FreePBX click on Admin - Module Admin and then click "Check Online". Then install the "Parking Lot" module.
-
The newer images from 2016 do receive kernel updates with the regular raspbx-upgrade or apt-get dist-upgrade calls. Eventually you are running an older image from 2015, please call rpi-update to get a newer kernel.
-
Yes, the discard option is generally not advised because of performance penalties. Calling fstrim regularly seems to be the better option. But not all SD cards support it. And I also wonder why the official Raspbian image does not use it? They should get the same benefit. Also here is a user reporting corruption issues using fstrim: https://www.raspberrypi.org/forums/viewtopic.php?t=39864&p=327161
-
To answer your question: FreePBX introduced the dashboard scheduler with version 12, and this wrote lots of data to the Mysql database every minute. A patch was delivered to RasPBX users in autumn 2016 to run the scheduler only once every hour. Since then writes decreased considerably. I did some research on this topic over many months. I have an old Pi1 still running an older image. This unit runs on the same 4GB standard SD card for over 4 years now without problems. I've checked the numbers shown...
-
RasPBX ships with a limited set of FreePBX modules preinstalled, but most of the modules can be added through Module Admin, except for the commercial ones.
-
Could you please try this: Edit the file /etc/systemd/system/freepbx.service and change this line from ExecStart=/usr/sbin/safe_fwconsole start to ExecStart=/usr/sbin/safe_fwconsole --skipchown start Then reboot. This will considerably speed up boot time. I took an old Pi 1 with a class 6 SD card here and it showed the same problem, but not every time I rebooted, just once in a while. It looks like a timeout in the fwconsole script. But it is not clear to me what really causes the timeout, because...
-
This issue can be resolved with the following steps: 1. Edit extension 150 in FreePBX and change host from localhost to 127.0.0.1 in the advanced tab. Click the Apply Config button. 2. Edit /etc/iaxmodem/ttyI150 and change server localhost to server 127.0.0.1 Reboot. The problem has been described before: https://sourceforge.net/p/raspbx/discussion/general/thread/37e14c65/ Obviously an issue appeared with connecting to localhost through IPv6 at some point... I've fixed the add-fax-extension script...
-
I'm sorry for this bug. I've added the missing library and updated the repository, you can get the codec with: apt-get update && apt-get install asterisk13-codecg729
-
Does it start when you call fwconsole start ? Is this a Pi1 with a rather slow SD...
-
You need to call the number this way: +18004337300 The default trunk from the base...
1 >