<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">This sounds like the Preboot Execution Environment (PXE) boot process. Overview here: <a href="https://en.wikipedia.org/wiki/Preboot_Execution_Environment" class="">https://en.wikipedia.org/wiki/Preboot_Execution_Environment</a><div class=""><br class=""></div><div class="">The simplified process is this:</div><blockquote class="" style="margin: 0px 0px 0px 40px; border: none; padding: 0px;"><div class="">client sends boots/dhcp request</div><div class="">dhcp server replies with address assignement and options - 60, 66 and 67 are most likely what you need</div><div class="">client uses TFTP to download boot image</div><div class="">client boots image</div></blockquote><div class=""><div class=""><br class="webkit-block-placeholder"></div><div class="">Option description here: <a href="https://www.experts-exchange.com/articles/2978/PXEClient-dhcp-options-60-66-and-67-what-are-they-for-Can-I-use-PXE-without-it.html" class="">https://www.experts-exchange.com/articles/2978/PXEClient-dhcp-options-60-66-and-67-what-are-they-for-Can-I-use-PXE-without-it.html</a></div><div class=""><br class=""></div><div class="">There are detailed descriptions for setup on various Linux distros - search for "{distro-name} PXE"</div><div class=""><br class="webkit-block-placeholder"></div><div class="">For Windows, you would set the options in your DHCP server. </div><div class=""><br class="">—<br class="">Otto Monnig</div><div class="">CTO</div><div class="">AtomAMPD, LLC</div></div><div class=""><br class=""><br class="">
</div>
<br class=""><div style=""><blockquote type="cite" class=""><div class="">On Jan 24, 2017, at 5:53 AM, jay binks <<a href="mailto:jaybinks@gmail.com" class="">jaybinks@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hey guys,<div class=""><br class=""></div><div class="">I have one particular Audiocodes Mediant 2000 SIP / ISDN gateway.</div><div class=""><br class=""></div><div class="">It seems that it doesn't have firmware on it, as it simply sits there sending BootP requests.</div><div class="">( found by watching packet captures from its ethernet )<br class=""><div class=""><div class=""><br class=""></div><div class="">Does anyone have any insight into the DHCP options AudioCodes require, to make these guys grab a new firmware via TFTP ?</div><div class=""><br class=""></div><div class="">I've got BootP responses going back to it, but for the life of me, I can not make it request anything over TFTP.</div><div class=""><br class=""></div><div class="">I have looked at trying the Audiocodes TFTP/Boop application, but the version I have won't run on any recent windows.</div><div class=""><br class=""></div><div class="">if anyone has the BootP application ( and how to make it run ), that would be great.</div><div class="">if you have any info on how to make the device grab a new firmware via standard DHCP / TFTP config that would also be brilliant.</div><div class=""><br class=""></div><div class="">On another note, the manual says this has a serial port.</div><div class="">does anyone know where to find this ?? :)</div><div class=""><br class=""></div>-- <br class=""><div class="gmail_signature" data-smartmail="gmail_signature">Sincerely<br class=""><br class="">Jay Binks</div>
</div></div></div>
_______________________________________________<br class="">VoiceOps mailing list<br class=""><a href="mailto:VoiceOps@voiceops.org" class="">VoiceOps@voiceops.org</a><br class="">https://puck.nether.net/mailman/listinfo/voiceops<br class=""></div></blockquote></div><br class=""></body></html>