Norstar MICS PRI protocol NI-1 or NI-2

[daveybc]

Would someone know the difference in the NI-1 compared to NI-2 protocol on a PRI. I have been told NI-2 is used for caller ID name and number display from one source, who commonly installs these on the new Panasonic systems. Is this correct? The contact placing the order for the PRI told me he thought that NI-1 was usually used on the Norstar systems. I think I have all the other parameters nailed down. Could someone help me out on this one? This is my first PRI install. Thanks for any input. Dave.

 

[NorstarOption]

NI-2

 

[aragon]

There is no selection in Norstar to support NI-2.
Typically the Norstar has issues with 5ESS switches supporting NI-2
Given the choice I would opt for NI to support the Norstar.

Norstar and BCM work best with DMS-100!!!!!

 

[daveybc]

The PRI is coming from a DMS 100. The MICS and all parts are brand new w/6.1 sw. NorstarOption figures NI-2, and Aragon figures NI? ( thought the options NI-1 or NI-2 ) Can else clarify. Thanks.

 

[aragon]

Norstar supports DMS-100 quite nicely.
DMS-100 is a Nortel product.
If the telco can deliver DMS-100 I recommend DMS-100 not NI-X

NI sucks on Norstar/BCM

 

[aragon]

Forgive me the manual does state support for NI-2 in Norstar and BCM.

I still run screaming from every NI-2 install and insist on DMS100 support from the telco, I am in Ontario therefore this is not a problem for me since Bell Canada uses DMS100's.

There are many NI-2 issues depending on the manufacturer's implementation of NI-2 most notably the Lucent 5ESS interoperability with Norstar and BCM.

 

[NorstarOption]

Usually, you use NI-2 protocol if the telco provider has an AT&T 5ESS switch. As you mentioned telco is using Nortel DMS100 so you will use DMS100 as your protocol.

 

[daveybc]

Allstream formally AT&T is providing the PRI coming from a DMS 100. The form I recieved has options like, Line coding B8ZS or AMI, I believe B8ZS is the choice. Line Framing: ESF or D4, I believe ESF is the choice.Trunk selection sequence: I believe Asequential is the choice. Type of connector: I believe RJ45 is the choice. Digits to outpulse: I believe 4 will be my choice. Protocol: NI-1 or NI-2 are the choices. From what I am hearing NI-1 should be the choice because it is easier to setup and is standard for most installations on MICS w/PRI. Is all of above standard choices? Any help I get is truley appriciated. Thanks, Dave.

 

[aragon]

Ask Allstream for DMS100, if not then NI-2.
Connector should be RJ48.
Bi-directional.
Ascending order.
B8ZS
ESF

If you are using a standard 3 digit DN length then be careful with your outpulse selection from Allstream.
Make sure Allstream understands you are connecting a Norstar to this circuit.
If ordering more than one PRI span make sure you receive a dedicated D channel for each PRI circuit. The backup D is not supported by Norstar.
Check your DID range if the last 4 digits look like x2xx or x9xx then you will want to select a different received DN length which does not conflict. It is not a good idea to create a conflict with your internal numbering plan or the default PBX co access code 9.

 

[daveybc]

I will be using 4 digit extensions starting at 3800-3830 and a 4 digit outpulse matching those extensions. I will ask Alltream to have a tech. contact me to answer some additional information. Thanks all for the input. Dave

 

[hawks]

NI2 is the new standard, some CO's that have upgraded there switch say they can not even offer NI1 anymore. They call it custom now if you want NI1 from them. I belive the DMS 100 can do either. At least that is what Verizon tells me. any thoughts..

 

[daveybc]

Thanks Hawks,
I got the contact to find another request form a local Norstar dealer, and they are asking for NI-2 aswell.
Aragon said previosly ask for a RJ48 connector. I figure that must be a typo since the choices are only RJ45 and DB15. I have asked for RJ45. I figure I am now on track.Thanks again.Dave.

 

[aragon]

Here is the scenario regarding received number length.
No outbound destination code can match a received number.
Example:
DID range received digits = 9100-9129
Received number length on Norstar = 4
Route 001 = PRI-A public
Destination Code = 9 = not allowed
Destination Code = 8 = workaround = use route 001 absorb all
Destination Code = 92= workaround = use route 001 absorb all

Example:
Local dialing plan startup DN = 2221 PBX template
Remote dialing plan startup DN = 3221 PBX template
Private DN length = 4
DID range received digits = 3100-3129
Received number length on Norstar = 4
Route 001 = PRI-A public
Route 002 = PRI-B private
Destination Code = 9 uses route 001
Destination Code = 3 uses route 002 = not allowed

A colleague of mine says you should have no problem getting Allstream to deliver DMS100

 

[aragon]

RJ45 spec uses pins 1,2,3,6
RJ48 spec uses pins 1,2,4,5

They look identical and a standard 8 conductor straight thru ethernet cable can be used for either, however the T1 spec uses the RJ48 standard for transmit and receive.