[asterisk-users] Possible Bug (Include ${HANGUPCAUSE} in CDR)

[Danny Nicholas]

  _____  

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Bryant
Zimmerman
Sent: Wednesday, December 22, 2010 11:43 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Cc: Asterisk Developers Mailing List
Subject: Re: [asterisk-users] Possible Bug (Include ${HANGUPCAUSE} in CDR)

 

Ok I can't get my CDR values to set from the h extension in either 1.6.2 or
1.8  What is wrong? Here is what I found in the cdr.conf

; Normally, CDR's are not closed out until after all extensions are finished

; executing. By enabling this option, the CDR will be ended before executing
; the "h" extension so that CDR values such as "end" and "billsec" may be
; retrieved inside of of this extension. The default value is "no".
endbeforehexten=no

The default is set to no so why can't I store any CDR values in my h
extension.

exp..
exten => h,n,Set(CDR(cause_code)=${HANGUPCAUSE})
I need the cause code stored.

Really what I need to be able to do is in the h quickly store some values to
the CDR then.
For the write of the CDR and stopping the billing seconds.  Then continue to
process some cleanup funcitons.

How can I work arround asterisk not honoring the endbeforehexten=no.
Is there some other way to achieve this?

Bryant

I need the cause code stored.Really what I need to be able to do is in the h
quickly store some values to the CDR then.For the write of the CDR and
stopping the billing seconds.  Then continue to process some cleanup
funcitons.How can I work arround asterisk not honoring the
endbeforehexten=no.Is there some other way to achieve this?Bryant 

 

Okay, this is a "mentally challenged" solution, but at the h extension you
have ${UNIQUEID} and ${HANGUPCAUSE} available to you.  Use DeadAGI to
"stuff" these values into the CDR or into another file that you can
cross-reference.  If you use the two-file method, you would just select the
matching file using uniqueid.  That's what I did when I had this problem on
a version of 1.4.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20101222/a21280ec/attachment.htm>