[asterisk-users] 1.6, CDR and h extension

[Benny Amorsen]

Tilghman Lesher <tilghman at mail.jeffandtilghman.com> writes:

> The only thing that occurs to me is that you might be using ForkCDR on your
> production machine, in which case, you might want:
> Set(CDR(hangupcause,r)=${HANGUPCAUSE})
> for recursive setting of the hangupcause.

You are onto something, even if I don't actually use ForkCDR. With
1.6.1beta4 the behaviour is consistent at least, for a particular call
scenario CDR(hangupcause) is either recorded correctly or not
recorded. Still, some call scenarios work and some don't.

In particular, some of the call scenarios create weird extra empty
CDR's like:

"","","s","from-ipvision","SIP/ipvision-0871eaa0","","","","2008-12-29
23:04:14","","2008-12-29 23:04:16","2","0","NO
ANSWER","DOCUMENTATION","","lpbx02-1230588254.29","",""

[..] time passes [..]

Hey, I think I have it! The problem appears when using the g option
for the Dial command! With asterisk 1.6.1 beta 4, that closes the CDR
once the Dial is done, but the dial plan continues and doesn't get to
the h extension until later -- and by then the setting of
CDR(hangupcause) does nothing at all.

I'll have to make a proper bug report, but it's time for bed now.


/Benny