[asterisk-bugs] [LibPRI 0016981]: [patch] PRI loopback support, when in CPE mode.

[Asterisk Bug Tracker]

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 18:12 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.
  
====================================================================== 

---------------------------------------------------------------------- 
 (0119166) alecdavis (manager) - 2010-03-08 18:12
 https://issues.asterisk.org/view.php?id=16981#c119166 
---------------------------------------------------------------------- 
This turns out to be only any good for a CPE-CPE crossover between 2 ports,
not loopback on the same port.

Channel conflict, prevents single port loopback. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-03-08 18:12 alecdavis      Note Added: 0119166                          
======================================================================