[asterisk-bugs] [Asterisk 0012160]: [patch] channel alarm set when a channel is opened

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12160 
====================================================================== 
Reported By:                tzafrir
Assigned To:                kpfleming
====================================================================== 
Project:                    Asterisk
Issue ID:                   12160
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 106393 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             03-06-2008 10:11 CST
Last Modified:              07-22-2008 17:24 CDT
====================================================================== 
Summary:                    [patch] channel alarm set when a channel is opened
Description: 
If a channel alarm is already set when a channel is opened by Asterisk,
whose responsibility is it to check for the alarms?

1. The channe l driver should detect that and re-send alarms on zt_open

2. Zaptel should  send an alarm event at channel open time. The
applicaiton opening the channel should then be able to read those events
and will have the proper information.

3. The application should read channel alarms at channel initialization
time. No need for Zaptel to send extra events.

As senseless as (1) is, it has been used in practice by the xpp d FXO
module driver. I figure you all agree with me it is not the way to go.


The behaviour with regards to span alarm seems in Asterisk seems to be
(3).

Attached are patches implementing both (2) and (3)
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012841 Unable to get the hook status for 100XP...
====================================================================== 

---------------------------------------------------------------------- 
 kpfleming - 07-22-08 17:24  
---------------------------------------------------------------------- 
resolved in r132712 of branches/1.4, and merged to trunk and 1.6.0 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-22-08 17:24  kpfleming      Note Added: 0090579                          
======================================================================