Adrian We are working on a fix and as usual you are entitled to your views - which we all know and love! I'm sure you'd be the first to raise it if we deployed a fix that causes other issues.
Neil. Sent from my iPhone > On 14 Jan 2014, at 09:40, "Adrian Kennard" <[email protected]> wrote: > >> On 14/01/14 09:20, Neil J. McRae wrote: >> Yes Adrian reported this to us after another ISP identified it also. OR and >> hauwei have been working with 4 providers very closely to pinpoint the >> issue and ensure it was the same root cause as symptoms had been different. >> >> We could of course rush out a fix and introduce more problems but given the >> disruptive nature of these updates and the risk of bricking the modem we >> want to ensure its seamless, feedback appreciated as always Adrian. > > Well, Huawei identified the exact issue that we reported. I agreed not > to go in to more detail with them (though did not sign an NDA, so that > is always an option). They also tested a simple "fix" to basically undo > the change that had introduced which caused the problem. It has been two > months - so I think I have been quite patient. > > However, as you are here, Neil. Can you confirm - have BT plc at least > stopped deploying this broken version of code to modems, or are you > currently, knowingly, breaking modems by updating to this version, still?
