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

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
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:                     ready for testing
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2009-10-12 12:40 CDT
Last Modified:              2009-10-18 04:07 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.
====================================================================== 

---------------------------------------------------------------------- 
 (0112387) tzafrir (manager) - 2009-10-18 04:07
 https://issues.asterisk.org/view.php?id=16060#c112387 
---------------------------------------------------------------------- 
While this fix looks too simple, it works for all the cases I've tried.

So now I challenge you all to find a scenario where this fix breaks
something :-) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-18 04:07 tzafrir        Note Added: 0112387                          
2009-10-18 04:07 tzafrir        Status                   acknowledged => ready
for testing
======================================================================