We have noticed that port 443 https is alway's reachable for the webinterface of FreePBX Distro. This is not adjustable in sysadmin, only http port 80 is adjustable.
So changing port 80 into something else for security or bot search reasons is not giving the result we want. We can change our httpd config, but it would be nice if this is supported in sysadmin.
Hi, I'm using FreePBX 13.0.46 and have 'Hide Queue No Answer' set to 'NO' in Advanced Settings. However, in the add/edit queue pages I can't see the option on any of the tabs - am I being blind or where should the option be?
I am trying to switch my backup strategy to SSH (and SFTP) and no matter what I do, I can't get the backup Module to successfully backup to the server I set up. I have done all the copying of the keys and from the cli of the FreePBX box.
I can ssh to my backup server logged in as root and I am not prompted for a password.
I can ssh to the backup server with a user name (sftpd@x.x.x.x) and am not prompted for a password.
I am specifying the key that I used to set up the SSH keys, but here is what I get:
The only thing I have found is that if I su to Asterisk on the FreePBX box, and then try to ssh to the backup server, I am prompted for a Password - I read in one of the other posts that the backup runs as Asterisk.
It doesn't seem to matter what User Name I use - I assumed that the user name would be used to form the command ssh username@backupserver, but even if I change the name, the error message is the same.
Here are all my blanks:
hostname: x.x.x.x Port: 22 User Name: sftpd, asterisk, root, bob - doesn't matter Key: /home/asterisk/.ssh/id_rsa (and id_rsa.pub for a try) Path: ~/backups/BDC-CoLo
Does anyone have this working? If so, would you share what worked for you?
So we took a server and installed FreePBX distro with 13 on it. An initial web interface credential was created on this new installation.
To make the transition more smooth, the 2.11 was upgraded to version 13. A backup was made on the old system with the now upgraded to 13. The backup was then uploaded to the new FreePBX distro and restored.
Now the credentials which were initially created, and the ones brought over from the old installation no longer function.
I was able to get around this in the mean time by completely disabling the authentication.
I migrated my 6.12.65 test/internal system to 10.13.66 at the end of December, have applied all module updates since. I've just noticed that I'm not receiving any notification emails since that time. That includes voicemail notifications, voicemail pager notifications, backup notification, module update notification, etc. I've tested postfix and can successfully send a test email by telnetting to port 25 on localhost. There is nothing at all in the /etc/maillog since the start of the year (aside from postfix stopping and starting).
Suggestions on where to start troubleshooting this further?
Just got a support message back that says Asterisk 13.7 will be included one month after its release? I thought @tm1000 said it'll be soon after its release?? I need this working sooner......
I apologize if this is not the place to post this. I was not sure of the best spot.
I am reporting this just to report it as much as anything else.
I use FreePBX (official distro) in Amazon AWS by way of VM imports. This has worked fine for me for a year or more. V11 and V12 worked great but I am having some issue with V13.
I tested this several times and it seems that this is the case. If I do an import of a working VM on V13 with Asterisk 13 and I crank that puppy up I will see am Error in the web interface saying "cannot connect to asterisk". If I log into the CLI via SSH it also complains and asks that an FWCONSOLE command be run. Something like fwconsole -zend_fix I think. Once I do that Asterisk will come back to life but then I have all sorts of issues with the box from that point on.
Now if I do this same process with v13 but with Asterisk 11 everything seems to run just fine. So of course for now I am just using v13 with Asterisk 11.
Again just thought I would report this just in case it helps anyone or helps development (not sure if you guys care about AWS or not).
I'm running FreePBX 13.0.49 patched and up to date. After recent updates in the last week I have noticed that the Call Event Logging Search Not Working page is not longer working - is anyone else experiencing the same thing or is it local to our installation
I am testing this, the first time I installed this, there were no issues, until I installed the available updates, I tried to go back and do a clean install, still no difference.
Tried different browsers,like I said above, a clean install, clearing browser cache...
I know what the red box is an error of, it is the built in shopping cart system, and every page I go to it pops up for a few seconds and is really annoying. I have a picture attached. Any help would be much appreciative.
I have some sip-phones without support long and quality local ringtones (but these phones have g722 codec). And i have some custom g722 sound in FreePBX "System Recordings". It is possible to use these recordings as ringtones for these phones?
I am trying to get this working with the latest distro 10.13.66 and hopefully someone can steer me in the right direction. I have tried the above mentioned guide and scoured the internet.
In logger_general_custom.conf I have: queue_adaptive_realtime = yes queue_log_to_file = yes
I did not have the extconfig.conf file or the res_config_mysql.conf files, so I created them:
CREATE TABLE tablename ( id bigint(255) unsigned NOT NULL AUTO_INCREMENT, time varchar(26) NOT NULL DEFAULT '', callid varchar(40) NOT NULL DEFAULT '', queuename varchar(20) NOT NULL DEFAULT '', agent varchar(20) NOT NULL DEFAULT '', event varchar(20) NOT NULL DEFAULT '', data varchar(100) NOT NULL DEFAULT '', data1 varchar(40) NOT NULL DEFAULT '', data2 varchar(40) NOT NULL DEFAULT '', data3 varchar(40) NOT NULL DEFAULT '', data4 varchar(40) NOT NULL DEFAULT '', data5 varchar(40) NOT NULL DEFAULT '', created timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP, PRIMARY KEY (id), KEY queue (queuename), KEY event (event) ) DEFAULT CHARSET=utf8;
Nothing seems to work. I also tried using the dsn,tablename instead of the [general] context for the extconfig and res_config_mysql files. I restarted MySQL and reloaded Asterisk afterward. Does anyone know the trick to getting the queue_log into MySQL with the FreePBX distro? It would be really useful for queue status boards and reports.
I read about using MondoRescue here for online cloning and retoration. As I'm about to make the jump from 6.12.65-32 to the rev 10 track, it's very appealing to me to image before proceeding. I've had trouble with Clonezilla before, so I wanted to try something new.
But I can't seem to get yum to work with the Mondo repo. I cd to /etc/yum.repos.d and then wget ftp://ftp.mondorescue.org/rhel/6/x86_64/mondorescue.repo
but when I do yum update I get this error
[root@pbx3 yum.repos.d]# yum update Loaded plugins: fastestmirror, kmod Loading mirror speeds from cached hostfile ftp://ftp.mondorescue.org//rhel/6/x86_64/repodata/repomd.xml: [Errno 14] PYCURL ERROR 19 - "Given file does not exist" Trying other mirror. Error: Cannot retrieve repository metadata (repomd.xml) for repository: mondorescue. Please verify its path and try again [root@pbx3 yum.repos.d]#
Yet I can successfully wget the repomd.xml with no problems.
Does anyone have the monorescue repo working on the FreePBX Distro?
I have my PBXes set to do Automatic Updates each month, but this last upgrade didn't happen.
When I run the upgrade to go from 6.12.65-31 to 6.12.65-32 using the WebGUI it says the upgrade process successfully upgraded... but then it didn't. rebooted. same result.
So then I ran the upgrade using the Linux CLI... and it looked nothing happened... but then it stopped responding and I guess it did upgrade, because I rebooted and I saw the following:
Looking at the wiki (http://wiki.freepbx.org/display/PPS/FreePBX-Distro-6.12.65) it says on the last Distro: "FreePBX Distro 6.12.65-100 This will take your 6.12.65 version system to a 10.13.66-1 version and track. Please note 10.13.66 is the Current STABLE and 6.12.65 will be End of Life 12-31-15" Should I really be running 10.13.66 instead of 6.12.65?
I just upgraded from 6-12-65-32 to 10.13.66-1 (Freepbx 13). I'm noticing a problem with some of the System Admin links. Network Settings has Loading.... in the Network Interface and it appears stuck. Time Zone, was America/Vancouver however it is also stuck on Loading... with Server time: Not received. All the other menu options (Support, Storage, HTTPS Setup, etc.) all seem to load correctly. The Internet is working fine and timezone is correct, so it's not a big problem, I just like it to work.
So while installing the 64-bit Distro on some random computer I kept running into the dreaded "There was a problem configuring your network interface." error. Installing the 32-bit version worked fine. Just in case anyone else runs into a similar issue, try the other Distro. http://www.aslab.com/support/kb/172.html says up to 16G is fine on 32-bit Centos, so I'll stick with 32-bit.
Anyone know when/why I would use the 64-bit Distro?