Needs Hint on E1 PRI Link



  • Dear All ,

    I am getting none stop of error on my E1 Gateway . Can you please hint me where could be the issue .

    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2

    Thank you so much in advance



  • "The HDLC Abort(6) message is actually not an error (or even a warning). It is a notice message generated by Asterisk, indicating that a frame on the span failed a consistency check and is being discarded or ignored." ... "It is not uncommon to see some HDLC Abort(6) messages on a perfectly normal PRI connection from time to time. The only time to be concerned about this message is if you see a lot of them, or if they appear to stream constantly to the CLI or Asterisk log."

    http://kb.digium.com/articles/Configuration/What-does-HDLC-Abort-6-mean



  • I'm not an Asterix expert, but this looks more serious:

    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2
    [2016-12-22 04:09:41] NOTICE[1047]: chan_dahdi.c:13484 pri_dchannel: PRI got event: HDLC Bad FCS (8) on Primary D-channel of span 2

    http://www.asteriskguru.com/tutorials/hdlc_bad_fcs.html



  • @thwr here is what the info page had to offer:

    1. Problem Description:

    If you sometimes see this error on a zaptel card, this might be caused by a network card or a harddisk taking an interrupt for too long. This will cause the calls to be dropped.

    This might be caused by:

    • Too much I/O activity
    • bad hardware
    • bad drivers

    If you see this error non stop scrolling on the asterisk CLI, you probably made a configuration error,

    Doublecheck your coding / framing specified in zaptel.conf.
    The below settings worked.

    1. Possible solutions:
    • If you are using an intel 100mbit network card, try replacing the standard drivers with the drivers from the intel website. The drivers included in the kernel have some latency problems

    • replace on board nics with some add-in cards

    • Try looking if you have any shared interrupts, and try playing with disabling onboard network cards and plugging in new ones.
      See also here

    • Try replacing SATA controllers with IDE controllers and tweak the hdparm settings. see this tutorial

    • Stop using the harddisk on the server as much. (get rid of updatedb lines in the cron jobs).

    • upgrade to a dual cpu system, more cpu's = an extra cpu to take an interrupt if the first one is busy with an interrupt that is waiting too long.

    • If you are using a dual port or quad port PRI digium card, you could try to do the hdlc in hardware instead of in software.

    • enable ACPI in the kernel config

    • enable your chipset in the kernel config


Log in to reply