CDR entry for each called device

Asterisk Asterisk Support
1

Hi,

we have replaced a really really old installation with Asterisk 16.

My Dialplan does something like this:

exten => 55,1,Dial(SIP/1&SIP/2&SIP/3, 12, t)

(let 3 phones ring when 55 is called)

When a call isn’t answered I get one line in Master.csv for each ringing device, like this:

"","11","55","sipcall","""Test"" <11>","SIP/sipcall-50-0000000a","SIP/1-0000000b","Dial","SIP/1&SIP/2&SIP/3,12,t","2021-11-29 22:15:28",,"2021-11-29 22:15:33",5,0,"NO ANSWER","DOCUMENTATION","1638224128.18",""
"","11","55","sipcall","""Test"" <11>","SIP/sipcall-50-0000000a","SIP/2-0000000c","Dial","SIP/1&SIP/2&SIP/3,12,t","2021-11-29 22:15:28",,"2021-11-29 22:15:33",5,0,"NO ANSWER","DOCUMENTATION","1638224128.18",""
"","11","55","sipcall","""Test"" <11>","SIP/sipcall-50-0000000a","SIP/3-0000000d","Dial","SIP/1&SIP/2&SIP/3,12,t","2021-11-29 22:15:28",,"2021-11-29 22:15:33",5,0,"NO ANSWER","DOCUMENTATION","1638224128.18",""

(records are slightly edited to match with my example)

The old version (1.6) made only one CDR entry for the same situation. Is there a way to force the old behaviour? Or am I doing something wrong?

2

I don’t think so, but there are the options unanswered/congestions in cdr.conf, which might help. On the other hand one could use a database and query the things one is looking for.

3

The comment associated with unanswered say that, as a matter of policy, unanswered outgoing leg are always logged.

This may reflect that the reverse of the OP’s request used to be a frequent request.

4

I’ve already read these requests :frowning: In my situation it’s unwanted. It gets even worse, because after the first 12 seconds, the rest of the phones also start ringing. That means: Every unanswered call generates 3+12 lines in Master.csv.

From the point of the user the call is incoming. Is there a way to tell Asterisk to see it this way? Or an alternate way to call the phones without Dial(SIP/…&SIP/… etc)?

5

I checked this setting, but unanswered is already set to “no” by default. Would be great to solve this without reprogramming my log reader.

6

You are coming from a very old version to a fairly recent version. You did not specify which version on the Asterisk 16 line. There have been a lot of major changes over that span. Most of the major changes happened in Asterisk 12. The CDR implementation was completely rewritten in Asterisk 12 to follow a defined specification.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+12+CDR+Specification
https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.