@mudslide567 wrote:
I installed latest and greatest FreePBX from SNG7 [asterisk 14.7.5). All good.
I tried to install DRBD using the RHEL repositories [kmod-drbd84.x86_64 8.4.11-1.1.el7_6.elrepo] which all seemed to work find until the “modprobe drbd” returns “Module drbd not found”.
This is usually a snap to install on Centos 7 systems. Has SNG7 done something to Centos 7 to prevent DRBD?
Posts: 1
Participants: 1
@alreilly wrote:
Warning: Cannot connect to online repository(s) (http://mirror1.freepbx.org ,http://mirror2.freepbx.org ). Online modules are not available.
Anyone else running into this issue today?
Posts: 1
Participants: 1
@esarant wrote:
Hello,
One of my installations has been hacked via dialplan and did unauthorized calls. Just to clarify there was no hack via HTTP or SSH since the FreePBX is not open to public internet.
Set original setup of the inbound route that has been used was:
InboundRoute -> Misc Destination -> Call to a number
So, this DID was used to “forward” the call to another number. This was the original setup.
What the hacker did was after he called the DID he, then, executed call tranfer (##) to transfer calls to another number. Also, he was able to setup speeddials via *75 as you can see:
asterisk -rx 'database show ampuser' | grep speeddials /AMPUSER//speeddials/ : /AMPUSER//speeddials/** : /AMPUSER//speeddials/0000 : 900442085350050 /AMPUSER//speeddials/1 : 900442085350050 /AMPUSER//speeddials/105 : 900442070871900The setting “Disallow transfer features for inbound callers” was set to No and the dial options were:
Asterisk Dial Options: trWw
Asterisk Outbound Trunk Dial Options: TWwHow can this happen? What does it need to be done so it wont happen again?
Running FreePBX 14.0.13.4 (SNG Distro 12.7.6-1904-1.sng7)
Regards,
esarant
Posts: 1
Participants: 1
@antonis77 wrote:
Hi,
Let’s talk about what you like or not FreePBX distro ?
- First i would like a way to uninstall a batch of commercial modules in case i don’t use them.
- Troubleshooting a call issue is difficult with over 50-100 lines in the verbose output.
- it would be nice if you had templates for different SIP providers.
What other things you like or not ?
Posts: 4
Participants: 4
@chemnic wrote:
I noticed a delay in shutdown and reboot with FreePBX distro in certain circumstances. After investigating I discovered that the problem is with httpd (apache). It won’t stop gracefully when I’m logged in the GUI.
FreePBX version:
$ cat /etc/schmooze/pbx-version 12.7.6-1904-1.sng7This is a testing environment in VM (Virtualbox and proxmox KVM). I have made tests with clean install (not even updated the system), with updates applied, with my configs applied (ansible), with a restore from the system in production. In all the cases the result is the same.
Steps to reproduce:
Login in the FreePBX GUI and stay logged in.
In the terminal (CLI) stop httpd (apache)
$ systemctl stop httpdThe command will take ~90 seconds to terminate.
This is the output of
journalctl -f -u httpd.serviceduring those 90 seconds:Oct 21 08:57:08 freepbx.sangoma.local systemd[1]: Stopping The Apache HTTP Server... Oct 21 08:58:38 freepbx.sangoma.local systemd[1]: httpd.service stop-sigterm timed out. Killing. Oct 21 08:58:38 freepbx.sangoma.local systemd[1]: httpd.service: main process exited, code=killed, status=9/KILL Oct 21 08:58:38 freepbx.sangoma.local systemd[1]: Stopped The Apache HTTP Server. Oct 21 08:58:38 freepbx.sangoma.local systemd[1]: Unit httpd.service entered failed state. Oct 21 08:58:38 freepbx.sangoma.local systemd[1]: httpd.service failed.If I start the service again and logout from the GUI, then the service takes ~2 seconds to stop, which I assume should be the normal behaviour.
I found nothing useful form apache logs. Not even with debug turned on. I can show you the logs if you want.
This is causing the VM to take ~1.5 minutes to shutdown, which is a problem for me.
Is this normal? One has to be logged out the GUI for the system to shutdown clean?
Posts: 1
Participants: 1
@dux wrote:
Hello, everyone. I have a FreePBX distro. How can I upgrade unixODBC to version 2.3.7 with yum? The current version is 2.3.1 Yum does not show any upgrade in the repository.
Posts: 1
Participants: 1
@WB3FFV wrote:
OK, I am thinking something got busted along the way, but just got asked why when you enter the company directory, it no longer gives you the default prompts on how to use it.
Sure enough, I called in and when you enter the directory from an IVR, it just sits there in silence, even though it is very much set to the default announcement. So then I went and tried it on my personal system as well, and sure enough it’s broken there as well. I tried rolling directory back a verson or two, but still no go.
I am running the current PBXact 12.7.6-1910-1.sng7 under Asterisk 13.27.1 as I made sure I was on the current release.
On the funny side, I tried to make a system recording and just put my own voice in as the prompt, but still I just get silence, so for some reason the directory module is not playing the initial announcement.
Any ideas or help would be great…
Posts: 2
Participants: 2
@jgiebler wrote:
Hello Community,
We were patching servers yesterday and noticed that directory browsing is available for the below 3 Sub directories of the “Admin” folder without authentication.
https://MyPbxServerAddress/admin/[modules | images | assets]
/var/www/html/admin/modules/ /var/www/html/admin/images/ /var/www/html/admin/assets/This seems like an unneeded security risk. Is there a reason for this? I found an old forum post from 2013 referencing this same issue but it appears to still exist. (Prevent browsing of FreePBX admin folder sub-directories)
As a quick work around, we executed the below lines of shell code on each server from SSH. They add an .htaccess file to the affected folders to stop allowing directory browsing. I have no idea if the .htaccess files will stay post whatever future updates.
echo "Options -Indexes" >> /var/www/html/admin/modules/.htaccess echo "Options -Indexes" >> /var/www/html/admin/images/.htaccess echo "Options -Indexes" >> /var/www/html/admin/assets/.htaccessHoping someone out there knows why these are left browse-able… especially without authentication.
Thank you
Posts: 4
Participants: 3
@johnjces wrote:
Ever since FreePBX version 14, maybe even 13, mostly in 14 and now in 15, currenlty FreePBX 15.0.16.27, I get an error after running gui updates that tells me to delete /dev/shm/yumwrapper/*. Well I do so and things sort of go along all happy, when you run “check for updates” it finds no updates which is correct as apparently it does install the updates. But when you check again you get this error to delete those files. If you don’t and you try to move on to say, Module Admin, you get a whoops. You have to delete those files.
This was so recurrent and a PITA that I stoppped doing any kind of system updates in Version14.
Why does this occur and why so frequently? I know I wrote about this on this forum months ago but really never got an answer much less a solution to prevent this issue.
1). Why does it occur?
2). What can I do to prevent it from occurring?
3). How long does it take before the CLI clears “Updates are Available. Run yum update… yada yada…”I am starting to wonder if it has something to do using the same browser for multiple boxes. One V15 box had no issue, but it is just getting set up. The one this error occurred on is online and running well. It was the first to get system updates this morning. The box that errored was the second.
Thanks for some answers and solutions.
John
Posts: 1
Participants: 1
@siili wrote:
After running sysadmin_update_system the web GUI broke. It looks like some PHP code was updated and requires PHP 5.4 but the system has only PHP 5.3. I ran:
On login in a shell it gives:
[Exception]
Unable to locate the FreePBX BMO Class 'Userman’A required module might be disabled or uninstalled. Recommended steps (run from the CLI): 1) fwconsole ma install userman 2) fwconsole ma enable usermanI ran:
fwconsole ma install userman --force
Updating tables userman_users, userman_users_settings, userman_groups, userman_groups_settings, userman_directories…Done
PHP Parse error: syntax error, unexpected ‘[’ in /var/www/html/admin/modules/userman/vendor/illuminate/support/helpers.php on line 359
Whoops\Exception\ErrorException: syntax error, unexpected ‘[’ in file /var/www/html/admin/modules/userman/vendor/illuminate/support/helpers.php on line 359
Stack trace:
- () /var/www/html/admin/modules/userman/vendor/illuminate/support/helpers.php:359
The offending line of code is “$result = []” and as far as I can tell, that syntax was deprecated with PHP 5.4. The system is at PHP 5.3.
amportal a ma list | grep framework
| framework | 13.0.197.8 | Disabled; Pending upgrade to 14.0.13.6 | GPLv2+ |
cat /etc/redhat-release
SHMZ release 6.6 (Final)
[edit]
cat /etc/schmooze/pbx-version
10.13.66-22
Regards,
David Koski
Posts: 1
Participants: 1
@bknv wrote:
Hello.
Help me pls, me need download .rpm asterisk verison 13.27, but i cannot search it…
Share link
Posts: 1
Participants: 1
@Flurd wrote:
On my test box I’ve configured bond0 to use eth1, eth2, eth3, and eth4 which all seems fine. I can see broadcast traffic on the bond0 interface but I cannot ping it or reach anything on it.
This is the configuration of bond0
DEVICE=bond0 Type=Bond NAME=bond0 BONDING_MASTER=yes BOOTPROTO=none ONBOOT=yes IPADDR=192.168.0.14 PREFIX=24 GATEWAY=192.168.0.1 NM_CONTROLLED=no BONDING_OPTS="mode=4 miimon=100 lacp_rate=1" ZONE=trusted DESCRIPTION="unset"This is eth1. I’ve not included the others because they only differ by NAME, DEVICE, and UUID
TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=yes IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME=eth1 UUID=e6f832db-45b2-46bb-b547-8481ea8c■■■■ DEVICE=eth1 ONBOOT=yes MASTER=bond0 SLAVE=yesThis is the output of ifconfig note that eth0 is intended to be a management-only port.
bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST> mtu 1500 inet 192.168.0.14 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::290:27ff:■■■■:■■■■ prefixlen 64 scopeid 0x20<link> ether 00:90:27:f4:■■:■■ txqueuelen 1000 (Ethernet) RX packets 704406 bytes 417374585 (398.0 MiB) RX errors 0 dropped 2454 overruns 0 frame 0 TX packets 32802 bytes 4179182 (3.9 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.13 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::290:27ff:■■■■:■■■■ prefixlen 64 scopeid 0x20<link> ether 00:90:27:f4:■■:■■ txqueuelen 1000 (Ethernet) RX packets 248314 bytes 47040406 (44.8 MiB) RX errors 0 dropped 14 overruns 0 frame 0 TX packets 47022 bytes 33023762 (31.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xf7d00000-f7d20000 eth1: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:90:27:f4:■■:■■ txqueuelen 1000 (Ethernet) RX packets 186295 bytes 71902948 (68.5 MiB) RX errors 0 dropped 2372 overruns 0 frame 0 TX packets 7012 bytes 894885 (873.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 17 memory 0xf7c00000-f7c20000 eth2: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:90:27:f4:■■:■■ txqueuelen 1000 (Ethernet) RX packets 25527 bytes 4198175 (4.0 MiB) RX errors 0 dropped 12 overruns 0 frame 0 TX packets 7762 bytes 993720 (970.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 18 memory 0xf7b00000-f7b20000 eth3: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:90:27:f4:■■:■■ txqueuelen 1000 (Ethernet) RX packets 144159 bytes 45285194 (43.1 MiB) RX errors 0 dropped 63 overruns 0 frame 0 TX packets 9094 bytes 1146779 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 19 memory 0xf7a00000-f7a20000 eth4: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST> mtu 1500 ether 00:90:27:f4:■■:■■ txqueuelen 1000 (Ethernet) RX packets 348425 bytes 295988268 (282.2 MiB) RX errors 0 dropped 7 overruns 0 frame 0 TX packets 8934 bytes 1143798 (1.0 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 16 memory 0xf7900000-f7920000 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 108404 bytes 632944935 (603.6 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 108404 bytes 632944935 (603.6 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0After starting a ping -I bond0 192.168.0.100 this is the output of tcpdump -nn -n -i bond0 ‘dst 192.168.0.100 or src 192.168.0.100’
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bond0, link-type EN10MB (Ethernet), capture size 262144 bytes 13:19:04.062467 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28 13:19:05.064409 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28 13:19:06.066422 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28 13:19:08.062459 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28 13:19:09.064421 ARP, Request who-has 192.168.0.100 tell 192.168.0.14, length 28A Wireshark trace on 192.168.0.100 shows the traffic is not reaching it. There’s no output from the tcpdump command when I try to ping 192.168.0.14 from 192.168.0.100. However, if I just do tcpdump -nn -n -i bond0 I can see ARP requests from other machines on the network so I know traffic is definitely reaching the interface.
PBXact saw the new interface and I have set it to the trusted zone but I can’t find a firewall log that might show what’s being blocked anyway.
So my question is, what am I missing to allow PBXact to use bond0?
EDIT: I rebooted PBXact and now bond0 is active but I can’t reach eth0. I’d like both interfaces to be available. I mainly want the LACP bond working for call traffic and the PBXact GUI so I have resilience on physical cables.
Posts: 1
Participants: 1
@ruben_p wrote:
12.7.6-1910-1.sng7
Fail2ban not ban anything,
2019-Dec-11 21:51:34] [freepbx_security.NOTICE]: Authentication failure for insisffndnndbfbtel from 95.127.155.2 [] []
[2019-Dec-11 21:51:54] [freepbx_security.NOTICE]: Authentication failure for insisffndnndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:12] [freepbx_security.NOTICE]: Authentication failure for insisffndnndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:18] [freepbx_security.NOTICE]: Authentication failure for insisffndnhndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:20] [freepbx_security.NOTICE]: Authentication failure for insisffndnhndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:22] [freepbx_security.NOTICE]: Authentication failure for insisffndnhndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:22] [freepbx_security.NOTICE]: Authentication failure for insisffndnhndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:23] [freepbx_security.NOTICE]: Authentication failure for insisffndnhndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:23] [freepbx_security.NOTICE]: Authentication failure for insisffndnhndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:23] [freepbx_security.NOTICE]: Authentication failure for insisffndnhndbfbtelhg from 95.127.155.2 [] []
[2019-Dec-11 21:53:36] [freepbx_security.NOTICE]: Authentication failure for insistelJjh from 95.127.155.2 [] []
[2019-Dec-11 21:53:49] [freepbx_security.NOTICE]: Authentication failure for Ehdj from 95.127.155.2 [] []
[2019-Dec-11 21:53:56] [freepbx_security.NOTICE]: Authentication failure for Hejdj from 95.127.155.2 [] []
[2019-Dec-11 21:54:02] [freepbx_security.NOTICE]: Authentication failure for Bfjdj from 95.127.155.2 [] []
[2019-Dec-11 21:58:19] [freepbx_security.NOTICE]: Authentication failure for insistel from 95.127.155.2 [] []
[2019-Dec-11 21:58:24] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:27] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:29] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:30] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:31] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:31] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:32] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:32] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:32] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:32] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []
[2019-Dec-11 21:58:32] [freepbx_security.NOTICE]: Authentication failure for insistelfbsbgb from 95.127.155.2 [] []fail2ban-client status
Status
|- Number of jail: 7
`- Jail list: apache-tcpwrapper, recidive, pbx-gui, apache-badbots, ssh-iptables, asterisk-iptables, vsftpd-iptables2019-12-11 22:23:52,528 fail2ban.server [25875]: INFO Changed logging target to /var/log/fail2ban.log for Fail2ban v0.8.14
2019-12-11 22:23:52,528 fail2ban.jail [25875]: INFO Creating new jail ‘asterisk-iptables’
2019-12-11 22:23:52,529 fail2ban.jail [25875]: INFO Jail ‘asterisk-iptables’ uses Gamin
2019-12-11 22:23:52,593 fail2ban.jail [25875]: INFO Initiated ‘gamin’ backend
2019-12-11 22:23:52,594 fail2ban.filter [25875]: INFO Added logfile = /var/log/asterisk/fail2ban
2019-12-11 22:23:52,595 fail2ban.filter [25875]: INFO Set maxRetry = 8
2019-12-11 22:23:52,597 fail2ban.filter [25875]: INFO Set findtime = 600
2019-12-11 22:23:52,598 fail2ban.actions[25875]: INFO Set banTime = 1800
2019-12-11 22:23:52,642 fail2ban.jail [25875]: INFO Creating new jail ‘pbx-gui’
2019-12-11 22:23:52,642 fail2ban.jail [25875]: INFO Jail ‘pbx-gui’ uses Gamin
2019-12-11 22:23:52,642 fail2ban.jail [25875]: INFO Initiated ‘gamin’ backend
2019-12-11 22:23:52,643 fail2ban.filter [25875]: INFO Added logfile = /var/log/asterisk/freepbx_security.log
2019-12-11 22:23:52,643 fail2ban.filter [25875]: INFO Set maxRetry = 8
2019-12-11 22:23:52,645 fail2ban.filter [25875]: INFO Set findtime = 600
2019-12-11 22:23:52,646 fail2ban.actions[25875]: INFO Set banTime = 1800
2019-12-11 22:23:52,651 fail2ban.jail [25875]: INFO Creating new jail ‘ssh-iptables’
2019-12-11 22:23:52,651 fail2ban.jail [25875]: INFO Jail ‘ssh-iptables’ uses Gamin
2019-12-11 22:23:52,651 fail2ban.jail [25875]: INFO Initiated ‘gamin’ backend
2019-12-11 22:23:52,652 fail2ban.filter [25875]: INFO Added logfile = /var/log/secure
2019-12-11 22:23:52,653 fail2ban.filter [25875]: INFO Set maxRetry = 8
2019-12-11 22:23:52,654 fail2ban.filter [25875]: INFO Set findtime = 600
2019-12-11 22:23:52,655 fail2ban.actions[25875]: INFO Set banTime = 1800
2019-12-11 22:23:52,682 fail2ban.jail [25875]: INFO Creating new jail ‘apache-tcpwrapper’
2019-12-11 22:23:52,682 fail2ban.jail [25875]: INFO Jail ‘apache-tcpwrapper’ uses Gamin
2019-12-11 22:23:52,682 fail2ban.jail [25875]: INFO Initiated ‘gamin’ backend
2019-12-11 22:23:52,683 fail2ban.filter [25875]: INFO Added logfile = /var/log/httpd/error_log
2019-12-11 22:23:52,683 fail2ban.filter [25875]: INFO Set maxRetry = 8
2019-12-11 22:23:52,685 fail2ban.filter [25875]: INFO Set findtime = 600
2019-12-11 22:23:52,685 fail2ban.actions[25875]: INFO Set banTime = 1800
2019-12-11 22:23:52,707 fail2ban.jail [25875]: INFO Creating new jail ‘vsftpd-iptables’
2019-12-11 22:23:52,707 fail2ban.jail [25875]: INFO Jail ‘vsftpd-iptables’ uses Gamin
2019-12-11 22:23:52,707 fail2ban.jail [25875]: INFO Initiated ‘gamin’ backend
2019-12-11 22:23:52,708 fail2ban.filter [25875]: INFO Added logfile = /var/log/vsftpd.log
2019-12-11 22:23:52,708 fail2ban.filter [25875]: INFO Set maxRetry = 8
2019-12-11 22:23:52,710 fail2ban.filter [25875]: INFO Set findtime = 600
2019-12-11 22:23:52,710 fail2ban.actions[25875]: INFO Set banTime = 1800
2019-12-11 22:23:52,718 fail2ban.jail [25875]: INFO Creating new jail ‘apache-badbots’
2019-12-11 22:23:52,718 fail2ban.jail [25875]: INFO Jail ‘apache-badbots’ uses Gamin
2019-12-11 22:23:52,718 fail2ban.jail [25875]: INFO Initiated ‘gamin’ backend
2019-12-11 22:23:52,719 fail2ban.filter [25875]: INFO Added logfile = /var/log/httpd/ssl_access_log
2019-12-11 22:23:52,719 fail2ban.filter [25875]: INFO Added logfile = /var/log/httpd/access_log
2019-12-11 22:23:52,720 fail2ban.filter [25875]: INFO Set maxRetry = 8
2019-12-11 22:23:52,721 fail2ban.filter [25875]: INFO Set findtime = 600
2019-12-11 22:23:52,722 fail2ban.actions[25875]: INFO Set banTime = 1800
2019-12-11 22:23:52,732 fail2ban.jail [25875]: INFO Creating new jail ‘recidive’
2019-12-11 22:23:52,733 fail2ban.jail [25875]: INFO Jail ‘recidive’ uses Gamin
2019-12-11 22:23:52,733 fail2ban.jail [25875]: INFO Initiated ‘gamin’ backend
2019-12-11 22:23:52,734 fail2ban.filter [25875]: INFO Added logfile = /var/log/fail2ban.log-20191204
2019-12-11 22:23:52,734 fail2ban.filter [25875]: INFO Added logfile = /var/log/fail2ban.log-20191201
2019-12-11 22:23:52,734 fail2ban.filter [25875]: INFO Added logfile = /var/log/fail2ban.log-20191210
2019-12-11 22:23:52,735 fail2ban.filter [25875]: INFO Added logfile = /var/log/fail2ban.log
2019-12-11 22:23:52,735 fail2ban.filter [25875]: INFO Added logfile = /var/log/fail2ban.log-20191207
2019-12-11 22:23:52,735 fail2ban.filter [25875]: INFO Set maxRetry = 20
2019-12-11 22:23:52,737 fail2ban.filter [25875]: INFO Set findtime = 86400
2019-12-11 22:23:52,738 fail2ban.actions[25875]: INFO Set banTime = 604800
2019-12-11 22:23:52,746 fail2ban.jail [25875]: INFO Jail ‘asterisk-iptables’ started
2019-12-11 22:23:52,756 fail2ban.jail [25875]: INFO Jail ‘pbx-gui’ started
2019-12-11 22:23:52,762 fail2ban.jail [25875]: INFO Jail ‘ssh-iptables’ started
2019-12-11 22:23:52,768 fail2ban.jail [25875]: INFO Jail ‘apache-tcpwrapper’ started
2019-12-11 22:23:52,781 fail2ban.jail [25875]: INFO Jail ‘vsftpd-iptables’ started
2019-12-11 22:23:52,791 fail2ban.jail [25875]: INFO Jail ‘apache-badbots’ started
2019-12-11 22:23:52,807 fail2ban.jail [25875]: INFO Jail ‘recidive’ started
Posts: 1
Participants: 1
@mvogel4949 wrote:
I’m looking to increase the moh file upload limit and I’m told I can alter the php.ini file. Could someone point me in the direction of where to locate this file in a FreePBX 14 distro? Thank you!
Posts: 8
Participants: 4
@johnjces wrote:
Just an FYI for whatever it is worth, but I did another 14 to 15 backup/restore. I upgraded the 14 Backup/Restore module to the Edge version, 14.0.10.10 and had the 15 Backup/Restore module also on the latest Edge version 15.0.8.77.
There were no runs no drips no errors and was pretty painless. EXCEPT and again, no voicemail settings were restored at all. No voicemail was enabled and no email address, no nohting when it comes to voice mail settings. I triple checked and ran another 14 backup and double checked that voicemail was selected in the backup and still no settings at all came over.
I also had the 14 backup backup the custom sounds (IVR announcements) and those did not restore to 15 again as well.
These are pretty minor, but if you have a bunch of email setups in one’s extensions, it can be pretty time intensive. Copying over the System sounds for the IVR is not big deal, BUT it would be cool if all this stuff could be backed up and restored.
Other than the above two issues, a piece of cake! Working pretty well but room for improvement!
Has this already been submitted to bug reports?
John
Posts: 1
Participants: 1
@dux wrote:
Hello, everyone.
can I upgrade PHP in freepbx distro? I would like to switch to PHP 7 from PHP 5. Is it safe for FreePBX?
Posts: 2
Participants: 2
@Aido21 wrote:
Hi,
I have a problem with updates sng-epel and sng-updatesLoaded plugins: fastestmirror, versionlock
Loading mirror speeds from cached hostfile
centos-base-source | 2.9 kB 00:00
centos-centosplus-source | 2.9 kB 00:00
centos-extras-source | 2.9 kB 00:00
centos-updates-source | 2.9 kB 00:00
sng-epel | 2.9 kB 00:00
sng-extras | 3.4 kB 00:00
sng-pkgs | 3.4 kB 00:00
sng-updates | 3.4 kB 00:01
sng-updates/7/x86_64/primary_d FAILED
http://sng7.com/os/7.6/updates/x86_64/repodata/4fe8f6973835a4a91d0b9bfac6433c1b3cbbdee589d8d82bc39c6db1661e0b8e-primary.sqlite.bz2: [Errno 14] curl#18 - “transfer closed with 6272116 bytes remaining to read”
Trying other mirror.
sng-epel/7/x86_64/primary_db FAILED
http://sng7.com/sng7/epel/repodata/20aeb851bd69f1273de3942f3a483287928a8daf01bf5e57cc0a42ef99d9d706-primary.sqlite.bz2: [Errno 14] curl#18 - “transfer closed with 7612718 bytes remaining to read”
Trying other mirror.
sng-epel/7/x86_64/primary_db FAILED
http://sng7.com/sng7/epel/repodata/20aeb851bd69f1273de3942f3a483287928a8daf01bf5e57cc0a42ef99d9d706-primary.sqlite.bz2: [Errno 14] curl#18 - “transfer closed with 7529334 bytes remaining to read”
Trying other mirror.
sng-updates/7/x86_64/primary_d FAILED
http://sng7.com/os/7.6/updates/x86_64/repodata/4fe8f6973835a4a91d0b9bfac6433c1b3cbbdee589d8d82bc39c6db1661e0b8e-primary.sqlite.bz2: [Errno 14] curl#18 - “transfer closed with 5774633 bytes remaining to read”
Trying other mirror.
http://sng7.com/sng7/epel/repodata/20aeb851bd69f1273de3942f3a483287928a8daf01bf5e57cc0a42ef99d9d706-primary.sqlite.bz2: [Errno 14] curl#18 - “transfer closed with 7284597 bytes remaining to read”
Trying other mirror.failure: repodata/20aeb851bd69f1273de3942f3a483287928a8daf01bf5e57cc0a42ef99d9d706-primary.sqlite.bz2 from sng-epel: [Errno 256] No more mirrors to try.
http://sng7.com/sng7/epel/repodata/20aeb851bd69f1273de3942f3a483287928a8daf01bf5e57cc0a42ef99d9d706-primary.sqlite.bz2: [Errno 14] curl#18 - “transfer closed with 7284597 bytes remaining to read”It looks like a problem with the connection… and it could be my isp’s problem but I cannot change it.
Is it possible to update them manually if I download them another way?
Posts: 1
Participants: 1
@dux wrote:
Hello, everyone!
Is it safe for FreePBX to update MariaDB to the latest version? I use FreePBX distro? The current MariaDB version is 5.5.6 which is old.
Posts: 1
Participants: 1
@azidhaka wrote:
Hi, I have moved asteriskcdrdb to the new database on the new host, but need help on configuring the connection in FreePBX.
From what i gather, Asterisk seems to be using ODBC to describe and connect to the current database on localhost. The configuration seems to be in /etc/odbc.ini
I’ve got asteriskcdrdb used in:
cel_odbc.conf
res_odbc_additional.conf
cdr_adaptive_odbc.confIf i am correct, i only need to update odbc.ini with the detauls of the new server. It’s contents are currenly:
[MySQL-asteriskcdrdb]
Description=MySQL connection to ‘asteriskcdrdb’ database
driver=MySQL
server=localhost
database=asteriskcdrdb
Port=3306
Socket=/var/lib/mysql/mysql.sock
option=3
Charset=utf8There is no user/password here, i guess ODBC connections are different from standard MySQL connections…
Do i need to install a plugin on the new MySQL server and can i connect to it over the network? I am not familiar with ODBC.FreePBX 13.0.197.21
Asterisk 13.29.2Thanks in advance!
Posts: 1
Participants: 1
@sorvani wrote:
Back in October, @lgaetz said this.
I’ve never looked at recompiling this tool, but the current version knows about the -k option, but says this.
Any chance of getting this a version compiled for TLS included? I ask first because, IMO making a feature request should be after a discussion if it is even feasible.
Looking at the project page, it doesn’t seem like it would be a big deal. The distro uses openssl already, does it not? The required package is libssl and should reside in openssl-devel which is in the sng-updates repo.
Posts: 5
Participants: 4
