1608 phones with matching MAC Addresses 2

[Pepp77]

We have a customer who has 5 x 1608 phones that are not connecting to the phone system. After much investigating we have discovered that all 5 are showing the same MAC address to the phone system, meaning that only 1 of them is able to work at any one time.

We have done the usual of clearing them and also upgrading them all to the latest firmware but nothing makes a difference.

I am thinking something went wrong when they were being built but the customer says they are from two different batches of phones they purchased at different times, but from the same supplier (not us!).

Anyone come across an issue like this before?

| ACSS SME |

 

[gwebster]

PSN004134u - Downgrade of 16xx H.323 phones to firmware 1.3.2 from 1.3.3 or 1.3.4 results in duplicate/default MAC and Serial Number

http://support.avaya.com/css/P8/documents/100178036

 

[Pepp77]

Perfect response - that is exactly the MAC address we are getting.

Have a star!

| ACSS SME |

 

[IPGuru]

So What happens if a 16XX needs replacing on an early version of IPO (V6.0 for example)
this is as bad as the 5410 upgrade fiasco

A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[amriddle01]

Avaya don't care about that IPGuru, it an unsupported release and they have already had and spent your money

 

[IPGuru]

Forgot to give Gwebster a *
we were caught by this one recently - system originally had V8.1.43

we have a large number of systems on this release & earlier so replacement handsets could prove quite an issue.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[tlpeter]

You could prevent this by uploading the newest files and upgrade all the phones.
This way they won't downgrade anymore.
But then you cannot downgrade them before you have the fix.


BAZINGA!

I'm not insane, my mother had me tested!

 

[IPGuru]

yes we could upgrade the affected system but this would mean visiting every site that might be affected

Not only would this tie up our engineering resources but would also require downtime for each customer as the phones upgrade.

will 1.3.3 firmware in the IP handsets even work on earlier systems ? if not they will need a firmware upgrade licence
& of course higher IP406DS units will not go beyond V6.1 anyway

We have nearly 3000 systems on record with at least 500 of them potential affected by this issue

upgrading 500+ sites is hardly an easy option, Thanks Avaya (Rant mode off)




A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[tlpeter]

I think that the firmware will work on older systems but as you know i cannot guarantee that

BAZINGA!

I'm not insane, my mother had me tested!

 

[amriddle01]

It's amazing how many of the hardware related "Accidents"/"Bugs" involve upgrading to the latest paid release to resolve

 

[ltxn]

Sorry to bump this thread.
I did some testing this week, after a few 16xx phones were returned because of this bug.

I tested with a phone that was on 1.3.3 and tried to connect it with a 7.0 (31) system, which expects 1.3.1 firmware.
The phone wouldn't downgrade.
When I connected the same phone with a 8.0 (46) system, the downgrade started immediately.
My conclusion was that firmware versions 1.3.3 and 1.3.4 allow a downgrade to 1.3.2, which cripples the phones, but not to a lower firmware version.
Hence the paragraph in the Avaya support notice:
[tt]Future Resolution – There will be a future software version released to Avaya Support website that prevents the downgrade of any phone 1.3.3 or newer to 1.3.2. Release Date TBD.[/tt]

I found firmware 1.3.2 in following releases:
8.0 (46), 8.0 (51), 8.0 (53), 8.0 (56)
8.1 (52), 8.1 (65), 8.1 (67)
Beware if you want to install a 16xx phone on these releases.

The only solution I see for now is to either upgrade the systems to the latest maintenance release 8.0 (66) & 8.1 (81) or to delete the 1.3.2 firmware files from the fileserver.

 

[IPGuru]

did your V7.0 system have a file server active?
i suspect not which would be why the phone survived.
Deleting the 1.3.2 & earlier bin files is certainly a worth while precaution.


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear