Im having an issue once in a while my phones fails to reconnect or do the registration for no reason, I just reset the phone an is able to reconnect with no issues.
Why could cause this?
My ip phones are Fanvil X3S/X3SP
Any advice?
Phones constantly failing to the registration
SQLSTATE[HY000]: General error: 130 Incorrect file format 'featurecodes'
I don’t know whats going on here but I’ve had a dozen servers take a dump in recent weeks. There are different symptoms but the results are the same, namely that asterisk continues to run but the GUI is unusable. Once the server is rebooted for any reason it wont start back up again. Restoring snapshots doesn’t work either. Most have some error or other about the database. If I see a message about tampered files in the dashboard that seems to be the precursor to this.
In this particular case I can get to most of the modules in the GUI but if I try to edit an extension I get the error in the thread title. I’ve seen half a dozen different errors starting with SQLSTATE.
How can I go about diagnosing this? And are these machines salvageable at all?
Automate running and emailing of queue reports
Is there a way to do this? It can be a cron job if need be.
Outbound trunk call received on inbound group
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
SQLSTATE[HY000]: General error: 130 Incorrect file format 'featurecodes'
That particular error is indicating a corrupted file for table ‘featurecodes’. Is the error always the same, or does it vary for the same server? It might be indicating a disk failure. Then again, if it is happening on multiple servers at the same time, that would be a great coincidence.
Callers ID does not show phone number
Then you need to get the information from your provider about the exact configuration of caller id that they are using. They will need to tell you which specific caller ID scheme they are using. Once you get that info, you should configure DAHDI accordingly. You might also need to modify the answer delay, because caller ID is generally not transmitted immediately after the line starts ringing, but after the 2nd or even the 3rd ring.
SQLSTATE[HY000]: General error: 130 Incorrect file format 'featurecodes'
On this machine its always the same error. Each server has its own error.
Phones constantly failing to the registration
You will need to provide a lot more info about your setup. Is freepbx on the same network as your phones? If not, is either freepbx and/or the phones behind a NAT device.
SQLSTATE[HY000]: General error: 130 Incorrect file format 'featurecodes'
My guess… Disk failure. Maybe it is a coincidence that all servers started failing at the same time, but mysql file corruption would point to that. Can you check SMART statistics on the disk?
It could also be related to RAM failure, but given that featurecodes is a table that is not modified frequently, or even at all, my guess would be disk failure.
If you are performing regular database backups, you could try a database recovery, at least to be able to start FreePBX and then decide how to move on from there.
FreePBX 14 GUI very slow
How are the VM resources? Do you see any high CPU or I/O usage while trying to access the HTTP GUI?
Follow Me Ring Time doesn't work for cell phones
It is very probable that once the call goes out to the cellphone and the cellphone starts ringing, your trunk provider is signalling your FreePBX server and telling it that the call has been answered.
Are you by any chance using a POTS line, either through DAHDI or an FXO gateway for the call out to the cellphone?
Trunk Balance Module Issue
I haven’t so much as looked at this module in years. If time permits, I will take a quick look over the weekend, but you may be on your own to get things running.
FreePBX 14 GUI very slow
No, they’re not high. I remove a network interface that was going to be the SIP input and changed the other network interface back to DHCP and that seemed to fix most of the issues as it seemed to be waiting for DNS response. The dashboard and everything is responsive in the GUI now, but mail is not going out and on the dashboard Asterisk is stuck at system running for 8 min 43 seconds for over an hour now. Also Restapps did not restart on its own after a reboot.
FreePBX 14 GUI very slow
Still getting the bit about depreciated function in that module lines 67 and 76 while running debug
Follow Me Ring Time doesn't work for cell phones
Have you tried to enable confirm calls?
Trunk Balance Module Issue
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
SQLSTATE[HY000]: General error: 130 Incorrect file format 'featurecodes'
Sure enough, one of the drives in the NAS has failed. Will replace that and see if this keeps happening. Thanks.
Trunk Balance Module Issue
@lgaetz Forget the last post, I thought I had it working but I was reading the cdrs wrong. Still working on this…I’ll keep working away at this and update if I get it working but if you have time to check it out over the weekend or really just any time that would be great. I’d love to get it working. I’m sure it’s something simple.
I’ll post my full sip log later after I test some more.
How to create freepbx Distro instance on Google Cloud GCP
Try to follow the steps in this link:
If you have issue with the most current distro iso, then try this iso image should work
https://downloads.freepbxdistro.org/ISO/SNG7-FPBX-64bit-1805-2.iso
I tested this iso on a local VM that is VHD. (VMDK
may work as well https://cloud.google.com/compute/docs/images/importing-virtual-disks ) wit fixed size.
Make sure you create a service account and download the JSON file https://cloud.google.com/compute/docs/vm-migration/using-cloud-endure
Here is some more guide https://www.youtube.com/watch?time_continue=39&v=R9JDCRCro-s
If you manage to have the VM instance up and running I recommend making Snapshot. I had issue updating the FreePBX system from the web interface. I recommend logging into your system via SSH and run the update from there.
Issue Installing Lets Encrypt Cert
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.