[asterisk-bugs] [Zaptel 0012841]: Unable to get the hook status for 100XP card on reboot

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12841 
====================================================================== 
Reported By:                ramaseshireddy
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   12841
Category:                   wcfxo
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Zaptel Version:             1.4.11 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-12-2008 06:29 CDT
Last Modified:              06-30-2008 06:54 CDT
====================================================================== 
Summary:                    Unable to get the hook status for 100XP card on
reboot
Description: 

I am Ramaseshi reddy from India.I am using asterisk-1.4 and latest zaptel
drivers.

I installed Asterisk 100XP card on linux box.

I connected one POT to 100XP card and made incoming and outgoing calls but
when i reboot system it is getting hookstatus.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012160 [patch] channel alarm set when a channe...
====================================================================== 

---------------------------------------------------------------------- 
 tzafrir - 06-30-08 06:54  
---------------------------------------------------------------------- 
Sorry for the noise. Thinking again: the fixes from
http://bugs.digium.com/view.php?id=12160 may not fix this
but they touch near by.

The thing is that chan_zap will clear inalarm for any channel that is not
in a PRI (if you have PRI support compiled in). 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-30-08 06:54  tzafrir        Note Added: 0089424                          
======================================================================