[asterisk-bugs] [Zaptel 0012394]: CallerID no longer works in 1.4.10
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed May 28 16:04:49 CDT 2008
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: 05-28-2008 16:04 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
======================================================================
----------------------------------------------------------------------
estokien - 05-28-08 16:04
----------------------------------------------------------------------
I can say that we are having this caller id issue in my office with a
tdm2400p, that it does not occur on a tdm400p, and that setting the zaptel
version back to 1.4.8 fixes this issue (but causes other issues to occur in
our case). I will also note that while this happens nearly all of the
time, there have been a few instances where the outside caller id
information did get through to asterisk, and displayed to the person being
called. There is no effect on the caller id when it is from one SIP phone
to another, only when it goes through the card. I'm in North America, and
am happy to provide any help that would be useful.
Issue History
Date Modified Username Field Change
======================================================================
05-28-08 16:04 estokien Note Added: 0087468
======================================================================
More information about the asterisk-bugs
mailing list