CDR/Logging each transfer as a call, not just the whole path call took?

Status
Not open for further replies.

wsd-tim

Free User
Joined
Sep 30, 2019
Messages
44
Reaction score
6
Is there any way to have the CDR output each call section as a new line in the log? Technically each transfer is a call in itself. (Or any other way? using CRM Templates?)

Coming from an NEC SL1100, this was the case and it just makes more sense.

Problem: Can not tell how long each Extension took on the call if there is more than 1 destination/transfer

Eg call: Trunk1 -> Queue1 -> Ext.1 -> Ext.7 -> Hangup

Current CDR:
  • Full duration, Start time when Trunk1 call in, End time on hang up, start Trunk1, Final Destination Ext.7, Path: Trunk1;Queue1;Ext1;Ext7;
Wanted result:
  • Start Time Trunk1, Origin Trunk1, Destination Queue1, End time
  • Start Time Queue1, Origin Queue1, Destination Ext1, End time
  • Start Time Ext1, Origin Ext1, Destination Ext7, End time
 
Can anyone shed some light before we purchase one or the other?

I have not yet tested with Template Generator. When does a call get journaled? At the end of each call or each leg of all?
 
Last edited:
Unfortunately this is the only way the CDR Format can be output in.

Call Journaling again won't show you the route through the system the call followed, it will just show the caller ID and which extension was ringing, then if or not it was answered. Also it will tell you the time the call entered the system and when it was terminated.
 
Thanks for your reply Nick. That was the answer I was afraid of.

I really like 3CX for it's simplicity, but our office can not operate without this feature :( I'll keep exploring other ways I guess, even if they are hacky ways

edit:
Nick, is the REST API mentioned here talking about the template/CRM intergration?
https://www.3cx.com/community/threads/api-command-before-and-after-a-call.65462/#post-279760

I have thought of a way which would be a pain to integrate:
- Call Control API to monitor status of all extensions and cross match with CDR report to generate the route.

This will only solve some of our issues since we have a call notes popup and if someone is transferred the person doing the transferring won't get the popup until whole call had ended
 
Last edited:
edit:
Nick, is the REST API mentioned here talking about the template/CRM intergration?
https://www.3cx.com/community/threads/api-command-before-and-after-a-call.65462/#post-279760

I have thought of a way which would be a pain to integrate:
- Call Control API to monitor status of all extensions and cross match with CDR report to generate the route.

This will only solve some of our issues since we have a call notes popup and if someone is transferred the person doing the transferring won't get the popup until whole call had ended
The REST API mentioned is a future plan we have to replace the Call Control API. The Call Control API was intended initially only for internal use by 3CX, so if misused can cause fairly big problems to the stability of the system, thus why public documentation was removed.
We don't yet have an ETA for the REST API, but it is currently on our future to-do list.

About the Call Control API, it does have some Event Listeners that could be used, but due to what I mentioned above, be very careful what you do when using it as it could impact the system.
 
Status
Not open for further replies.

Forum statistics

Threads
111,934
Messages
589,818
Members
164,811
Latest member
aurorasigntrtechitnet