Wait, because you�ll just stress yourself out trying to tell whom you feel should know.

Specify upon ordering that service required in building B .... (or whichever) and hopefully it�ll trigger a visit from a survey officer. Thrash it out with them.

If this doesn�t happen, then you�ll have to discuss with the installer... who will, if not feasible on the day, send the job for survey.

In reply to a post by Zarjaz:

Wait, because you�ll just stress yourself out trying to tell whom you feel should know.

Specify upon ordering that service required in building B .... (or whichever) and hopefully it�ll trigger a visit from a survey officer. Thrash it out with them.

If this doesn�t happen, then you�ll have to discuss with the installer... who will, if not feasible on the day, send the job for survey.

thanks, clear!

In reply to a post by Zarjaz:

The SASA is the bundle of 32 fibres �E sides� if such a thing existed on FTTP.

Each of the 32 goes to specific point/tray in the the head end at the exchange. If the fibre from the DP/CBT. has been misrouted to the wrong SASA then upon activation the ONT serial number input will never be �seen� by the head end and the whole thing just will not come into service.

PITA but sadly it does happen.

Guess what? The install happened today, and Dave B. did the install... flashing PON light! Apparently the wrong SASA... funny.. I sort of understand what he meant after your comment above! So the poor guy of the phone had to turn off sections to find out where we were connected on (we are the first to be connected today, tomorrow the 2nd on the street). Luckily Dave was pretty sussed and arranged an ID engineer (as you have said) to sort it out.... but Dave wasn�t happy.. he said it happens far too often that these are wrongly routed.

I also noticed that when they were installing the cable on the street and connecting them up. They needed to test it... because we had this �extra� CBT on our site, it was all missed. Seems like the job was a bit hushed to say the least. Anyway... let�s hope tomorrow it is all fine!

Oh dear ........

Yep, it is happening too frequently at present. Too many noobs out there in ID-land.

To me they ought to spend a couple of days out with an installer, this way they would have a better understanding of how it all fits together. The �old skool� bods were trained to do both, and then they split later ..... but then they all knew how it should be.

Good luck tomorrow.

In reply to a post by Zarjaz:

Oh dear ........

Yep, it is happening too frequently at present. Too many noobs out there in ID-land.

To me they ought to spend a couple of days out with an installer, this way they would have a better understanding of how it all fits together. The �old skool� bods were trained to do both, and then they split later ..... but then they all knew how it should be.

Good luck tomorrow.

Guess what, the fibre engineer came and the ID guys from Milton Keynes. They found that only us (with the special CBT on site) was connected to the wrong SASA, it took them a good 3 hours to connect it. Amazing how much time it cost... can't imagine that every fttp connection will require so much time! You will need a lot of BT engineers to get everyone on full fibre!

p.s the ID guys were also complaining about the crazy 95% goal last xmas. So many issues have come up since then they said!

So you are in service now ?

In reply to a post by Zarjaz:

So you are in service now ?

Yess!!!! Not sure about how constant the 300 mbps is.... I have done a few speed tests and it is difficult to get that speed. But it is easy to get the 50 upload. So yes..... very happy coming from a 4x 2.5 Mbps ASDL load balanding

Well done, waytago.

In reply to a post by FTTP2:

I have done a few speed tests and it is difficult to get that speed.

I've done some speed testing on gigabit (Cityfibre) connections. The key thing is to make sure you're on a direct, wired ethernet connection into your switch or router - not on wireless.

Even with that, sadly I've seen many Windows laptops only achieve 100-200Mbps, whereas a Mac or Linux laptop gets the full speed on the same connection.

It may be possible to tune Windows with the right drivers, but the point to remember is that it may be that your computer that's the bottleneck, not the link.

Aside: full speed on a gigabit link is actually about 942Mbps. That's what you get left for payload, after TCP/IP and ethernet headers have taken their toll. Seeing the dial crank up to 942 is pretty cool

In reply to a post by candlerb:

Even with that, sadly I've seen many Windows laptops only achieve 100-200Mbps, whereas a Mac or Linux laptop gets the full speed on the same connection.

It may be possible to tune Windows with the right drivers, but the point to remember is that it may be that your computer that's the bottleneck, not the link.

Aside: full speed on a gigabit link is actually about 942Mbps. That's what you get left for payload, after TCP/IP and ethernet headers have taken their toll. Seeing the dial crank up to 942 is pretty cool

It might be a hardware/chipset issue with the LAN port.Although gigabit, it sometimes can�t support gigabit transfers...only gigabit connection! (Yes... it is poor marketing/sales).

It is indeed extremely cool to see 100+ Mbps for us... a dream come true! But then again, not many servers out there support this max speed anyway! But we are a site with 50+ users, so it is great to have more bandwidth to play with.