Succession 4.0

[phnechic]

I am trying to connect an Option 11C running Succession 4.0 (no signalling server attached) to an Option 81C running Succession 3.0 (no signalling server attached)over a point-to-point T1 using PRI. I am able to get the loop to enable, and the DCH to establish, but all channels stay in a MBUSY state and call attempts receive a fast busy. There are no alarms. Is anyone aware of any compatibility issues with 4.0?

 

[johnpoole]

do the d's stay up? if so look at the start arangement, also do a load 96 enl msgi x on your d to see msg's that may give you a hint of where your mis-match happens.. also stat serv in load 96.. /you may want to bring those up.. another show stopper is not doing a fdl on your msdl and/or tmdi after each change.. those are smart cards that need the changes down loaded to them.. i can't see a patch out for a known problem between 3 and 4.. if you can't find the problem, post your d's and your rdb's, maybe one of us can spot something

john poole
bellsouth business
columbia,sc

 

[phnechic]

The d's don't stay up. They establish and release every few minutes. The MSGI is a good idea. I'll check that on-site tomorrow. I did do a FDL. Here are is the DLOP,d's, and rdb's from the Z end (which is the end not communicating). If anyone has any ideas, I'm open for anything. I have replaced every piece of hardware, and built it on a different loop with no results. Thanks for the help!

CEQU
MPED 8D
SUPL 000 004 008 012
016 032 036 040
044 048 064 068
072 P096
TDS 000
CONF 029 030 031 062
094 095

DLOP NUM DCH FRM TMDI LCMT YALM T1TE TRSH
PRI 02 24 ESF YES B8S FDL 0 00
MISP

---------------------
ADAN DCH 5
CTYP TMDI
CARD 02
PORT 1
DES TO_CORP
USR PRI
DCHL 2
OTBF 32
PARM RS232 DTE
DRAT 64KC
CLOK EXT
NASA NO
IFC SL1
SIDE USR
CNEG 1
RLS ID 25
RCAP ND2
MBGA NO
OVLR NO
OVLS NO
T200 3
T203 10
N200 3
N201 260
K 7
------------------------
TYPE RDB
CUST 00
DMOD
ROUT 0
DES TIE_TO_CORP
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC SL1
PNI 00001
NCNA YES
NCRD YES
TRO NO
CHTY BCH
CTYP UKWN
INAC YES
ISAR NO
DAPC NO
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 8000
TCPP NO
TARG
CLEN 1
BILN NO
OABS
INST
ANTK
SIGO ESN5
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 YES
MRT 20
OHQ NO
OHQT 00
CBQ YES
AUTH NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO
---------------------------

 

[unkalary]

What does the DCH on the big switch look like? Is the DCH set for NET as user? Does anyone know what RLS should be used for 4 and 3?

 

[johnpoole]

the only reason to set user to net is to provide clocking to a downstream switch.. some of my pri's are to opt 11's so i am net and the far end is usr.. if they match you'll see the connection come up then rls wronge mode.. ie they match, if you do a loop back on a pri, that is the response.

john poole
bellsouth business
columbia,sc

 

[phnechic]

Thanks for the help. Turned out that the mux was optioned incorrectly for an AMI circuit instead of B8ZS. Took a few days to narrow it down, but I really appreciate you looking at it.