Hello,
Digging a bit further, having a local cdr_custom CSV seems to make
updatings work !
I did have enough time to properly test this and become more affirmative
but it seems to depend on active CDR backend;
2018-02-21 22:19 GMT+01:00 Olivier :
> As a complement to my
As a complement to my previous post, may I add that I observed the
following behaviours:
1. On one system (Debian Stretch/asterisk 13.19 compiled from source),
hangup causes are correctly saved in a custom CDR column.
2. On an other system (Debian Stretch/packaged asterisk), some rtcp stats
are
Hi,
Reading this old thread, may I ask if keeping hangup handlers from updating
CDR values still enforced in Asterisk 15 ?
If positive, would it be very complex to add in Asterisk, a configuration
option allowing a system administrator to list in cdr.conf, the CDR fields
allowed to be updated in
On Tue, Aug 4, 2015 at 9:16 AM, Filip Jenicek fjeni...@kerio.com wrote:
With endbeforehexten=no I actually get two CDR entries. One for the call
and a second one for the h extension.
,13,10,sip-locals,13
13,SIP/13-0006,SIP/10-0007,Dial,SIP/10,2015-08-04
06:28:44,2015-08-04
With endbeforehexten=no I actually get two CDR entries. One for the call
and a second one for the h extension.
,13,10,sip-locals,13
13,SIP/13-0006,SIP/10-0007,Dial,SIP/10,2015-08-04
06:28:44,2015-08-04 06:28:45,2015-08-04
06:28:47,3,1,ANSWERED,DOCUMENTATION,1438669724.6,empty
Hi,
I'm trying to migrate from Asterisk 1.8 to Asterisk 13 and can't figure
this one out. I'm pretty sure the question has been already asked, but I
failed to find a solution.
Can you modify CDR values in an h-extension?
My cdr.conf contains:
[general]
enable=yes
unanswered=yes
I'm trying to migrate from Asterisk 1.8 to Asterisk 13 and can't figure this one out. I'm
pretty sure the question has been already asked, but I failed to find a solution.
Can you modify CDR values in an h-extension?
My cdr.conf contains:
[general]
enable=yes
unanswered=yes