Calls getting barred 1

[crutchie]

First I'd like to thank all the people that have helped me with programming before. John Poole you've helped a lot. Right now I'm trying to build a T1 trunk of between my main switch (opt 11) and a US Redcom switch so that our 2 bases can talk to each other. I've sorted out the majority of programming, changing my d-channel to talk in ess 5 and we have a d-channel link. I can call thru to the redcom switch and have it pick up on the other end. Trouble is, when they call to us I get these messages.

BUG083
BUG083 : 00000016 00000221
BUG083 + 1067FA70 109E2DC0 109E2D1C 109C7702 109C5B0A
BUG83 + 109C3402 109C1E54 109C1890 104B3036 104BB23E
BUG083 + 104BAF64 104B931E 104B1CE0 10888D98 10885BE8
BUG83 + 10885800 10E6C9F8 10E67BFA

DCH 10 IMSG SETUP REF 00008019 CH 0 TOD 13:59:02
CALLING #:3188412156 NUM PLAN: E164
CALLED #:4142 NUM PLAN: E164

PRI227 DCH: 10 DATA: 00000004

DCH 10 OMSG REL COMP REF 00008019 CH 0 TOD 13:59:02
CAUSE :INCOMING CALL BARRED

I've tried changing the barring settings, on the trunks, tried looking at the IDC tables, but I don't believe that since I can see the numbers. So what could be possibly barring the calls?

 

[mikeyb123]

Are these numbers valid extns on each switch?

It's not getting any smarter out there. You have to come to terms with stupidity, and make it work for you.

 

[johnpoole]

look at the dsel prompt on you t, that may need changing. another tool is enl msgi x and enl msgo x on your d in ld 96. that may give you a clue. another tool would be entc x x x x 0100 on your tn then try the call, that will show you the call process.. to help with that, what's your routing between switches? cdp dsc acod?

john poole
bellsouth business
columbia,sc

 

[crutchie]

yes what I printed out was what gets spit out when my msgi and msgo was enabled on the dch.
BUG083
BUG083 : 00000016 00000221
BUG083 + 1067FA70 109E2DC0 109E2D1C 109C7702 109C5B0A
BUG83 + 109C3402 109C1E54 109C1890 104B3036 104BB23E
BUG083 + 104BAF64 104B931E 104B1CE0 10888D98 10885BE8
BUG83 + 10885800 10E6C9F8 10E67BFA

DCH 10 IMSG SETUP REF 00008019 CH 0 TOD 13:59:02
CALLING #:3188412156 NUM PLAN: E164
CALLED #:4142 NUM PLAN: E164the numbers are both correct. The bug 0083 says quotiennt out-of-range in the procedure BCH_to_TN. Right now I'm just using a straight access code to talk to the american side, I was going to add the esn data later once I know the call is correct. What's strange to me is that once my switch gets a valid phone number across the T1 into my switch, it doesn't know what to do with the valid number and barrs it.

Sometimes my calls get barred too, and I know that will not fly with an unstable t1 route. when that happens i get this message:

dch 10 imsg release ref 000000017 ch 3 23 tod 21:01:54
cause:invalid ie contents
here is my route 5 data.

ROUT 5

TYPE RDB
CUST 00
DMOD
ROUT 5
DES DSN
TKTP TIE
NPID_TBL_NUM 0
ESN NO
RPA NO
CNVT NO
SAT NO
RCLS EXT
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00001
SRVC NNSF
NCNA YES
NCRD NO
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
PREM NO
SRCH LIN
TRMB NO
STEP
ACOD 2270
TCPP NO
PII NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC no
DEXT NO
DNAM NO
ANTK
SIGO ETN
MFC NO
ICIS YES
OGIS YES
PTUT 0
TIMR ICF 1920
OGF 1920
EOD 13952
LCT 256
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
PRPS 800
NBS 2048
NBL 4096
TFD 0
DTD NO
SCDT NO
2 DT NO
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
MUS NO
PANS YES
FRL 0 0
FRL 1 0
FRL 2 2
FRL 3 3
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
ATAN NO
PLEV 2
ALRM NO
ART 0
TIDY 2270 5
SGRP 0
CCBA NO
AACR NO