Call Detail Records - Empty

[Jason Cornell]

Hello,

We are currently running 24.01.0 update 6 and are having issues getting any records, Historic or Active, to show up in Call Detail Records. The records in history are working up until January 13th but haven't shown anything since then. We didn't notice it until last week due to having to check something in the logs.

Any assistance you are able to provide will be greatly appreciated!

Thanks in advance!

[Support]

Hello Jason,

Is your sipXcdr service enabled and running, and if so what is the outpout of systemctl status sipxcdr?

Also have you checked sipxcallresolver.log? You can change log level under Settings - CDR.

Waynesboro Area School District Mission Statement

EMPOWERING INDIVIDUALS FOR FUTURE OPPORTUNITIES - FIRST CHOICE

Pursuant to Waynesboro Area School District (WASD) policy and administrative procedures, this e-mail system is to be used for official WASD business only.  All users are cautioned that messages sent and received through this system are subject to the Freedom of Information Act, and Pennsylvania public disclosure laws, and may be reviewed at anytime by WASD.  There should be no expectation of privacy.

Please consider the cost and the environment before printing this email or any attachments.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/871b0e07-5d3d-4f91-9a39-7611325b2599n%40googlegroups.com.

[Gerald Drouillard]

This worked for me in the past....

 enabling or disabling service "Callback on Busy" was enough to fix the CDR database

SIPX_PROXY_CALL_STATE : ENABLE

in 

/etc/sipxpbx/sipXproxy-config

Then mark the file immutable and retest. You need to restart sipxproxy. You need to remember that you made this file immutable in case you need to change settings, for this you need to make it normal again, send profiles then modify this setting and immutable again

[Jason Cornell]

Good morning,

Thank you for your response! The response from Gerald is exactly what fixed our issue. The only part we didn't do was the bottom section of making the file immutable as disabling the callback feature and restart sipxcdr resolved it immediately. We are going to continue to monitor to see if it breaks again. I have included it below in case it wasn't seen on the OnRelay support side.

enabling or disabling service "Callback on Busy" was enough to fix the CDR database

SIPX_PROXY_CALL_STATE : ENABLE

in

/etc/sipxpbx/sipXproxy-config

Then mark the file immutable and retest. You need to restart sipxproxy. You need to remember that you made this file immutable in case you need to change settings, for this you need to make it normal again, send profiles then modify this setting and immutable again

Thanks again!

--

[Jason Cornell]

Good morning Gerald,

Thank you so much, this resolved our problem! We didn't perform the file change you mentioned as disabling callback on busy and restarting the sipxcdr service via SSH resolved it immediately for us. We are going to continue to monitor to see if it breaks again and then we can look at modifying the files. We don't send server profiles very often but I"m assuming, if I"m reading your solution correctly, that would cause this to break again if we have to do that.

Thanks again!

--

[Ivar Plahte]

Thank you, Jason,

Seems like something worth checking in the source. Appears the call resolver config just had to be regenerated. We will record the issue.

To view this discussion visit https://groups.google.com/d/msgid/sipxcom-users/CAJuZDkzPoZvNm8mFqoE%3Drs3UwZic7j3%3DQNxywkCZyy9a3BdZFA%40mail.gmail.com.

[Jason Cornell]

Sounds good Ivar, I appreciate you recording it!