Did you mean Audiocodes BOOTP tool? - MM
On Tue, May 17, 2011 at 12:23, Matthew Kitchin (public/usenet) < [email protected]> wrote: > FYI, after de-bricking it with with the Polycom BOOTP tool, it took the > latest 5.8 fine. No more 6.x for me! > > > On 5/16/2011 7:24 PM, Todd Hodgen wrote: > > Can you run them on 5.8 or 5.6 and not mess with updating them to 6.0? > > > > Seems like an issue needs to be opened with Audiocodes. > > > > *From:* [email protected] [ > mailto:[email protected]<[email protected]>] > *On Behalf Of *Tony Graziano > *Sent:* Monday, May 16, 2011 4:44 PM > *To:* [email protected]; Discussion list for users of sipXecs > software > *Subject:* Re: [sipx-users] Slightly OT: Bricking Audiocodes MP114 > > > > I recall a lot of chatter a while back with the larger gateways and a bad > PS but what you are seeing is different. Ask me again why "I don't prefer AC > gateways...". > > > > To restore MP-11x to factory default settings, take these 3 steps: > 1. Disconnect the Ethernet cable from the device. > 2. With a paper clip or any other similar pointed object, press and hold > down the Reset > button (located on the rear panel) for about six seconds; the Fail LED > turns red and > the device restores to factory default settings. > 3. When the Fail LED turns off, reconnect the Ethernet cable to the device. > > On Mon, May 16, 2011 at 7:11 PM, Matthew Kitchin (usenet/public) < > [email protected]> wrote: > > I seem to have become an expert in bricking Audiocodes MP114s. I'm not an > expert with these. I deploy one per site as a backup line. That's about it. > The last 5 or so, I have flashed with firmware 6.x.24.x. Sorry for the > missing decimal places, I don't have the file handy. 5 or so in a row went > fine. Now, I am bricking about 66% of them during the upgrade process. They > take the firmware through the web interface, and then don't come back to > life. The fail light comes on. On all but 1 of these so far, we have been > able to bring them back to life with the Audiocodes BOOTP tool. I RMA'd the > one that wouldn't. I got a new one in today, and same thing. I got it back > to 5.4.x with the BOOTP method. I then tried 6.x.38.x through the gui. Dead > with the fail light again. I tried different browsers, direct connection > with a crossover cable, etc. Does someone know something I'm missing? I > noticed the manufacture date on the one I got in today is 11/09. Could that > matter? This is becomin > g a pain. > Thanks as always, > Matthew > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > > -- > ====================== > Tony Graziano, Manager > Telephone: 434.984.8430 > sip: [email protected] > Fax: 434.326.5325 > > Email: [email protected] > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > sip: [email protected] > > Helpdesk Contract Customers: > http://support.myitdepartment.net > > > > Blog: > > http://blog.myitdepartment.net > > > > Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 > > > ------------------------------ > > No virus found in this message. > Checked by AVG - www.avg.com > Version: 10.0.1375 / Virus Database: 1500/3641 - Release Date: 05/16/11 > > > _______________________________________________ > sipx-users mailing [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
