This sounds like the Preboot Execution Environment (PXE) boot process. Overview here: https://en.wikipedia.org/wiki/Preboot_Execution_Environment <https://en.wikipedia.org/wiki/Preboot_Execution_Environment> The simplified process is this: client sends boots/dhcp request dhcp server replies with address assignement and options - 60, 66 and 67 are most likely what you need client uses TFTP to download boot image client boots image Option description here: https://www.experts-exchange.com/articles/2978/PXEClient-dhcp-options-60-66-... <https://www.experts-exchange.com/articles/2978/PXEClient-dhcp-options-60-66-...> There are detailed descriptions for setup on various Linux distros - search for "{distro-name} PXE" For Windows, you would set the options in your DHCP server. ? Otto Monnig CTO AtomAMPD, LLC
On Jan 24, 2017, at 5:53 AM, jay binks <jaybinks at gmail.com> wrote:
Hey guys,
I have one particular Audiocodes Mediant 2000 SIP / ISDN gateway.
It seems that it doesn't have firmware on it, as it simply sits there sending BootP requests. ( found by watching packet captures from its ethernet )
Does anyone have any insight into the DHCP options AudioCodes require, to make these guys grab a new firmware via TFTP ?
I've got BootP responses going back to it, but for the life of me, I can not make it request anything over TFTP.
I have looked at trying the Audiocodes TFTP/Boop application, but the version I have won't run on any recent windows.
if anyone has the BootP application ( and how to make it run ), that would be great. 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.
On another note, the manual says this has a serial port. does anyone know where to find this ?? :)
-- Sincerely
Jay Binks _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops