Dahdi support B200P-B400P

I saw your post in Digium bugs section. Have yo tested B800P? ¨What do you think about rewrite driver on hw.id basis instead ports basis??

hello,
I am testing the code with B800P, but i got an error:
====================================================================
Running dahdi_cfg: DAHDI_SPANCONFIG failed on span 1: Invalid argument (22)
====================================================================
I am checking that error. if you rewrite code on hw.id base, i think you can do like mISDN, the style is good. i prefer ports base because some business concern is here, Digium will not really want to you add third party product ID in their code. this is my concern.
regards!
James.zhu

Hi!
take a look at new code in digium bug section. It's card based. In that basis we can tune it for all our needs. Have you demo cards in Spain representative? I have Axxp (analogs) B200P and some E1 cards., but no plans for 800s. Or perhaps could you prepare for me a test server with one 800 & give me ssh access.
Give me some info about this card. Chips & quantity.... something.

Dahdi driver is misdn/qozap ported in many sections. The trick is work in "Digium" mode for adding drivers natively, because if they are not included in Dahdi trunk, automatic updates are impossible... Think about all Trixbox & Elastix users, for example. Not native support, no low skills users....so in the end, asterisk is open source & you can support them via Elastix for example. (kmoddded rpms).
Our main at this point is making it stable.

Take a look at /dev/dahdi/
what's there?
if card is starting wc4bxxp driver it might have (nothing else dahdi-complaint plugged)

channel
ctl
pseudo
timer
1
2
3
.......
24

Is they exist, one more thing to edit . Delete etc/dahdi/system.conf
make dahdi_genconf again
dahdi_cfg -d 999
whats in line 22??

i] Last edited by Jose at 2009-2-26 09:13 [/i