[asterisk-bugs] [DAHDI-linux 0013897]: [patch] Support for generic HFC-4S cards
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Mar 11 08:27:11 CDT 2009
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13897
======================================================================
Reported By: tzafrir
Assigned To: tzafrir
======================================================================
Project: DAHDI-linux
Issue ID: 13897
Category: wcb4xxp
Reproducibility: N/A
Severity: feature
Priority: normal
Status: confirmed
======================================================================
Date Submitted: 2008-11-13 16:17 CST
Last Modified: 2009-03-11 08:27 CDT
======================================================================
Summary: [patch] Support for generic HFC-4S cards
Description:
A patch to add some basic support of other HFC-4S -based PCI cards (such as
the ones made by Junghanns).
Status: gets rid of the echo canceller messages when not needed, but still
needs work.
Specifically:
* It adds too broad a range of cards (which also include bero.net cards)
* The range may include some 2-ports cards, which will probably not work.
Not yet tested to work, though it it is at least configured.
======================================================================
----------------------------------------------------------------------
(0101521) lanzaandrea (reporter) - 2009-03-11 08:27
http://bugs.digium.com/view.php?id=13897#c101521
----------------------------------------------------------------------
I see you are looking for testers. I am trying to use dahdi instead of my
years-running mISDN.
My box include 2 single span HFC cards, in TE mode (p2mp TE mode )
dahdi_hardware recognizes them as:
pci:0000:00:09.0 zaphfc- 1397:2bd0 HFC-S ISDN BRI card
pci:0000:00:0a.0 zaphfc- 1397:2bd0 HFC-S ISDN BRI card
but dahdi_genconf does not produce any valuable configuration.
If I try to write by myself a "reasonable" system.conf:
loadzone = it
defaultzone = it
span=1,1,0,ccs,ami
span=2,2,0,ccs,ami
bchan=1,2
hardhdlc=3
bchan=4,5
hardhdlc=6
using svn trunk ( 6111) and giving :
modprobe wcb4xxp -vvv
dahdi_cfg -vvv
I get:
DAHDI Tools Version - SVN-trunk-r6110
DAHDI Version: SVN-trunk-r6096
Echo Canceller(s):
Configuration
======================
SPAN 1: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 2: CCS/ AMI Build-out: 0 db (CSU)/0-133 feet (DSX-1)
Channel map:
Channel 01: Clear channel (Default) (Slaves: 01)
Channel 02: Clear channel (Default) (Slaves: 02)
Channel 03: Hardware assisted D-channel (Default) (Slaves: 03)
Channel 04: Clear channel (Default) (Slaves: 04)
Channel 05: Clear channel (Default) (Slaves: 05)
Channel 06: Hardware assisted D-channel (Default) (Slaves: 06)
6 channels to configure.
DAHDI_SPANCONFIG failed on span 1: No such device or address (6)
The question is: should in principle my configuration be acceptable and
further testing is required/appreciated, or should I revert to mISDN ?
I also own a Beronet card, a duan span BN2S0 card: is better to test also
with that card ?
asterisk:1.4.23.2 (1.6 strictly needed ?)
libpri-1.4.9
dahdi-tools-2.1.0.2 or svn 6111
dahdi-linux-2.1.0.4 or svn 6111
openSUSE 11.1 2.6.27.19-3.2-pae
I also tested dahdi-tools-2.1.0.2 and dahdi-linux-2.1.0.4 with
the here provided patches dated 9-3-2009 with no difference
Issue History
Date Modified Username Field Change
======================================================================
2009-03-11 08:27 lanzaandrea Note Added: 0101521
======================================================================
More information about the asterisk-bugs
mailing list