[asterisk-bugs] [LibPRI 0016981]: [patch] PRI support for CPE-CPE crossover

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Jun 3 11:09:43 CDT 2010


The following issue is now READY FOR TESTING. 
====================================================================== 
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:                     ready for testing
Asterisk Version:           SVN 
JIRA:                       SWP-1609 
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-06-03 11:09 CDT
====================================================================== 
Summary:                    [patch] PRI support for CPE-CPE crossover
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.
  
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-06-03 11:09 lmadsen        Status                   acknowledged => ready
for testing
======================================================================




More information about the asterisk-bugs mailing list