PRI to Nortel 2

[franke]

Hi all,
I have to connect a point to point PRI to from an IPO 406V2 to a Nortel OPT51(?). Not having done a p to p before and knowing absolutly nothing about Nortel, any help would be appreciated. Should the TG be set up as Local Company, NI2?

Thanks,
franke

 

[BigWill]

I have done P to P T-1's before, but not with a Nortel Option 51. Always with another IP Office, Magix, or a Definity. These are the things that I think you should based on pure opinion, NOT EXPERIENCE. Because a P to P is nothing more than a "Pipe", it is what you make it. Since NI2 is a Nortel Protocol and the IP Office is compatible I would stick with that. Make sure you have a "Master" and a "Slave" as far a clocking is concerned so dropped calls and T-1 slips aren't happening. The T-1 in the IP Office would of course have its own incoming and outgoing line groups for routing between the PBX's. Other than the obvious that is all that I can help with, I don't even know anyone that is literate on the "Option" series Nortels. I only have delt with the MICS, CICS, and the old DR series. Good luck

 

[franke]

Thanks much for the info BigWill, I'll give you a star now, and if it works on Friday, I'll give you another.

 

[kristiandg]

Two things. First, is it a 51 or 51c? If its a 51c, there's a chance QSIG is enabled on it. If so, you can set up QSIG and have name/number delivery between the systems (very swank). Also, if the 51 is running 25.40b (again it'd have to be a "c" class machine) you can use NI2 and still get name/number delivery, just not updated as transfers occur.

For incoming routing, if you're using QSIG, you don't have to build a thing. If you're using a PSTN protocol like NI2, you can just create 1 incoming route with a * (star), it will take the inbound digits and pass them directly to the system for processing. You don't have to build each extension in your Incoming Route table (thats a pain).

Oh, don't forget to make a T1 crossover cable.

Hope this helps...

Kris G.

 

[franke]

ok, first, a second star as promised for bigwill and one for you as well kris. Set up the trunk group as NI2,b8zs,esf,local telco,Nortel as master clock. Pipe came right up!!! (unlike verizon, which was a 6 hour ordeal). since verizon and nortel were sending the same digits to me, i used the same incoming routing for both (didn't even think of the * ), for outgoing i set up short codes for their ext ranges, i.e.
1xxxx
1NsE
9
dial

i get name & number from nortel but they only get number from me...i don't know , kris, what machine they are running but i will check on that...i was tooo happy just to see it work

thx both,
franke

 

[kristiandg]

Remember that Nortel is a Canadian company. In Canada, PBXs are permitted to send end-to-end Station Data over the PSTN. In other words, you could call your house and it will show "3rd Floor Conf Rm" (really, really cool). This is not permitted in the US. That is why you're seeing their name/number data, because the switch is set up to send it in case its in Canada (the US LECs strip it and replace with a lookup based on the number). Now, you should NOT see if they make a connection w/ you, then xfer the call. It shouldn't update.

Now, the other direction (To the Nortel). You won't be able to have Name delivery. Thats part of my "25.40b" statement above. Nortel permitted Name delivery on NI2 with 25.40b software (granted it was buggy as hell). Prior to that, they will strip the data, as they won't understand how to display it.

BUT, just for the heck of it, you can try in the RCAP section of the DCH programming (Nortel-speak for "Remote Capabilities" and "D-Channel"), entering "NDS" (Name Display Svcs). If you have 25.40b and the appropriate feature pkg, it will take that. If not, experiment with "ND2" and "ND3", but I doubt those will work.

Hope this helps...

Kris G.

 

[joeloh]

I have setup QSIG between IPO and Nortel Option55. Everyhting is wotking fine. However, only extensions are presented no names for users on both sides. Is there any thing needs to be done on the Nortel side.

Thanks
Joe

 

[franke]

Thanks Kris, very informative. I will pass on your suggestions to thir Nortel tech and see if he's up to experimenting.

franke

 

[IPOUK]

1 other thing - make sure the number of channels match on both systems!!! Nortel set this to 10, and I had ours on the default 30. No calls went through. Changed ours to 10 and has worked perfectly since.

 

[franke]

Thnx IPOUK, I'll check that today, but first I have to get the circuit back up. Seems it went down Friday afternoon and Verizon is saying it's a problem with the IPO...again.

franke

 

[BoyRacer1001]

We have dual PRI connected to Nortel Option 11, running sweet. Only catch was to use a dual PRI card in the Nortel for Both PRIs' - had trouble with clocking when using separate cards.
We have nothing in the Incomming call route other than the defaults.

We have got a private build of IP406V2 software though - problems with reboots when calls went direct to VM pro AA.
Fixed in 3.2

 

[franke]

Yeah, had a bit of a problem as well, so I set the clock on the p to p (Nortel ckt) to fallback and that seems to have solved that problem...now we are trying to figure out why the licenses are showing as invalid for VMPro (worked fine prior to upgrading to .65 release ), but today i promised myself i'd only think about beer and fireworks

franke