In reply to a post by Anonymous:

The next step after beta is the alpha or release version.

Cobblers.

Alpha => Beta => (Public Beta) => Release candidate => Final version.

Until the Service pack to fix the undiscovered bugs, anyway

BT speedtester is a load of tosh any way, never really been able to get a proper result off it, Just done 1 and it's come back as:-
Download speed achieved during the test was - 1Mbps IP Profile 77.43Mbps
Upload speed achieved during the test was - 16.38Mpbs IP Profile 20Mbps
The part I like is:-
We are unable to identify any performance problem with your services at this time.
Classic.
iechyd da

In reply to a post by paul1360:

BT speedtester is a load of tosh any way

Agreed, but afaik it's the only one they'll take any notice of

That's the silly part about it ISP's will only take notice and yet what would they say if I rang up would they look into it or take no performance problem's. lol crazy
iechyd da

In reply to a post by MrSaffron:

My day rate to re-write the page for them is fairly cheap these days

No doubt, but then BT would have to address customers' legitimate grievances or even admit that they might be at fault... and we can't have that

Edited by billford (Fri 27-Apr-12 11:25:01)

In reply to a post by Croftie:

The mods on the bt forum are adamant about the 10 day training period now aswell, they claim to have double checked it's existance and that most faults aren't accepted within the first 10 days:-

http://community.bt.com/t5/BT-Infinity/Bt-Infinity-u...
http://community.bt.com/t5/BT-Infinity/Speed-dropped...

I think this "10 day stabilisation period" claim is being used to allow time for any congestion to be alleviated. I've seen a few instances of people reporting slow speeds on the bt forums which have sorted themselves out by the end of the 10 days.

For what it's worth my line saw a drop in latency yesterday morning:

My Broadband Ping

The interesting thing is that my connection went live Monday the 16th and it was mid-morning before the engineer had finished faffing around. So that's ten days quite possibly to the hour. Now perhaps it's a coincidence but seems unlikely. Oh and as noted in another thread my upstream speed on TBB jumped up about 1Mb/s. Didn't change on the other testers I use but then they always reported it as higher than TBB. It now nearly brings TBB into the same ballpark.

Edited by Andrue (Fri 27-Apr-12 11:43:07)

In reply to a post by Bald_Eagle1:

FWIW, my ISP told me that yes, the 2 day DLM "training" period is indeed valid, but up to 10 days have to be allowed for the connection's MSR (Maximum Stable Rate) to be determined before "faults" can be reported.

First, your ISP has no choice but to repeat what brainwashed BT staff tell them. It does not make the BT statement correct. The BT documentation itself debunks the myth.

Second, in the case of ADSLx, it is true that the 10-day period establishes the MSR and hence the FTR. Nobody has ever disputed that. But there are many cases where there is a clear fault during that period, where an extremely low sync can occur, not just a feasible DLM line adjustment.

In such cases the fault needs to be corrected and the 10 days re-started. Otherwise the MSR and FTR are incorrect and the whole point of the 10-day period is negated. Hah - fat chance! (It does occasionally happen, but I think only with on-the-ball ISPs).

Third, in the case of FTTC, the MSR and FTR may be retained by BT Wholesale in their DLM, for ease of implementation similar to those described in my previous post, but they are totally irrelevant to the Openreach process line management system. The initial stabilisation takes place in the first couple of days, and that's all there is to it. If BT Wholesale continue, for some unkown reason, to want to wait 10 days before setting the MSR/FTR for admin purposes, then they should change the name to something like Line Assessment Period. Even in the two community threads linked to earlier they still say "stabilisation period". It simply, incontrovertibly. has nothing to do with stabilising anything.

In fact it contributes greatly to the destabilisation of customers' confidence in BT.

In reply to a post by RobertoS:

In fact it contributes greatly to the destabilisation of customers' confidence in BT.

I couldn't agree more.

It seems like BT OR should by now have issued a FTTC/VDSL2 "Myths & Legends" document to help us numpties actually understand (see through) the drivel that some CS agents read from a script.

BT OR should by now have issued a FTTC/VDSL2 "Myths & Legends" document

Wow hang on this is BT we are talking about and to do that would be to easy for them and that's 1 thing BT don't do "Easy", that's like Sky letting all android devices use sky go.
lol not going to happen
iechyd da

In reply to a post by Anonymous:

Nope in software development terms the gamma build is the first in house one where the code is put together and sees if it even works.

The next step after beta is the alpha or release version.

Did not know that. I always assumed 'alpha' was a pre-beta/internal release and my gamma comment was a poor attempt at humour.