9608 phones stuck at "Discover"

[BDaglian]

I am working on an installation with 9608 phones. The IP Office is on release 8.1(52). I am using my laptop as the HTTP server for now (it is a UCM, so no voicemail server). The customer's DHCP server has been loaded with Option 242 MCIPADD=<IP OFFICE IP>,MCPORT=1719,HTTPSRVR=<MY LAPTOP IP>. There are no vlans on this network, everything is on the same subnet. When I boot the phone, it grabs an IP, downloads firmware files, but then fails to "Discover <IP OFFICE IP>". I can ping the IP Office from my laptop (connected via the network) so I know the IP Office is on the network. The phone is getting a valid IP address on the same subnet. Any thoughts?

 

[mforrence]

Try configuring the phone with static IP info to determine if trouble is phone/network/DHCP info. Should take all of 90 seconds to change.

 

[BDaglian]

Thanks, I tried that already. I do not believe it is a DHCP issue. The phone boots up with a valid IP address, the correct call server address, and the correct HTTP server address. It also gets the correct gateway, subnet, etc. It has already downloaded firmware and gone through the upgrade process. I can ping the phone from my laptop, and I can ping the IP Office from my laptop.

 

[Hovus]

IP Route created in the IPO?

I have dreamed a dream, but now that dream has gone from me.

 

[BDaglian]

Problem solved. Customer gave me an IP address for the IP Office that was assigned to another device. Thanks anyway for your help.

 

[amriddle01]

Yeah, customers do this, I have gotten into the habit of pinging any address the customer gives


Avaya Implementation Qualified Professional Specialist Technical Engineer (AIQPSTE)

 

[BDaglian]

That will be my policy too, moving forward

 

[tlpeter]

That is no garanty as Windows 7 and server 2008 do not reply on ping by default.
Better is to run a scan with for example angry IP scanner.
This will show used IP addresses.


BAZINGA!

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