[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:              04-28-2008 14:17 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 - 04-28-08 14:17  
---------------------------------------------------------------------- 
I can confirm I have also seen the BATTERY & NO BATTERY bug in version
1.4.10 (I jumped from 1.4.5.1)

I live in the UK, in order to detect the hangup from the remote party, I
enabled the hanguponpolarity switch which when the BATTERY issue raises it
head causes the call to be dropped. Always reproducible and usually occurs
within a few mins of an outgoing call. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-28-08 14:17  mattbrown      Note Added: 0086110                          
======================================================================