[asterisk-bugs] [Asterisk 0015733]: Analog phone displays unknown caller after hangup
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Oct 6 05:09:46 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=15733
======================================================================
Reported By: joeservo
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15733
Category: Channels/chan_dahdi
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Asterisk Version: 1.6.1.4
JIRA: SWP-219
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-08-17 20:28 CDT
Last Modified: 2009-10-06 05:09 CDT
======================================================================
Summary: Analog phone displays unknown caller after hangup
Description:
I upgraded from 1.4.26 which has been working for many months with no
issues. After the upgrade whenever an analog phone hangups it suddenly
shows unknown caller. The phone does not ring but does display a missed
called message. It appears the DAHDI drivers does not know the phone has
hung up. I will put my dahdi configs below.
======================================================================
----------------------------------------------------------------------
(0111901) joeservo (reporter) - 2009-10-06 05:09
https://issues.asterisk.org/view.php?id=15733#c111901
----------------------------------------------------------------------
I am not certain if it is a Digium board or not. I know I bought it off of
ebay well over a year ago. It is feasible it is another vendor. I would
need to shut the server down and pull the card out to determine the vendor.
Since my linux box runs the internet and phone at home I will have to wait
till this weekend to shut it down or risk the wife and kids implimenting a
change management system at home ;). I pasted below a snap shot from
dahdi_scan not sure if that is accurate. It would be weird if it was the
hardware. It worked fine on the older version running zap instead of dahdi.
Once I completed the upgrade thats when it started.
[root at starfleetHQ ~]# dahdi_scan
[1]
active=yes
alarms=OK
description=Wildcard S400P Prototype Board 5
name=WCTDM/4
manufacturer=Digium
devicetype=Wildcard S400P Prototype
location=PCI Bus 02 Slot 11
basechan=1
totchans=4
irq=22
type=analog
port=1,FXO
port=2,FXO
port=3,FXS
port=4,FXS
[root at starfleetHQ ~]#
Issue History
Date Modified Username Field Change
======================================================================
2009-10-06 05:09 joeservo Note Added: 0111901
======================================================================
More information about the asterisk-bugs
mailing list