Displaying 6 results from an estimated 6 matches for "c01a016a".
Did you mean:
c01a0164
2008 Apr 14
8
zaptel 1.4.10 regression with TE220B on Proliant DL380 G5 ?
...leteness sake, driver was previously loaded ok:
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.10
Zaptel Echo Canceller: MG2
ACPI: PCI Interrupt 0000:18:08.0[A] -> GSI 19 (level, low) -> IRQ 98
Found TE2XXP at base address fdff0000, remapped to f8854000
TE2XXP version c01a016a, burst ON
Octasic optimized!
FALC version: 00000005, Board ID: 00
Reg 0: 0x375a2400
Reg 1: 0x375a2000
Reg 2: 0xffffffff
Reg 3: 0x00000000
Reg 4: 0x00003101
Reg 5: 0x00000000
Reg 6: 0xc01a016a
Reg 7: 0x00001300
Reg 8: 0x00000000
Reg 9: 0x00ff2031
Reg 10: 0x0000004a
TE2XXP: Launching card: 0
TE2XXP:...
2007 May 18
2
TE212P octastic initialization failure
...IC-level ioc0
217: 1153 0 IO-APIC-level eth1
225: 160247 0 IO-APIC-level wct2xxp
NMI: 64 42
LOC: 42340 42317
ERR: 0
MIS: 0
# dmesg
[...]
Found TE2XXP at base address fe7ffc00, remapped to ffffc20000004c00
TE2XXP version c01a016a, burst OFF, slip debug: OFF
Octasic optimized!
FALC version: 00000005, Board ID: 00
Reg 0: 0x7daa5400
Reg 1: 0x7daa5000
Reg 2: 0xffffffff
Reg 3: 0x00000000
Reg 4: 0x00000101
Reg 5: 0x00000000
Reg 6: 0xc01a016a
Reg 7: 0x00001300
Reg 8: 0x00000000
Reg 9: 0x00ff0001
Reg 10: 0x0000004a
TE2XXP: Launchin...
2009 Jan 26
3
Digium TE220 card partially detected
Hello folks.
I've got a strange issue.
When I modprobe TE220 I do not see mesages like Launching card: 0 <..>
Setting up global serial parameters.
You can see how I loaded and unloaded the card for several times -
http://asteriskpbx.ru/pastebin/11
lspci can detect the card: 03:08.0 Communication controller: Digium, Inc.
Device 0220 (rev 02)
dahdi_hardware also:
astpbx ~ # dahdi_hardware
2007 Jun 07
2
Bridged PRI calls - processor involvement?
On a zaptel TE410p, when a call is bridged PRI - PRI how much involvement does the processor have?
We're now seeing chunks of missing audio and I can't tell whether this is due to a kernel upgrade or to a zaptel/libpri/asterisk upgrade.
I'm not seeing missed interrupts (from a cat of the proc/zaptel files), any other ideas on how I could go about tracking this down?
I'm
2009 Apr 24
3
timing source problem
hi all,
we do have some troubles with zaptel timing source - we have a setup
with 3 telco PRI lines, connected to asterisk digium card 0 - asterisk
does some handling - calls are leaving on digium card 1 - going to a
siemens hipath - there is some call handling - some of the calls then
are going from the hipath over a qsig line to a bosch integral PBX -
handling the rest of the calls.
To be able
2006 Dec 18
2
Digium TE405P with French E1 => Red Alert
...8 12:46:39 ipbx zaptel: Loading zaptel framework: succeeded
Dec 18 12:46:39 ipbx kernel: ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI
24 (level, low) -> IRQ 24
Dec 18 12:46:39 ipbx kernel: Found TE4XXP at base address febffc00,
remapped to f8afec00
Dec 18 12:46:39 ipbx kernel: TE4XXP version c01a016a, burst OFF, slip
debug: OFF
Dec 18 12:46:39 ipbx kernel: FALC version: 00000005, Board ID: 00
Dec 18 12:46:39 ipbx kernel: Reg 0: 0x186ec400
Dec 18 12:46:39 ipbx kernel: Reg 1: 0x186ec000
Dec 18 12:46:39 ipbx kernel: Reg 2: 0xffffffff
Dec 18 12:46:39 ipbx kernel: Reg 3: 0x00000000
Dec 18 12:46:39...