[asterisk-bugs] [Asterisk 0012453]: [patch] British Telecom line testing causes segfault on chan_zap.c

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=12453 
====================================================================== 
Reported By:                Alex728
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   12453
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.19 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             04-15-2008 19:39 CDT
Last Modified:              06-19-2008 17:46 CDT
====================================================================== 
Summary:                    [patch] British Telecom line testing causes segfault
on chan_zap.c
Description: 
Telephone lines in the UK are subjected to various automatic line tests in
the evening. These include a polarity reversal, and alternate application
of earth and battery (-48V) to the A and B wires (Tip and ring) 

Since version 1.4.18 of Asterisk, these conditions are detected first as a
spurious zaptel alarm, then a polarity reversal before caller ID. For some
reason this causes chan_zap.c to crash with a segmentation fault.

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

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-19-08 17:46  svnbot         Status                   feedback => resolved
06-19-08 17:46  svnbot         Resolution               open => fixed       
======================================================================