[asterisk-users] AMI and CDR(answer)

Murthy Gandikota mgandikota at nts.net
Thu Oct 16 11:44:45 CDT 2014


Suppose we have a dialplan as follows and sip.conf is set to forward the
call to [start] context, the CDR(diposition) in [start] context will be
"ANSWER" and in [next] will be "NO ANSWER". Right?

 

[start]

exten = s,1,answer()

same =>n,gotoif($[${SOMEVAR} = SOME_VAL]?next)

same =>n, hangup()

 

[next]

exten = s,1, VERBOSE(WE ARE HERE)

same =>n,hangup()

 

________________________________

From: asterisk-users-bounces at lists.digium.com
[mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Matthew
Jordan
Sent: Thursday, October 16, 2014 8:55 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] AMI and CDR(answer)

 

 

 

On Wed, Oct 15, 2014 at 9:31 PM, Murthy Gandikota <mgandikota at nts.net>
wrote:

Thanks, Matthew. I think CDR(answer) is, in the end, not very useful to
me if it changes from context to context. Suppose from AMI we generate a
status

 

I'm not sure what you mean by "changes from context to context". The
answer time on a CDR is reflective of when the channel was answered.
That can be altered if you choose to alter it in the dialplan via
ForkCDR, but generally, that time is conveyed from one CDR to another.

A specific example would help here.

 

	event, what will be the CDR(answer)? I see that sometimes it is
returned
	as the literal "Production" instead of a Date/Time or a blank
value.

 

I don't know what you mean here either. What version of Asterisk are you
using? Can you provide an example where you get said literal back, as
well as the dialplan that produces this behavior?

 

	I
	am only puzzled that no one created a patch for the first
timestamp when
	a call is answered. If I get some free time, I will try to
create one.
	
	


-- 

Matthew Jordan

Digium, Inc. | Engineering Manager

445 Jan Davis Drive NW - Huntsville, AL 35806 - USA

Check us out at: http://digium.com & http://asterisk.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20141016/d9366ec4/attachment.html>


More information about the asterisk-users mailing list