[asterisk-bugs] [Asterisk 0014163]: [patch] UK (BT) lines produce uncleared red alarm on TDM400P during line tests
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jul 22 14:51:40 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=14163
======================================================================
Reported By: jedi98
Assigned To: sruffell
======================================================================
Project: Asterisk
Issue ID: 14163
Category: Channels/chan_dahdi
Reproducibility: always
Severity: minor
Priority: normal
Status: ready for review
Asterisk Version: 1.4.22
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-01-02 10:29 CST
Last Modified: 2009-07-22 14:51 CDT
======================================================================
Summary: [patch] UK (BT) lines produce uncleared red alarm on
TDM400P during line tests
Description:
Asterisk: 1.4.22, dahdi-linux: 2.1.0.3
The automatic overnight line tests (or manual ones) used on UK (BT) lines
causes a red alarm on a dahdi / TDM400P connected channel. This is because
the line uses voltage tests (battery loss) and polarity reversal. The
polarity reversal causes chan_dahdi to initiate v23 CallerID processing but
during this the event DAHDI_EVENT_NOALARM is ignored so that the alarm is
never cleared.
All this means that the channel is unusable until a "dahdi restart"
occurs.
I have a patch for chan_dahdi which works well for me but it's not the
nicest solution an it needs more people to test / refine. I will attach the
patch.
Syslog: -
Dec 29 22:09:56 39net-server2 kernel: NO BATTERY on 1/3!
Dec 29 22:09:58 39net-server2 kernel: 436822404 Polarity reversed (-1 ->
1)
Dec 29 22:09:58 39net-server2 kernel: BATTERY on 1/3 (+)!
Dec 29 22:10:00 39net-server2 kernel: NO BATTERY on 1/3!
Dec 29 22:10:02 39net-server2 kernel: 436823620 Polarity reversed (1 ->
-1)
Dec 29 22:10:03 39net-server2 kernel: BATTERY on 1/3 (-)!
Dec 29 22:10:05 39net-server2 kernel: NO BATTERY on 1/3!
Dec 29 22:10:05 39net-server2 kernel: 436824308 Polarity reversed (-1 ->
1)
Dec 29 22:10:07 39net-server2 kernel: BATTERY on 1/3 (-)!
Dec 29 22:10:07 39net-server2 kernel: 436824688 Polarity reversed (1 ->
-1)
Asterisk log: -
[Dec 29 22:09:57] WARNING[10309]: chan_dahdi.c:3784 handle_alarms:
Detected alarm on channel 3: Red Alarm
== Starting post polarity CID detection on channel 3
-- Starting simple switch on 'DAHDI/3-1'
[Dec 29 22:09:59] NOTICE[10332]: chan_dahdi.c:6319 ss_thread: Got event 5
(No more alarm)...
[Dec 29 22:10:01] WARNING[10332]: chan_dahdi.c:6380 ss_thread: CID timed
out waiting for ring. Exiting simple switch
-- Hungup 'DAHDI/3-1'
[Dec 29 22:10:01] WARNING[10309]: chan_dahdi.c:3784 handle_alarms:
Detected alarm on channel 3: Red Alarm
== Starting post polarity CID detection on channel 3
-- Starting simple switch on 'DAHDI/3-1'
[Dec 29 22:10:03] NOTICE[10333]: chan_dahdi.c:6319 ss_thread: Got event 5
(No more alarm)...
[Dec 29 22:10:06] WARNING[10333]: chan_dahdi.c:6380 ss_thread: CID timed
out waiting for ring. Exiting simple switch
-- Hungup 'DAHDI/3-1'
[Dec 29 22:10:06] WARNING[10309]: chan_dahdi.c:3784 handle_alarms:
Detected alarm on channel 3: Red Alarm
== Starting post polarity CID detection on channel 3
-- Starting simple switch on 'DAHDI/3-1'
[Dec 29 22:10:08] NOTICE[10334]: chan_dahdi.c:6319 ss_thread: Got event 5
(No more alarm)...
[Dec 29 22:10:10] WARNING[10334]: chan_dahdi.c:6380 ss_thread: CID timed
out waiting for ring. Exiting simple switch
======================================================================
----------------------------------------------------------------------
(0108092) benbrown (reporter) - 2009-07-22 14:51
https://issues.asterisk.org/view.php?id=14163#c108092
----------------------------------------------------------------------
I recently updated to asterisk 1.6.1.1 and dahdi 2.2.0.
Needed to apply this patch (needed modifying to apply cleanly to 1.6.1) to
avoid the issue of the daily BT line test putting the channel in alarm.
BT CID working OK for last year with unpatch Asterisk/DAHDI configured
as:
modprobe.conf:
opermode=uk fwringdetect=1 batthresh=4
chan_dahdi.conf:
usecallerid=yes
cidsignalling=v23
cidstart=polarity
hanguponpolarityswitch=yes
battthresh and hanguponpolarityswitch required otherwise phone continues
to ring if the caller hangs up.
Issue History
Date Modified Username Field Change
======================================================================
2009-07-22 14:51 benbrown Note Added: 0108092
======================================================================
More information about the asterisk-bugs
mailing list