Line errors

Started by .Griff., Sep 08, 2011, 15:31:21

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Lance

Hopefully though he will be able to tell you exactly what to say to the engineer! He sounds like a very useful person to know.
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Quote from: Lance on Sep 20, 2011, 22:35:57
Hopefully though he will be able to tell you exactly what to say to the engineer! He sounds like a very useful person to know.

He's been really helpful and a good mate.

That aside he also knows the pitfalls of, how shall I say, less "enthusiastic" Openreach engineers which is making me even more paranoid.

I'm now in a dilemma. Do I let the visit stand and risk someone turning up who runs a few basic tests and goes away saying there's no fault or hope an OR engineer, with the correct equipment, arrives and decides to take an interest.

Personally I believe I have more than enough evidence there's a fault either within my block or with the line leading into it but it's a gamble, financially too, which engineer turns up.

You only have to read Nialls extended thread to see some OR engineers differ in their approach to others.  :-\

Lance

Indeed. Are all engineers equipped equally? If not, maybe you could suggest particular checks using particular pieces of equipment which might surprise them but also reinforce you know what you are talking about and that if you say there is a fault there must be one. Just be careful not to lay it on too much as people don't always take too well to suggestions!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

Looks out of window for a white van... What are the chances he turns up at 5.59pm!

.Griff.

Well that didn't exactly go to plan but all is not lost.

As is ever so typical with BT none of the information had been passed onto the OR engineer so I had to explain all the relevant issues to him -

"the intermittent noise during calls, the CRC errors, the fact my neighbours (in the same block) also hear intermittent noise, the previous OR guys seeing errors on their "Hawk" "

He did a few basic checks and said OR had sent the wrong engineer and he had none of the relevant test equipment with him. He's arranging for another engineer to visit me who has the necessary equipment to diagnose the fault.

Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

No wonder BT keep increasing their charges, they have to meet the cost of all this incompetence and failure to communicate. :mad:
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

The BT agent I spoke to yesterday said  he'd call me "personally" between 5pm and 6pm today to see how the engineer visit went. Do you think he called? Did he #@%$...


Simon

Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Rik

BT speak with forked tongue. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

joe

griff,

finally got my act together and can join in!

Initial stats:-



After 86 mins:-



It appears to confirm what you already know!

.Griff.

Cheers Joe. Looking good! Any idea how long your copper run is?

As for me I've had a txt from BT this morning saying the fault is outstanding and advising me to visit the BT website for an update. The website in turn tells me the engineer will be with me shortly (yesterday) and hasn't been updated since.


joe

more than 250, less than 300 metres.

.Griff.

Quote from: joe on Sep 23, 2011, 18:18:33
more than 250, less than 300 metres.

Pretty much the same as me then. 300 metres according the OR engineer who originally installed it.

If you'd be kind enough to let me know your error count after 72 hours I'd appreciate it.

joe

griff,

my graphs:-




current status (21hrs 10mins):-



Will repeat at 72hrs (Monday lunchtime).


.Griff.

BT couldn't get much more incompetent!!  :mad:

I've just checked the "fault page" on their website (I've checked it multiple times each day) and it's just been updated to show an engineer will be attending at 8am on Tuesday morning.

No one has called me to arrange this, there's been no email(s) and there's been no txt's. If I hadn't checked their website multiple times each day I'd have had no idea of this visit and the engineer would have turned up with me at work.

:mad: :mad:

Rik

I doubt IDNet have been told yet, Griff. That's assuming he turns up, of course. ;)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

.Griff.

I'm not blaming Idnet at all. They've got nothing to do with this.

I'm sure the engineer will turn up.. However it will probably be the wrong one yet again!!

Rik

Toes crossed for you. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

joe

griff,

As requested, after 72 hrs:-


.Griff.

Thanks Joe.

7000 crc errors compared with 2million for me  :-\

Openreach are due here any minute now so I'll update this thread a little later.

zappaDPJ

zap
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

esh

Isn't it sad that no one is at all surprised by this? :(

Hope something comes of this. To be honest I had the exact same treatment from Verizon in the USA. Maybe it's just telecomms companies.
CompuServe 28.8k/33.6k 1994-1998, BT 56k 1998-2001, NTL Cable 512k 2001-2004, 2x F2S 1M 2004-2008, IDNet 8M 2008 - LLU 11M 2011

.Griff.

Looking out of the window every time I hear a vehicle pull up is fast losing it's appeal.  :(

Rik

The waiting game - something I've always hated. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.