This was always possible in the past, however does not work in the current
release.
I believe this is a bug.
To: [email protected]
From: [email protected]
Date: Fri, 9 Oct 2015 10:04:47 +0200
Subject: Re: [asterisk-users] Storing HANGUPCAUSE in CDR
search in archives
save the records to another table like cdr_extended
Dne 7.10.2015 v 15:26 Ross Beer napsal(a):
Hi,
I have the following code that operates when a channel is
hung-up:
[record-hangupcause]
exten => 1,n,Set(CDR(hangupcause)=${HANGUPCAUSE})
exten => s,n,Return()
Before the dial a hangup handler is registered:
Set(CHANNEL(hangup_handler_push)=record-hangupcause,s,1)
The routine is called and the variables are being set,
however not on the channel's CDR which made the call. I
believe this is due to the CDR being closes as soon as the
dial returns.
By changing the cdr option 'endbeforehexten=no' this should
keep the CDR accessible, however all this does is cause
another CDR to be created for the 'h' extension.
Is there a way to update the CDR so that a result can be
stored per dial?
Thank you in advance,
Ross
--
---------------------------------------
Marek Cervenka
=======================================
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
