[asterisk-bugs] [Zaptel 0012099]: wctdm24xxp / wctdm drivers can generate erroneous battery alarms depending on location.

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12099 
====================================================================== 
Reported By:                sruffell
Assigned To:                sruffell
====================================================================== 
Project:                    Zaptel
Issue ID:                   12099
Category:                   wctdm24xxp
Reproducibility:            sometimes
Severity:                   minor
Priority:                   normal
Status:                     assigned
Zaptel Version:              SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 3869 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             02-28-2008 11:09 CST
Last Modified:              02-29-2008 15:44 CST
====================================================================== 
Summary:                    wctdm24xxp / wctdm drivers can generate erroneous
battery alarms depending on location.
Description: 
In some locations, there are short glitches in the battery alarm from the
telco that causes zaptel to generate battery alarms when it takes an FXO
line off-hook.


[Feb 25 17:28:13] VERBOSE[25071] logger.c:     -- Executing
[s at macro-dialout-trunk:23] Dial("Zap/1-1", "ZAP/4/www411|300|wW") in new
stack
[Feb 25 17:28:13] DEBUG[25071] chan_zap.c: Dialing 'www411'
[Feb 25 17:28:13] DEBUG[25071] chan_zap.c: Deferring dialing...
[Feb 25 17:28:13] VERBOSE[25071] logger.c:     -- Called 4/www411
[Feb 25 17:28:14] WARNING[25071] chan_zap.c: Detected alarm on channel 4:
No Alarm
[Feb 25 17:28:14] VERBOSE[25071] logger.c:     -- Hungup 'Zap/4-1'
[Feb 25 17:28:14] VERBOSE[25071] logger.c:   == Everyone is busy/congested
at this time (1:0/0/1)


====================================================================== 

---------------------------------------------------------------------- 
 kpfleming - 02-29-08 15:44  
---------------------------------------------------------------------- 
Unfortunately we'll need more than just 'calls are not received'. Were
there no log messages at all when a call was ringing on the FXO port? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-29-08 15:44  kpfleming      Note Added: 0083167                          
======================================================================