[asterisk-bugs] [Asterisk 0015971]: [patch] Support for physical tapping in PRI lines
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue May 18 10:25:38 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=15971
======================================================================
Reported By: moy
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 15971
Category: Channels/chan_dahdi/NewFeature
Reproducibility: N/A
Severity: feature
Priority: normal
Status: ready for testing
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 220626
Request Review:
======================================================================
Date Submitted: 2009-09-26 20:27 CDT
Last Modified: 2010-05-18 10:25 CDT
======================================================================
Summary: [patch] Support for physical tapping in PRI lines
Description:
It is possible to tap E1/T1 links physically and receive 2 E1/T1 cables to
receive Tx and Rx media and signaling in another box for the tapped line.
This patch and Asterisk branch allows to handle this tapping lines.
Asterisk (through chan_dahdi.so) will detect a call in any direction (to or
from CPE/NET) and create a new call in the monitoring PBX, of course any
transmission is disabled (therefore dahdi_write drop any frames being
sent). Given that tx and rx are separated in 2 dahdi chans, chan_dahdi
creates internally a dahdi conference that is used to mix the tx and rx
streams into a single stream that dahdi_read will use to return frames to
the core.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-05-18 10:25 lmadsen Steps to Reproduce Updated
======================================================================
More information about the asterisk-bugs
mailing list