I have a NTRB21AB installed in an option 11 and when I stat msdl 9 I get:

.stat msdl 9
MSDL 9: MAN DSBL
DCH 9 DIS PORT 1
.

So naturally I do a:

enl msdl 9

and it returns:

DOWNLOADING BASE
REASON: NONE ON CARD

OVL021 IDLE

SDL100 BUSY
........................
TIM000 11:50 20/7/2012 CPU 0

SDL000 MSDL 9 , VERSION 73 , MAINT MODE.

And eventually:
.
MSDL011
No response received to the enable card command

If I do a enl msdl 9 again I get a:

MSDL016
Failed enable attempt. If this message is not accompanied by any other
error message, the card may be in the process of performing self-tests
or the self-tests may have already failed.
Wait a few minutes, then execute the self-tests with the SLFT MSDL x
command. If self-tests pass, try to enable the card again.
Severity: Critical

so I run the slft and it posts results:

slft msdl 9
..............................
..............................
..............................
..............................
..............................
..............................
..............................
..............................
........
SELFTESTS PASSED
CARDID = NTRB21AB 01 NNTM5009PC10

and the cycle repets iself. I have attempted enl msdl 9 fdl with the same results. Any suggestions?

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

isnt a NTRB21 a TMDI or am I remembering wrong?

Thanks,

Buddy

Linked in Profile
http://www.linkedin.com/in/buddyhassell

I thought that too...When I try and add the dch with ctyp tmdi it asks me for cdno. I enter 9 as this is the slot that the card is in and I get a:

SCH3722
Added loops must be of the same type as DCHL.

so I configured it as msdl and it appeared to configure correctly...and tests correctly. Thanks!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

is it a TMDI in CEQU? It will ask TMDI and you have to answer yes, then you can build your DCH and card type will be TMDI

Thanks,

Buddy

Linked in Profile
http://www.linkedin.com/in/buddyhassell

So I double checked and did a chg the cdqu for dlop 9 (the slot number) mode is pri tmdi is yes.

REQ chg
TYPE cequ
TDS
CONF
DLOP 9
MODE pri
TMDI yes
LCMT b8s
YALM fdl
T1TE
TRSH 0

Same result when attempting to build the dch as ctyp tmdi when I get to the cdno and attempt to put 9 i get:

SCH3722
Added loops must be of the same type as DCHL

do I need to build a "dchl" first?

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

What are you doing when you get the SCH3722?

HAve you done a ENL TMDI 9 FDL in LD 96 to enable the card?

Thanks,

Buddy

Linked in Profile
http://www.linkedin.com/in/buddyhassell

I would out the dch if it is built, go to LD 17 and chg cequ and at dlop put x9 and enter through and then re-add it in cequ wiht tmdi yes and see if that solves your issue adding dch

Thanks,

Buddy

Linked in Profile
http://www.linkedin.com/in/buddyhassell

I agree with Buddy...dump it all, change the digital loop, rebuild the d channel and then you should be able to build your TMDI in LD 96 and then enl all and est

Jim

"If I had known it would turn out like this, I would have became a locksmith" Albert Einstein

NCSS NCTS NCTE CS1000E
Mitel 3300 4.2 basic & advanced, 5000 4.0, NuPoint I&M 4.2

Sorry it took me so long to reply I went home for the weekend it looks like removing it from cequ did the trick. Now I have to see if my programming is going to jive with frontier! This card pins out to be on vilot green vilote brown pairs correct? I believe that is what I have read. Thanks Again for the help!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

What type of connector did you get with the TMDI card? AMP to DB15 or AMP RJ45? Make a T1 loopback plug by looping pins 1&4 and 2&5. This will allow your circuit to come up when you enable it, though the D channel won't. Don't forget to build the clock controller in LD 73.

"If I had known it would turn out like this, I would have became a locksmith" Albert Einstein

NCSS NCTS NCTE CS1000E
Mitel 3300 4.2 basic & advanced, 5000 4.0, NuPoint I&M 4.2

The interesting thing is that the card didn't come with any connector. Just the card. So on my option 11 when they installed it they brought all the ports out to 110 blocks. So according to what I read some ware else on this forum the TMDI card pins out on vlgr vlbr pairs right? So in theory I could loop the card by connecting the violet pairs and the colored pairs?

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

check pdf "Circuit card reference" for the TMDI
and the DS-1 line interface pinout for NTBK04 cable

__________________________________________________________
Find a job you love and you'll never work a day in your life. - Confucius

Yes, you can use the V/GR and V/BR pairs on the amphenol connected to that slot. I've done it many times.

OK, yes you can loop violet to violet and colored together for a loopback if needed

"If I had known it would turn out like this, I would have became a locksmith" Albert Einstein

NCSS NCTS NCTE CS1000E
Mitel 3300 4.2 basic & advanced, 5000 4.0, NuPoint I&M 4.2

That worked great! I have the PRI installed and up and running now...but now I am running into another problem. I have been searching all afternoon looking for an answer but no dice. So when I make an inbound call with the msgo / msgi enabled I see the call I see the digits I see the caller id but I get:

DCH 9 UIPE_IMSG CC_SETUP_IND REF 00000600 CH 9 23 TOD 15:10:38 CK F5FE0396
CALLED #:3460 NUM PLAN: E164 TON: LOCL
PROGRESS: ORIGINATING END IS NOT ISDN
CALLING #:2694205481 NUM PLAN: E164 TON: NATL

DCH 9 UIPE_OMSG CC_REJECT_REQ REF 00008600 CH 9 23 TOD 15:10:38 CK F5FE03C6
CAUSE: #21 - CALL REJECTED

