Config for PRI to an ESS5

[ohno2]

Hello,
I'm trying to resolve a problem with outbound caller ID.
I suspected the problem was that my 11c (Rel. 25.30) PRI wasn't configured properly for MCI's switch. My current PRI config lists the IFC as NI2 and RCAP as COLP ND2.
MCI's tech says I'm connected to an ESS5 switch, yet when I rebuild my PRI for an ESS5 I can't get my DCH to stay up (and my trunks all stay busy.)
Each time I try something else, I forced to out trunks, rdb, dch and pop the cards.

The initial problem may have been created when I upgraded to Rel. 25.30 (and put in ITG cards) about a year ago.

Thanks in advance,
Fred

 

[johnpoole]

if your running tmdi cards don't pop them just dis and enl with a fdl, your running the same protocol i would for a number 5.. rls 33.. in ld 96 have you tried enl msgo x with x=to your dch.. that will tell you what you are sending out. never take a network techs word for what they are getting, i know i used to be one..look at what your sending, and go from there. i never use rcap unless i am running between sl-1's.. my name display works as well as clid entries

john poole
bellsouth business
columbia,sc

 

[hawks]

Keep it at NI2 that is what it sounds like the 5ess is set at also. If you set yours for 5ess then you are really just setting it to the NI1 standard.

 

[Avaya911PLM]

Also VERY IMPORTANT if you change your protocols on a DCH (NI2 to ESS5, etc.) you MUST FDL (Force Download) the DCH to make sure the proper firmware is loaded onto the card. This applies to TMDI cards as well as DCH's provisioned on MSDL cards.

--
Fletch
Visit the Nortel Technical Support Portal at:

http://www.nortelnetworks.com/support

 

[ohno2]

Thanks for the feedback, I've confirmed with MCI that the correct setting is NI2 and could have used FDL rather than popping the card (doop). I'm now waiting for my next change window to change the PIN from 1 to 4 to see if that clears up the signaling.

 

[unkalary]

If the network is programed as NI2 protocol, you MUST have the pbx programed as NI2 also both on the DCHL and the RDB for the route programed on the T1. If it is not programed the same as the network, it will not work correctly and the DCHL wont stay up.