Dual Pri cards

[grnichol]

I have a CS1000m MG cppiv release 5 issue 50
There are 2 Dual Pri cards (NT5D12AH 01) in the pbx. There are 2 local and 1 long distance pri's going into the pbx. I beleive there is a 4th one available to use? I am wanting to be able to use it as a tie to a cisco system we are going to be demoing. Is this possible and if so is there any hardware needed to set up the D Channels? Any help or guidence on how to make this work.


There are 3 D Channels setup now
Channel 10, 11 and 12

 

[johnpoole]

ld 96
map dch

will show you device/port numbers.. since msdl's are built as dual or quad.. you should have a spare.. you can use the second half of the dual card.. if you need names, msg lamps etc.. check your switch to see if you can use qsig.. for a tdm ckt, it's your best bet

john poole
bellsouth business
columbia,sc

 

[grnichol]

.map dch
DCH 010 : GROUP 00 MSDL 10 PORT 1
DCH 011 : GROUP 00 MSDL 10 PORT 2
DCH 012 : GROUP 00 MSDL 12 PORT 0

On the pbx all these 3 ports have a cable plugged into them the 4th does not.

 

[bhassell2000]

should be able to use port 3 for your additional dch

Thanks,

Buddy

 

[grnichol]

I will try using port 3 and see what happens Will I need a cord to plug into the port on the front of the card, If so where does it goto.

 

[bhassell2000]

There is a cable that goes to the front of the dual pri card and has two connectors, usually marked port 0 and port 1, to plug into the MSDL card. Check your existing cables to see if there is a spare cable connector not being used from diual pri card that has only one circuit programmed on it.

Thanks,

Buddy

 

[grnichol]

On 1 of the PRI cards there is a cable that goes to the Msdl
card port 1 and port 2. The second PRI card does not have a cable going to the Msdl card. On the Msdl card port 0 there is a cable going to a pc and is labled as tty10?? Does this seem correct.

Is there a way to tell what pri card has what loops assigned to it.

 

[bhassell2000]

then port 0 is a TTY to the PBX, you can look at that in LD 22 prt ADAN. You will need a cable to run from the PRI card to msdl

Thanks,

Buddy

 

[johnpoole]

your map shows two msdl cards in group 0.. device 10 and 12, one may be a daughter board..

remember after you program the dch and loop you have to ld 96 dis msdl x all, then enl msdl x fdl to write the change to that card.. that does not disl the loop, but it stops all new calls, for about a minute and a half.

john poole
bellsouth business
columbia,sc

 

[grnichol]

There is only 1 MSDL card that i can see So i guess the other is a daughter board is there a way i can verify this.

 

[bhassell2000]

what do you get when you

LD 96
stat msdl

Thanks,

Buddy

 

[grnichol]

LD 96
stat msdl


GROUP 0 MSDL 10: ENBL
GROUP 0 MSDL 12: ENBL

 

[grnichol]

is there a way to tell what loop numbers are assoicated with which PRI card and port number

 

[bhassell2000]

you can prt ADAN and it will tell you which PRI DCH is on which msdl and which port (msdl number is dnum and port is port on msdl)


ADAN PRIM DCH 2
BDCH 19
CTYP MSDL
DNUM 6
PORT 0
DES tie.dot.sl100
USR PRI
DCHL 2
OTBF 45
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC S100
SIDE USR
CNEG 1
RLS ID **
RCAP ND2 MWI
MBGA NO
OVLR NO
OVLS NO
PRI INTERFACE ID
003 2
018 3
T200 3
T203 10
N200 3
N201 260
K 7


Thanks,

Buddy

 

[WarbleKing]

This is a good doc to setup the Nortel/Cisco Integration using QSIG if you need it. Hopefully I linked it correctly.

 

[grnichol]

