Страница 1 из 2
Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 13:21
utcon
Добрый день.
решил обратится за помощью.
Работала связка Asterisk (TE205P) - Hipath 3750 по PRI
Потом пропало электричество.
После появления оного - ситуация
[root@voip dahdi-linux-complete-2.6.1+2.6.1]# lsdahdi
### Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" HDB3/CCS/CRC4 RED
1 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
2 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
3 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
4 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
5 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
6 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
7 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
8 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
9 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
10 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
11 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
12 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
13 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
14 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
15 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
16 PRI HDLCFCS (In use) RED
17 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
18 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
19 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
20 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
21 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
22 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
23 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
24 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
25 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
26 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
27 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
28 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
29 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
30 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
31 PRI Clear (In use) (EC: MG2 - INACTIVE) RED
### Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" (MASTER) HDB3/CCS/CRC4 ClockSource
32 PRI Clear (In use) (EC: MG2 - INACTIVE)
33 PRI Clear (In use) (EC: MG2 - INACTIVE)
34 PRI Clear (In use) (EC: MG2 - INACTIVE)
35 PRI Clear (In use) (EC: MG2 - INACTIVE)
36 PRI Clear (In use) (EC: MG2 - INACTIVE)
37 PRI Clear (In use) (EC: MG2 - INACTIVE)
38 PRI Clear (In use) (EC: MG2 - INACTIVE)
39 PRI Clear (In use) (EC: MG2 - INACTIVE)
40 PRI Clear (In use) (EC: MG2 - INACTIVE)
41 PRI Clear (In use) (EC: MG2 - INACTIVE)
42 PRI Clear (In use) (EC: MG2 - INACTIVE)
43 PRI Clear (In use) (EC: MG2 - INACTIVE)
44 PRI Clear (In use) (EC: MG2 - INACTIVE)
45 PRI Clear (In use) (EC: MG2 - INACTIVE)
46 PRI Clear (In use) (EC: MG2 - INACTIVE)
47 PRI HDLCFCS (In use)
48 PRI Clear (In use) (EC: MG2 - INACTIVE)
49 PRI Clear (In use) (EC: MG2 - INACTIVE)
50 PRI Clear (In use) (EC: MG2 - INACTIVE)
51 PRI Clear (In use) (EC: MG2 - INACTIVE)
52 PRI Clear (In use) (EC: MG2 - INACTIVE)
53 PRI Clear (In use) (EC: MG2 - INACTIVE)
54 PRI Clear (In use) (EC: MG2 - INACTIVE)
55 PRI Clear (In use) (EC: MG2 - INACTIVE)
56 PRI Clear (In use) (EC: MG2 - INACTIVE)
57 PRI Clear (In use) (EC: MG2 - INACTIVE)
58 PRI Clear (In use) (EC: MG2 - INACTIVE)
59 PRI Clear (In use) (EC: MG2 - INACTIVE)
60 PRI Clear (In use) (EC: MG2 - INACTIVE)
61 PRI Clear (In use) (EC: MG2 - INACTIVE)
62 PRI Clear (In use) (EC: MG2 - INACTIVE)
pri set debug on span 2
Код: Выделить всё
PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 2 TEI=0 Sending SABME
voip*CLI> pri set debug on span 2
Disconnected from Asterisk server
Подскажите пожалуйста, кто сталкивался с подобной ситуацией, что скорее всего случилось ? Вышла из строя плата PRI ?
Астериск и АТС соят рядом, длина патчкорда небольшая, его никто не трогал.
Тем более, что
dahdi_scan
Код: Выделить всё
[2]
active=yes
alarms=OK
description=T2XXP (PCI) Card 0 Span 2
name=TE2/0/2
manufacturer=Digium
devicetype=Wildcard TE205P
location=Board ID Switch 0
basechan=32
totchans=31
irq=0
type=digital-E1
syncsrc=2
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=AMI,HDB3
framing_opts=CCS,CRC4
coding=HDB3
framing=CCS/CRC4
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 13:35
utcon
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 13:51
utcon
Понизил версию dahdi и libpri - ситуация не изменилась.
Код: Выделить всё
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 14:25
ded
Hipath 3750 - это Span 2? А что воткнуто в Span 1?
Что показывает dahdi_tool? ОК на обоих портах?
как описаны порты в /etc/dahdi/system.conf?
Что говорит Астериск если выгрузить и снова загрузить chan_dahdi
module unload chan_dahdi.so
module load chan_dahdi.so
dahdi show channels ?
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 14:36
utcon
voip*CLI> dahdi show channels
Chan Extension Context Language MOH Interpret Blocked State
pseudo default default In Service
1 from-pstn default In Service
2 from-pstn default In Service
3 from-pstn default In Service
4 from-pstn default In Service
5 from-pstn default In Service
6 from-pstn default In Service
7 from-pstn default In Service
8 from-pstn default In Service
9 from-pstn default In Service
10 from-pstn default In Service
11 from-pstn default In Service
12 from-pstn default In Service
13 from-pstn default In Service
14 from-pstn default In Service
15 from-pstn default In Service
17 from-pstn default In Service
18 from-pstn default In Service
19 from-pstn default In Service
20 from-pstn default In Service
21 from-pstn default In Service
22 from-pstn default In Service
23 from-pstn default In Service
24 from-pstn default In Service
25 from-pstn default In Service
26 from-pstn default In Service
27 from-pstn default In Service
28 from-pstn default In Service
29 from-pstn default In Service
30 from-pstn default In Service
31 from-pstn default In Service
32 from-pstn default In Service
33 from-pstn default In Service
34 from-pstn default In Service
35 from-pstn default In Service
36 from-pstn default In Service
37 from-pstn default In Service
38 from-pstn default In Service
39 from-pstn default In Service
40 from-pstn default In Service
41 from-pstn default In Service
42 from-pstn default In Service
43 from-pstn default In Service
44 from-pstn default In Service
45 from-pstn default In Service
46 from-pstn default In Service
48 from-pstn default In Service
49 from-pstn default In Service
50 from-pstn default In Service
51 from-pstn default In Service
52 from-pstn default In Service
53 from-pstn default In Service
54 from-pstn default In Service
55 from-pstn default In Service
56 from-pstn default In Service
57 from-pstn default In Service
58 from-pstn default In Service
59 from-pstn default In Service
60 from-pstn default In Service
61 from-pstn default In Service
62 from-pstn default In Service
voip*CLI> module unload chan_dahdi.so
Unloaded chan_dahdi.so
== Unregistered application 'DAHDISendKeypadFacility'
== Manager unregistered action DAHDIDialOffhook
== Manager unregistered action DAHDIHangup
== Manager unregistered action DAHDITransfer
== Manager unregistered action DAHDIDNDoff
== Manager unregistered action DAHDIDNDon
== Manager unregistered action DAHDIShowChannels
== Manager unregistered action DAHDIRestart
== Unregistered channel type 'DAHDI'
-- Unregistered channel -2
-- Unregistered channel 1
-- Unregistered channel 2
-- Unregistered channel 3
-- Unregistered channel 4
-- Unregistered channel 5
-- Unregistered channel 6
-- Unregistered channel 7
-- Unregistered channel 8
-- Unregistered channel 9
-- Unregistered channel 10
-- Unregistered channel 11
-- Unregistered channel 12
-- Unregistered channel 13
-- Unregistered channel 14
-- Unregistered channel 15
-- Unregistered channel 17
-- Unregistered channel 18
-- Unregistered channel 19
-- Unregistered channel 20
-- Unregistered channel 21
-- Unregistered channel 22
-- Unregistered channel 23
-- Unregistered channel 24
-- Unregistered channel 25
-- Unregistered channel 26
-- Unregistered channel 27
-- Unregistered channel 28
-- Unregistered channel 29
-- Unregistered channel 30
-- Unregistered channel 31
-- Unregistered channel 32
-- Unregistered channel 33
-- Unregistered channel 34
-- Unregistered channel 35
-- Unregistered channel 36
-- Unregistered channel 37
-- Unregistered channel 38
-- Unregistered channel 39
-- Unregistered channel 40
-- Unregistered channel 41
-- Unregistered channel 42
-- Unregistered channel 43
-- Unregistered channel 44
-- Unregistered channel 45
-- Unregistered channel 46
-- Unregistered channel 48
-- Unregistered channel 49
-- Unregistered channel 50
-- Unregistered channel 51
-- Unregistered channel 52
-- Unregistered channel 53
-- Unregistered channel 54
-- Unregistered channel 55
-- Unregistered channel 56
-- Unregistered channel 57
-- Unregistered channel 58
-- Unregistered channel 59
-- Unregistered channel 60
-- Unregistered channel 61
-- Unregistered channel 62
voip*CLI> module load chan_dahdi.so
Loaded chan_dahdi.so
== Registered application 'DAHDISendKeypadFacility'
== Parsing '/etc/asterisk/chan_dahdi.conf': == Found
== Parsing '/etc/asterisk/dahdi-channels.conf': == Found
== Parsing '/etc/asterisk/users.conf': == Found
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 1: Red Alarm
-- Registered channel 1, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 2: Red Alarm
-- Registered channel 2, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 3: Red Alarm
-- Registered channel 3, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 4: Red Alarm
-- Registered channel 4, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 5: Red Alarm
-- Registered channel 5, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 6: Red Alarm
-- Registered channel 6, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 7: Red Alarm
-- Registered channel 7, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 8: Red Alarm
-- Registered channel 8, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 9: Red Alarm
-- Registered channel 9, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 10: Red Alarm
-- Registered channel 10, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 11: Red Alarm
-- Registered channel 11, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 12: Red Alarm
-- Registered channel 12, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 13: Red Alarm
-- Registered channel 13, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 14: Red Alarm
-- Registered channel 14, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 15: Red Alarm
-- Registered channel 15, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 17: Red Alarm
-- Registered channel 17, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 18: Red Alarm
-- Registered channel 18, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 19: Red Alarm
-- Registered channel 19, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 20: Red Alarm
-- Registered channel 20, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 21: Red Alarm
-- Registered channel 21, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 22: Red Alarm
-- Registered channel 22, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 23: Red Alarm
-- Registered channel 23, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 24: Red Alarm
-- Registered channel 24, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 25: Red Alarm
-- Registered channel 25, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 26: Red Alarm
-- Registered channel 26, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 27: Red Alarm
-- Registered channel 27, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 28: Red Alarm
-- Registered channel 28, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 29: Red Alarm
-- Registered channel 29, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 30: Red Alarm
-- Registered channel 30, ISDN PRI signalling
[Feb 12 12:32:58] WARNING[14610]: chan_dahdi.c:7745 handle_alarms: Detected alarm on channel 31: Red Alarm
-- Registered channel 31, ISDN PRI signalling
-- Registered channel 32, ISDN PRI signalling
-- Registered channel 33, ISDN PRI signalling
-- Registered channel 34, ISDN PRI signalling
-- Registered channel 35, ISDN PRI signalling
-- Registered channel 36, ISDN PRI signalling
-- Registered channel 37, ISDN PRI signalling
-- Registered channel 38, ISDN PRI signalling
-- Registered channel 39, ISDN PRI signalling
-- Registered channel 40, ISDN PRI signalling
-- Registered channel 41, ISDN PRI signalling
-- Registered channel 42, ISDN PRI signalling
-- Registered channel 43, ISDN PRI signalling
-- Registered channel 44, ISDN PRI signalling
-- Registered channel 45, ISDN PRI signalling
-- Registered channel 46, ISDN PRI signalling
-- Registered channel 48, ISDN PRI signalling
-- Registered channel 49, ISDN PRI signalling
-- Registered channel 50, ISDN PRI signalling
-- Registered channel 51, ISDN PRI signalling
-- Registered channel 52, ISDN PRI signalling
-- Registered channel 53, ISDN PRI signalling
-- Registered channel 54, ISDN PRI signalling
-- Registered channel 55, ISDN PRI signalling
-- Registered channel 56, ISDN PRI signalling
-- Registered channel 57, ISDN PRI signalling
-- Registered channel 58, ISDN PRI signalling
-- Registered channel 59, ISDN PRI signalling
-- Registered channel 60, ISDN PRI signalling
-- Registered channel 61, ISDN PRI signalling
-- Registered channel 62, ISDN PRI signalling
-- Automatically generated pseudo channel
== Starting D-Channel on span 1
== Starting D-Channel on span 2
== Registered channel type 'DAHDI' (DAHDI Telephony Driver w/PRI)
== Manager registered action DAHDITransfer
== Manager registered action DAHDIHangup
== Manager registered action DAHDIDialOffhook
== Manager registered action DAHDIDNDon
== Manager registered action DAHDIDNDoff
== Manager registered action DAHDIShowChannels
== Manager registered action DAHDIRestart
Loaded chan_dahdi.so => (DAHDI Telephony Driver w/PRI)
[root@voip asterisk-1.8.7.1]# cat /etc/dahdi/system.conf
# Autogenerated by /usr/sbin/dahdi_genconf on Tue Feb 12 11:42:27 2013
# If you edit this file and execute /usr/sbin/dahdi_genconf again,
# your manual changes will be LOST.
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" HDB3/CCS/CRC4 RED
span=1,1,0,ccs,hdb3,crc4
# termtype: te
bchan=1-15,17-31
dchan=16
echocanceller=mg2,1-15,17-31
# Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" (MASTER) HDB3/CCS/CRC4 ClockSource
span=2,2,0,ccs,hdb3,crc4
# termtype: te
bchan=32-46,48-62
dchan=47
echocanceller=mg2,32-46,48-62
# Global data
loadzone = us
defaultzone = us
dahdi_tool на втором показывает Ок, на первом RED
Вытащил из первого воткнул во второй, думал может порт выгорел.
Пытался dahdi_dencfg генерить дефалтные конфиги - проблема такая же
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 15:02
ded
На сколько я понимаю, если в первом порту город (ответ так и не увидел на этот вопрос) то синхра получается от города а на первом как раз RED.
Если нет синхры из города, то и с Hipath её не будет, ибо она сквозная.
Смотрите состояния мультиплексора, откуда прибегает ваш город, возможно именно он и завис.
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 15:11
utcon
У меня нет города на первом порту.
Плата двухпортовая. В один из портов подключена АТС Hipath.
Во втором ничего нет.
Кстати сделал даунгрейд астериска до 1.8.6.0 проблема осталась
.
Уже не знаю, что и делать.
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 15:22
utcon
Самое интересное, что при корректной конфигурации сигнализации
voip*CLI> pri show spans
PRI span 1/0: In Alarm, Down, Active
PRI span 2/0: Up, Active
О в Апе. Но все равно ломятся ошибки тайминга насколько я понимаю.
I Span: 2 TEI=0 MDL-ERROR (G): T200 expired N200 times sending SABME in state 5(Awaiting establishment)
PRI Span: 2 Changing from state 5(Awaiting establishment) to 4(TEI assigned)
PRI Span: 2 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3)
PRI Span: 2 SAPI/TEI=0/0 Kick starting link
PRI Span: 2 TEI=0 Sending SABME
PRI Span: 2 Changing from state 4(TEI assigned) to 5(Awaiting establishment)
PRI Span: 2 TEI=0 Sending SABME
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 15:25
utcon
ddkprog писал(а):ЛОЛ!
Работала связка Asterisk (TE205P) - Hipath 3750 по PRI
Потом пропало электричество.
После появления оного - ситуация
после этого вы уже и libpri даунгрейдили и астериск
что еще остается? ну линукс даунгрейдите
Я начал это делать после того как нарыл
http://openvox.cn/pipermail/supportgrou ... 01941.html
От безысходности
.
Re: Синхронизация по PRI Sending SABME
Добавлено: 12 фев 2013, 15:48
utcon
Перегружал АТС. Не помогло.
перепроверял настройки на ее стороне, qsig slave как и должно быть.
Там особо по настройкам не разгонишься.
Лажа возникла как раз после перезагрузки АТС.