Solved CDR not working with V18

[petermac]

Anyone else having issues with V18 connecting to the system and extracting CDR records using passive socket (Server), pre V18 no problems, none of the systems that I have that are V18 will allow the connection. We use CallVitesse for record extraction.

 

[Cjay]

What port is your 3CX listening on? The 'usual' issue (aside from firewalls etc.) is that 3CX may have reverted back to listening on port 3000 whereas CallSequitur or CallVitesse will most likely be trying on port 5015 (as this port is usually left open after install). You can try telnet to see if it connects.

 

[ChrisC_3CX]

I've just tested this on the latest version of v18 (18.0.1.237) and can confirm everything works as intended. I'd recommend checking what port is set for CDR in the "Management Console >> Reports >> CDR" and then perhaps try connecting to it via telnet as @Cjay recommended.

If that fails, try connecting to it locally as well in order to determine if the issue is perhaps firewall related.

 

[petermac]

Also running the latest version (18.0.1.237), instance is on a local machine on premises running linux, I have tried changing the port and still cannot connect using the telnet command.....

 

[petermac]

I just had a look at the firewall, does not appear to be any rules in place for either port 3000 or 5015?

 

[petermac]

After adding port 3000 into the nftables it now works, I would have assumed given the standard port for CDR is 3000 that this would be included as part of the package, all working now

 

[ChrisC_3CX]

Excellent! Glad to see you managed to get this sorted!