DHCP and 1616 handsets knocking off other andsets

[m1kep]

Hello
I have a client who was getting DHCP Conflict error on new Avaya 1616 (6 off) handsets even though there are 100 ip addresses free on the range. I asked him to mute clear# the handsets and manually input the call server etc and try again. The 1616 handset logged on and was operational. He then did the same to another handset and when it came up, it knocked the other handset off! He has assured me that there is enough leases on the range and cannot understand it. Anyone else had this?

 

[gwebster]

Downgrade of 16xx H.323 phones to firmware 1.3.2 from 1.3.3 or 1.3.4B results in duplicate/default MAC address -

https://downloads.avaya.com/css/P8/documents/100178036

 

[gwebster]

From the PSN:

Replace 1.3.2 with 1.3.4D (GA - March 14th, 2014) or newer (Firmware 1.3.5 went GA on - April 7th, 2014) and upgrade unaffected phones immediately. Upgrading unaffected phones to one of these releases will prevent the duplicate MAC condition if downgraded to 1.3.2

Affected 1600 Series IP Deskphones downgraded from 1.3.3 or 1.3.4.B to 1.3.2 resulting in the defaulted/duplicated MAC address condition cannot be recovered in the field, and should be returned to Avaya under warranty, ideally within the first 90 days under the DOA process, for a free of charge replacement.