NEC IPK-I Moving from T1 to PRI

[RuralHospital]

Hello Everybody,
I've been managing an IPK-1 system for about 12 years.
( IPK-I, pk192, R4.2sw, T1 DID, COI, 48 PBX stations, 48 SLI stations, Elite Mail )

It's an old system but it's been completely reliable and the staff is satisfied with it except that we need caller ID and our Telco says that requires a PRI interface.
When I converted the system from CO lines to T1, about 8 years ago, I had a tech help me with the setup and warn me of any potential problems, which there were none.
I get the suspicion that PRI is not going to be as straight-forward so I'm looking for advice.
Reviewing the manuals and some older threads I have come up with this work list of which I would greatly appreciate any comments or suggestions:

1) Must use MIFM-U20 ETU with KMM chip installed to capture caller ID numbers.

2) Must use PRI-U20 ETU on "newer" IPK systems. The older PRI-U10 won't work.

3) Must remove all COI trunks, evidently their presence in the system is not compatible with PRI ?

4) Remove T1 ETU and replace with PRI ETU ( 7-1)

5) Delete the T1 trunk group, Build new, PRI trunk group:
Telco must provide PRI D channel on time slot 24
span type: b8zs ( 1.13.xx)
trunk type: WINK (3-14)
trunk type DID (3-91)
assign DID ( 1-1-20,21,22)

6) Set up CAP keys on the stations and remove any CO appearance keys. ( 4-12 )
Currently we are using both CAP and CO on the same phones.

What else am I missing or mistaken on ?
Thank you for reading this post...

 

[gbtac3]

Here is what I have in my notes, although I started working on the SV9100 and only rarely field calls for IPK. I am not sure if there is a specific license for ISDN/PRI, as I could not find one on the SV9100.

ISDN-PRI

10-03-01 Leave set to T-Point
The other options are not supported by the IPKII.

10-03-02 Logical Port
This gives you the starting trunk number for the card.

10-03-03 CRC4
Leave this set to OFF: this is not used in the US. CRC4 is for E1.

10-03-04 Layer 3 Timer Type
1~5 = Refers to 1~5 in 81-06 to adjust all the Layer 3 timers

10-03-05 CLIP Information
ON = Sends the CPN from station or trunk in the setup message
OFF = Will not send the CPN information to Telco even if it is programmed to do so.

10-03-06 Length of cable
0 = 0~40 meters (0~131 feet)
1 = 41~80 meters (131~262 feet)
2 = 81~121 meters (262~396 feet)
3 = 122~162 meters (396~531 feet)
4 = 163~200 meters (531~656 feet)

10-03-07 Digit 0
Leave this at 0. This is for DID digits when using a S-Bus Connection.
S-Bus connections are used for ISDN terminals where T-Bus connections are used to connect trunks to the CO.
The IPKII does not currently support S-Bus connections.

10-03-08 PRT Send
0 = Enbloc
1 = Overlap
Enbloc sends the dialed number in the setup message all at once.
Overlap sends the setup message then sends one by one the dialed Digits. Overlap is usually used in BRI, not PRI.
Currently the IPKII only supports Enbloc.

10-03-09 Info
0 = Keypad
1 = Called Number
This block only comes into play when assigned as Overlap.
Since Overlap is not currently supported, this block does not matter.

10-03-10 System
0 = Slave
1 = Master
Leave as Slave: the IPKII does not support a Point to Point ISDN connection

10-03-11 Network
0~ 50 = Network number in Point to Point connection.
Leave at 0 because the IPKII does not support Point to Point links

10-03-12 Short/Long Haul
0 = Short
1 = Long

10-03-13 Receive Pulse Short/Long
In Short Haul Mode
0 = 0.91V
1 = 0.74V
2 = 0.59V
3 = 0.42V
4 = 0.32V
5 = 0.21V
6 = 0.16V
7 = 0.10V
In Long Haul Mode
0 = 1.70V
1 = 0.84V
2 = 0.84V
3 = 0.45V
4 = 0.45V
5 = 0.20V
6 = 0.10V
7 = Not Defined

10-03-14 Service Protocol for S-point
0 = Keypad Facility
1 = Specified Protocol for IPK II
S-Point is currently not supported for the IPKII: do not change.

10-03-15 Alert Tone when S-Bus Terminal Calls a Busy Extension
0 = Alert Tone
1 = Disconnected
S-Point is currently not supported for the IPKII: do not change.


10-03-16 Two B-Channel Transfer
0 = Off
1 = ON
A two B-Channel transfer frees up the trunk on the IPKII.
Think of this like a Centrex transfer on POTS lines.
Telco must first support this feature before enabling it.

10-03-17 ISDN Line Ring back Tone
0 = Disable
1 = Enable

10-03-18 Type
0 = Unknown
1 = International
2 = National
3 = Network
4 = Subscriber
5 = SPD
This is the Numbering Plan Identification/ Type of number specified in the Called Party Number Information Element. This affects Byte #3
Then 10-03-18 and 10-03-19 affect bits 1~7 of Byte #3.

10-03-19 Plan
0 = Unknown
1 = ISDN
2 = Data
3 = Telex
4 = National
5 = Private


This is the Numbering Plan Identification/ Type of number specified in the Called Party Number Information Element. This affects Byte #3
Then 10-03-18 and 10-03-19 affect bits 1~7 of Byte #3.

10-03-20 Protocol
0 = Standard (Do not use)
1 = Reserved (Do not use)
2 = Reserved (Do not use)
3 = DMS A211 (DMS 100 Custom)
4 = 5ESS
5 = DMS A233 (DMS 100 National; ISDN)
6 = 4ESS
7 = NI2

14-05-01 Trunk Groups
Assign the PRI trunks to a valid trunk group.
Leave the D-Channel in trunk group 0.
Remember to also set the Priority opposite of how Telco is set to prevent call collision

22-02-01 Trunk type
Assign all channels including D-channel as a (3) for DID.

20-09-02 Caller ID Display
Turn ON or OFF a class of services ability to receive caller ID.

21-12-01 ISDN Calling Party Number for Trunks
This sends the CPN to Telco on a trunk basis.
This does not affect inbound calls.

21-13-01 ISDN Calling Party Number for Stations
This sends the CPN to Telco on a station basis.
This block overrides 21-12-01
In order for the DID’s to route properly you still have to set up DID digit conversion in 22-11.

 

[RuralHospital]

Hi gbtac3,
Thanks for the quick reply.
Looking through my manuals I see that those commands for for the IPK-II.
I'm running the IPK-I so the commands are different but I will reference your outline against my IPK-I manual.

One thing I am wondering: Have you ever heard of using PRI interface cards to build a TIE between two switches?
I have two spare IPK-I and I have prototyped a TIE between them using T1 cards so I was thinking that one way to verify the basic
confguration would be to try it with PRI cards.

Thanks again for your reply.

RH

 

[RuralHospital]

I think I found the answer to my TIE question in your notes:
10-03-10 System
0 = Slave
1 = Master
Leave as Slave: the IPKII does not support a Point to Point ISDN connection

Thanks for posting those notes!

 

[DoubleDriveLine]

You also need the clocking card that mounts on the CPU.

The MIFM with KMM chip is only necessary for caller ID scrolling. Caller ID will work without it.

It is still good to have the MIFM because that allows you to do the PC Programming.

 

[RuralHospital]

Thanks, DoubleDriveLine.
The switch is currently on a T1 so I think the clocking card it has now will also work with PRI ?
Wondering if there is a command to turn on Caller ID or if it automatically comes with PRI.
I don't see anything in the manual about that...

 

[DoubleDriveLine]

If the clock card is on the cPU that is the one the PrI will use. The source might need to change if you put the PrI card in a slot other than the T-1 slot. Caller ID coming in I think was automatic. I am not sure if caller Id name is available. I don't remember ever seeing it on those.

 

[RuralHospital]

Well I used the same slot, were the DTI-U30 ETU (T1) was, for the PRI-U20 ETU.
I used the SAT software to modify the IPK program to replace the DTI with a PRI card, with the Wizzard feature as a guide.
I then uploaded it to my test switch and got the message "Layer 1 Down: COxx Layer 1 DOWN" and the red line keys, which seemed normal.
Then I modified the station button assignments to replace the CO with CAP keys, and changed the trunks from CO to DID.
When I tested that program I found that the "Layer 1 Down..." status message was gone!
I'm suspicious; the switch is not connected to a PRI circuit yet so why did that message disappear ?
Later today is cut-over with the Telco; should I be worried ?
Any ideas ?