PRI stops working when upgraded from 406 R4.2 to IP500v2 R9.0

[fakename05]

Customer has had an IP Office 406 running 4.2 software for years and they decided to upgrade to IP500v2 running R9.0 software. They are in a remote area and have a Verizon PRI. The old config shows the switch type as "5ESS". The central office is a DMS10. (The only way it would work on the old system is to configure it to be a "5ESS".)

When I installed the IP500v2 (all licenses and new hardware is in place and valid) the PRI acts like it is going to work and then if you watch System Status then all (or a couple of times 1 or 2) B-channels go from "Idle" to "Out of Service". If you unplug the PRI then they will go all go out of service. When you reconnect the line then they will flash "Idle" and then go back to "Out of Service".

We have been able to make a few calls but no incoming calls can come in and after a successful call is ended then no more calls can be made.

I talked to someone with Verizon and they show no problems with the D-channel. If I change the PRI switch type to "NI2" all of the channels will show to be "Idle" but you still can't make or receive calls. Changing the switch type to any other choice still results in the channels to appear as "Out of Service".

I'm not sure if it a problem with the hardware on the new system or if it is a software issue on R9.0.

I ended up switching back to the old hardware and downgrading the expansion unit back to the old software release and the PRI synched up immediately.

Unfortunately, this customer is 250 miles away. I'm not sure what steps to take next. I'm torn between seeing if R8.1 software would work but I'm not happy about having to pay to downgrade the software to a different release or changing out the hardware in case there is a problem with the PRI card.

Does anyone have any ideas?

 

[Mic5353]

Try changing the switch type till pri comes up.

 

[smokinjoe2938]

Did you enable the csu on the pri settings?

 

[fakename05]

Yes, the CSU is enabled and I did try changing the switch type to every possibility that was offered. (4ESS, 5ESS, NI2, DMS10) The only one that looked like it might work was NI2 but still no calls could be made.

Since I wrote the original post I have also downgraded the software from R9.0 to R8.1. We conducted a test today with the same results so I'm doubting it is software at this point. Perhaps the PRI card is defective. I'm a little skeptical because I've never had one that had any issues. However, I'm going to replace this card and see if there is any difference.

As I mentioned, the customer is very far away so my contact there is having to do some of the tech work as I monitor their system remotely. I was hoping it was a simple software glitch to try to avoid multiple trips.

 

[Ekster]

Have you checked the channels settings on the line?

By default they will be out of service, you need to put each one into service manually.



+++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++

 

[Telecomboy]

I had a client I upgraded and the PRI stopped working outbound (inbound did work). I had to put the following in the no user:

NI2_CALLED_PARTY_TYPE=UNKNOWN

You'll need to set your PRI to NI2 for this to work

 

[Telecomboy]

Some additional info: Mine was on an R8.1 not R9 so I have no idea if this will help, but it is worth a try. And your service provider should be set to NI2 as well.

 

[fakename05]

I did put them in service. That is why they showed "idle" temporarily while being reset.

I can put the statement in the no user setting to see if that helps.

The real issue is that they don't ever stay in service. Neither in-bound nor out-bound calls work. I have been able to place a few calls out right after the trunks are reset but they all go out of service within 30 seconds or so.

Telecomboy, were your channels in service? I have now downgraded to R8.1 but the results are the same.

I'm in the process of having the PRI card replaced but, since I've never had a bad PRI card, I'm not full of confidence about that.