| Summary: | DAHLIN-00212: HDLC Abort (6) on Primary D-channel of span 2 | ||
| Reporter: | nquesada (nquesada) | Labels: | |
| Date Opened: | 2010-09-22 14:39:44 | Date Closed: | 2010-09-24 14:06:01 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | dahdi (the module) |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I have a Digium 210 conected one port with cisco 5300 an the other port with a channelbank orion E1 GSM gateway revived the following error over cli pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 2 pri_dchannel: PRI got event: HDLC Abort (6) on Primary D-channel of span 1 ****** ADDITIONAL INFORMATION ****** group=1 switchtype=euroisdn signalling=pri_cpe echocancel=yes context=from-cisco channel => 1-15 , 17-31 group=2 switchtype=euroisdn echocancel=yes signalling=pri_net context=to-channelbank channel => 32-46 , 48-62 # Span 1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) HDB3/CCS/CRC4 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" HDB3/CCS/CRC4 span=2,0,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 CENTos 5.2 ASterisk 1.6.2 libpri-1.4.11.3 DAHDI Tools Version - 2.4.0 DAHDI Version: 2.4.0 Echo Canceller(s): MG2 Configuration SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1) SPAN 2: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1) | ||
| Comments: | By: Michael Spiceland (mspiceland) 2010-09-22 16:38:33 Have you verified the timing on your interfaces? In particular, check the timing variables in system.conf. Have you done any pattern tests? You have several options for looping back interfaces at various points. This should allow you to do pattern tests. I recommend you start by using a loopback into the Digium TE210P or using dahdi_maint to turn on a local loopback. You can then use patlooptest to send a pattern and check that you can receive the same pattern back. For this test, the interface will need to provide timing if it isn't already (0 for the timing variable in timing.conf). If that passes cleanly, you can then turn off any loopbacks on the Digium interface and turn on a loopback back towards the Digium card. Again, make sure that the timing is set up properly for this test. If the Cisco unit is supposed to provide timing, make sure that its loopback mode will still allow it to provide timing on the span. You can then perform the same patlooptest to the Cisco and back to ensure that link is ok. If you have questions about this or need assistance, I suggest you call Digium technical support, who will be happy to assist you. By: nquesada (nquesada) 2010-09-24 13:52:33 fixed removing crc4 span=1,1,0,ccs,hdb3 span=2,0,0,ccs,hdb3 By: Shaun Ruffell (sruffell) 2010-09-24 14:06:01 nquesada: Thank you for reporting back your resolution. | ||