[asterisk-users] Logging to CDR after call file Not Answered

[Tech Support]

Why don’t you try it and see what happens.

Regards;

John

 

From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of er ic
Sent: Thursday, December 31, 2015 9:41 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Logging to CDR after call file Not Answered

 

I dont have this info in my cdr.conf.sample

 

Nor do I think this is what I need.

 

I believe that will log unanswered calls inside a dialplan. Meaning, if I call directly from my extension to another extension/number, if they do not pick up, it will log; as it currently does now.

 

With call files, it is not logging. There is no execution of a dialplan inside my assigned context.

 

On Thu, Dec 31, 2015 at 9:29 AM, Tech Support <asterisk at voipbusiness.us> wrote:

Here you go… Found this in cdr.conf.sample.

 

; Define whether or not to log unanswered calls. Setting this to "yes" will

; report every attempt to ring a phone in dialing attempts, when it was not

; answered. For example, if you try to dial 3 extensions, and this option is "yes",

; you will get 3 CDR's, one for each phone that was rung. Default is "no". Some

; find this information horribly useless. Others find it very valuable. Note, in "yes"

; mode, you will see one CDR, with one of the call targets on one side, and the originating

; channel on the other, and then one CDR for each channel attempted. This may seem

; redundant, but cannot be helped.

;

; 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;

John

 

From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of er ic
Sent: Thursday, December 31, 2015 7:05 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: [asterisk-users] Logging to CDR after call file Not Answered

 

If the end user does not pick up the phone, is there a way to log to the CDR about the call file failing?

 

 

/var/log/asterisk/messages does show a NOTICE message

[2015-12-31 06:58:46] NOTICE[28059] pbx_spool.c: Call failed to go through, reason (3) Remote end Ringing

[2015-12-31 06:58:46] NOTICE[28059] pbx_spool.c: Queued call to SIP/102 expired without completion after 0 attempts

 

but I would rather not have to run a script and search the call log for those two strings, extrapolate the reason code and then compare it to my custom php/database driven scheduler. 

 

Is there a way to have it logged to the server?

 

Also, both chanunavail attempts and NA attempts both register the status as expried. Is this correct or should one of them be failed? I am trying to be able to distinguish the two conditions by looking at the archived message.

 

Thanks,

--E


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

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

 

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