Good to know, even if I try to stay away from Polycom as much as I can.

On 2012-03-14, at 4:23 PM, Chris Chen wrote:

> Thanks Andre and Lloyd for your great ideas, actually Lloyd's "hold
> down 4, 6, 8, and *" trick to get into reset mode, then getting
> configuration from the DHCP/FTP provisioning server did the all
> required jobs.
> 
> Now the phone is back and I can setup the way I need, your great ideas
> is much cost effective than Polycom official support of around 300
> bucks for the repair.
> 
> TAUG rocks!
> 
> Please share this just in case somebody runs into this again in future.
> 
> Thanks,
> 
> Chris
> 
> 
> On Wed, Mar 14, 2012 at 3:42 PM, Andre Courchesne
> <[email protected]> wrote:
>> In PoE check your switch log, maybe it's going above the maximum power of 
>> the port. When in AC adapter mode, you have the right adapter for that 
>> device ?
>> 
>> Not sure if polycom supports this but you may want to have the phone send 
>> it's syslog to the asterisk server and see if you spot something there.
>> 
>> 
>> On 2012-03-14, at 9:21 AM, Chris Chen wrote:
>> 
>>> Hi fellow TAUGers, could any Polycom expert shed some light on how to
>>> resolve the following SoundPoint IP650 issue:
>>> 
>>>  The phone SoundPoint IP650 is connected to the LAN, with DHCP
>>> options 66 pointing to the local ftp server homing the firmware for
>>> the IP650. When the phone powers up (either by power adapter or POE
>>> switch), it never ends just keeping the cycle of restarting even after
>>> it loads the sip.ld and loading configurations locally etc, and not
>>> really connecting to the ftp server for either firmware or
>>> configuration files.
>>> 
>>> Thanks for sharing any idea to break this loop.
>>> 
>>> Chris
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to