TDM800 Help on clean 2.6.07 install
Submitted by nbruner on Fri, 05/09/2008 - 7:02am.
I'm about to pull my hair out, I'm sure I'm doing something stupid. Here's what I need help with. I'll give the cliff-notes version instead of posting every-single log file 1st go round.. ;-)
I slapped my TDM800 (4 FXO's) card in my new box, downloaded and installed trixbox 2.6.07, no errors, ran the yum -y update, no errors. From what I've been reading in multiple forums, the zaptel drivers should already be in this trixbox version for the TDM?
Update: forgot to add my issue.. I'm not seeing any FXO channels to even start to configure.
When I do a lspci , I do see the "Digium, Inc. Wildcard TDM800P 8-port analog card (rev 11)".
When i do a dmesg , I do see a "Found a Wildcard TDM: Wildcard TDM800P (8 modules)"
I've run a genzaptelconf several times with nothing added in conf.
In the zaptel.conf, I see the
# Span 1: WCTDM/0 "Wildcard TDM800P Board 1" (MASTER)
# channel 1, WCTDM, no module.
# channel 2, WCTDM, no module.
# channel 3, WCTDM, no module.
# channel 4, WCTDM, no module.
# channel 5, WCTDM, no module.
# channel 6, WCTDM, no module.
# channel 7, WCTDM, no module.
# channel 8, WCTDM, no module.
# Global data
loadzone = us
defaultzone = us
When I look in the Asterisk Info and expand Zaptel Driver Info, it only shows the 1 line of "pseudo from-zaptel en default" but no channels.
Side note: Again after reading other posts, I see the "rebuild_zaptel" is not really needed (maybe??) except I was going to try it anyway (ha) but when I run it, I get
-bash: rebuild_zaptel: command not found (and no idea where it would be located)
Tried to keep this short, hope this is enough info to point me in the right direction.
Thanks...
done this a year ago..
Fri, 05/09/2008 - 11:52am
hey bro, i've done this a year ago no support from the company where we bought the 800P, i even talked to them for the whole day but i just got a reply of "sorry sir i never done or supporte this product yet because it is new in the market" so that is the dead end to me. but with the help of all available forums around the internet i got this running with any problem.
i remember what i did before is that i just followed the instructions on the docs they provided but i choose the 2400P drivers to make this working..... and i will be building another box for this kind of card soon!
stupid card...
Mon, 05/12/2008 - 10:21am
pinoybox, man thanks for the reply.. sorry for the delay, got stuck on my sql server crashing friday and didn't have a recent image of the drive (whoops) but yea, I can't figure this out.
I'm gonna get back on it and try again but i'll look for the 2400 stuff. I had setup the cheap single FXO cards like a champ but this TDM is kicking my @ss. IF I can get it working, I'll post back what I find - before I blast the inside of this computer with a fire extinguisher. ha!
Always looking for info so post anything you got...
Small update
Mon, 05/12/2008 - 1:25pm
Well, so no one wastes their time on my issue, I fianally broke down and called Digium and their tech guy SSH'd into my system and said either the card or more than likely the module was bad and to RMA it. Assuming he knew what he was doing (which it seemed he did), Very helpful there. Did a bunch of changes and updates.
Side note for anyone who reads this, the 1st comment he made was that they really didn't support Trixbox, only Asterisk. He wasn't ugly at all towards Trixbox but made it clear the driver issues.
And pinoybox, he also confirmed "exactly what you said" about with Trixbox you have to use the 2400 drivers for the exact same reason, I didn't even ask him that. He suggested I re-look at Asterisk again. hahaha
Thanks.. now I got to get my vendor to RMA my $#@$ card and module so even more time I can't play.. arr...
Member Since:
2006-06-03