DSN

[glennbtn]

Hi All

I noticed on the very latest install that the postgres.sh no longer creates a freeswitch database so setting up the dsn setup fails. Whilst I can hack this to work does anyone know a reason for this as a new install does not have any dsn settings from what I can see

 

[markjcrane]

I made that change so I'm the best person to answer this question.

FusionPBX and FreeSWITCH should NOT share the same instance of the PostgreSQL database. A long-running query for FusionPBX can block requests for FreeSWITCH which could be used for new calls or registrations. In other words, a long query could block registrations or new calls. This can be catastrophic to the stability of your system. For this reason, if you put the FreeSWITCH database in PostgreSQL it should have its own instance so that it is not blocked by requests to the FusionPBX database.

The FusionPBX install defaults to using the SQLite database, which is better than FusionPBX and FreeSWITCH sharing the same instance of PostgreSQL.

 

[glennbtn]

Thanks for that info Mark. I though it was may be a dodgy update and manually created the database and then ran the DSN. So does this include large multi tenants to use SQLite as well

 

[markjcrane]

FreeSWITCH's default database is SQLite and always has been. FreeSWITCH can still be set up to use the PostgreSQL database.

In the latest release, this is done using the following

• Advanced -> Variables to define the DSN
• SIP Profiles by changing odbc_dsn
• Update the /etc/fusionpbx/config.conf file.