Summary:ASTERISK-14650: Outgoing DAHDI Calls run to completion without verifying that other end actually answers
Reporter:Danny Nicholas (sethsdad)Labels:
Date Opened:2009-08-13 09:41:12Date Closed:2011-06-07 14:07:57
Versions:Frequency of
Description:I use a call script to call cell phones and other numbers using DAHDI on Asterisk SVN-branch-1.4-r204834M.  The script simply calls the number, does music on hold for 20 seconds, plays 2 short files and hangs up.  Because I have no way of knowing if/when the other end actually picks up the phone, I don't know if the call was a good call.


This occurs using TDM400P and TDM410P cards.

Tzafrir Cohen and Jared Smith had previously addressed this issue as a possible wctdm* driver regression possibility.
Comments:By: Danny Nicholas (sethsdad) 2009-08-13 10:37:23

libpri is

tried immediate=yes and immediate=no in dahdi.conf; no effect

May be a QOS issue - We use POTS lines and Telco does not offer supervision on that level of service.

By: Kevin P. Fleming (kpfleming) 2009-08-21 14:07:06

libpri is not relevant for calls on analog lines.

Without answer supervision, there is no way for Asterisk to 'know' that the call has been answered, and thus it can't help you determine whether a call is 'good' or 'bad'. There are answering machine detection modules, voice detection modules, and call-progress-analysis modules available from various parties that can be used to help with this sort of thing.