Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New PRI

Status
Not open for further replies.

telepath

IS-IT--Management
Mar 26, 2003
86
0
0
MX
I'm trying to set up a new PRI link between my CS1000M v5.5, I created the DCH,Loop, route, etc.
the problem comes at enabling the DCH, it floods the terminal qith an error and it crashes the other PRI in the same Dual PRI card, until I disable the new DCH.I am not an expert at PRI DCH creation, but I'm not completly ignorant, I used the unused link in a ddp2 and used the (working and in use) 1st Loop/DCH as a guide.
Here are the print outs:
Working At U1 against a CS1000e:
ADAN DCH 4
CTYP MSDL
GRP 3
DNUM 4
PORT 0
DES
USR PRI
DCHL 126
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
NASA YES
IFC SL1
SIDE NET
SEMT 1
CNEG 1
RLS ID 7
RCAP ND2 MWI
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7

Not Working at U2. Not yet connected to anything.
ADAN DCH 127
CTYP MSDL
GRP 3
DNUM 4
PORT 1
DES toVoip
USR PRI
DCHL 127
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ISGF
PINX_CUST 0
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE NET
CNEG 1
RLS ID **
QCHID YES
RCAP COLP
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
********************************************
CEQU
MPED 8D
TERM
REMO
TERD
REMD
TERQ
REMQ
SUPL 004 008 020 024
036 040 052 056
068 072 084 088
100 V200
SUPC
SUPF
DDCS
DTCS
XCT 002 016 032 048
064 080 096 112
TDS * 002 * 016 * 032 * 048
* 064 * 080 * 096 * 112
CONF * 003 * 017 * 033 * 049
* 065 * 081 * 097 * 113
MFSD * 002 * 016 * 032 * 048
* 064 * 080 * 096 * 112
PRI2 001 014 015 034
035 076 077 098
099 126 127
APVL
DTI2
050
MISP
SYNM 0
EXT0 3PE
CNI 009 000 000
CNI 009 001 001
CNI 010 000 002
CNI 010 001 003
CNI 011 000 004
CNI 011 001 005
CNI 012 000 006
CNI 012 001 007
EXT1 3PE
CNI 009 000 000
CNI 009 001 001
CNI 010 000 002
CNI 010 001 003
CNI 011 000 004
CNI 011 001 005
CNI 012 000 006
CNI 012 001 007
MCFN 509 MB
The error flooding the terminal is: ERR9999 DCH:127 EXP (XBFR QUE FULL)
which is undocumented, my guess is a buffer overflow.
 
Is the DCH Cable connected to the PRI card or is this an on board DCH Card? This is a Euro PRI I'm assuming, hence the PRI2
 
It's internal DCH daughtercard, and Yes it is E1.
 
Have you set up the extended mode addressing on the paddle board for 127?.

I think I have attached the correct NTP for you.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
I don't know, I'll check it out. I just have to find how. And yes, it is the right NTP, thanks , i'll post any proggress.
 
I can't find where to see that mode, but I have dch's 98 & 99 active, does that mean I have it on? and If I hadn't, Would it let me create DCH 127?
Thanks.

DCH 004 : OPER EST ACTV AUTO DES : CCCN
DCH 010 : OPER EST ACTV AUTO DES : HOSPITAL
DCH 011 : OPER EST ACTV AUTO DES : AUDCODES
DCH 013 : OPER EST ACTV AUTO DES : valt
DCH 014 : OPER EST ACTV AUTO DES : PRI2
DCH 015 : OPER EST ACTV AUTO DES : IRA
DCH 076 : OPER EST ACTV AUTO DES : DUCT
DCH 098 : OPER EST ACTV AUTO DES : QUER
DCH 099 : OPER EST ACTV AUTO DES : SEC
DCH 127 : DSBL RST AUTO DES : huawei
 
I took out the ddp2 card to check the dip switches, they seem ok, at first I tought that it had an address for each trunk, but I learnt that is one address per DCH daughtercard (S9=0010).
L126_20170215_13_03_05_Pro_kqe7cx.jpg


¿Could it be that enabling the DCH I didn't use the DIS MSDL 4 / ENL MSDL 4 FDL? And if I do dis msdl 4, would this drop both PRI's?
 
It is apparently solved, but I'm not sure what was the issue. After checking step by step all the programming I disabled both units, and disabled/enabled the msdl with the FDL option. After that I enabled both trunks. The first one connected to the remote site in seconds, trunk 1 enabled just fine (the remote site is not ready yet) and is awaiting connection, I have no more FATAL ERROR messages and it seems to have been a simple mistake (enabling a loop without reseting the MSDL) but I learnt some interesting stuff.
So thanks to everyone
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top