Avaya D100 SIP DECT Base Unit and D160 DECT Phone will not work on 8.1.79

[RodneyMcSnow]

I have been trying to get a Avaya D100 SIP DECT Base Unit and D160 DECT Phone to work on an IPOffice 500v2 with 8.1.79 firmware for the past several days and I have replaced the D100 and D160 twice.

The starnge thing is that I have 80-H323 phones and 7-SIP Polycoms working with no problem. I can Register new H323 and SIP Phones but the dang D100 Base Station does not want to work.

I have 29-spare Avaya IP Licenses, and since I can register new phones this makes no sense.

1) I have created the SIP DECT LINE and have tried both DHCP (from the IP Office) and Static.
2) I have created a SIP DECT Phone/User and associated Extension.
3) I am able to login to the WEB Page of the D100 and verify the settings.

The problem is that as soon as I connect the D100 Base Station to the System both Blue and Green lights fail to light up. I cannot access anything I have to go into Maintenance Mode on the D100 Base Station but as soon as the system reboots or I do a firmware upgrade the only way to regain access is by going into Maintenance Mode on the D100 Base Station.

I have made no progress on this. I even took the equipment and connected it to our DEMO KIT running 8.1.79 and the same thing occurs.

I have installed many of these units but for some reason this time I have nothing but issues.

Any help is appreciated.

 

[intrigrant]

Did you delete the D100.cfg file on the fileserver?
You can check the settings using a web browser and go to

http://<fileserver

ip address>/d100.cfg
If the contents shown starts with a line containing "autogenerated" then that is OK, when not then delete the file on the file server and check again.
That is a issue on 8.1

Did you enter the MAC address of the station in manager, if not do so although the manual states otherwise.
Check with systemstatus if the unit is recognized, it should show mac address and firmware version.

 

[critchey]

I am going to assume that the serial number for your D100 starts 16WZ or 17WZ. It seems like newer D100 bases do this on 8.1. I fought this issue myself. It seems like the base will not take 8.1 firmware without crapping out. If you try to force newer firmware (editing the d100.cfg I believe it was) the lights stay on but will not register. If you can get one of these to work let me know but I was unable to ever get one made in the past 2 years to ever work with R8.1. The same base worked on R9.0.12 and R9.1.9 without issue.

The truth is just an excuse for lack of imagination.

 

[RodneyMcSnow]

Since the base unit fails to respond each time after a reboot I have to put the unit into Maint Mode and start over to do a firmware upgrade, which it does but after the upgrade the unit d100 fails and locks up again.

It does show an "AUTOGENERATED" and all the info looks correct but the d100 WILL NOT WORK.

Yes, I did enter the MAC Address, and in the System Status Monitor it shows that the sytstem sees the d100, when I click on the d100 it shows the MAC ADDRESS and Market Unkown.

Yes, it does start with a 17xxx


Any other Help is appreciated.

 

[critchey]

I bet if you look at the logs for the D100 you see something about some setting with alloc in it set to high. This seems to be a R8.1 bug with newer D100 bases. I would be shocked if Avaya does anything to fix it since it is new hardware on no longer updated software.

*by no longer updated software I mean R8.1. Since it works on R9.0 and R9.1 (and I assumse R10) they have no reason to fix it.