[asterisk-bugs] [DAHDI-linux 0014577]: [patch] FXO channels "hookstate" incorrect on startup
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Aug 13 20:09:40 CDT 2009
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
======================================================================
Date Submitted: 2009-03-01 16:16 CST
Last Modified: 2009-08-13 20:09 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...
======================================================================
----------------------------------------------------------------------
(0109025) sruffell (administrator) - 2009-08-13 20:09
https://issues.asterisk.org/view.php?id=14577#c109025
----------------------------------------------------------------------
While the easiest place to fix this is with the Asterisk patches, there is
still a bug in the drivers. I looked into it some today, and the rxhooksig
is changed back to initial so that digital boards that call dahdi_rbsbits
will have new events queued to the channel after the channel is configured
(which could change the type of CAS signalling used on the span).
Therefore, it appears that the 'proper' fix was to make the analog drivers
recognize the DAHDI_RXSIG_INITIAL rxhooksig state as an indication to
re-report the current hookstate of it's lines.
Issue History
Date Modified Username Field Change
======================================================================
2009-08-13 20:09 sruffell Note Added: 0109025
======================================================================
More information about the asterisk-bugs
mailing list