I had working setup of FusionPBX on Debian 8 jessie. I updated freeswitch packages at Jun 23 2017. After that I discovered FusionPBX can't update registered agents status, so FusionPBX can't forward calls from queue to registered agent:
2017-07-18 10:09:30.024419 [WARNING] sofia_reg.c:1792 SIP auth challenge (REGISTER) on sofia profile 'internal' for [260@domain.my] from ip 10.10.1.5
2017-07-18 10:11:01.524419 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [unable to open database file]
freeswitch@server1> show registrations
reg_user,realm,token,url,expires,network_ip,network_port,network_proto,hostname,metadata
260,domain.my,4eagr1EcI6D2qM06nLqBaw..,sofia/internal/sip:260@10.40.1.5:34072;rinstance=daf4c450a7d0be02;transport=tcp;fs_nat=yes;fs_path=sip%3A260%4010.40.1.5%3A58203%3Brinstance%3Ddaf4c450a7d0be02%3Btransport%3Dtcp,1500351030,10.40.1.5,58203,tcp,server1
I upgraded FusionPBX several times but it's not solved this issue. PostgreSQL is working, FusionPBX has access to database. Which database files FusionPBX can't open and how can I fix this issue?
2017-07-18 10:09:30.024419 [WARNING] sofia_reg.c:1792 SIP auth challenge (REGISTER) on sofia profile 'internal' for [260@domain.my] from ip 10.10.1.5
2017-07-18 10:11:01.524419 [ERR] switch_core_sqldb.c:587 NATIVE SQL ERR [unable to open database file]
freeswitch@server1> show registrations
reg_user,realm,token,url,expires,network_ip,network_port,network_proto,hostname,metadata
260,domain.my,4eagr1EcI6D2qM06nLqBaw..,sofia/internal/sip:260@10.40.1.5:34072;rinstance=daf4c450a7d0be02;transport=tcp;fs_nat=yes;fs_path=sip%3A260%4010.40.1.5%3A58203%3Brinstance%3Ddaf4c450a7d0be02%3Btransport%3Dtcp,1500351030,10.40.1.5,58203,tcp,server1
I upgraded FusionPBX several times but it's not solved this issue. PostgreSQL is working, FusionPBX has access to database. Which database files FusionPBX can't open and how can I fix this issue?
Last edited: