|
|
A possibility too.
But nothing posted has made any of the areas a certainty.
If the noise environment has not changed at all, i.e. has been consistently noise in the ADSL2+ range, then the one bit that has changed is the jumpering at the exchange.
To be honest thats where i suspect the issue lays, but if they refuse to send out the correct engineers it wont be resolved will it.
|
|
|
In reply to a post by Anonymous: And for the second time you aint getting it until you show why its important. Which it isnt. If you have issue with that tough.
You're the one who is suppressing it meaning you think it's important, not me
|
|
|
An SFI will attend for maybe an hour, and unless the disconnects show up in that frame it is not likely to solve anything.
When did Be say they would continue looking at the issue, and escalate things? That is why the date of the correspondence is important, i.e was that six months ago or last week?
Do you understand what I am saying? An SFI is unlikely to find any issues if it is an intermittment to the point of only once every 24 or 48 hours the disconnects. Also Openreach may not want to even dispatch an SFI on the basis of a fault that is so infrequent.
Just because you were stable before with another ISP, does not mean there is a fault, you are now just experiencing DSL like most of the world does, i.e. the only minute or two where you lose connection once a day or every couple of days.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
In reply to a post by Anonymous: And for the second time you aint getting it until you show why its important. Which it isnt. If you have issue with that tough. You're the one who is suppressing it meaning you think it's important, not me 
Yep its important thats why its blanked out, but not important for the reasons your tiny mind thinks
|
|
|
In reply to a post by Anonymous: To be honest thats where i suspect the issue lays, but if they refuse to send out the correct engineers it wont be resolved will it.
It's quite obvious the OP thinks the issue is not his fault, that's why he doth protest so much
|
|
|
In reply to a post by Anonymous: In reply to a post by Anonymous: And for the second time you aint getting it until you show why its important. Which it isnt. If you have issue with that tough. You're the one who is suppressing it meaning you think it's important, not me 
Yep its important thats why its blanked out, but not important for the reasons your tiny mind thinks
As I said, you're the one who thinks it's important, not me
|
|
|
I agree, jumpering issues in the traditional sense are much more frequent disconnects. I am thinking perhaps it is now 3 inches of untwisted pair in the exchange, just picking up a little random noise that did not see it before.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
I agree, jumpering issues in the traditional sense are much more frequent disconnects. I am thinking perhaps it is now 3 inches of untwisted pair in the exchange, just picking up a little random noise that did not see it before. And I think the issue is the opposite end of the connection, in the customer premises
|
|
|
In reply to a post by Anonymous: To be honest thats where i suspect the issue lays, but if they refuse to send out the correct engineers it wont be resolved will it. It's quite obvious the OP thinks the issue is not his fault, that's why he doth protest so much 
it's looking that way
some people think there always right no matter how much you try to help
|
|
|
Without seeing a SNR margin plot that covers a number of hours I will hold off saying that
if the upstream noise margin is most variable, exchange end is more likely, if the downstream is the variable one then customer end or interference from a property nearby is the issue
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|