Received two new Polycom 500 phones. Dhcp and ftp configured properly to load the various files including v2.5.0 bootrom.ld, etc. One of the phones loaded all firmware and config files properly, registers with *, and is usable.
The second phone loads bootrom.ld (from the same ftp server on the same wire as the phone), but towards the end of the bootrom.ld load process (about 430 pkts as seen by a Sniffer) the phone display says "Downloading new bootrom" followed by "Error upadating bootrom!". I've refreshed the bootrom.ld file from the original to ensure it wasn't somehow damaged since the first phone was loaded (the file is 766,749 bytes). Still get the same error. (Never gets past loading the bootrom.ld, therefore the other associated files are never requested from the ftp server. The /var/log/message log contains: "Nov 23 07:11:05 phoenix vsftpd: warning: can't get client address: Bad file descriptor". That's really helpful.) The sniffer trace indicates a reliable ftp connection as the transfer involves three tcp packets followed by the phone ACK'ing those packets throughout the ftp download. (Eg, had the path been unreliable in any form, the tcp packet backoff mechanism would have dropped to one/two packets followed by an ACK.) Anyone seen such an issue? Maybe a bad phone? Anything else I should be looking at before returning the phone to the reseller for replacement? Rich _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
