[asterisk-bugs] [Asterisk 0017318]: [patch] FXS Polarity Reversal on Hangup or Answer
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Aug 12 00:14:08 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17318
======================================================================
Reported By: armeniki
Assigned To: alecdavis
======================================================================
Project: Asterisk
Issue ID: 17318
Category: NewFeature
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Asterisk Version: I did not set the version :(
JIRA:
Regression: No
Reviewboard Link: https://reviewboard.asterisk.org/r/797/
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-05-11 06:12 CDT
Last Modified: 2010-08-12 00:14 CDT
======================================================================
Summary: [patch] FXS Polarity Reversal on Hangup or Answer
Description:
FXS lines normally connect to a telephone. However, when FXS lines are
routed to an external PBX or Key System to act as "external" or "CO" lines,
it is extremely difficult, if not impossible for the external PBX to know
when the call has been disconnected without receiving a polarity reversal
on the line.
DAHDI/Asterisk should have a feature to allow a setting someplace, perhaps
in chan_dahdi.conf, to allow a FXS channel to provide a polarity reversal
on channel hangup.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0017724 [patch] Race condition in handling writ...
======================================================================
----------------------------------------------------------------------
(0125879) alecdavis (manager) - 2010-08-12 00:14
https://issues.asterisk.org/view.php?id=17318#c125879
----------------------------------------------------------------------
Loop Start should be fine on a TDM400P
Apply the patch bug17318_debug_output.diff.txt and start monitoring
/var/log/full.
note: /etc/asterisk/logger.conf requires
[logfiles]
.....
full => notice,warning,error,debug,verbose
Issue History
Date Modified Username Field Change
======================================================================
2010-08-12 00:14 alecdavis Note Added: 0125879
======================================================================
More information about the asterisk-bugs
mailing list