[asterisk-bugs] [DAHDI-linux 0014577]: [patch] FXO channels "hookstate" incorrect on startup

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=14577 
====================================================================== 
Reported By:                jkroon
Assigned To:                sruffell
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   14577
Category:                   dahdi (the module)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     confirmed
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2009-03-01 16:16 CST
Last Modified:              2010-02-14 06:39 CST
====================================================================== 
Summary:                    [patch] FXO channels "hookstate" incorrect on
startup
Description: 
Referencing bug 13786 (http://bugs.digium.com/view.php?id=13786) which
attempts to work around an underlying problem in userspace (chan_dahdi). 
The issue seems to be (as described by tzafrir):

It seems to expose a bug(?) in zaptel/dahdi where chan->rxhooksig is set
to RX_HOOKSIG_INITIAL at the end of chanconfig() which leaves the channel's
state there "uninitialized" and even if the channel driver knows better it
cannot override this decision. But I'm not sure what's the intended
behaviour, so I avoid a seperate bug report on that for now.

This is manifested in that I cannot make outbound calls on an FXO card
(Using FXSKS signalling) until I've received an incoming call resetting the
hookstate to offhook (A single ring is good enough), or alternatively,
disconnecting and reconnecting the telephone line.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0015429 After the system reboot calls do not go...
====================================================================== 

---------------------------------------------------------------------- 
 (0118066) frawd (reporter) - 2010-02-14 06:39
 https://issues.asterisk.org/view.php?id=14577#c118066 
---------------------------------------------------------------------- 
Hi,
For some reason when using Sangoma A100 with their latest stable driver
(wanpipe 3.4.8 at this time), no alarm is set when no battery is on the
line. I don't know if this is a dahdi or wanpipe bug that should be
reported to Sangoma.

In order to detect battery status I then still rely on the Offhook-Onhook
status, and while tzafrir's patch makes outgoing calls work, the initial
state shown by "dahdi show channel X" is still set to Onhook even when
there is battery. An incoming call or re-plugging the line makes the hook
status correct again.

Patch 0001-dahdi-base-Do-not-overwrite-the-hookstate-at-channe.patch makes
it work for me. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-14 06:39 frawd          Note Added: 0118066                          
======================================================================