I am not certian if there is a pri loop For the 4th port on the pri cards? I built a new pri loop 19 , i have also built a dch on msdl 12 port 1 which I believe is a daughterboard. I am not seeing how th pri card knows port 1 is going to daughter board port 1. Or how pri loop 19 is attached to either the pri card or the dch?

 

[grnichol]

thanks to everyone for their help i got it setup. The only question i have is about the alarm status: red. I do not have this hooked to the cisco system yet wil that clear when it is hooked to the cisco system. Is there a
way to do a loop back and test the pri before hooking it up ?

PRI* TRK LOOP 3 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : RED
CH 01 - IDLE TIE VOD * CH 02 - IDLE TIE VOD *
CH 03 - IDLE TIE VOD * CH 04 - IDLE TIE VOD *
CH 05 - IDLE TIE VOD * CH 06 - IDLE TIE VOD *
CH 07 - IDLE TIE VOD * CH 08 - IDLE TIE VOD *
CH 09 - IDLE TIE VOD * CH 10 - IDLE TIE VOD *
CH 11 - IDLE TIE VOD * CH 12 - IDLE TIE VOD *
CH 13 - IDLE TIE VOD * CH 14 - IDLE TIE VOD *
CH 15 - IDLE TIE VOD * CH 16 - IDLE TIE VOD *
CH 17 - IDLE TIE VOD * CH 18 - IDLE TIE VOD *
CH 19 - IDLE TIE VOD * CH 20 - IDLE TIE VOD *
CH 21 - IDLE TIE VOD * CH 22 - IDLE TIE VOD *
CH 23 - IDLE TIE VOD * CH 24 - DCH 13

 

[bhassell2000]

if you loop the PRI back to yourself you should get a mesage that says Release Wrong Mode appearing on your screen after about a minute. Are you not looped already? Why are your trunks idle if you are not connected to the far end? Is the D Channel established in LD 96?

Thanks,

Buddy

 

[grnichol]

im not sure why they were idle but here is what i got this morming. If i do a loop back will it go from rls to est.


>ld 60
DTI000
.stat 3

PRI* TRK LOOP 3 - ENBL
FFMT/LCMT/YALMT: ESF/B8Z/FDL
SERVICE RESTORE: YES
YEL ALM PROCESS: YES
ALARM STATUS : RED
CH 01 - DSBL TIE VOD * CH 02 - DSBL TIE VOD
CH 03 - DSBL TIE VOD * CH 04 - DSBL TIE VOD
CH 05 - DSBL TIE VOD * CH 06 - DSBL TIE VOD
CH 07 - DSBL TIE VOD * CH 08 - DSBL TIE VOD
CH 09 - DSBL TIE VOD * CH 10 - DSBL TIE VOD
CH 11 - DSBL TIE VOD * CH 12 - DSBL TIE VOD
CH 13 - DSBL TIE VOD * CH 14 - DSBL TIE VOD
CH 15 - DSBL TIE VOD * CH 16 - DSBL TIE VOD
CH 17 - DSBL TIE VOD * CH 18 - DSBL TIE VOD
CH 19 - DSBL TIE VOD * CH 20 - DSBL TIE VOD
CH 21 - DSBL TIE VOD * CH 22 - DSBL TIE VOD
CH 23 - DSBL TIE VOD * CH 24 - DCH 13
.
TIM098 07:00 17/12/2009 CPU 0


>ld 96
.stat dch
DCH 010 : OPER EST ACTV AUTO BKUP 011 DES : PRI_LOCAL_RT_7
DCH 011 : OPER EST STBY AUTO PRIM 010 DES : PRI_LOCAL_RT_7
DCH 012 : OPER EST ACTV AUTO DES : QWESTLD
DCH 013 : OPER RLS AUTO DES : cisco_tie
.

 

[Reusser]

ALARM STATUS : RED

Red is a physical layer problem - cable to Cisco may need to reverse transmit and receive so the transmit from PBX is recv to Cisco and transmit from Cisco is receive to PBX

probably reason chanels showed idle before is because you built channels after T1 was enabled.