Meridian to Asterisk PRI SLIPD, LOSFA Errors

[jtSBA]

Trying to make an asterisk server talk to my nortel and having a hard time determining what sides to blame. The d-channel on this loop (loop 4) alternates between RLS and AEST.

Soon after disabling the d-channel and the loop, re-enabling and an rcnt, I get:
.lcnt 4

PRI LOOP 4
TRSH CNT:
BPV -000
SLIPD -007
SLIPR -000
CRC -000
LOSFA -004
OS_BPV -000
OS_LOSFA-000
OS_YEL -000
and both SLIPD/LOSFA continue to increment.

stat 4:
PRI* TRK LOOP 4 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : NO ALARM
CH 01 - MBSY TIE VOD * CH 02 - MBSY TIE VOD *
CH 03 - MBSY TIE VOD * CH 04 - MBSY TIE VOD *
CH 05 - MBSY TIE VOD * CH 06 - MBSY TIE VOD *
CH 07 - MBSY TIE VOD * CH 08 - MBSY TIE VOD *
CH 09 - MBSY TIE VOD * CH 10 - MBSY TIE VOD *
CH 11 - MBSY TIE VOD * CH 12 - MBSY TIE VOD *
CH 13 - MBSY TIE VOD * CH 14 - MBSY TIE VOD *
CH 15 - MBSY TIE VOD * CH 16 - MBSY TIE VOD *
CH 17 - MBSY TIE VOD * CH 18 - MBSY TIE VOD *
CH 19 - MBSY TIE VOD * CH 20 - MBSY TIE VOD *
CH 21 - MBSY TIE VOD * CH 22 - MBSY TIE VOD *
CH 23 - MBSY TIE VOD * CH 24 - DCH 4

dahdi_tool output on Asterisk server:
Current Alarms: No alarms.
Sync Source: Internally clocked
IRQ Misses: 630
Bipolar Viol: 0
Tx/Rx Levels: 0/0
Total/Conf/Act: 24/ 24/0

Would an IRQ issue cause the link to have these issues?

Does the lack of RED alarms rule out a cabling issue? I made the xover T1 myself and I'm not confident in my skills.

I'm unclear about the clocking setup. The hardware is a Dual Pri card using an MSDL card for d-channel. I have CLOK EXT on the DCH, and on the asterisk side, the span is set up as:

span=1,0,0,esf,b8zs

I'll post more config in my next post, but is there anywhere obvious I can start looking?

 

[jtSBA]

Here's some more of my config. I want to troubleshoot the most I can on the Nortel side first. Should my next step be to re-seat the MSDL card and a "force download". What does that do exactly?

D-channel:
ADAN DCH 4
CTYP MSDL
DNUM 11
PORT 2
DES ASTERISK_VOIP
USR PRI
DCHL 4
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ESS5
SIDE USR
CNEG 1
RLS ID 1
RCAP ND2
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7
************
Route:
TYPE RDB
CUST 00
ROUT 80
DES ASTERISK_VOIP
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS INT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00001
SRVC NNSF
NCNA YES
NCRD YES
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 07980
TCPP NO
PII NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0
NDNO 0
DEXT NO
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096
IENB 5
TFD 0
VSS 0
VGD 6
DRNG NO
CDR NO
VRAT NO
MUS NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TDET NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
ARDN NO
AACR NO
***************
RLI 80
ENTR 0
LTER NO
ROUT 80
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
CNV NO
EXP NO
FRL 0
DMI 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 0
OVLL 0
************
Trunk member example:
DES ASTERISK_VOIP
TN 004 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 10
RTMB 80 1
B-CHANNEL SIGNALING
TGAR 1
AST NO
IAPG 0
CLS CTD DIP WTA LPR APN THFD HKD
P10 VNL
TKID
AACR NO
DATE 21 JUN 201

 

[drifter56]

First off I do not know the Asterick system but here are some general thoughts. The SLIPD and LOSFA errors are T1 level alarms and are probably the reason the D channel is not running properly. These could easily be caused by a timing issue between the two machines. If the Nortel is your main system and has other carrier T-1's coming into it I would guess you are using one of them as a clocking source? If that is true then the clock card in the Nortel is syncronizing all the other transmit T-1 signals to that frequency. In that case you need to tell the Asterisk to take it's timing from the Nortel T-1 circuit.
Also I am not sure your D channel will work the way it is programmed unless the Asterisk can actually emulate an ESS5 Central Office. Normally you would use QSIG to connect two different vendors equipment.

 

[jtSBA]

Thanks drifter. Yes we have other carrier T-1's and yes we're using one as the clocking source. I tried all different timing settings on the Asterisk all with the same results. It was recommended I use the ESS5 switch type in the asterisk-meridian setup document I used, so yes, that should be the proper setting.

I think my only option is to disable and reseat the MSDL card, I was hoping it wouldn't come to this, we have 3 providers PRI's that will be affected. I'm new to the PBX world and have never done it but good time to learn I guess. I hope I have my commands straight..

Resume is up to date.