pri card is not sinking 2

[gullsinn]

we have 2 sites on same location
got another e1 for second site
i setup pri card for second site with all same values as first one
printed in ld 22 cequ adan
rdb in ld 21
did in ld 20
stated in 60 and all values are same as first site
however second site is not dialing to any out network number
both e1 lines are working on first site checked one by one
LED status on pri card is
ACT is on (Green)
Red is on (RED)
CC green but blinking
DCH is on (green)

 

[KCFLHRC]

We don't have E1's here in the US but Red is bad. Flashing clock controller means enable but no sync. D-channels would need to be set up different, one master and one slave.How far apart are these switches and how are they connected?

 

[gullsinn]

both sites are in same room
the second site is not a fresh install and it was installed in another city with different city code maybe this could be problem
nodeid of first site was 8018 and second was 8015
i added another node as 8018 and make it primary then set old one as false but no luck weather node id is 8015 or 8018

 

[gullsinn]

Ahh i found a difference between both sites but dont know how do i change it
working PRI site

REQ  prt
TYPE adan

ADAN   HIST
  SIZE   25000
  USER MTC BUG
ADAN     TTY 0
  CTYP QSDI
  GRP
  DNUM 0
  DES
  FLOW NO
  USER MTC OSN
  XSM  YES
  TTYLOG       0
  BANR YES

non working PRI site

REQ  prt
TYPE adan

ADAN   HIST
  SIZE   25000
  USER MTC BUG
ADAN     TTY 0
  CTYP MGC
  IPMG 4 0
  DNUM 0
  PORT 0
  DES  mtc
  BPS  9600
  BITL 8
  STOP 1
  PARY NONE
  FLOW NO
  USER MTC SCH BUG
  XSM  NO
  TTYLOG       0
  BANR YES

in pri working site CTYP is set to QSDI and in seond site CTYP is set to MGC

 

[KCFLHRC]

Doesn't look like your d-channel printed out. However, if they are in the same room you very well may need a crossover cable

 

[MossEng]

The print out has nothing to do with the PRI configuration, its a serial port configuration for maintenance/admin. you need to look at/post the DCH configuraton, also have you checked DIP switch settings on PRI card?

 

[bignose21]

LD 73
req prt
type pri2
feat syti

LD 22
req prt
type adan

req prt
type cequ

ld 20
req prt
type tnb
tn <channel of the PRI>

Ld 21
req prt
type RDB
rout <route number>

and we can take a look at the config

 

[gullsinn]

Here is a print said by bogone21
E1 provider says there is no alarm at there end and seems working fine
however i get fast busy when i dial access code

ld 73
DDB000
MEM AVAIL: (U/P): 98886601    USED U P: 5318473 64747    TOT: 104269821
SCH5066

REQ  prt
TYPE pri2
FEAT syti
DTA308 12

DTA108 12 CR



MGCLK 4 0 3
PREF  4 0 3
SREF
CCGD   15
CCAR   15
EFCS  NO

MEM AVAIL: (U/P): 98886601    USED U P: 5318473 64747    TOT: 104269821
SCH5066

REQ  ***
OVL000
>
DTA305 12

DTA109 12 CR

DTA203 12 0 2

DTA203 12 0 1
ld 22
PT2000

REQ  prt
TYPE adan

ADAN   HIST
  SIZE   25000
  USER MTC BUG
ADAN     TTY 0
  CTYP MGC
  IPMG 4 0
  DNUM 0
  PORT 0
  DES  mtc
  BPS  9600
  BITL 8
  STOP 1
  PARY NONE
  FLOW NO
  USER MTC SCH BUG
  XSM  NO
  TTYLOG       0
  BANR YES
ADAN     TTY 1
  CTYP MGC
  IPMG 4 0
  DNUM 1
  PORT 1
  DES  mtc
  BPS  9600
  BITL 8
  STOP 1
  PARY NONE
  FLOW NO
  USER MTC SCH CTY BUG
  XSM  NO
  TTYLOG      66
  BANR YES
ADAN     TTY 2
  CTYP MGC
  IPMG 4 0
  DNUM 2
  PORT 2
  DES  cdr
  BPS  9600
  BITL 8
  STOP 1
  PARY NONE
  FLOW NO
  USER MTC
  XSM  NO
  TTYLOG      66
  BANR YES
ADAN     TTY 4
  CTYP CPSI
  DNUM 4
  PORT 0
  DES
  BPS  9600
  BITL 8
  STOP 1
  PARY NONE
  FLOW NO
  USER MTC TRF SCH BUG OSN
  XSM  NO



PAGE 001

  TTYLOG       0
  BANR YES
