(another) Call Control API thread, specifically DNmonitor

[Louis1976]

In V15/V15.5 we wrote an application to monitor all the calls and write them to an MySQL database.

I've waited all this time to upgrade to V16 and all my nightmares come true.

I simply want to log all the call's that pass through 3CX.
I've used the DN Monitor for this purpose.
We use this as a CDR replacement, but also to see if a call comes in on the queue.
And to check who is in a call in our CRM system.

The CRM integration can't do this.
1) It only logs if it's an known customer
2) It only logs when the call has ended.

So, I've tried to following things:
a) The Call Control API V16, here I made the mistake to move from Windows to the DEBIAN 3CX ISO.
I'm not a pro in VisualStudio, but I can't get the DLL working on the Debian.

b) Tried to access the PostGres DB directly.
Still busy on this, but it probably prohibits access from outside.
I changed some .conf files, but still can't reach the server.

If someone can help me with either a or b, I would be very gratefull.

Unfortunately I'm getting the feeling that despite of all the effort of the 3CX Team the features I'm using in 3CX are gettign downgraded intead of upgraded.
The core-function of 3CX hasn't improved at all for us. Maybe we only use 1% of the total what 3CX can do. ;-)

 

[VoIPTools]

Louis1976,

The dll is now .Net Core. You will need to convert your application to .Net Core. You can't reference a .Net Core DLL from a .Net Framework application.

Also, you need to be very, very careful about how you connect directly to the PostgreSQL database. This is NOT supported by 3CX and they can get pretty assertive about it if they discover you are doing it. I strongly urge you not to go down this road.

If you need real-time information the ONLY way to get it is using the Call Control API. Even accessing the database (don't do it) is not real-time. It appears to me that 3CX caches some of their writes so it may be some time before things actually show up in the database.