Apr 15
    2009

    4690 IP Polycom Phone Not Booting Up After Outage

    Al Keel
    [Subscriber Members]
    We had a power outage last Friday that caused everything to reboot. Everything came up except our 4690s IP Polycom phones. For some reason all the 4690s are getting an IP address (10.0.12.63) that is not within our subnet ranges. We thought maybe that's a default IP, but Avaya said No. We are running QIP as our DHCP. We've checked all the settings and they are correct, i.e. call server, dns, router, etc.. Does anybody know what the problem may be?

    I am running CM 3.1. Firmware on the polycoms are 2.5. QIP version 6.2 Rel 48 (Win2K)
    Jim Bennett
    [DFCU Financial]
    Check your internal PBX ip addresses and network regions. We had something similar and we had to change the network region of an incidental ip adress. Do a "display ip-network-map" and see if you get anywhere from there!

    Perhaps someone out there with better understanding of this topic could add more -- I had a tech make the change, so I don't fully understand the topic.
    Steven Schafetz
    [Federal Reserve System]
    Maybe someone is running a ghost DHCP server somewhere? I would try to get a packet capture to look at the DHCP discover and see if the DHCP reply is your QIP platform or somewhere else.
    Al Keel
    [Subscriber Members]
    Well, I think I may have found the problem but not the solution. DHCP Packet can only handle up to 576 bytes for 4690s. We have so many applications running that it's hard to cut down the bytes to be below 576. Any suggestions?
    bart sikkes
    [Subscriber Members]
    i assume you mean that the 4690 can't handle dhcp packets larger then 576 bytes? could you perhaps place them in a seperate scope with less extra options configured?
    Al Keel
    [Subscriber Members]
    Yes, thanks for catching that. I will give it a try.
    Al Keel
    [Subscriber Members]
    Our first thought was the size limit of DHCP, but after doing several tests we found it may be something else.

    We've recently added Wyse on to our DHCP Packet with 4 tags, 161, 162, 184, and 185. We found the 4690 boots up when we removed the 184 tag from the DHCP and gives a "No VLAN" when it's added. Anybody ran into this issue and know of any fixes?
    bart sikkes
    [Subscriber Members]
    running latest firmware on the 4690? a work around would be again running them in a seperate dhcp scope without the wyse options.
    Inactive Forum User
    [Subscriber Members]
    Hi,

    My IP Phone 4610 is going into call server discovered mode,what have to do ?
    bart sikkes
    [Subscriber Members]
    My IP Phone 4610 is going into call server discovered mode,what have to do ?
    first time on a forum? please don't hijack a thread on a different subject but start a new one for a new subject.

    have you tried clearing the values for the phone? press hold and then 25327#
    Tammy Wysocki
    [Subscriber Members]
    We have a 46 Polycom set. While trying to get this on line we did the following which notes indicated that if he DOWNGRADES DIRECTLY FROM R2.3 to R1.7.7 –THIS RENDERS THE SET USELESS! Instead, you can downgrade from R2.3 to R2.0 and then to R1.7.7

    Is there anyway to reverse this? The phone is dead.
    Sheila Seidel Clark, NA
    [Great-West Financial]
    4690's must be hardcoded on the switch port. Do you know this has been done?
    Robert Holmes
    [Subscriber Members]
    4690's must be hardcoded on the switch port. Do you know this has been done?

    What do you mean? I don't think this is true.
    Mien Tien
    [Subscriber Members]
    Any one show me the link that I can down load version 1.7.7 of IP phone 4690

    Tien Mien

    //////////////////////////
    We have a 46 Polycom set. While trying to get this on line we did the following which notes indicated that if he DOWNGRADES DIRECTLY FROM R2.3 to R1.7.7 –THIS RENDERS THE SET USELESS! Instead, you can downgrade from R2.3 to R2.0 and then to R1.7.7

    Is there anyway to reverse this? The phone is dead.
    Neil Miller
    [Subscriber Members]
    I had the same issue where 4690's would boot and pickup an IP address of 10.0.12.63. The problem was in the scope option 176 with a typing mistake at the end oe the string options, our scope read L2QUD=5,L2QSIG=3. The scope should have read L2QAUD=5,L2QSIG=3 so basically the A was missing!!!
    Bill Brewer
    [Subscriber Members]
    We thought maybe that's a default IP, but Avaya said No.

    I suspect that's not entirely accurate - since I've got 2 4690's that are in a rolling reboot with the same 10.0.12.63 when you interrupt with *. The only problem is I haven't figured out how to reset the phones to factory settings - the MUTE 73738# only works once the phone has come up. Tried * then zeroing all values - but they keep coming back with 10.0.12.63.
    Jeff Ray
    [Subscriber Members]
    I have the same exact problem, getting the very same IP on the 4690. Can't get the phone booted fully, so can't enter the reset code.

    Did anyone come up with a solution for this?

    Thanks.

    All Times America/New_York


    Copyright © '.date("Y").'The International Avaya User Group. All Rights Reserved

    All material, files, logos and tradarks within this site are properties of their respective organizations.


    Terms of Service - Privacy Policy - Contact