I am was thinking it had to be in the rdb but now I am not so sure. Someone in another forum mentioned makeing sure it is set to NATL and I believe it is but I see on the CALLED number line TON: LOCL and I am not sure how to change that or if I am barking up the wrong tree. Below are fresh prts of the dch, bch example and the rdb:

ADAN DCH 9
CTYP TMDI
CARD 09
PORT 1
DES FrontierPRI
USR PRI
DCHL 9
OTBF 32
PARM RS232 DTE
DRAT 64KC
CLOK EXT
IFC NI2
ISDN_MCNT 300
CLID OPT0
CO_TYPE STD
SIDE USR
CNEG 1
RLS ID 25
RCAP COLP
MBGA NO
OVLR NO
OVLS NO
T310 120
T200 3
T203 10
N200 3
N201 260
K 7
BSRV NO

DES FRONTIER PRI
TN 009 23
TYPE DID
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 0
RTMB 9 23
B-CHANNEL SIGNALING
NITE
STRI/STRO OWK OWK
AST NO
IAPG 0
CLS UNR DTN WTA LPR APN THFD HKD
P10 VNL
TKID
AACR NO
DATE 23 JUL 2012

TYPE RDB
CUST 00
DMOD
ROUT 9
DES FRONTIER PRI
TKTP DID
M911_ANI NO
M911_TONE NO
NPID_TBL_NUM 0
SAT NO
RCLS EXT
VTRK NO
NODE
DTRK YES
BRIP NO
DGTP PRI
ISDN YES
MODE PRA
IFC NI2
CBCR NO
NCOS 0
SBN NO
PNI 00001
NCNA YES
NCRD YES
CHTY BCH
CPFXS YES
CPUB OFF
DAPC NO
BCOT 0
INTC NO
DSEL 3VCE
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
RANX NO
SRCH LIN
TRMB YES
STEP
ACOD 3909
TCPP NO
PII NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 1
NDNO 1 *
DEXT NO
DNAM NO
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
FLH 510


PAGE 002

GRD 896
SFB 3
NBS 2048
NBL 4096

IENB 5
VSS 0
VGD 6
DRNG YES
NDRI 00
CDR YES
INC YES
LAST NO
TTA YES
ABAN YES
CDRB NO
QREC NO
OAL YES
AIA NO
OAN YES
OPD NO
CDRX NO
NATL YES
VRAT NO
MUS NO
EQAR 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
TTBL 0
ATAN NO
PLEV 2
MCTS NO
ALRM NO
ART 0
SGRP 0
AACR NO

Hopefuly there is something glaring that I just don't know to look for. Thanks again I couldn't do it without everyone here!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

Is this your 1st PRI on this system? Go to LD 21 and print LDN. Verify you have a 4 digit number programmed under LDN 0.

No not the first pri but the first telco pri. I have an existing pri for internal 4 digit dial / lcr and whatnot. I did the prt and this is what I got:

TYPE LDN_DATA
CUST 00
OPT
DLDN NO
LDN0
LDN1
LDN2
LDN3
LDN4
LDN5
ICI 00
ICI 01
ICI 02
ICI 03
ICI 04
ICI 05
ICI 06
ICI 07
ICI 08
ICI 09

According to what I see on a working PRI in my 61 it should look something like:

TYPE LDN_DATA
CUST 00
OPT XLDN
DLDN YES
LDN0 4000 <-----Change this to the reception at this site maybe?
LDA0 09
LDN1
LDA1
LDN2
LDA2
LDN3
LDA3
LDN4
LDA4
LDN5
LDA5
LDBZ 1
ICI 00 LD0
ICI 01 DL0
ICI 02 INT
ICI 03 RLL
ICI 04 CFN
ICI 05 CFB
ICI 06
ICI 07
ICI 08 IADN
ICI 09 LD1


Thanks again!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

Correct. The system uses that field to know how many digits to expect. Is it working now?

Worked Perfect!...Now 1 more thing I want to run by you =-) Currently my copper trunks use ACOD 3900 for outbound calls. If I change the ACOD on the RDB for the copper trunks to something other than 3900 and change the ACOD for my pri group to 3900 in theory it will behave the same as the copper RDB did? I really appreciate all the help!! Once this one is done I only have to replicate it 3 more times on 3 different switches. I think I will be in good shape once I have this one behind me!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

So I did what I asked about above...I changed my rdb 0 to some invalid acod and changed my new pri to acod 3900 and I was able to create an acd that forwarded to my cell phone and it worked. I am waiting for people to arrive to test call but I am suspecting that it should be good to go. What I am not sure of is what 3900 is referencing. I know that it is probably in the bars/nars/lcr tables but I don't know where to see specifically where that 3900 is. All 5 of our switches use that 3900 as their acod. It doesn’t really matter at this point but if anyone has and insight on that it would be great. Again I can't that everyone enough...This forum has made pbx work for a network guy much much easier!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

BARS/NARS uses the route number not the ACOD.
You will need to change all RLB's in LD 86 that reference the original copper route number. Otherwise your calls will continue to use the old route.

That seemed to work great...So I changed all the RLI's that pointed at the copper rdb 0 to 9 and it appears that my local calling is working great now! So the flow of things is this as I understand it:

NPA matches and sends it to a RLI that tells it what trunk to go out and adds and / or removes digits as needed for those trunks. How does it get to the NPA? Everything is working now I believe I appreciate all the help!!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

Nobody explains it better than GHTROUT
http://www.ghtrout.com/bars/index.html

ahha!! Thanks! So because we are using bars/rli/lcr then the acod on the route group really dosn't do anything except provide a direct access to bypass bars. Cool thanks again!

Bradley A. Fuller
Manager, Network Infrastructure
Kellogg Community College

ACOD also comes into play with CDR.
Most CDR software applications need to know the ACOD for all the trunk routes because it shows up in the CDR record.