[asterisk-users] Digium TE110P
Elman Efendiyev
elman at protechtele.com
Wed Feb 7 00:29:28 MST 2007
Helo,
I have problem with Digium TE110P connected to CISCO 3640 (port on
NM-HDV-2E1-60) wth PRI E1 link. I use CISCO now for testing but when I
tried with real PBX problem was exactly same.
I have this messages in Asterisk conole and log sometimes:
NOTICE[1115] chan_zap.c: PRI got event: HDLC Abort (6) on Primary D-channel
of span 1
Usually 2-5 such messages in series, can be repeated after 10 minutes, or
after 30 minutes, or after 1-2 hours. I can't find any system when these
message occurs. This is ta test server with only Asterisk running, i left in
idle for couple hours (no calls at all), then put in under some traffic - no
difference. When I call trouth this * box and this messagw occurs I can hear
littlee click but not always. This wouldn't be a critical problem but over
some time (couple hors or day) I see this in log:
[Feb 7 01:01:10] NOTICE[614]: chan_zap.c:8431 pri_dchannel: PRI got event:
Alarm (4) on Primary D-channel of span 1
[Feb 7 01:01:10] WARNING[614]: chan_zap.c:2416 pri_find_dchan: No
D-channels available! Using Primary channel 16 as D-channel anyway!
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 1: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 2: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 3: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 4: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 5: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 6: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 7: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 8: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 9: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 10: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 11: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 12: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 13: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 14: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 15: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 17: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 18: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 19: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 20: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 21: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 22: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 23: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 24: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 25: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 26: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 27: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 28: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 29: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 30: Yellow Alarm
[Feb 7 01:01:10] WARNING[615]: chan_zap.c:6640 handle_init_event: Detected
alarm on channel 31: Yellow Alarm
[Feb 7 01:01:10] NOTICE[614]: chan_zap.c:8431 pri_dchannel: PRI got event:
No more alarm (5) on Primary D-channel of span 1
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 1
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 2
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 3
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 4
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 5
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 6
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 7
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 8
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 9
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 10
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 11
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 12
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 13
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 14
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 15
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 17
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 18
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 19
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 20
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 21
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 22
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 23
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 24
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 25
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 26
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 27
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 28
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 29
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 30
[Feb 7 01:01:10] NOTICE[615]: chan_zap.c:6633 handle_init_event: Alarm
cleared on channel 31
== Primary D-Channel on span 1 up
and ofcourse all calls are droped.
I searched wiki and maillists and found that this is a common problem with
TE110P, but I tried most known solutions without success. I changed
motherboard, CPU, etc.
My configs:
/etc/zaptel.conf:
loadzone = us
defaultzone=us
span=1,0,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
/etc/asterisk/zapata.conf
[trunkgroups]
[channels]
context=default
group=1
signalling=pri_net
switchtype=euroisdn
resetinterval = never
channel=>1-15,17-31
CISCO config:
controller E1 2/1
framing NO-CRC4
pri-group timeslots 1-31
interface Serial2/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
no cdp enable
More strange thing: when I changed master/slave (CISCO master and TE110P
slave) like this:
/etc/zaptel.conf:
loadzone = us
defaultzone=us
span=1,1,0,ccs,hdb3
bchan=1-15,17-31
dchan=16
/etc/asterisk/zapata.conf
[trunkgroups]
[channels]
context=default
group=1
signalling=pri_cpe
switchtype=euroisdn
resetinterval = never
channel=>1-15,17-31
CISCO config:
controller E1 2/1
framing NO-CRC4
clock source internal
pri-group timeslots 1-31
interface Serial2/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
I have continuously Yellow alarm messages, and zttool still thinks that
TE110p is master:
Current Alarms: No alarms.
│ Sync Source: Internally clocked
│ IRQ Misses: 0
│ Bipolar Viol: 0
│ Tx/Rx Levels: 0/ 0
│ Total/Conf/Act: 31/ 31/ 0
So I can't make TE110P slave at all....
Also I can't get 100% pseudo zap interface accuracy:
zaptel-1.4.0/zttest
Opened pseudo zap interface, measuring accuracy...
99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%
.....
99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793% 99.987793%
99.987793%
--- Results after 46 passes ---
Best: 100.000000 -- Worst: 99.987793 -- Average: 99.988058
But when I run it for long (hour or more) worst can be 95....96%
I think this is a reason for above troubles but can't find a way to fix it.
Also I can't understand why TE110P can't be a slave...
Hardware:
Motherboard Intel SE-7210TP1-E with Gigabit Ethernet disabled in BIOS, using
100M ethernet (tried two other model motherboards, Intel and VIA)
Pention 4 HT 3.0GHz 800MHz FSB (tried Celeron 2.4GHz too)
IDE HDD with UDMA2 (hdparm -u1c1d1X66 /dev/hda)
Asterisk, libpri and zaptel versions 1.4.0 release, Linux 2.6.20 (tried
2.6.17 and 2.6.19)
I disabled all not needed devices on motherboard BIOS (even video) and
compiled only needed drivers in kernel, tried preemptable and
not-preemptable kernel, 100, 250 and 1000Hz timer.
Looks like I haven't IRQ problem:
cat /proc/interrupts
CPU0
0: 182503 IO-APIC-edge timer
1: 8 IO-APIC-edge i8042
2: 0 XT-PIC-XT cascade
8: 1 IO-APIC-edge rtc
12: 3 IO-APIC-edge i8042
14: 2989 IO-APIC-edge ide0
16: 725232 IO-APIC-fasteoi wcte11xp
17: 2233 IO-APIC-fasteoi eth0
NMI: 0
LOC: 182461
ERR: 0
MIS: 0
lspci -v
00:00.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub
(rev 02)
Flags: bus master, fast devsel, latency 0
Memory at fe800000 (32-bit, prefetchable) [size=4M]
Capabilities: [e4] Vendor Specific Information
00:1c.0 PCI bridge: Intel Corporation 6300ESB 64-bit PCI-X Bridge (rev 02)
(prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
Capabilities: [50] PCI-X bridge device
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 0a) (prog-if 00
[Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fe600000-fe6fffff
00:1f.0 ISA bridge: Intel Corporation 6300ESB LPC Interface Controller (rev
02)
Flags: bus master, medium devsel, latency 0
00:1f.1 IDE interface: Intel Corporation 6300ESB PATA Storage Controller
(rev 02) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 0, IRQ 18
I/O ports at 01f0 [size=8]
I/O ports at 03f4 [size=1]
I/O ports at 0170 [size=8]
I/O ports at 0374 [size=1]
I/O ports at fc00 [size=16]
Memory at 50000000 (32-bit, non-prefetchable) [size=1K]
00:1f.3 SMBus: Intel Corporation 6300ESB SMBus Controller (rev 02)
Flags: medium devsel, IRQ 17
I/O ports at 0400 [size=32]
02:01.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
(rev 10)
Subsystem: Intel Corporation Unknown device 342f
Flags: bus master, medium devsel, latency 64, IRQ 17
Memory at fe6fe000 (32-bit, non-prefetchable) [size=4K]
I/O ports at ec00 [size=64]
Memory at fe6a0000 (32-bit, non-prefetchable) [size=128K]
Capabilities: [dc] Power Management version 2
02:02.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
interface
Subsystem: Unknown device 795e:0001
Flags: bus master, medium devsel, latency 64, IRQ 16
I/O ports at e800 [size=256]
Memory at fe6fd000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2
lspci -vb
00:00.0 Host bridge: Intel Corporation 82875P/E7210 Memory Controller Hub
(rev 02)
Flags: bus master, fast devsel, latency 0
Memory at fe800000 (32-bit, prefetchable)
Capabilities: [e4] Vendor Specific Information
00:1c.0 PCI bridge: Intel Corporation 6300ESB 64-bit PCI-X Bridge (rev 02)
(prog-if 00 [Normal decode])
Flags: bus master, 66MHz, fast devsel, latency 64
Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
Capabilities: [50] PCI-X bridge device
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 0a) (prog-if 00
[Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000e000-0000efff
Memory behind bridge: fe600000-fe6fffff
00:1f.0 ISA bridge: Intel Corporation 6300ESB LPC Interface Controller (rev
02)
Flags: bus master, medium devsel, latency 0
00:1f.1 IDE interface: Intel Corporation 6300ESB PATA Storage Controller
(rev 02) (prog-if 8a [Master SecP PriP])
Flags: bus master, medium devsel, latency 0
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at <unassigned>
I/O ports at fc00
Memory at 50000000 (32-bit, non-prefetchable)
00:1f.3 SMBus: Intel Corporation 6300ESB SMBus Controller (rev 02)
Flags: medium devsel, IRQ 11
I/O ports at 0400
02:01.0 Ethernet controller: Intel Corporation 82557/8/9 [Ethernet Pro 100]
(rev 10)
Subsystem: Intel Corporation Unknown device 342f
Flags: bus master, medium devsel, latency 64, IRQ 11
Memory at fe6fe000 (32-bit, non-prefetchable)
I/O ports at ec00
Memory at fe6a0000 (32-bit, non-prefetchable)
Capabilities: [dc] Power Management version 2
02:02.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN
interface
Subsystem: Unknown device 795e:0001
Flags: bus master, medium devsel, latency 64, IRQ 9
I/O ports at e800
Memory at fe6fd000 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 2
I appreciate any ideas.
Thank you.
--
Sincerely,
Elman Efendiyev
More information about the asterisk-users
mailing list