@BlazeStudios Upload Local FreePBX to Cloud and Sync Between local FreePBX and cloud, If I make any changes in Local FreePBX , I want to Sync changes to Cloud Freepbx.
In another Brands Like Grandstream and Yeastar, I can access Local PBX from Cloud by activate Licence and when I make any changes to Cloud, it Sync to Local PBX.
The Idea here I install FreePBX on my local server, I want to make FreePBX on cloud and sync between them.
By this way I can make calls via cloud and local and sync any changes between them.
@BlazeStudios If I am not in the Local network, I can make calls via cloud from any where.
And sync CDR like call history, call record files to Local FreePBX
Yes, I get what the syncing does. Iâm just curious as to how you would jump between both. This does seem to be overkill for when not on the local network and need to reach the PBX.
@BlazeStudios, I understand from your answer the best solution for this, installing Advanced Recovery Module in the Local FreePBX and link it with Cloud FreePBX.
If I make any changes to local, it will sync to cloud FreePBX and the opposite is correct.
No, itâs not real time syncing back and forth. Itâs a backup/failover solution. Based on the details youâve provided so far you want real-time syncing but that isnât something FreePBX does. It is going to require to you to do your own solution. Then youâll need to solve how you connect between the two when youâre inside or outside the LAN.
Again, this seems to be overkill in order to use your PBX remotely.
If you work on another Brand Like 3CX ,Yeastar, Grandstream any one of them have a private cloud and you have image from local PBX on the cloud by activate license.
The idea have an image from Local PBX on the cloud Like 3CX,Grandstream, Yeastar.
Any one of them have a private cloud and you have image from local PBX on the cloud by activate license, If you make any changes on cloud it Sync to Local.
Ignore this statement âI can use both at the same timeâ.
There are three databases that need syncing, the easiest is the flatfile voicemail.conf. The second one is the MySQL/MariaDB storage that is used for CDRâs and configuration, the configuration is easy to âsyncâ using standard mysql master/slave or master/master procedures but you will need to build a trigger to commit any changed tables which âpushesâ the GUI changes to the /etc/asterisk/*.conf files and then reload the Asteerisk dial-plan, the CDRâs can be written to many âbackendsâ
Perhaps the hardest thing you will encounter is the sqlite3 database that maintains the âstateâ of the asterisk instance, this can only be safely synced through the asterisk âdatabaseâ calls, or a complicated and unsupported by FReePBX network sync.
Making this all bi-directional increases your challenges a lot.