asterisk users - Jul 2014 - 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

-- 

Ishfaq Malik
Department: VOIP Support
Company: Packnet Limited
t: +44 (0)845 004 4994
f: +44 (0)161 660 9825
e: ish at pack-net.co.uk
w: http://www.pack-net.co.uk

Registered Address: PACKNET LIMITED, Duplex 2, Ducie House
37 Ducie Street
Manchester, M1 2JW
COMPANY REG NO. 04920552
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20140707/3ed73d78/attachment.html>

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 at lists.digium.com [mailto:asterisk-users-bounces
at 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


 

-- 

Ishfaq Malik 
Department: VOIP Support
Company: Packnet Limited
t: +44 (0)845 004 4994
f: +44 (0)161 660 9825
e: ish at pack-net.co.uk
w: http://www.pack-net.co.uk
 
Registered Address: PACKNET LIMITED, Duplex 2, Ducie House
37 Ducie Street 
Manchester, M1 2JW
COMPANY REG NO. 04920552
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20140707/85cb49a3/attachment.html>