ADAN     TTY 5
  CTYP CPSI
  DNUM 5
  PORT 1
  DES
  BPS  9600
  BITL 8
  STOP 1
  PARY NONE
  FLOW NO
  USER MTC TRF SCH BUG OSN
  XSM  NO
  TTYLOG       0
  BANR YES
ADAN     TTY 6
  CTYP PTY
  DNUM 6
  PORT 1
  DES  otm
  FLOW NO
  USER MTC SCH CTY
  XSM  NO
  TTYLOG      66
  BANR NO
ADAN     TTY 7
  CTYP PTY
  DNUM 7
  PORT 0
  DES  otm2
  FLOW NO
  USER MTC SCH CTY
  XSM  NO
  TTYLOG      66
  BANR NO
ADAN     DCH 12
  CTYP MSDL
  MG_CARD  004  0  03
  PORT 1
  DES  pascom1
  USR  PRI
  DCHL 12
  OTBF 32
  PARM RS422  DTE
  DRAT 64KC
  CLOK EXT
  IFC  ESGF
    PINX_CUST 0
    ISDN_MCNT 300
  CLID OPT0
  CO_TYPE  STD
  SIDE USR
  CNEG 1
  RLS  ID  **
  QCHID YES
  RCAP COLP
  MBGA NO
  OVLR YES
  DIDD 0
  OVLS YES



PAGE 002

  OVLT 0
  T310 120
  T200 3
  T203 10
  N200 3
  N201 260
  K    7

REQ  prt
TYPE cequ

CEQU
  MPED 8D
  TERM
  REMO
  TERD
  REMD
  TERQ
  REMQ
  SUPL V004 V008 V100
  SUPC
  SUPF
  DDCS         MG_CARD
  DTCS
  XCT  000 016
  CONF *001 *017
  MGTDS        IPMG  IPMG_TYPE
         080  004  0   MGC
         082  004  1   MGC
         086  008  0   MGC
  MGCONF       IPMG  PORTS  IPMG_TYPE
         070  004  0   30    MGC
         072  004  1   30    MGC
         076  008  0   30    MGC
  MFSD * 000 * 016 * 080 * 082
       * 086
  PRI2       MG_CARD
      012    004  0  03
      021    004  1  01
      031    008  0  01
  APVL
  DTI2         MG_CARD
  MISP         MG_CARD
  SYNM 0
  EXT0  3PE
  EXT1  3PE
  MCFN  011 MB

REQ  ***
OVL000
>ld 20

PT0000
REQ: prt
TYPE: tnb
TN   12 1
DATE
PAGE
DES

DES  PASCOM1
TN   012 01  VIRTUAL
TYPE DID
CDEN SD
CUST 0
TRK  PRI2
PDCA 1
PCML A
NCOS 0
RTMB 12 1
B-CHANNEL SIGNALING
NITE
AST  NO
IAPG 0
CLS  UNR DTN CND ECD WTA LPR APN THFD SPCD
     P10 VNL
TKID 8018
DTCR NO
AACR NO
DATE 27 JUN 2015


NACT ***
OVL000
>ld 21
PT1000

REQ: prt
TYPE: rdb
CUST 0
ROUT 12

TYPE RDB
CUST 00
ROUT 12
DES  PASCOM1
TKTP DID
TW_ROUTE  NO
NPID_TBL_NUM   0
SAT  NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI2
ISDN YES
    MODE PRA
    IFC  ESGF
    SBN  NO
    PNI  00000
    NCNA NO
    NCRD NO
    ISAR NO
    CPFXS YES
    DAPC NO
    INTC NO
MBXR NO
DSEL VOD
PTYP DCO
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 6602
TCPP NO
TARG 01
CLEN 1
BILN NO
OABS
INST
MFC  NO
ICIS YES
OGIS YES
PTUT 0
TIMR ICF  512
     OGF  512
     EOD  13952
     NRD  10112
     DDL  70
     ODT  4096
     RGV  640
     FLH  510
     GTO  896
     GTI  896
     SFB  3
     NBS  2048
     NBL  4096

     IENB  5
     VSS  0


PAGE 002

     VGD  6
DTD  NO
SCDT NO
2 DT NO
DDO  NO
DRNG NO
CDR  NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS  NO
PANS YES
EQAR YES
  NTOL ALOW
  ITOL ALOW
FRL  0 0
FRL  1 1
FRL  2 2
FRL  3 3
FRL  4 4
FRL  5 5
FRL  6 6
FRL  7 7
OHQ  NO
OHQT 00
TDET NO
TTBL 0
ATAN NO
PLEV 2
OPR  NO
PRDL NO
EOS  NO
DNSZ 0
RCAL NO
MCTS NO
ALRM NO
BTT  30
ACKW NO
ART  0
PECL NO
DCTI 0
TIDY 6602 12
SGRP 0
ARDN NO
AACR NO

