|Summary:||ASTERISK-14671: Analog phone displays unknown caller after hangup|
|Date Opened:||2009-08-17 20:28:51||Date Closed:||2011-06-07 14:07:19|
|Environment:||Attachments:||( 0) asterisk.log|
( 1) logger.conf
|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. |
****** ADDITIONAL INFORMATION ******
# Autogenerated by /usr/sbin/dahdi_genconf on Sun Aug 16 17:09:57 2009
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
# This file is parsed by the Dahdi Configurator, dahdi_cfg
# Span 1: WCTDM/4 "Wildcard S400P Prototype Board 5" (MASTER)
# Global data
loadzone = us
defaultzone = us
context=phones ; Uses the [internal] context in extensions.conf
signalling=fxo_ks ; Uses FXO signalling for an FXS channel
channel => 4 ; Telephone atta
transfer = yes
|Comments:||By: Leif Madsen (lmadsen) 2009-09-17 15:17:57|
Can you retest with the latest 220.127.116.11-rc1 release and tell me if it is still doing the same thing?
If so, we'll need the asterisk console output, along with debugging logs (logger.conf, enable debug on the console line, then do 'core set debug 10' on the asterisk console after doing a 'logger reload').
Attach that information to this issue. If no issue still exists, let me know, and we'll get this closed out. Thanks!
By: joeservo (joeservo) 2009-09-17 20:40:07
I will load it tomorrow night. If I still have issues I will send you the requested information and even give you remote access to the server if you want look at it as well.
By: joeservo (joeservo) 2009-09-19 08:35:19
Still has the issue. Sorry I did not do it last night got hung up at work and did not get home till late. I can also load the newer version 18.104.22.168 if you would like me to try that. I have uploaded the files you requested as well. I did not see any output on the console that explains the unknown call on the analog phone. It shows up at or close to the Dahdi hungup display. If I make a call from sip I do not have the issue. It will also do it just by going onhook/offhook and not dialing a call. Let me know if you would access to the box it is on the internet and I do not mind being a beta tester.
By: Leif Madsen (lmadsen) 2009-09-22 09:32:53
I'm not sure what else to ask for at this time, so I'm going to set this issue to Acknowledged.
By: joeservo (joeservo) 2009-09-22 09:41:56
Ok let me know if you need access. I can do a live video so you can see the phone at the same time as the cli.
By: John Todd (jtodd) 2009-10-05 11:34:26
Is this a Digium board you're using, and if so, what is the serial number on the board? There are suspicions that this is a hardware problem, and we'd like to have you talk to our technical support group via the phone if this is Digium hardware as this is a very odd issue. We'd like a bit more debug information before we tackle this one, and we need to understand what hardware is being used.
By: joeservo (joeservo) 2009-10-06 05:09:45
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@starfleetHQ ~]# dahdi_scan
description=Wildcard S400P Prototype Board 5
devicetype=Wildcard S400P Prototype
location=PCI Bus 02 Slot 11
By: Leif Madsen (lmadsen) 2009-10-07 09:01:17
OK, we will wait for you to verify, but since the S400P is no longer in production, it is possible there might not be much that can be done here.
By: Russell Bryant (russell) 2009-10-08 11:33:49
If you bought it off of ebay, it is unlikely that it is actually a Digium board. However, it could be.
I would recommend that you contact Digium technical support for further assistance. If they are able to determine that this is Digium hardware, they can help you further troubleshoot this issue. If it's not our hardware, you will need to contact your hardware vendor for support.