[asterisk-dev] Function CDR() borked in 1.6.2.4?

Kirill 'Big K' Katsnelson kkm at adaptiveai.com
Sun Mar 21 16:30:01 CDT 2010


On 100321 1416, my dear self wrote:
> CDR(billsec), CDR(duration) and CDR(disposition) always return 0, 0, and 
> NO ANSWER respectively in an "h" extension routine. Is that design 
> change or a bug? `endbeforehexten' is not set, explicitly setting it to 
> `no' changes nothing.

There seems to be even deeper borkage. I assign some call quality 
metrics to custom CDR fields. These are logged as NULLs into the 
database now, unlike 1.6.1. So the write part of the function is also 
broken.

I'm logging a bug, clear enough.

  -kkm



More information about the asterisk-dev mailing list