[VoiceOps] Broadsoft/AMS/Firmware woes
Max Mühlbronner
mm at 42com.com
Wed May 9 10:23:01 EDT 2012
Sounds interesting, so please share it to the community :P
BR.
Max M.
On 05/09/2012 03:03 PM, Tim Bray wrote:
> On 27/04/12 16:32, Robert Dawson wrote:
>> For everyone running AMS – what do you deal with all the Cisco firmware
>> peculiarities, reboot loops from incompatible firmwares, trying to
>> onboard phones that have old firmwares that need an interim upgrade,
>> etc. This is a highly manual process for us right now and a huge pain.
>>
>
>
> Not for Cisco.
>
> But for Snom we have a script which when given a target version, spits
> out the URL to the next version needed. We read the User Agent header
> to work out where the phone is now.
>
> It does all the intermediate steps and works with any kind of snom phone.
>
> So you can take a version 4 phone all the way through to version 8,
> via every step on the way. And do the bootloaders too.
>
> It also knows to only upgrade some phones at night, also has counted
> limits on how many phones to upgrade per day.
>
>
> It is just a script I wrote, but has 5 or 6 years of experience into it.
>
>
> Tim
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
--
Max Mühlbronner
42com Telecommunication GmbH
Straße der Pariser Kommune 12-16
10243 Berlin
E-Mail: mm at 42com.com
Web: www.42com.com
Firmenangaben/Company information:
Handelsregister/Commercial register: Amtsgericht Berlin HRB 99071 B
Umsatzsteuer-ID/VAT-ID: DE223812306
Geschäftsführer/CEO: Thomas Reinig, Alexander Reinig
Diese E-Mail enthält Informationen von 42com Telecommunication GmbH. Diese sind möglicherweise vertraulich und ausschließlich für den Adressaten bestimmt. Sollten Sie diese elektronische Nachricht irrtümlicherweise erhalten haben, so informieren Sie uns bitte unverzüglich telefonisch oder per E-Mail.
This message is intended only for the use of the individual or entity to which it is addressed. If you have received this message by mistake, please notify us immediately.
More information about the VoiceOps
mailing list