Search results

The proxy setting controls your outbound traffic. Not inbound. Most providers expect inbound traffic on port 5060.

For inbound, it may matter, but all providers can automatically fail over to another IP if there is no response from the primary IP. You just need to set up your trunks to do so.

In your screenshot, you clearly disabled the REGISTER option. But you only need it when you set up a provider to use registration vs IP authentication. For IP authentication, it's ok to have no registration.

Does the server have a local IP? Set up your .env file to work with the local IP. Use your local IP instead of a domain. https://www.fspbx.com/docs/troubleshooting/error-419/

It made you run the command because it needed to update the file. It makes sense now. If we didn’t have an update for this file it wouldn’t have asked to do it.

We upgraded to php 8.4 and introduced web sockets in this update. Perhaps one of those required changes to that file. This won’t be happening often. Another possible cause is if you used git stash command before the update.

Check the logs and browser console for any errors. https://www.fspbx.com/docs/troubleshooting/retrieving-logs/

These records probably take up very little space unless we are talking about millions of them over a few years. Voicemails and call recordings take way more space on the hard drive where they are stored than their reference records in the DB. Call detail records can take up significant space...

You can use anything, but some devices will require manual provisioning. Grandstreams can be provisioned automatically as long as they have a template in the system. Aastras are way too old, and they can't talk to any modern provisioning servers unless you disable authentication (I highly...

Here is how to log in very easily: su postgres psql fusionpbx

I suggest you continue to run your script and perform a vacuum periodically. It's not enough to just delete records

In most environments that I had worked in, I ended up needing to set those values up. The hostname, too, if replication is involved.

Go to Fax Sent and delete it from there. Fax queue entries can't be deleted as of now

Here it is. You have an extra \ in your regex. "\(" That means match a literal opening parenthesis character "(" Should be like this ^9999(\d{11})$

This originates in your dialplan regex for your outbound route. It means your regex is missing a closing parenthesis somewhere.

I committed the fix for faxes.sent.list warning. Pleaase update again. For your other error, No outbound route found - you need to check your outbound routes. If you had removed the prefix, then it should have chosen your regular outbound route. I just tried sending both ways with a prefix...

Do you have a route with a 9999 prefix? It's used by default for all faxes. If not, remove the prefix from the fax server settings.

It has already been pushed.

@yaboc Thanks for reporting this. A fix has been pushed

@jdumais Freeswitch generates a separate CDR for each attempt. You need to find and count those.