Took 3 days without errors like "dahdi: Master changed to TE2/0/2" having installed the dahdi 2.6.1 But I have warnings that I copy below
[Sep 17 09:25:27] WARNING[24233] mtp.c: MTP2 timer T3 timeout (failed to receive 'N', or 'E' after sending 'O'), initial alignment failed on link 'i1'. [Sep 17 09:25:28] NOTICE[24233] mtp.c: Got event on link 'i1': 5 (0/500). [Sep 17 09:25:28] NOTICE[2872] l4isup.c: Unhandled zaptel event 0x5 on CIC=30. [Sep 17 09:25:28] NOTICE[2872] l4isup.c: Unhandled zaptel event 0x4 on CIC=30. [Sep 17 09:25:28] NOTICE[24233] mtp.c: Got event on link 'i1': 4 (0/11). [Sep 17 09:25:29] NOTICE[2872] l4isup.c: Unhandled zaptel event 0x5 on CIC=30. [Sep 17 09:25:29] NOTICE[24233] mtp.c: Got event on link 'i1': 5 (0/500). [Sep 17 09:25:29] NOTICE[24233] l4isup.c: T1 timeout (waiting for RLC) CIC=20. [Sep 17 09:25:29] WARNING[24233] mtp.c: No signalling links inservice and no cluster receivers alive, dropping packet! [Sep 17 09:25:29] WARNING[24233] chan_ss7.c: MTP is now UP on link 'i1'. [Sep 17 09:25:29] NOTICE[24233] mtp.c: Sending TRA to peer on link 'i1'.... [Sep 17 09:25:29] WARNING[24233] mtp.c: Got SLTM with unexpected sls=1, OPC=13152 DPC=8458 on 'i1/16' sls=0, state=5. [Sep 17 09:25:30] NOTICE[24233] l4isup.c: Got GROUP RESET message, opc=0x3360, dpc=0x210a, sls=0x1, cic=17, range=14. [Sep 17 09:25:30] NOTICE[24233] l4isup.c: Got GROUP RESET message, opc=0x3360, dpc=0x210a, sls=0x1, cic=1, range=14. [Sep 17 09:25:58] NOTICE[24233] l4isup.c: Process CGU, cic=1, range=14 [Sep 17 09:25:58] NOTICE[24233] l4isup.c: Process CGU, cic=33, range=30 [Sep 17 09:26:00] NOTICE[24233] l4isup.c: Got GROUP RESET message, opc=0x3360, dpc=0x210a, sls=0x1, cic=33, range=30. [Sep 17 09:26:00] NOTICE[24233] l4isup.c: Process CGU, cic=17, range=14 [Sep 17 09:26:13] NOTICE[2925] l4isup.c: Short read on linkset "siuc" CIC=24 (read only 0 of 160) errno=11 (Resource temporarily unavailable) (supressed 0). [Sep 17 09:26:58] NOTICE[24233] l4isup.c: Process CGU, cic=1, range=14 [Sep 17 09:27:00] NOTICE[24233] l4isup.c: Process CGU, cic=17, range=14 [Sep 17 09:27:17] NOTICE[24233] mtp.c: Got status indication 'OS' while INSERVICE on link 'i1'. [Sep 17 09:27:17] WARNING[24233] chan_ss7.c: MTP is now DOWN on link 'i1'. [Sep 17 09:27:17] NOTICE[24233] mtp.c: MTP changeover last_ack=34, last_sent=34, from schannel 16, no INSERVICE schannel found [Sep 17 09:27:17] NOTICE[24233] mtp.c: Failover not possible, no other signalling link and no other host available. [Sep 17 09:27:17] WARNING[24233] chan_ss7.c: MTP is now DOWN on link 'i1'. [Sep 17 09:27:17] NOTICE[2947] l4isup.c: Unhandled zaptel event 0x4 on CIC=2. [Sep 17 09:27:17] NOTICE[24233] mtp.c: Got event on link 'i1': 4 (0/500). [Sep 17 09:27:19] NOTICE[24233] mtp.c: Got event on link 'i1': 5 (0/500). [Sep 17 09:27:19] NOTICE[2947] l4isup.c: Unhandled zaptel event 0x5 on CIC=2. [Sep 17 09:27:19] NOTICE[2947] l4isup.c: Unhandled zaptel event 0x4 on CIC=2. [Sep 17 09:27:19] NOTICE[24233] mtp.c: Got event on link 'i1': 4 (0/11). [Sep 17 09:27:19] WARNING[24233] mtp.c: MTP2 timer T3 timeout (failed to receive 'N', or 'E' after sending 'O'), initial alignment failed on link 'i1'. [Sep 17 09:27:21] NOTICE[24233] mtp.c: Got event on link 'i1': 5 (0/500). [Sep 17 09:27:21] NOTICE[2947] l4isup.c: Unhandled zaptel event 0x5 on CIC=2. [Sep 17 09:27:21] WARNING[24233] chan_ss7.c: MTP is now UP on link 'i1'. [Sep 17 09:27:21] NOTICE[24233] mtp.c: Sending TRA to peer on link 'i1'.... [Sep 17 09:27:21] WARNING[24233] mtp.c: Got SLTM with unexpected sls=1, OPC=13152 DPC=8458 on 'i1/16' sls=0, state=5. [Sep 17 09:27:22] NOTICE[24233] l4isup.c: Got GROUP RESET message, opc=0x3360, dpc=0x210a, sls=0x1, cic=17, range=14. [Sep 17 09:27:22] NOTICE[24233] l4isup.c: Got GROUP RESET message, opc=0x3360, dpc=0x210a, sls=0x1, cic=1, range=14. On Fri, Sep 14, 2012 at 1:09 PM, Shaun Ruffell <[email protected]> wrote: > [friendly request that you inline or bottom post and trim your replies. > See http://brooksreview.net/2011/01/interleaved-email/ which makes > most of the points I would make on the subject] > > On Fri, Sep 14, 2012 at 09:00:39AM -0300, equis software wrote: > > My test were... > > > > SIEMENS -> LTG1 <--- cable1 - SS7 ---> IVR1 (have errors) > > |-> LTG2 <--- cable2 - SS7 ---> IVR2 (OK) > > > > minutes later... > > > > SIEMENS -> LTG1 <--- cable1 - SS7 ---> IVR2 (OK) > > |-> LTG2 <--- cable2 - SS7 ---> IVR1 (have same errors) > > And your problem follows the server not the card or the cable? Have > you tried other slots? Are you screwing the cards down? > > -- > Shaun Ruffell > Digium, Inc. | Linux Kernel Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA > Check us out at: www.digium.com & www.asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
