Hello. I have been trying for days to get a Digum TE207P card working on fresh install of Trixbox. I'm getting no where fast and I need to get this working. Is there someone out there I can pay to SSH into the box and setup the zatel drivers etc? I have bought an hours support from trixbox.org but after more than 20 calls over the last 8 days I've given up on them. They have never answered the phone or returned the voicemails I have left, a waste of $150 I guess.
Rob
Need someone to setup TE207P PRI card-Will pay
I can probably help. Email me and I'll get back to you.
Ok, I need to see the output of the following command:
cat /proc/interrupts
and please paste the answer using the code tags. See the dentist's post if you don't know what that is, but it makes it much easier to read.
Also, please paste your /etc/zaptel.conf too.
Thanks, here are the outputs.
[trixbox1.localdomain ~]# cat /proc/interrupts
CPU0
0: 22270650 IO-APIC-edge timer
1: 8 IO-APIC-edge i8042
8: 1 IO-APIC-edge rtc
9: 1 IO-APIC-level acpi
14: 199710 IO-APIC-edge ide0
169: 7840 IO-APIC-level eth0
201: 53534 IO-APIC-level ahci
209: 0 IO-APIC-level wct2xxp
217: 22247661 IO-APIC-level wctdm
NMI: 0
LOC: 21771216
ERR: 0
MIS: 0
# Autogenerated by /usr/sbin/genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#
# It must be in the module loading order
/etc/zaptel.conf
# Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" (MASTER)
fxsks=1
fxsks=2
fxsks=3
fxsks=4
# Span 2: TE2/0/1 "T2XXP (PCI) Card 0 Span 1"
span=2,1,0,ccs,hdb3,crc4
# termtype: te
bchan=5-19,21-35
dchan=20
# Span 3: TE2/0/2 "T2XXP (PCI) Card 0 Span 2"
span=3,2,0,ccs,hdb3,crc4
# termtype: te
bchan=36-50,52-66
dchan=51
# Global data
loadzone = us
defaultzone = us
The family wants to go out and get some food, so I'll take a look when I get back.
Is there a reason nobody ever uses the code tags like I ask?
My mind immediately goes to IRQ conflicts when I see IRQs like that. Have you tried turning off APIC in the kernel boot params?
A hard lock like you're describing is, in my experience, almost always a hardware issue. Not that it can't be solved.
Just tried that, rebooted and did the cat /proc/interrupts again.
Heres the result:
CPU0
0: 53228 IO-APIC-edge timer
1: 8 IO-APIC-edge i8042
2: 0 XT-PIC cascade
8: 1 IO-APIC-edge rtc
14: 216 IO-APIC-edge ide0
121: 135 IO-APIC-level eth0
137: 7223 IO-APIC-level ahci
145: 0 IO-APIC-level wct2xxp
153: 34308 IO-APIC-level wctdm
NMI: 0
LOC: 52334
ERR: 0
MIS: 0
[trixbox1.localdomain ~]#
What kernel params did you pass? Because that's still using virtual IRQs. Try using both:
noapic acpi=no
I hope I'm not leading you down the wrong path, but I really think this sounds like IRQ conflicts. Do you need both the analog card and the digital, or is the digital card going to replace the analog? If it's replacing it, you may want to take it out.
get in the bios, try 1 or all, or any combo of below.
1. disable EVERYTHING you dont need in the bios - any un-used ide/sata/fdd ports, usb etc.
2. try switching any SMP or multicore junk off
3. try toggling the plug-n-play option in the bios (if your bios doesnt have this consider a better board)
4. set any option to "reset configuration data"
5. switch off acpi in bios
switch PCI slots if open.
try Kodaks boot params.
Sorry of the late reply,
I added the line in grub.conf and disabled all unused devices and this is the result.
The same thing still happens, made four or five short calls then the server locked up.
It did report on the console a do_IRQ: stack overflow: 212
CPU0
0: 204482 XT-PIC timer
1: 281 XT-PIC i8042
2: 0 XT-PIC cascade
5: 186575 XT-PIC wctdm
7: 0 XT-PIC wct2xxp
8: 1 XT-PIC rtc
10: 449 XT-PIC eth0
11: 5920 XT-PIC ahci
14: 1561 XT-PIC ide0
NMI: 0
LOC: 204387
ERR: 0
MIS: 0
I'm starting to think it must be a duff TE207P card.
I've tried taking out the TM400 card and still get the same result.
I have also put the TE207P card in another IBM machine, installed Trixbox and it did same, locking up after 3 or four calls.
Found out what was causing the problem. I unpluged the Echo cancellation board from the main card and its now running fine. I guess it must be a faulty board.
Thanks for everyones help.
I just purchased two TE207Ps.
They *BOTH* exhibit the behavior you are describing here.
Did you ever get a resolution? I really am *not* comfortable with the idea of paying for hardware echo canceling then having to remove it so that I don't have lock issues. :(
I tried two different systems altogether.
I just purchased two TE207Ps.
They *BOTH* exhibit the behavior you are describing here.
Did you ever get a resolution? I really am *not* comfortable with the idea of paying for hardware echo canceling then having to remove it so that I don't have lock issues. :(
I tried two different systems altogether.
No nothing, spoke to Digium support they said to send it back to my supplier. I sent it back to voipdepot.co.uk 10 weeks ago and still heard nothing. To be fair the system works fine but I feel the same as you paying for it and it won't work. I will ring voipdepot.co.uk again to see what they say but I'm not holding my breath. My system is now working so Im worried about putting it back in anyway, it was such a random lockup.
Not so random for me. :) Was definite all the time.
I am wondering if it is specific to the zaptel drivers in Trixbox ?
I had Digium support SSH into the box and change the drivers several times, no joy :-(
Member Since:
2006-06-01