[asterisk-bugs] [LibPRI 0016981]: [patch] PRI loopback support, when in CPE mode.
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Mar 8 03:18:46 CST 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16981
======================================================================
Reported By: alecdavis
Assigned To:
======================================================================
Project: LibPRI
Issue ID: 16981
Category: NewFeature
Reproducibility: always
Severity: tweak
Priority: normal
Status: new
Asterisk Version: SVN
JIRA:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!): 249405
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2010-03-08 03:06 CST
Last Modified: 2010-03-08 03:18 CST
======================================================================
Summary: [patch] PRI loopback support, when in CPE mode.
Description:
Loopback at the RJ45 connector has been disabled since revision 3.
The main change here is the is_command() function, currently we test if
'we' are the CPE or the NETWORK, the logic change is to test if the
'remote' is a NETWORK or CPE.
This then allows us to do CPE-CPE or CPE loopback.
NETWORK-NETWORK is hindered due to explicit channel selection.
======================================================================
----------------------------------------------------------------------
(0119081) alecdavis (manager) - 2010-03-08 03:18
https://issues.asterisk.org/view.php?id=16981#c119081
----------------------------------------------------------------------
PRI RJ45 loopback connections required:<pre>1----o
2----|--o
3 | |
4----o |
5-------o
6
7
8</pre>
Issue History
Date Modified Username Field Change
======================================================================
2010-03-08 03:18 alecdavis Note Added: 0119081
======================================================================
More information about the asterisk-bugs
mailing list