3cx integration and CDR interface

[Hayward-i1]

Hi,

I have an odd problem. I have been using 3cx for simply ages (V9 and possibly earlier)

Over that time I have developed a simple system that interfaces with the CDR logs to capture call termination so recordings can be filed and records placed on customers records so an audit trail exists.

It has worked beautifully for years.

But recently when the server is restarted, it has been slow to establish the required network socket.

Today it doesn't want to connect at all and it is about 4 hours since the servicer was rebooted.

The error message being received is that 3cx is refusing the connection.

I am using a passive connection. the IP address of the receiving client is correct as is the receiving port.

As far as I can tell it is 3CX not initialising the CDR port that is causing the problem.

Can anyone shed any light on what might be going on?

Thanks in advance.

 

[Cjay]

CDRs are working fine for me, never had any issue with the connection being established with 3CX passive socket mode even after restarts (currently running v20 U9).

Without knowing how your system operates it is hard to diagnose, but a simple thing you could try is to run CallVitesse (my software that probably does the same things as yours). If it still fails to connect then we can be sure that something is afoot...

You can find my program here (follow link to CallVitesse - Downloads & Documentation): https://drive.google.com/drive/folders/1u5FCXOYDouODivjz1kj3OsNmyaRcKP9Y

[Program is very lightweight and easily removed]

 

[Hayward-i1]

Thanks CJay,

Curiously, the connection is now working again (it took about 6 hours), but I have missed the CDR records for most of the day. I will download your software and wait until the next time as a double check...

My version is very different as I coded it as a system service so it starts doing it's thing as soon as 3CX starts (well, with a slight delay)

 

[CXBridge Ops]

Hi Hayward,

I was thinking about your issue, but I only think in read logs and found what was the problem, and based on the diagnostic, create a service that automatically the system restart, monitorize the services to be sure all services are up with any problem. Maybe this could solve in the future events your unavalability. but it needs a good diagnostic.

I would be happy to assist you with a diagnostic meeting if the need arises—should this happen again—and help ensure it doesn't recur.