[asterisk-bugs] [DAHDI-linux 0013897]: [patch] Support for generic HFC-4S cards

[Asterisk Bug Tracker]

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-01-05 05:07 CST
====================================================================== 
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.

====================================================================== 

---------------------------------------------------------------------- 
 (0097033) timking (reporter) - 2009-01-05 05:07
 http://bugs.digium.com/view.php?id=13897#c97033 
---------------------------------------------------------------------- 
I have both Junghanns and OpenVox cards here in the UK. Testing using
asterisk-1.6.0.3-rc1 and dahdi 2.1.0.3.

Testing this patch first on OpenVox B200p. I needed to alter the NT /TE
test as described above (nt = ((gpio & (1 << (i + 4))) != 0)) to get TE
mode detected; I assume that this is the other way round for Digium cards?

I can make and receive calls fine, except that I get D Channel Up and down
messages on a regular basis. pri debug is

Sending Unnumbered Acknowledgement
q921.c:798 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
  == Primary D-Channel on span 1 down
[Jan  5 11:06:34] WARNING[17400]: chan_dahdi.c:2997 pri_find_dchan: No
D-channels available!  Using Primary channel 3 as D-channel anyway!
Sending Set Asynchronous Balanced Mode Extended
q921.c:211 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH
-- Got UA from network peer  Link up.
q921.c:798 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:749 q921_dchannel_up: q921_state now is
Q921_LINK_CONNECTION_ESTABLISHED
  == Primary D-Channel on span 1 up
-- Got Disconnect from peer.
Sending Unnumbered Acknowledgement
q921.c:798 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
  == Primary D-Channel on span 1 down
[Jan  5 11:07:25] WARNING[17400]: chan_dahdi.c:2997 pri_find_dchan: No
D-channels available!  Using Primary channel 3 as D-channel anyway!
Sending Set Asynchronous Balanced Mode Extended
q921.c:211 q921_send_sabme: q921_state now is Q921_AWAITING_ESTABLISH
-- Got UA from network peer  Link up.
q921.c:798 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
q921.c:749 q921_dchannel_up: q921_state now is
Q921_LINK_CONNECTION_ESTABLISHED
  == Primary D-Channel on span 1 up 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-05 05:07 timking        Note Added: 0097033                          
======================================================================