VoIP Mailing List Archives

[ish at pack-net.co.uk]

Hi

We're using asterisk 1.8.23.1. Our inbound calls are routed into the default context with explicit number matching. If found they are passed on to a distinct context for the number being called using the Goto application.


If the call is successful or even if it has no answer, the cdr dcontext field has the correct second context.


However, if the call fails or is busy, and even though we can see it is executing a step in the second context as show in the cdr lastdata field, the dcontext still shows as default.


Is this a bug or expected behaviour? If it is expected behaviour, what is the reasoning behind it?


Thanks in advance


Ish

--

[asterisk at voipbusine...]

Hello;
    Check out this in cdr.conf. You may want to set it to yes. From cdr.conf.sample:

; In brief, this option controls the reporting of unanswered calls which only have an A
; party. Calls which get offered to an outgoing line, but are unanswered, are still
; logged, and that is the intended behaviour. (It also results in some B side CDRs being
; output, as they have the B side channel as their source channel, and no destination
; channel.)
;unanswered = no

Regards;
FSD

From: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] On Behalf Of Ishfaq Malik
Sent: Monday, July 07, 2014 9:26 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] CDR dcontext not updated on FAILED and BUSY calls


Hi


We're using asterisk 1.8.23.1. Our inbound calls are routed into the default context with explicit number matching. If found they are passed on to a distinct context for the number being called using the Goto application.



If the call is successful or even if it has no answer, the cdr dcontext field has the correct second context.



However, if the call fails or is busy, and even though we can see it is executing a step in the second context as show in the cdr lastdata field, the dcontext still shows as default.



Is this a bug or expected behaviour? If it is expected behaviour, what is the reasoning behind it?



Thanks in advance



Ish


--