Problems After 5.2.1 Upgrade

[joelatlincoln]

We use CM at our core and G450 w/8300's at our remote sites. We are having a weird issue where after the upgrade, the call path seems to be corrupted. The problem is intermittent. Sometimes callers cant hear the person on the other side but the person on the other side can hear them. Also, callers receive a busy signal when they are bounced to voicemail. We have also experienced issues with people trying to check their voicemail and getting a busy signal. The problem is intermittent but its making me crazy. When we performed the software upgrade, we also performed a needed firmware update in order to use 5.2.1.

Any help or ideas would be greatly appreciated.

 

[mojoputter]

So you also have the latest patches in th VM..?

 

[joelatlincoln]

We do have the latest patches on the MM. The problem with MM actually cleared.

The problem with dropping calls on the 450 still exists though. At this point Im thinking about swapping out the gateway with another 450. Something became corrupted when we went to 5.2.1 and Avaya hasnt been able to figure it out yet. We actually downgraded to 5.2 to see if that cleared the issue but it still exists.

 

[jimbojimbo]

Did you upgrade the gateways to the 30.xx.xx firmware? If you believe the firmware was somehow corrupt you might wnat to download the firmware again to the off line boot bank and then switch. Also verify the data switch and G450 are both locked down to 100/Full. I have upgraded several systems to 5.2.1 with G450 gateways and have not seen this specific problem.

 

[AvayaInstaller]

You will need to make sure that:
The CM patches match
Make sure to go into the 450 and lock down 100/full
Of course Firmware on 450

What set types are they, -IP?

 

[eatlog]

Are you using S8300B/S8300C/S8300D. Is this a stand-alone or an LSP.

 

[joelatlincoln]

Well, here is what we found. The 450 was setup incorrectly as a standalone system as opposed to an LSP. The patches seem to all be correct and we are at 4.5.1. After the system was correctly setup as an LSP and when the vendor turned off "ephemeral caching", the voice quality issues went away. Voice quality is much better for the past two days.