DAHDI Digium TE220 E1 with MFC/R2 support

[PaulScott]

Guys,

I know that Digium cards is not what you like, since Sangoma is what Matt uses. But right now I need to setup our Digium TE220 with openr2 (mfc/r2) support for a E1 TRUNK on a Redux 3.0.9 standalone server install.

Hardware is DELL POWEREDGE 2900 (8cores), 4GB Mem and RAID 10.

The problem that I have is Dahdi do not start up any SPAN, even whit right /etc/dahdi/system.conf manually edited.

Code: Select all

# MFC/R2 requires CAS signaling
# # channel 16 is required to transmit ABCD bits so is not used for voice
span=1,1,0,cas,hdb3
cas=1-15:1101
dchan=16
cas=17-31:1101

loadzone=us
defaultzone=us

dahdi_cfg -vv output this error message:

Code: Select all

"DAHDI_SPANCONFIG failed on span 1: No such device or address"

I just compiled openr2-1.3.0 and applied openr2-asterisk-1.4.32-p1.patch from http://code.google.com/p/openr2/downloads/list

Then recompiled dahdi and asterisk, without success.

Can anyone help me on this?....

Regards.

[williamconley]

try a stock installation of asterisk (or trixbox or anthing similar) and see if you can get one of those to auto-install it for you properly. If so, steal the setup and see if it will work on vicibox. If you find something useful that would help Vicibox 3.0.X, please be sure to inform Kumba.

I realize it's extra effort, but since trixbox and asterisk are both free ... and a generic Ubuntu or OpenSuSE installation will provide Asterisk setup ... it should not be that much of an issue. And Trixbox has been around long enough to have generic installation scripts for most hardware out there.

So instead of reinventing the wheel (or having a mechanic diagnose your issue ...) see if you can sidestep it with some install time while you're doing other things and hopefully come up with a free solution

[PaulScott]

I've been doing some testing and get it working after realize that dahdi isn't loading wct4xxp driver needed by TE220 to work properly.

After manually run:
modprobe wct4xxp
dahdi_cfg -vv
dmesg

mfc/r2 span's are loaded just right.

But if I reboot the server, changes are not taken and dahdi isn't load wct4xxp.

There is a line in /etc/init.d/vicidial that reads:

Code: Select all

# Zaptel module name, please replace with driver name for hardware card
# If using a wanpipe_voicetime modules, please change to wanpipe_voicetime
ZAP_MOD=dahdi_dummy


Could be possible that we need to specify wct4xxp here to force it load properly?... or is another place where it must be done?...

Thanks.

[williamconley]

excellent post-back!

test your theory and post that back, too ... even if only so when you build your next system you can find your notes easily.

[Kumba]

Yes, that line is where you specify the dahdi/zaptel module to load. change it from dahdi_dummy to whatever you need.

[PaulScott]

Thank you all.

I'm working to setup a second card (Yeastar TDM1600 FXO) on same server, I need to patch dahdi to get it recognized and setup a new span on.

We will use this 16 fxo span to route cell phone calls through Fixed Wireless Terminal FWT, so we can save on cell phone rates.

Regards,

[striker]

commet the driver from the following conf fie and then reboot and check

vi /etc/modprobe.d/dahdi.blacklist.conf

[PaulScott]

Guys,

How could I force dahdi to load modules when we have more than one card?...

I need that modules get loaded in specific order:

1st wct4xxp
2nd ystdm16xx

Because my spans works only with that order.

I have a Digium TE210 with module 'wct4xxp' loading fine.

But when adding second card 'ystdm16xx' module in:

/etc/dahdi/modules

Code: Select all

wct4xxp
ystdm16xx


then reboot, and module 'ystdm16xx' is not loading.

I wonder how could I add this second module to /etc/init.d/vicidial on section:
ZAP_MOD=wct4xxp

I also have

/etc/modprobe.d/dahdi.blacklisted

Code: Select all

blacklist wct4xxp
blacklist ystdm16xx
blacklist ystdm8xx
blacklist wcte12xp
blacklist wct1xxp
blacklist wcte11xp
blacklist wctdm24xxp
blacklist wcfxo
blacklist wctdm
blacklist wctc4xxp
blacklist wcb4xxp
blacklist netjet


[Kumba]

You will have to edit /etc/init.d/vicidial and manually add the extra drivers you want loaded. You will probably want to add it below lines 298 and 303, right after the ZAP_MOD is loaded.