Hello,
I have a customer who wants to document the programming of his system. It is an 0X32, 4.1 software. I would like to know how does one go about documenting how the Pri was setup? I dont know where to find the values. Everything else is easy.
Thanks,
Gabriel
Example:
DMS-100
BCHANSEQ: DESEND OR ASSEND= use the opposite of TELCO
COFAIL: TIA-547A
I/F LEVELS: ISDN
FRAMING: ESF OR SF
INTERNAL CSU: ON OR OFF: ( LEAVE ON)
CSU LINE BUILD: 0
LINE CODING: B8ZS OR AMI: (NORMALLY SET TO B8ZS)
CLOCKSRC: PRIMARY OR SECONDARY
How to Program PRI?
To enter the software key code:
From Terminals & Sets – Next until get to software keys – Show
Sys ID – Next
Password Keys – Show
Key 1: (enter 1st key code)
Key 2: (enter 2nd key code)
Key 3: (enter 3rd key code)
You must disable the card first, program the card for PRI, then re-enable the card.
To Disable / Enable Card
From Terminals & Sets – Next until you get to Maintenance – Show
Next until get to Module Status – Show
Show module – Next
KSU (1): Next or State if using (2) cards
KSU (2): State
( ) Ports Busy – Press Disable or Enable
Disable at Once? – Yes
Protocols & Signaling
Hardware – Show
Show Module – Next
Cards on KSU – Show
Cd1 – KSU: Change to PRI – Show
Card Type PRI – Next
Lines: 001-023 – Next
Protocol: SL1 – Next (check with your Telco Carrier for setting)
Type Slave – Next
Bchanseq: Ascend or Descend – Next (check with your Telco for setting)
CO Fail: TIA–547A – Next
IF Levels: ISDN – Next
Framing: ESF – Next (usually ESF, check with your Carrier
Internal CSU: ON – Next
{Need to have either an external CSU or turn the internal one on. If customer needs to use some channels for data then they’ll need a CSU/DSU to split off channels before the 0X32. Or to split off data channels after 0X32 they’ll need a Nortel Data Interface (NDI) plus bandwidth allocation key codes}
DSX1 Bld: 000-100
Line Coding: B8ZS (usually B8ZS, check with the Carrier)
ClockSrc: Primary (second card would be secondary)
Users cannot access PRI lines directly through line appearances or line pools (except PRI line pools). All outgoing PRI calls are dialed via intercom using routing codes.
When a trunk card is changed to PRI, all existing line appearances for that card are automatically removed.
To Build a Route
Services – Show
Ringing Service – Next to
Routing Service – Show
Routes – Show
Show Route: 001 – Show
Dialout: No Numbr – Leave alone – Next
Use: ( ) – Change to PRI
DN Type: Public
To Build Destination Codes:
Routing Service – Show
Routes – Next
Dest Codes – Show
Show destcode: (enter code) - Next
DstCode: (enter code) – Show
Normal: 000 – Change to route built – Show
AbsorbLength: ALL
Don’t usually have to worry about Night schedule etc.
Line Set Up
Assign each channel (001-023) as trunk type PRI, Line Type: PRI –A.
PRI Lines are always configured Auto Answer. (Never Manual Answer.)
Target Lines Programming:
From Lines – Show
Show LN: 145 – Show (target line range from 145-275 non-XC SW, 145-336 XC SW)
Target LN – Next
Private to: (extension number) – Next
Rec’d #: (enter digits Telco is sending) – Next
If Busy: to prime – Next
PrimeSet: 221 (change to the extension #)- Next
CLID Set: None – Next
Aux. Ringer: N – Next
End of list
This info should get you started on your documentation. Do not forget to write down the PRI Key Codes.
If you just want to see what the current settings are you do not need to disable anything. Go to >Hardware -> Show module -> Cards on KSU -> PRI (at least that is how it is on my 0x32)and look at how it is setup. From what I read in your first post the PRI has already been setup and you just want to look. If I am incorrect please forgive the mixup....
It would seem not, i just don't want to mess anything up. I will try to see how far i get, and hopefully be able to get all the info. Thanks to everyone who responded, you guys are great.
Gabriel
Executone,
Thanks. I don't have a N* PRI customer to try this with. It just seemed to me that it might be a soft way for Gabriel to get what was required for that customer.
But do let me know.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.