- Joined
- Dec 19, 2015
- Messages
- 10
- Reaction score
- 0
Has anyone any pointers for read only access to postgreSQL used by 3CX
The only thing I can think of is something that I noticed a while back
it is a 64bit driver however it seems to be a 32bit database connection
and there seems to be some conflict
Firstly I would like to say I have been using 3CX in different versions for many years,
I have found, every version, to be very robust, reliable and flexible, even under load,
I cant praise the product enough, rating it up there with the likes of VMware ESX, which is high praise indeed.
It has been worth the cost, and the initial very steep learning curve.
With version 14 I like the WebRTC option, which we are to be using on the website very soon.
and the Pro version has some nice features with the call centre editions.
The only problem I have had with it is the access to the call data outside the call reports,
which to be honest the reports are the only thing in my opinion that let it down.
I am trying to access Postgres in read only mode in version 14, I only want to read the call data,
and export it into MySQL or MS SQL so I can manipulate it and further automate it
and deliver bespoke web reports to customers.
You could do this in v9, v10 and v11 (didn't try v12), but I cant seem to make the
same DSN connection as previous but I either get invalid password or no server response.
I am using the info from the ini file as usual (See below),
Correct driver installed in System DSN : PostgreSQL Unicode (x64)
[CallReports]
USERNAME=logsreader
DRIVER=PostgreSQL Unicode
PASSWORD=logsreader
DATABASE=phonesystem
PORT=5480
SERVER=localhost
ReadOnly=1
[MIME_TYPES]
MESSAGE=x-chat/control
[DbAdminREADONLY]
User=phonesystem
Password=***************
[instance1]
pbxSLNIC=127.0.0.1
cmPort=5482
pbxuser=instance_instance184475
pbxpass=**************
If anyone can shed some light on to this I would be grateful
Other than that the product is excellent, near perfect,
It would be nice if the following were added / amended
1. WAV converts to MP3 (I have written a routine using lame that converts it for me, so not important)
2. Option to use either MySQL or MS SQL rather than Postgres would be excellent
I don't mind paying extra for the MS SQL licenses or MySQL Enterprise.
3. Export of CSV / Excel Reports is one long list and doesn't break up into various sheets
As I am having to remove all the gaps on 300 + pages manually each month.
Many Thanks, Appreciated.
The only thing I can think of is something that I noticed a while back
it is a 64bit driver however it seems to be a 32bit database connection
and there seems to be some conflict
Firstly I would like to say I have been using 3CX in different versions for many years,
I have found, every version, to be very robust, reliable and flexible, even under load,
I cant praise the product enough, rating it up there with the likes of VMware ESX, which is high praise indeed.
It has been worth the cost, and the initial very steep learning curve.
With version 14 I like the WebRTC option, which we are to be using on the website very soon.
and the Pro version has some nice features with the call centre editions.
The only problem I have had with it is the access to the call data outside the call reports,
which to be honest the reports are the only thing in my opinion that let it down.
I am trying to access Postgres in read only mode in version 14, I only want to read the call data,
and export it into MySQL or MS SQL so I can manipulate it and further automate it
and deliver bespoke web reports to customers.
You could do this in v9, v10 and v11 (didn't try v12), but I cant seem to make the
same DSN connection as previous but I either get invalid password or no server response.
I am using the info from the ini file as usual (See below),
Correct driver installed in System DSN : PostgreSQL Unicode (x64)
[CallReports]
USERNAME=logsreader
DRIVER=PostgreSQL Unicode
PASSWORD=logsreader
DATABASE=phonesystem
PORT=5480
SERVER=localhost
ReadOnly=1
[MIME_TYPES]
MESSAGE=x-chat/control
[DbAdminREADONLY]
User=phonesystem
Password=***************
[instance1]
pbxSLNIC=127.0.0.1
cmPort=5482
pbxuser=instance_instance184475
pbxpass=**************
If anyone can shed some light on to this I would be grateful
Other than that the product is excellent, near perfect,
It would be nice if the following were added / amended
1. WAV converts to MP3 (I have written a routine using lame that converts it for me, so not important)
2. Option to use either MySQL or MS SQL rather than Postgres would be excellent
I don't mind paying extra for the MS SQL licenses or MySQL Enterprise.
3. Export of CSV / Excel Reports is one long list and doesn't break up into various sheets
As I am having to remove all the gaps on 300 + pages manually each month.
Many Thanks, Appreciated.