Freeswitch Failing on no Primary Key

[mydigitalself]

Good Afternoon All,

I am in the process of testing a replicated setup, with an end goal of a realtime backup server for failover and for users to log into the web interface of either server to see active calls and registrations on their domain.

My test setup is 2 servers both running:
Debian 10
Freeswitch 10.0.1
FusionPBX 4.5.13
PostgreSQL 9.4

Replicating via BDR FusionPBX works perfectly

Freeswitch can be added to the BDR but starts to fail once a variable of dsn is set with a value of below, in the fusionpbx gui.
"pgsql://hostaddr=127.0.0.1 port=5432 dbname=freeswitch user=fusionpbx password=<password> options=''"

ERROR: Cannot run UPDATE or DELETE on table tasks because it does not have a PRIMARY KEY.
HINT: Add a PRIMARY KEY to the table

From the FusionPBX install scripts it appears to be creating a _uuid column in all freeswitch tables and setting a primary key.

I have Freeswitch setup to use pgsql as it's core database.

Any suggestions and/or a possible different method to be able to see calls/registrations from server1 while logged into server2's GUI?

Thanks,

 

[sudoRmRf]

Did you ever figure this out I am facing this same issue.

 

[mydigitalself]

I did and while it was a relatively simple fix the amount of time it took to figure out, makes me wish I had taken the advanced class. I recreated the freeswitch database.

 

[Neyamt]

I did and while it was a relatively simple fix the amount of time it took to figure out, makes me wish I had taken the advanced class. I recreated the freeswitch database.

How you did it ?, because when i try to drop the database its complaining about BDR relation. Anyone can help on this ?