[asterisk-users] Storing HANGUPCAUSE in CDR

Ross Beer ross.beer at outlook.com
Fri Oct 9 06:52:24 CDT 2015

This was always possible in the past, however does not work in the current release.
I believe this is a bug.
To: asterisk-users at lists.digium.com
From: cervajs at fpf.slu.cz
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):


        I have the following code that operates when a channel is

            exten => 1,n,Set(CDR(hangupcause)=${HANGUPCAUSE})
            exten => s,n,Return()

        Before the dial a hangup handler is registered:


        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,









Marek Cervenka


-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20151009/a5ef7554/attachment.html>

More information about the asterisk-users mailing list