D160 wont connect

[redswine]

I have an IP500 running 9.0.3 software. 80 standard ip endpoint licenses and 12 virtual, I assume these are the ones that come with the VCM. Monitor shows I have 78 registered and 81 configured under the H323 phone status window. I installed 2 D160 phones with no problems at all. The customer liked them and ordered 2 more. I programmed these 2 identical to the first 2 and they won't connect to the IP Office. The IP Office is handing out IP addresses for the phone network, the base units are getting an ip address in the proper scheme and i can connect to it through the web browser. But it will not connect. The firmware is the same as the other ones. I have confirmed that the switch ports are vlan'd properly because the existing ones work in those ports. The monitor window shows all 4621 as phone types except for 3 unknown (i deleted one of the d160 phones and am trying to just get one working at a time), so i assume the 3 unknown are the D160's, they not only show unknown, but no license. So I'm assuming this is a licensing issue, I just don't know why.

As a test, I disconnected a regular ip phone and waited 10 minutes for the license to free up to test if it's I'm short licenses, and it still does not come up

TCC Telecom
Westminster, MD

Avaya IP Office & Partner, Nortel BCM & ICS, ESI

 

[redswine]

Additional info: the base unit when originally plugged in it takes about 5 seconds for the blue light to go solid, about another 10 seconds and the green light quickly flashes for about 3-4 seconds and then goes dark.

TCC Telecom
Westminster, MD

Avaya IP Office & Partner, Nortel BCM & ICS, ESI

 

[Telecomboy]

It's a D100 base issue. I had the same thing happen recently with an install. I replaced the d100 finally and that took care of the issue. They have put a stop sale on d100's as of now in the US. I don't think they are available again until the end of Sept while they fix the issue. If you bought it from a legit distributor call them and tell them the issue.

 

[Telecomboy]

FYI, the only way I was able to get the replacement to work was to set the IP address manually. DHCP would not work.