Possible problem with 16xx 1.31S firmware

[davis124]

Hello All -

I wanted to run this past the group and see if anyone else has seen this:

We just upgraded all of our 16xx IP Phones to the 1.31 load from support.avaya.com and from the inital testing all appears ok. We are running CM 5.2.

But as luck would have it, after a few days we ran into an issue with this firmware, in our enviorment we have 2 Audixes and depending on the extension will determine which voice mail the extension will go. On these phones, we utilize the Voice-Mail Number to make use of the Message button on the phone (For the user to call into voice mail), and again depending on which extension number it will be pointed to either one of our Audixes.

After the upgrade we noticed that people who were on the 2nd Audix, when they pressed the button they were being directed to the 1st Audix Hunt Group (Instead of the 2nd Audix Hunt group). The station form clearly shows we are directing the phone to the 2nd Audix. Our 46xxsettings file does have MSGNUM pointing to Audix 1 BUT again if we adminstered the CM Station form to point to Audix 2 then it would just call that hunt group instead.

So in a pinch we downgraded one of the phones to the older firmware of 1.3B and guess what, it started working as we expected.

So the question is, is the new firmware broke? OR was the old Firmware broke and the new firmware correct "An Issue"?

Anyone else run into this problem?
James

[davis124]

UPDATE - New problem with Firmware 1.32 (Upgraded from 1.31s)

Avaya has just released PCN 1822Pu (Release 1.32) for the 16xx IP Phones on May 1, 2012

This PCN somewhat "Fixes" the Voicemail button but in doing so it broke other features, like reading data from the 46xxsettings.txt file, specifically:

It will not read the value of MSGNUM

It does not read the value of PROCPSWD

Nor does it read the values of:

SET AGCHAND 0
SET AGCHEAD 0
SET AGCSPKR 0

IN FACT it's my observation it's not reading any values of the 46xxsetting.txt file.

My 16xx IP phones that are running 1.30B are working fine, will read the data from the 46xxsetting.txt file correctly AND allow for the functioning Voicemail button.

Can anyone from Avaya confirm this and/or duplicate this in their labs?

Thank you,

James

[vranjan]

Problem with Firmware 1.32 for 16xx phones (upgraded from 1.31s)

Hi Davis,

It looks like an in-depth investigation is required. We needs to replicate this one in our lab to understand the issue. I would suggest you to open a ticket with avaya as it would be difficult to address this one through forum.

You can open a ticket via new support site(support.avaya.com) by clicking on the service request tab and then filling out the necessary details.

Regard

Vikas

[davis124]

Update: Avaya had Developmental Firmware to address issue

After opening a case with Avaya they have created a Developmental load to address this issue. The load they have available (Through TIER III/IV) is:

1.359a

James