[asterisk-bugs] [Zaptel 0012394]: CallerID no longer works in 1.4.10

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12394 
====================================================================== 
Reported By:                eeman
Assigned To:                sruffell
====================================================================== 
Project:                    Zaptel
Issue ID:                   12394
Category:                   wctdm24xxp
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Zaptel Version:             1.4.10 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-09-2008 08:31 CDT
Last Modified:              06-04-2008 03:01 CDT
====================================================================== 
Summary:                    CallerID no longer works in 1.4.10
Description: 
Have a TDM800P and a TDM410P. Due to a battery bug in the last couple
versions of zaptel I cannot specify exactly when this bug crept into the
code. I went from 1.4.6 to 1.4.10, previous attempts to run 1.4.8 and
1.4.9.x resulted in the inability to make calls due to a misperceived alarm
state. 

I can confirm that I am able to make calls out using 1.4.10, however all
inbound calls fail to get the callerid name or number. I have added up to 1
second of wait at the beginning of the dialplan to give more time to
collect callerid (common pri trick) but still no CallerID information.
CallerID works flawlessly in 1.4.6
====================================================================== 

---------------------------------------------------------------------- 
 mattbrown - 06-04-08 03:01  
---------------------------------------------------------------------- 
Battery bug still seems to be an issue for me in Zaptel 1.4.11:

Jun  4 09:04:30 max kernel: [22341818.860000] RING on 1/4!
Jun  4 09:04:30 max kernel: [22341818.860000] 1290487419 Polarity reversed
(-1 -> 1)
Jun  4 09:04:30 max kernel: [22341819.116000] NO RING on 1/4!
Jun  4 09:04:32 max kernel: [22341820.588000] RING on 1/4!
Jun  4 09:04:33 max kernel: [22341821.804000] NO RING on 1/4!
Jun  4 09:04:33 max kernel: [22341822.076000] RING on 1/4!
Jun  4 09:04:33 max kernel: [22341822.076000] 1290488223 Polarity reversed
(1 -> -1)
Jun  4 09:04:33 max kernel: [22341822.332000] NO RING on 1/4!
Jun  4 09:04:47 max kernel: [22341835.512000] RING on 1/4!
Jun  4 09:04:47 max kernel: [22341835.512000] 1290491582 Polarity reversed
(-1 -> 1)
Jun  4 09:04:47 max kernel: [22341835.768000] NO RING on 1/4!
Jun  4 09:04:48 max kernel: [22341837.272000] RING on 1/4!
Jun  4 09:04:49 max kernel: [22341838.472000] 1290492322 Polarity reversed
(1 -> -1)
Jun  4 09:04:50 max kernel: [22341838.808000] NO RING on 1/4!
Jun  4 09:05:09 max kernel: [22341858.344000] NO BATTERY on 1/4!
Jun  4 09:05:09 max kernel: [22341858.440000] BATTERY on 1/4 (-)!

After this last (3rd) ring the line is off hook and callers get an engaged
tone when calling - this usually remains in this state for 30-60 secs or is
cleared if the card is reset.

I am using a Digium TDM400P 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-04-08 03:01  mattbrown      Note Added: 0087775                          
======================================================================