Norstar MICS 4.0 PRI

[gwics1]

I have a norstar MICS 4.0 w/ a PRI. I believe I have all routes and det codes set up but I am still getting no route dest when dialing a call. The PRI provider is telling me that I am sending them an unknown numbering plan and numbering plan type. Can I change the the numbering plan type to ISDN?

 

[executone]

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


Good Luck!!

 

[gwics1]

Thanks for the tip executone but I have got that portion down. heck I can almost do it my sleep. The problem at hand is that the PRI carrier is telling me that they are recieving an unknown numbering plan and an unknown numbering type. To them it means that the calls are initiating but not completing because their switch does not know where to route the call. They put in place a temporary solution. They put some equipment in front of the switch to tell it where to send calls. This does not tell me if I can solve the problem from my end.

 

[PERRYPJ]

There was a lot of problems with 4.0 and Pri enabled only fix was to upgrade, in fact there was a free upgrade program that ended about a year ago.

OLD ROLMEN WORKING ON NORTELS

 

[nortechie]

gwics1 do you know what type of switch that your PRI is comming off...It may be provisioned for None SL-1 (because its on a Public Network and not a Private network), and therefore the protocol would have to be NI-2,DMS-100 or ESS.

Check it out
Good Luck

 

[gwics1]

The CO switch is some off brand and I do not Know what it is. I did confirm that it should be NI-2.

 

[Roldan]

Have you tried DMS100 or even 4ess, I've had instances where Telco told me to set as NI-2 and things just didn't work right and when I changed this setting evrything worked better. I'm definitely not saying this will work, but can't hurt to try.

 

[nortechie]

gwics1,
Roldan has a point. I have also had a similar problem. ITAS told me to use NI-2...But the C.O. that it was comming from had not updated it's software on the DMS so the caller ID and some other miner things did not work correctly. Once it was set to DMS-100 ALL the problems went away.

If you go with a software upgrade use 4.1 wi6.15 or 5.0 wi6.06,don't use lower working issues the had problems.

 

[gwics1]

The CO Put some equipment in front of their switch that tells it where to send unknown routing or numbering plans. The MICS is currently set up for NI-2 and calls are going out. Apparently this is supposed to be a temporary fix until they can figure out another solution.