[asterisk-bugs] [DAHDI-linux 0016060]: [patch] RX RBS signalling not reset on alarm
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Oct 12 12:42:00 CDT 2009
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=16060
======================================================================
Reported By: tzafrir
Assigned To:
======================================================================
Project: DAHDI-linux
Issue ID: 16060
Category: dahdi (the module)
Reproducibility: always
Severity: minor
Priority: normal
Status: new
JIRA:
Reviewboard Link:
======================================================================
Date Submitted: 2009-10-12 12:40 CDT
Last Modified: 2009-10-12 12:42 CDT
======================================================================
Summary: [patch] RX RBS signalling not reset on alarm
Description:
A had an incoming call in a CAS channel was running when an alarm was set.
The alarm triggered disconnecting the call. However once the alarm is
cleared, the channel can no longer be used for outgoing call until a call
comes in.
The hardware driver reported an alarm. But the fact that the state of the
call has changed is not exactly a concern of the hardware driver. In case
of CAS the state is maintained by DAHDI. And indeed the call has failed
because nobody bothered updating the RX rbsbits of the channel.
The attached patch aims at doing so.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-10-12 12:42 tzafrir Summary RX RBS signalling not
reset on alarm => [patch] RX RBS signalling not reset on alarm
======================================================================
More information about the asterisk-bugs
mailing list