Mitel PRI Card Firmware Crash

[Visegrip]

Hello all. I would greatly appreciate some advice on our Mitel SX2000Light.
Firmware version: 34.2.3.8_SP1
Mitel Universal T-1/PRI card. We are adding Cisco C.M. over link #1 setup as PRI/QSIG and this has been working correctly for several months as a test. We recently tried adding an outside T-1/PRI circuit for another long distance trunk on link #2 and have not had any luck getting the D-Channel to connect reliably w/ SDN's Nortel DMS500 switch. the D-Channel 'bounces' between 'in service' and 'lockout'. In the process we were led to believe that we needed to upgrade the software on the PRI card from 8.2.1.4 to 8.2.1.5, which I performed via IMAT version 7.5.1.2. This morning. Now the Card will not reload and be recognized by the MC. From what I've been able to find out, I'm assuming that my MC can't talk to the PRI card loaded w/ the new firmware. I need to take the firmware back to 8.2.1.4???? Thank you for your help..

 

[kwbMitel]

Things get very complicated when you try to run 2 different protocols on the same card. Although Mitel supports dual protocols, I have had numerous issues that have led me to believe that some protocols can be used but not others.

Best practice is to use different cards if you can.

Run it by a Mitel Engineer if you can't.


*******************************************************
If we don't take care of the customer, Maybe they'll stop bugging us.

 

[Visegrip]

Thank you, I wondered about that from the beginning but was assured by Mitel, through our rep that our configuration was OK. If that winds up being the case, then I'll have our LEC turn up the T1 provisioned w/ QSIG. Right now I'm sweating the fact that the Card is not recognized by the MC at all.

 

[Lundah]

If you connect to the serial port on the back of the DSU cabinet, watch the boot sequence of the PRI card, it should give you a good indication of what the problem is. I'm guessing either the firmware upgrade on the PRI card went south, or your IMAT Database is missing/corrupted.

 

[Lundah]

Also, if indeed the firmware upgrade didn't take on the PRI card (I've seen this happen a few times), there's a tech bulletin on MOL that outlines the procedure for re-flashing the card manually.