Search results

I was mistaken, I thought you said, 'I' created inbound routes, didn't read properly.

"I created an inbound destination with one of my trunks. Then (as it suggested), it created inbound routes accordingly" Yes, destinations is a tool to create inbound routes.

With regards to why destinations, the reason is security. You can give access to destinations to a domain admin but giving access to inbound routes creates problems, they could potentially break the server.

Destinations create the inbound route for you. Where do you see in the documentation that it says to do both?

Sorry, in that case I have no idea.

Click the tab key to move it to the ok

Just keep the local, no idea why it wants to change that file

Yes, I just did: mv /etc/cron.daily/fusionpbx-backup /etc/cron.daily/fusionpbx-backup.conf Now when I do the run parts, the backup of the db does not happen

It would appear, in the latest version that it actually DOES run. I was unaware oif this and certainly do not want a db backup every night on the same box :) You can test it running by: run-parts /etc/cron.daily I think in older version, the file had a suffix, like .conf or something and...

Something along the lines of this in crontab: 0 2 * * * /usr/bin/find /var/lib/freeswitch/recordings/*/archive -type f -mtime +90 -exec rm -rf {} \;

create them a custom php page if necessary to set that var

That var should definitely be accessible at that point, you may need to export it to other legs to ensure it gets passed along

It may help you to call the application "info" in your dialplan for debugging purposes, this will dump all the vars available to you in the cli/log.

Far from dead :)

AWS Route53 and healthchecks

On the linux command line do an iptables -L -n See if the ip is listed there.

It depends on your traffic, how many channels do you need?

We've been replicating cross datacenter for years, first using bdr, now moved to pglogical, and @markjcrane now has his own solution using wal to json that is a recently released member feature, I haven't tested that one yet but have no reason to believe it won't be has good as the bdr one was...

I believe its purpose is just to improve the accuracy of the cdr reporting. That for example marks the call as outbound.

If you are running it in tmpfs there is no need to delete anything, it went when the reboot happened