[asterisk-bugs] [Asterisk 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:                    Asterisk
Issue ID:                   14577
Category:                   Channels/chan_dahdi
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     confirmed
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-03-01 16:16 CST
Last Modified:              2010-03-16 08:30 CDT
====================================================================== 
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...
====================================================================== 

---------------------------------------------------------------------- 
 (0119436) frawd (reporter) - 2010-03-16 08:30
 https://issues.asterisk.org/view.php?id=14577#c119436 
---------------------------------------------------------------------- 
I agree that the wctdm and wctdm24xxp patches might have been ugly
solutions.

What I was saying is that removing this behavior with the patch
0001-dahdi-base-Do-not-overwrite-the-hookstate-at-channe.patch uploaded by
sruffell and explained in Note 0105153 also resolves this particular bug
for me without side effects, meaning the initial hookstate is again correct
for a card that is not wctdm nor wctdm24xxp (Sangoma). No need for channel
driver specific patches.