[asterisk-bugs] [DAHDI-linux 0016447]: [patch] typo in Junghanns QuadBRI PCI id

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16447 
====================================================================== 
Reported By:                lpistone
Assigned To:                
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   16447
Category:                   wcb4xxp
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
JIRA:                        
Reviewboard Link:            
====================================================================== 
Date Submitted:             2009-12-15 09:42 CST
Last Modified:              2009-12-17 08:54 CST
====================================================================== 
Summary:                    [patch] typo in Junghanns QuadBRI PCI id
Description: 
Subsystem ID for the Junghanns QuadBRI card is 1397:b550 and not 1397:b520.
====================================================================== 

---------------------------------------------------------------------- 
 (0115374) lpistone (reporter) - 2009-12-17 08:54
 https://issues.asterisk.org/view.php?id=16447#c115374 
---------------------------------------------------------------------- 
Reading through notes on issue 0013897, I didn't see anyone reporting
success on a Junghanns QuadBRI. I only know my card was bought in 2007 and
have no idea wheather there are other versions of it with different
pciid's. I didn't get much success. Dahdi_tool shows my alarm status as
"OK" but when I try to call I get  strange error messages: 
dahdi_call: unrecognized prilocaldialplan NPI modifier: s
where "s" is the first character of the SIP name of the device i'm using
to place the call. I also configured a port as NT, but connecting it to a
legacy PBX, the alarm is still RED. Tried with a isdn cross cable, but no
luck: still RED. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-12-17 08:54 lpistone       Note Added: 0115374                          
======================================================================