[asterisk-bugs] [Zaptel 0013188]: zaptel as of 1.2.25 no longer recognizes incoming rings on wctdm fxo ports

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13188 
====================================================================== 
Reported By:                pyves
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   13188
Category:                   wctdm
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Zaptel Version:              1.2.25 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-29 04:49 CDT
Last Modified:              2008-07-29 14:10 CDT
====================================================================== 
Summary:                    zaptel as of 1.2.25 no longer recognizes incoming
rings on wctdm fxo ports
Description: 
Upgrading from zaptel 1.2.24 to 1.2.25 breaks asterisk's (all versions
tried, including 1.2.30.1) ability to detect incoming calls on wctdm fxo
ports. I also tried 1.2.26, but got the same result.

Downgrading to 1.2.24 or earlier, fixes the problem.

This issue has also been observed by others:

http://lists.digium.com/pipermail/asterisk-users/2008-July/215238.html


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

---------------------------------------------------------------------- 
 (0090812) tzafrir (manager) - 2008-07-29 14:10
 http://bugs.digium.com/view.php?id=13188#c90812 
---------------------------------------------------------------------- 
http://lists.digium.com/pipermail/asterisk-users/2008-July/215986.html

In response to another thread on the same issue, Kevin Fleming writes:

It is very likely 4128, based on the code it affects and the behavior
that is being reported. Please let us know as soon as you can (anyone
who has this problem), if reverting r4128 from current Zaptel branch 1.2
SVN solves the problem. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-07-29 14:10 tzafrir        Note Added: 0090812                          
======================================================================