Hello, I have a question about the CDR-records.
We have an extensive custom reporting based on the CDR-records.
We update our 3cx from update 2 to update 3 & 4 in one move, and I discovered that since then I see a specific change in the CDR-records.
My question is if the change I describe next has something to do with these updates.
(I already looked in the V20 change history of these updates but didn't find something)
Situation:
When a call is made to a queue, and there is a forward to another queue in the f.e. (we use only this forward) "Destination if no answer"...
… In update 2,
the fields "dial_no" and "to_no" were (more or less always) the same and showed the queue that was receiving the call.
(f.e. dial_no = '01819' and to_no = 'Ext.01819')
the final_no showed the number of the Queue/Extension where the call was finally forwarded or answered by.
… Since update 3 or 4,
the fields "dial_no" and "to_no" aren't the same anymore.
(f.e. dial_no = '01819' and to_no = 'Ext.03004')
The "dial_no" still shows the queue that was called, but "to_no" now shows the queue where the call has been forwarded to.
Is this by design (a particular change/fix or so), or can this be controlled/manipulated by a specific setting in 'Voice & Chat" trunk-options?
We have an extensive custom reporting based on the CDR-records.
We update our 3cx from update 2 to update 3 & 4 in one move, and I discovered that since then I see a specific change in the CDR-records.
My question is if the change I describe next has something to do with these updates.
(I already looked in the V20 change history of these updates but didn't find something)
Situation:
When a call is made to a queue, and there is a forward to another queue in the f.e. (we use only this forward) "Destination if no answer"...
… In update 2,
the fields "dial_no" and "to_no" were (more or less always) the same and showed the queue that was receiving the call.
(f.e. dial_no = '01819' and to_no = 'Ext.01819')
the final_no showed the number of the Queue/Extension where the call was finally forwarded or answered by.
… Since update 3 or 4,
the fields "dial_no" and "to_no" aren't the same anymore.
(f.e. dial_no = '01819' and to_no = 'Ext.03004')
The "dial_no" still shows the queue that was called, but "to_no" now shows the queue where the call has been forwarded to.
Is this by design (a particular change/fix or so), or can this be controlled/manipulated by a specific setting in 'Voice & Chat" trunk-options?
