Solved CDR - Refusing connection

[Hayward-i1]

Hi, I rebooted 3CX over the weekend and I now have an odd error.

I use a bit of software that reads 3CX CDR data off of a defined port. It has worked faultlessly for 2-3 years (I am currently on V18), but today, the connection is being refused with the error message "System.netsockets.socketexception: "No connection could be made because target machine actively refused it - "Then the IP address and defined port"

The CDR data is correct on 3cx, it just appear 3CX hasn't opened this port so I can not listen. Any ideas?

There

 

[edossantos_sipcaller]

Looks like a firewall issue. Check the firewall of your 3CX server operating system.

 

[Hayward-i1]

Looks like a firewall issue. Check the firewall of your 3CX server operating system.

That's what I thought, so I turned the firewall off! Problem still there.

 

[OlegR_3CX]

Something on the network there, break the connection.
You could save the data to the file locally on the server, and then find the way to have the file passed and send over once it is updated to the remote side. This way you know that you won't lose the call, and it will always be saved into the file.

 

[Cjay]

@Hayward-i1 - What port are you trying to connect on?

 

[Hayward-i1]

It was a design choice to pick up the CDR messages and has been bullet proof for several years. What you are talking about requires a redesign of the process involved which really is a option of last resort.

So I would really like to find the problem.

 

[Hayward-i1]

@Hayward-i1 - What port are you trying to connect on?

A user defined port, 10033

 

[edossantos_sipcaller]

First, check if you can connect locally, try opening telnet to that port. If that works, it's a firewall issue somewhere. You can use nmap from another server to check if you can see the port open in the PBX server. This way you can see if this is a firewall issue in the 3CX server or somewhere else in the network.

 

[Hayward-i1]

First, check if you can connect locally, try opening telnet to that port. If that works, it's a firewall issue somewhere. You can use nmap from another server to check if you can see the port open in the PBX server. This way you can see if this is a firewall issue in the 3CX server or somewhere else in the network.

Great advice and I will do more diagnostics next time.

However in desperation, I decided to re-boot the server, problem resolved! I have no idea why this fix it because in theory it should not of worked!!!! Go figure.