Hi there,

Thanks for all the replies everyone. I can't tell you what happened because according the graphs it was around 9:50am that I suddenly jumped to 79995 kbps down and 19999 kbps up! Woohoo.

Anyway there we go - the village has FTTC 4 months ahead of schedule - and more importantly... I finally have a decent upload speed (I was always happy with my download speed, but 1260k upload was horrendous!)

https://s29.postimg.org/djqfn4qiv/rrd_dsync_6h.png

It's physically impossible to disconnect an electrical circuit from one location and connect it to another location without interrupting the flow of electrons.

That is incorrect. You've clearly never come across jumpering. The new cable is added to the existing and then the original cable cut and the current flows through the new cables to the new cab and then back again. The only point at which your service is likely to be cut is when the line is rerouted by the DSLAM in the AIO cab and even then should only be a momentary break.

Sorry but its you who is wrong !

Zarjaz (who i know) has done lots of jumpering (as i have) and he is 100% right when he says

"for most cab termination types to do this would be a physical impossibility anyway"

And the line will only be down for about 2 minutes anyway.

Seen mention of AIO cab a few times in this thread now - there is NO AIO cab here.
As per original post - a Fibre cabinet and a PCP cabinet were installed in November. Not a single AIO cab.

In any case - whether people are right or wrong - BT still deserve a huge amount of thanks - so anyone who works for them - reading this thread - Thanks! You guys are stars! (from everyone connected to ESGRE)

Both cabs: https://goo.gl/photos/YwDrAsoQxVTzhss96

Edited by deleted (Thu 12-Jan-17 21:34:00)

Nah, MCM is right. The jointers will cut in the AIO cab with 3M MS2 half tap modules so there will be no break in service.

The installer will cause a break when they connect the service up to the VDSL. Not because they have to, but because they haven't been trained how to.

They haven't been trained how to because of the tests they are obliged to do.

Edited by deleted (Thu 12-Jan-17 21:42:49)

In reply to a post by MC31:

Sorry but its you who is wrong !

Zarjaz (who i know) has done lots of jumpering (as i have) and he is 100% right when he says

"for most cab termination types to do this would be a physical impossibility anyway"

And the line will only be down for about 2 minutes anyway.

In which case you need to speak to the two guys who carried out the network rearrangement here when they wired/inserted the WRVAUX54 AIO cab into the EO bundle serving this development in July 2016 since they did this WITHOUT breaking a single one of the connections. Something that caused comment from several of the residents none of whom saw any down time on their router stats. Due to this being a community funded upgrade many of the residents took particular and close interest in the upgrade, hence their comments.

When the strowgers were updated it involved the new exchange wiring to be 'wedged' out on the internal side of the MDF and all circuits jumpered. When D Day came all the wedges had a piece of string on them and an almighty heave hoe ensued.

When the exchanges were going to be updated to 21cn the thinking was to wire everything to a plug and socket and literally unplug and plug in the new kit. They don't talk about 21cn much now.

As I said. they use half tap modules. No break ( apart from tea and lunch breaks )

Thank you. I'm not the one saying the links would have been broken since I know that in our case they were not as was confirmed to me at the time by the two guys that did the work and by a number of residents' router/modem logs that showed no breaks in service, not even just the two minutes mentioned elsewhere.

As I have already mentioned I'm referring to the "block" network rearrangement as part of the cab build stage rather than when individual users subsequently moved to an FTTC connection when breaks did occur.

I was the original poster and mentioned AIO, since thats what we have.. thats why perhaps AIO has been mentioned.