REQ: ***
OVL000
>ld 60
DTI000
.stat 12

PRI2 LOOP 12 - ENBL
REF CLK: ENBL
TRACKING
SERVICE RESTORE: YES
ALARM STATUS: OOS   REMOTE ALARM:  AIS
CH 01 - DSBL DID   VOD  *           CH 02 - DSBL DID   VOD  *
CH 03 - DSBL DID   VOD  *           CH 04 - DSBL DID   VOD  *
CH 05 - DSBL DID   VOD  *           CH 06 - DSBL DID   VOD  *
CH 07 - DSBL DID   VOD  *           CH 08 - DSBL DID   VOD  *
CH 09 - DSBL DID   VOD  *           CH 10 - DSBL DID   VOD  *
CH 11 - DSBL DID   VOD  *           CH 12 - DSBL DID   VOD  *
CH 13 - DSBL DID   VOD  *           CH 14 - DSBL DID   VOD  *
CH 15 - DSBL DID   VOD  *           CH 16 - DSBL DID   VOD  *
CH 17 - DSBL DID   VOD  *           CH 18 - DSBL DID   VOD  *
CH 19 - DSBL DID   VOD  *           CH 20 - DSBL DID   VOD  *
CH 21 - DSBL DID   VOD  *           CH 22 - DSBL DID   VOD  *
CH 23 - DSBL DID   VOD  *           CH 24 - DSBL DID   VOD  *
CH 25 - DSBL DID   VOD  *           CH 26 - DSBL DID   VOD  *
CH 27 - DSBL DID   VOD  *           CH 28 - DSBL DID   VOD  *
CH 29 - DSBL DID   VOD  *           CH 30 - DSBL DID   VOD  *
CH 31 - DCH 12
.stat msdl dch

DTI005

.stat msdl 4 0
DTI002

.3

DTI002

.***
OVL000
>ld 96
DCH000
.stat dch 12
DCH 012 : OPER       RLS         AUTO
 DES : pascom1
.

 

[bignose21]

So config is for loop 12 in card slot 4-0-3 its an ESGF QSIG circuit and config looks ok if thats what the other end is set up to. Looking at the STAT you did in LD60 says that you have a Layer 1 issue and you are getting Alarm Indication Signal (AIS constant stream of 1's). this would normally be coming from transmission equipment for example:

PABX -------TX------- MUX_________Failed______________MUX-------RX-------PABX
A -------RX ------ A B -------TX------ B

So link has failed between the MUX's they would send AIS towards the PABX's.

Have you got the same CRC settings both ends LD 73
req prt
type pri2
feat lpti

Look at the MFF prompt AFF=Off CRC=On

 

[gullsinn]

Thank you very very much all of you helping to alive a site which our vendor declared as dead and not repairable.

not sure if it relates however i configure LDN 0 in ld 15 and CHG ISDN to yes again in RDB soon after it start working
you can not set ISDN to yes if LDN0 is not configured though it prints YES in LD 21 RDB

 

[KCFLHRC]

I don't know how you even configured a PRI or D-channel without ISDN set to YES. My guess is someone changed it afterwards.

 

[gullsinn]

actually it gave a SCH but did not stuck on that and just moved to next prompt which i ignored when i do see it as YES in print

 

[gullsinn]

Ahh here i am stuck on incoming calls
i can dial outbound calls from second/both sites however if i call to DN on second site either from first site or or out side
the call is not being routed to second site.
in INT CTVN is not set to ovf ovf ovf ovf so all wrong incoming calls routed to console therefore from out side the call is treated as wrong dialing and routed to console and from first site it just gives fast busy tone like the DN does not exists.

how do i fix that

 

[KCFLHRC]

You need to point those numbers in CDP from site A to site B and build an RLI to carry that traffic.

 

[bignose21]

btw the lenght of the LDN0 you set is the number of trailing digits it will look at for routing in IDC etc.

 

[KCFLHRC]

And the digit length it looks at for DID and DNIS Digits

 

[gullsinn]

Sorry i don't understand "btw the lenght of the LDN0 you set is the number of trailing digits it will look at for routing in IDC etc."
my LDN0 is 10 on second site (not printed yet on first) and DCH rout is 12 on both sites
on first sites DNs are starting from 35500 and on second site DNs are starting from 400
i advised to no direct incoming call on second site and operator of first site will manually transfer from m2250 console to requested DN however both sites will be able to dial each other.
can you please help seting up CDP in these conditions

 

[bignose21]

say LDN0 is 1234 then on ISDN DID trunks the system would look at the last 4 digits of the received called number.

 

[KCFLHRC]

LDN has absolutely nothing to do with IDC other than the length of your numbering plan.