[asterisk-bugs] [DAHDI-linux 0016060]: [patch] RX RBS signalling not reset on alarm

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16060 
====================================================================== 
Reported By:                tzafrir
Assigned To:                tzafrir
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   16060
Category:                   dahdi (the module)
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
JIRA:                        
Reviewboard Link:            
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-10-12 12:40 CDT
Last Modified:              2010-01-10 09:33 CST
====================================================================== 
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.
====================================================================== 

---------------------------------------------------------------------- 
 (0116421) tzafrir (manager) - 2010-01-10 09:33
 https://issues.asterisk.org/view.php?id=16060#c116421 
---------------------------------------------------------------------- 
It turned out that this issue is basically an issue that should be resolved
on the driver level. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-10 09:33 tzafrir        Note Added: 0116421                          
2010-01-10 09:33 tzafrir        Status                   ready for testing =>
resolved
2010-01-10 09:33 tzafrir        Resolution               open => no change
required
2010-01-10 09:33 tzafrir        Status                   resolved => closed  
======================================================================