Review Board 1.7.16

Add Congestion detail in CDR call logs when Congestion application is used.

Review Request #454 - Created Jan. 5, 2010 and submitted

Alec Davis
Cuurently if the dialplan is designed for whatever reason to terminate a call with the Congestion() application a CDR log is not recorded for that call.

This adds that functionality.
Tested and currently been in use with 1.6.1 branch.

Tested for functionality with trunk.

exten => 2001,1,Congestion(0)
exten => 2098,1,Playback(echo-test)

output: /var/log/asterisk/cdr-csv/Master.csv for 2 calls, first to Playback application, 2nd to Congestion(). 
"","857","2098","phones","857","SIP/cisco4-00000000","","Playback","echo-test","2010-01-06 20:47:45","2010-01-06 20:47:45","2010-01-06 20:47:47",2,2,"ANSWERED","DOCUMENTATION","1262764065.2",""
"","857","2001","phones","857","SIP/cisco4-00000000","","Congestion","0","2010-01-06 20:50:09",,"2010-01-06 20:50:09",0,0,"CONGESTION","DOCUMENTATION","1262764209.0",""
Review request changed
Updated (Jan. 7, 2010, 6:45 a.m.)
Posted (Feb. 2, 2010, 5:47 a.m.)
By default, Asterisk does not record unanswered calls in the CDR log. In cdr.conf, if you set unanswered=yes, you will see a "NO ANSWER" result in the cdr. If anything else was required, I would think that modifying pbx_builtin_congestion to call ast_cdr_failed() would suffice as opposed to adding a whole new CDR disposition.
  1. cdr.conf as you say requires unanswered=yes, which from the cdr.conf file
    "Some find this information horribly useless. Others find it very valuable."
    Many sites would be running with unanswered=no. runs on a server provided by Digium, Inc. and uses bandwidth donated to the open source Asterisk community by API Digital Communications in Huntsville, AL USA.
Please report problems with this site to