[asterisk-bugs] [DAHDI-linux 0015429]: After the system reboot calls do not go out on TDM410P FXO channels until an incoming call comes in

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15429 
====================================================================== 
Reported By:                vmikhelson
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   15429
Category:                   wctdm24xxp
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             2009-07-01 01:35 CDT
Last Modified:              2009-07-02 21:14 CDT
====================================================================== 
Summary:                    After the system reboot calls do not go out on
TDM410P FXO channels until an incoming call comes in
Description: 
After the system reboot any attempt to dial out on DAHDI FXO line fails.
The normal functionality is restored after the first call comes in that FXO
line.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0014577 [patch] FXO channels "hookstate&qu...
====================================================================== 

---------------------------------------------------------------------- 
 (0107379) vmikhelson (reporter) - 2009-07-02 21:14
 https://issues.asterisk.org/view.php?id=15429#c107379 
---------------------------------------------------------------------- 
Tried applying the patch. Ran into two problems.

1. Link in comment https://issues.asterisk.org/view.php?id=107364 produces
"Access Denied." and asks for
authentication. Clicking on "Click here to login" or on "Click here to
proceed" brings a user to the issues tracking Home Page. It makes
impossible reviewing the patch prior to installing.

2. Attempt to apply the patch to the released version 2.0.1.4 produced the
following:

can't find file to patch at input line 20
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|From 788d21e9724516bab68d62d1567b7ab06c060561 Mon Sep 17 00:00:00 2001
|From: Shaun Ruffell <sruffell at digium.com>
|Date: Wed, 20 May 2009 15:10:12 -0500
|Subject: [PATCH] wctdm24xxp: Detect if our hookstate has been set back to
the i                nitial state.
|
|Check if our hookstate has been set back to the initial state, typically
the
|result of a chanconfig, and if so, if we're an FXO port, forget our
current
|battery state.  This allows the driver to determine and report again what
the
|hook state of the port is.
|
|(related to issue https://issues.asterisk.org/view.php?id=14577)
|---
| drivers/dahdi/wctdm24xxp/base.c |    7 +++++++
| 1 files changed, 7 insertions(+), 0 deletions(-)
|
|diff --git a/drivers/dahdi/wctdm24xxp/base.c
b/drivers/dahdi/wctdm24xxp/base.c
|index c4d6b12..eb39d18 100644
|--- a/drivers/dahdi/wctdm24xxp/base.c
|+++ b/drivers/dahdi/wctdm24xxp/base.c
--------------------------
File to patch:

Please advise.  I thought about applying the patch manually, but
discovered a different code around line 1403.

Thank you,
Vladimir 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-07-02 21:14 vmikhelson     Note Added: 0107379                          
======================================================================