|
|
I'm out of my line testing period and now have the following stats with the brightbox:
Broadband Type: ADSL
Broadband State: Connected
Internet State: Connected
Time Connected: 1 day 01:22:10
Downstream Rate: 3068kbps
Upstream Rate: 444kbps
| Text | 1
23
45
67
89
1011
12 | Status:
Configured Current
Line Status --- SHOWTIMELink Type --- Interleaved Path
Operation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate Information:
Stream Type Actual Data RateUpstream 444 (Kbps.)
Downstream 3068 (Kbps.) |
| Text | 1
23
| Operation Data Upstream Downstream
Noise Margin 7.9 dB 3.8 dBLine Attenuation 20.7 dB 34.0 dB |
| Text | 1
23
45
67
89
10 | Indicator Name Near End Indicator Far End Indicator
Output Power 10.1 dBm 0.0 dBmFast Path FEC Correction NA NA
Interleaved Path 53790991 0Fast Path CRC Error NA NA
Interleaved Path CRC Error 1167 0Loss of Signal Defect 0 0
Fast Path HEC Error STR NA NAInterleaved Path HEC Error 1176 0
Error Seconds 1054 0 |
Should i be expecting more with these stats, or is this what i'm stuck with?
I'm connected to the test socket at the master socket and the phone is disconnected.
Here's the exchange information: http://www.samknows.com/broadband/exchange/MYIDL
The exchange is ~1.4 miles by road and ~0.9 miles as the crow flies.
EDIT: Added extra information.
Edited by deleted (Wed 12-Sep-12 16:25:08)
|
|
|
Yes expecting a lot more.
http://www.coolwebhome.co.uk/calc/calculator.php suggests 11 to 14Meg for the attenuation.
The 444 Kbps upstream suggests this is probably a 21CN WBC service that has had a manual profile applied, i.e. Orange support need to reset the line profile.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
You left out this bit Status:
Configured Current
Line Status --- SHOWTIME
Link Type --- Fast Path
Operation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate Information:
Stream Type Actual Data Rate
Upstream 1179 (Kbps.)
Downstream 19495 (Kbps.) while I think about it,
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
On the Downstream you should be getting over 13 Meg Sync speed but Orange are not constraining it as has happened to others. So it's time to look at your wiring. Usually I'd suggest removing the ring wire, but you say you are connected to test socket. Even so, are there any extensions bypassing the faceplate but connected to the fixed box?
On the Upstream you should be getting about 1 Meg Sync speed but it looks as if Orange are applying a 20 CN profile (Sync = 444K) as has happened to others. But 1st give it a few days to improve.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
As far as I can tell there are no extensions in the house, there's only one telephone socket.
This is the inside of the socket:
Socket
I'll post back in this thread in a couple of days with any changes.
|
|
|
As far as I can tell there are no extensions in the house, there's only one telephone socket.
This is the inside of the socket:
Socket
I'll post back in this thread in a couple of days with any changes.
Looks like everythings OK at the back of the NTE5 - have you also tried different filters and/or filtered faceplate?
|
|
|
|
I have a number of different filters, I can try them out but was wondering if I should wait a couple of days before trying anything else as XRaySpeX suggested.
|
|
|
I have a number of different filters, I can try them out but was wondering if I should wait a couple of days before trying anything else as XRaySpeX suggested.
Sure do as XRaySpeX suggests first
|
|
|
Odds on Orange has screwed up
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
...but a 3068Kbps downstream sync?
|
|
|
If its WBC all manner of odd sync steps are possible
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
If its WBC all manner of odd sync steps are possible
Oh! Right
|
|
|
...but a 3068Kbps downstream sync? With a 3.8 dB NM?
We've seen similar but with a 15 or 18 dB NM!
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
I'm back! Had one disconnect since my last post and it immediately reconnected at exactly the same speed, current stats are:
| Text | 1
23
45
6 | Broadband Type: ADSL
Broadband State: ConnectedInternet State: Connected
Time Connected: 1 day 17:08:04Downstream Rate: 3070kbps
Upstream Rate: 444kbps |
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
24 | Line Status --- SHOWTIME
Link Type --- Interleaved PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate Information:
Stream Type Actual Data RateUpstream 444 (Kbps.)
Downstream 3070 (Kbps.)
Defect/Failure Indication:Operation Data Upstream Downstream
Noise Margin 17.5 dB 7.3 dBLine Attenuation 20.1 dB 33.5 dB
Indicator Name Near End Indicator Far End Indicator
Output Power 10.1 dBm 0.0 dBmFast Path FEC Correction NA NA
Interleaved Path FEC Correction 3736694836 0Fast Path CRC Error NA NA
Interleaved Path CRC Error 82 1Loss of Signal Defect 2 0
Fast Path HEC Error STR NA NAInterleaved Path HEC Error 329 0
Error Seconds 2516 5 |
Over the past couple of days the line attenuation has remained the same and noise margin has varied by no more than 2dB.
Is it time to start trying to talk to Orange? If so what should i say?
EDIT: I also tried setting the modem mode to ADSL2 through one of the hidden router pages but that resulted in the same connection speed.
Edited by deleted (Sat 15-Sep-12 23:29:26)
|
|
|
Yes talk to Orange. Automatic system has probably been overriden by them at some point.
You need to point out that the line is under 3km long and only syncing at 3Meg when using the test socket, and appears to be a fixed speed profile. Can they alter the banded profile to allow a higher profile, or let the DLM system free-run and find its own sweet point.
Oddly Orange lines suffer this problem more than any other provider, suggesting there is someone on their team who thinks slow syncs are a good thing, and why they often show up with slower speeds on Ofcom testing
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
I just got off the phone with them, and after having to reset my router to defaults (so glad you can backup config) the lady said she would place a 'reset' on my line that will take 24-48 hours from Monday. So i guess we'll see what happens.
Thanks for your help.
|
|
|
It looks like my upload speeds have been improved, unfortunately nothing has been done to my download speeds. BT speed tester says my IP profile is 2.7 Mbps. Current stats:
Connected for: 07:21:28
| Text | 1
23
| Line Status --- SHOWTIME
Link Type --- Interleaved PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+) |
| Text | 1
23
45
67
8 | Stream Type Actual Data Rate
Upstream 809 (Kbps.)Downstream 3068 (Kbps.)
Defect/Failure Indication:
Operation Data Upstream DownstreamNoise Margin 7.3 dB 11.2 dB
Line Attenuation 20.4 dB 34.0 dB |
| Text | 1
23
45
67
89
10 | Indicator Name Near End Indicator Far End Indicator
Output Power 10.1 dBm 0.0 dBmFast Path FEC Correction NA NA
Interleaved Path FEC Correction 19502 75Fast Path CRC Error NA NA
Interleaved Path CRC Error 24 0Loss of Signal Defect 3 0
Fast Path HEC Error STR NA NAInterleaved Path HEC Error 43 0
Error Seconds 118 0 |
EDIT: Requested info added.
Edited by deleted (Tue 18-Sep-12 15:10:09)
|
|
|
Please show these lines as well: | Text | 1
23
45
67
89
1011
1213
1415
16 | Line Status --- SHOWTIME
Link Type --- Interleaved PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+)
...
Indicator Name Near End Indicator Far End Indicator
Output Power 10.1 dBm 0.0 dBmFast Path FEC Correction NA NA
Interleaved Path FEC Correction 3736694836 0Fast Path CRC Error NA NA
Interleaved Path CRC Error 82 1Loss of Signal Defect 2 0
Fast Path HEC Error STR NA NAInterleaved Path HEC Error 329 0
Error Seconds 2516 5 |
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
|
Looks like all that Orange have done is uncap the upstream sync - yet downstream sync is about the same although the downstream SNRM is larger.
|
|
|
Looks like all that Orange have done is uncap the upstream sync - yet downstream sync is about the same although the downstream SNRM is larger.
Is the SNRM being larger better?
(Extra info. added to my previous post)
|
|
|
Is the SNRM being larger better?
It should improve stability but not speed.
Possibly time to get back to Orange about this since your downstream sync is very poor with a 34dB attenuation and an adsl2+ connection.
|
|
|
|
Just spoken to them on the phone, they said that there was a problem with the line test (an exclamation mark) which meant it could be a problem with the line or something in the house. The fault has been escalated to another team who can get in touch with Openreach, so now i have to wait to see if I will get a call.
|
|
|
Just spoken to them on the phone, they said that there was a problem with the line test (an exclamation mark) which meant it could be a problem with the line or something in the house. The fault has been escalated to another team who can get in touch with Openreach, so now i have to wait to see if I will get a call.
I guess you still have the router connected to the NTE5 test socket?
|
|
|
|
The router is still in the test socket.
|
|
|
As far as I can tell there are no extensions in the house, there's only one telephone socket.
This is the inside of the socket:
Socket
I'll post back in this thread in a couple of days with any changes.
Looks like everythings OK at the back of the NTE5 - have you also tried different filters and/or filtered faceplate?
Are you insane? Thats not even got a test socket inside it... its empty just a front plate on with no SPLIT faceplate. This is an obsolette master socket, likely one with a T in a circle or a non-split BT socket with the piper man logo. I can't quite tell from the angles there but it looks like an LJU (just an extention plate as its quite thin and the socket itself recesses into the wall).
Whats more it looks like theres a lot of matter inside the socket walling (dead insects flies or dust etc) which have caused issues before especially if they are in contact with any of the wiring or circuitry. Whats more is if this is indeed the master socket or only socket in the property it still probably has a functional ringer wire, these are no longer needed as they used to work with older phones to make them ring now all they are useful for is sending interference down your telephone line into your modem.
Basically that socket needs replacing with either a modern openreach socket or an already filtered faceplate - this will require a broadband engineer from your provider.
|
|
|
It is you who is mad, if you insist on rudeness  !
That is the backplate of a NTE5 Master with the faceplate removed and out of sight.
It is the top one of these: http://www.kitz.co.uk/adsl/btsockets.htm with the guts in green instead of white.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
|
The only part you are allowed to remove as a customer is the bottom faceplate cover, not anything else otherwise BT can and will charge for a replacement due to tampering.
It should still not have that level of matter inside the socket therefore further compounding the tampering theory.
Apologise if it sounded rude however what I believed I was looking at was not a master due to the thickness of the plate hanging down and the backplatings position inside the wall.
Regardless the first two observations in this post stand, if a BT engineer comes out and sees that muck and that hanging off he will have to charge for a replacement due to suspected tampering.
Which is something to avoid!
|
|
|
The only part you are allowed to remove as a customer is the bottom faceplate cover, not anything else otherwise BT can and will charge for a replacement due to tampering. So what! I removed nothing and it's already been done! My observation still stand regardless.
EDIT: There is still no reason to be rude even when you think you disagree with a post
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
Edited by XRaySpeX (Wed 19-Sep-12 14:54:09)
|
|
|
The only part you are allowed to remove as a customer is the bottom faceplate cover, not anything else otherwise BT can and will charge for a replacement due to tampering. So what! I removed nothing and it's already been done! My observation still stand regardless.
Never said you did remove it, but that should have been pointed out to the original poster incase he's arranged an engineer in the interim so he can avoid being charged!
I'm not going to argue with you on an internet thread, I apologise for being rude however what I was looking at looked incredulous to me. I'm not going to debate this with you so if you want to carry this into other threads I will no longer be replying to it and will continue to assist other users.
|
|
|
Then learn to press the correct Reply button.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
|
Beardedwonder,
I really suggest that you clean up the inside of that backplate and re-attach the central layer to the backplate before any further engineer visit. Apologies to you for the argument in this thread. Its probably something you've been told to do and if its questioned by any engineers that are despatched that'll have to be your excuse!
|
|
|
Are you doing this deliberately?
http://forums.thinkbroadband.com/freeserve/t/4158336...
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
Clean up what?
The dust looks like the usual you get when fitting the socket to the wall. If it was insect and cobweb then I'd expect to see more on other flat surfaces, e.g. top of the gree section and the contact areas which look pretty good really.
I suggest a look inside some the external boxes when engineers have them open to see the amount of wildlife that makes home in them.
General advice is NOT to remove faceplate from wall to this extent due to the risk of being charged if you break something, but I have NEVER seen someone getting charged for having a dirty back box to the master socket. In the case of water ingress from damp possibly, but no sign of that in the socket.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Clean up what?
The dust looks like the usual you get when fitting the socket to the wall. If it was insect and cobweb then I'd expect to see more on other flat surfaces, e.g. top of the gree section and the contact areas which look pretty good really.
I suggest a look inside some the external boxes when engineers have them open to see the amount of wildlife that makes home in them.
General advice is NOT to remove faceplate from wall to this extent due to the risk of being charged if you break something, but I have NEVER seen someone getting charged for having a dirty back box to the master socket. In the case of water ingress from damp possibly, but no sign of that in the socket.
Agreed on the fact of removing the faceplate from the wall to this extent, as I have seen someone get charged. My point is that on first glance if there is dust there, then there is a way for more to get in i.e; some form of exposure to external elements.
Maybe I am being over-critical, I just wanted to save the OP from a potentially costly experience!
|
|
|
End user is allowed to remove the face plate which leaves a nice hole for the entry of dust, so dust presence is not defacto evidence of tampering.
If BT ever tried that, rather than people think they might, then I would ensure the issue was taken up with CEO
For all you know that dust is present from when socket was put on the wall, and having seen inside a few sockets in my lifetime that would be my conclusion.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
End user is allowed to remove the face plate which leaves a nice hole for the entry of dust, so dust presence is not defacto evidence of tampering.
If BT ever tried that, rather than people think they might, then I would ensure the issue was taken up with CEO
For all you know that dust is present from when socket was put on the wall, and having seen inside a few sockets in my lifetime that would be my conclusion.
Thats a fair enough point, I just have my own experiences in having worked for an ADSL provider previously...
|
|
|
...I just have my own experiences in having worked for an ADSL provider previously...
Phew! Thought I'd misidentified a NTE5 for a minute or two there
|
|
|
...I just have my own experiences in having worked for an ADSL provider previously...
Phew! Thought I'd misidentified a NTE5 for a minute or two there 
lol, to be fair my eyes shouldn't have been looking at the inner plate hanging down from a backplate like that, hence the confusion
|
|
|
...I just have my own experiences in having worked for an ADSL provider previously...
Phew! Thought I'd misidentified a NTE5 for a minute or two there 
lol, to be fair my eyes shouldn't have been looking at the inner plate hanging down from a backplate like that, hence the confusion 
No problem - it's an old type, note the brass threaded holes that take the threaded screws for holding the faceplate in position. More modern NTE5's use self taping screws for attaching the faceplate. It can be a problem fitting filtered faceplates to old NTE5's with the supplied self taping screws or if one doesn't have threaded screws that are long enough.
Agreed the OP shouldn't really have tampered with the NTE5 but what's done is done
|
|
|
... nested quotes trimmed ...
Phew! Thought I'd misidentified a NTE5 for a minute or two there 
lol, to be fair my eyes shouldn't have been looking at the inner plate hanging down from a backplate like that, hence the confusion 
No problem - it's an old type, note the brass threaded holes that take the threaded screws for holding the faceplate in position. More modern NTE5's use self taping screws for attaching the faceplate. It can be a problem fitting filtered faceplates to old NTE5's with the supplied self taping screws or if one doesn't have threaded screws that are long enough.
Agreed the OP shouldn't really have tampered with the NTE5 but what's done is done 
Even if that is a more modern socket than I first realised on a quick glimpse of it, there still is potential for that to be upgraded to an NTE5a or an SSFP which should offer better common mode noise protection than the old standard NTE5.
|
|
|
Even if that is a more modern socket than I first realised on a quick glimpse of it, there still is potential for that to be upgraded to an NTE5a...should offer better common mode noise protection than the old standard NTE5.
Maybe the old ones are better than the new ones?
|
|
|
lol maybe the copper and in some cases aluminium lines aren't meant for broadband?  We could debate this stuff all day
Edited by deleted (Wed 19-Sep-12 16:34:19)
|
|
|
lol maybe the copper and in some cases aluminium lines aren't meant for broadband? We could debate this stuff all day 
Sure - over and out.
|
|
|
Even if that is a more modern socket than I first realised on a quick glimpse of it, there still is potential for that to be upgraded to an NTE5a or an SSFP which should offer better common mode noise protection than the old standard NTE5. Where you went wrong when you first looked at it was in not realising it is hanging sideways. The top is at the right, and on the left you can see where the faceplate fits onto it.
FYI the NTE5 is the part that screws to the wall, including the part hanging down in the picture. An "NTE5" has never been a complete assembly.
An NTE5A is a single phone socket faceplate to fit to an NTE5, as opposed to SSFPs or an NTE5B. The latter being a faceplate with no socket, for use where the NTE5 is, for example, installed in a loft with no use of it for a phone being envisaged.
My broadband basic info/help site - www.robertos.me.uk
Domains,website and mail hosting - Tsohost. Connection - Plusnet Extra Fibre (FTTC). Sync ~ 56.0/13.9Mbps @ 600m.
"Where talent is a dwarf, self-esteem is a giant." - Jean-Antoine Petit-Senn.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Allergy information: This post was manufactured in an environment where nuts are present. It may include traces of understatement, litotes and humour.
|
|
|
Even if that is a more modern socket than I first realised on a quick glimpse of it, there still is potential for that to be upgraded to an NTE5a or an SSFP which should offer better common mode noise protection than the old standard NTE5. Where you went wrong when you first looked at it was in not realising it is hanging sideways. The top is at the right, and on the left you can see where the faceplate fits onto it.
FYI the NTE5 is the part that screws to the wall, including the part hanging down in the picture. An "NTE5" has never been a complete assembly.
An NTE5A is a single phone socket faceplate to fit to an NTE5, as opposed to SSFPs or an NTE5B. The latter being a faceplate with no socket, for use where the NTE5 is, for example, installed in a loft with no use of it for a phone being envisaged.
Yes, I just made the mistake of quickly looking at the socket and coming to an incorrect conclusion to start with, thanks for the info. The NTE5a's are the standard Openreach branded sockets arent they? The ones that come with bell wire removed as opposed to the BT with piper man logo sockets that still have it?
|
|
|
|
Well, all that was very interesting! Just so you know I have not kept the socket like that, I only opened it to that extent to have it correctly identified and make sure there were no extension wires and only two wires in use.
I now only have removed the bottom 2/3 (held in with flat head screws), to access the test socket. Contrary to what has been said, there is very little dust, a lot less than you would find inside an RJ45 wall socket in an office, and no wildlife whatsoever!!
Moving on to what this thread was originally about: I had a call from the Orange resolution department, they performed a line test and then rang someone to remove the cap on my profile. I now have the same stats as before but with a speed of: Downstream Rate: 7291kbps
The BT speedtester also shows that my IP profile has doubled. I think I should still be getting more, but will wait as they said they would ring tomorrow.
|
|
|
If other stats are all the same, then 7291 still sounds low, and maybe they have un capped you, but not to a totally uncapped profile.
Orange support seems to prefer capped line profiles, rather than letting the DLM adjust itself.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
If other stats are all the same, then 7291 still sounds low, and maybe they have un capped you, but not to a totally uncapped profile.
Orange support seems to prefer capped line profiles, rather than letting the DLM adjust itself.
I'll ask tomorrow when they ring me back, if they don't get back to me at least they left me with an 0800 number
|
|
|
They will have performed an SNR reset no doubt.
You will have to monitor your line as it will take a good amount of time to settle down. If there is an underlying issue causing the line to be capped then it may very well happen again.
An SNR reset is only usually a viable option if the underlying fault has been taken care of or if some physical changes have been made to the line itself in my experience, but a lot of ISPs use it as a quick fix and get rid without taking the care to examine whats going on under the hood.
EDIT: @ Saffron
I was told recently that Orange don't do fixed profiles, its the standard TR101 ranges are banded to 160k - 24mb for WBC. Unless hes not on TR101 and on Max in which case it would probably be your standard ADSL threshold profiles in the case of that sync speed probably ADSL6500.
In looking back at the initial stats the modulation is for ADSL2+ so I would guess he's on WBC.
Edited by deleted (Wed 19-Sep-12 18:20:06)
|
|
|
The NTE5a's are the standard Openreach branded sockets arent they? The ones that come with bell wire removed as opposed to the BT with piper man logo sockets that still have it?
I have a "spare" NTE5 that is very similar to the OP's (a green protective covering and A&B plus E terminals at the rear.) The front of the NTE5 has a "T" within a circle marking at top right and the single phone socket faceplate is unmarked externally.
|
|
|
Yes its WBC
And Banded Profiles are part of WBC, not to be confused with IP Profile. Seen plenty of people with similar caps from only Orange of late, so they are doing something.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
I've also seen quite a few folk who having been migrated to WBC haven't been told to keep their router switched on 24/7 and have caps as a result. This can easily be seen through with the sync uptime in an RRT database check. And just plain asking the user.
But I digress on that point.
Best thing the the OP can do is ask whoever put the SNR reset through (because they should have access to perform a KBD test) to take a look at the local access network part of the test and see if its failing.
|
|
|
I've also seen quite a few folk who having been migrated to WBC haven't been told to keep their router switched on 24/7 and have caps as a result. This can easily be seen through with the sync uptime in an RRT database check. And just plain asking the user.
But I digress on that point.
Best thing the the OP can do is ask whoever put the SNR reset through (because they should have access to perform a KBD test) to take a look at the local access network part of the test and see if its failing.
Thanks for this info. I do keep the router on 24/7. How long should i expect the router to keep a connection? I don't think I've ever seen it connected for more than 2 days.
|
|
|
Nice myth that WBC requires you to keep router on 24/7
Also what do you think an SNR reset is going to do? It is already looking like it on the lowest target margin, a reset usually only gains speed if their SN margin is high
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Nice myth that WBC requires you to keep router on 24/7
Also what do you think an SNR reset is going to do? It is already looking like it on the lowest target margin, a reset usually only gains speed if their SN margin is high
Its not a myth, dealt with at least a dozen folk in the past year who have had caps and a very low sync uptime over the 2 weeks RRT check, asked them myself and they said yes they turn the router off at night/when not in use. Only explaination in my mind is that DLM can't tell the diff between a router being turned off and it dropping connection due to a fault, so to try and stabilise it lowers the range. We'd never had this explained officially so its a working theory unless you have another one?
Yes I agreed on that hence why I stated to have them check if local network shows as a failure. They should also look at status check and see if there are a lot of downstream or upstream errored seconds and or HEC errors displayed there.
EDIT:
What I think the OP needs to concentrate on is the loss of connection as if he moans about the speed after this SNR reset all he will find is that its considered a stabilisation period for the next 10 days. BT can't ignore the drops in connection!
Edited by deleted (Wed 19-Sep-12 20:30:26)
|
|
|
If your connection is stable and you turn it off for a few hours, and then when back on it comes back at the same speed (within margin of tolerance) this should not see it enabled as unstable.
Unstable is meant to take a number of resyncs in an hour, to avoid simple things like turning off electrical hardware at night.
Why should the user be asking for a SNR reset? Interested to hear the explanation of how this helps the line with the characteristics we have seen?
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
OP is on WBC!
How can they have caused an SNR reset if he is still on the same NM?
its the standard TR101 ranges are banded to 160k - 24mb for WBC. WBC IP Profiles are not banded (stepwise), unlike IPStream; they are continuous 88.2 % of Sync.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
Seen plenty of people with similar caps from only Orange of late, so they are doing something. In all other cases we've seen they were holding the Target NM unnecessarily high. Not in this case!
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
I do keep the router on 24/7. How long should i expect the router to keep a connection? I don't think I've ever seen it connected for more than 2 days.
Are you saying that the dsl link is normally dropped at least once every 48 hours even though you leave the router powered on 24/7?
|
|
|
|
You should expect it to drop very rarely. I have had literally months and months without drop outs and no router reboot.
I can see in connection uptime that it hasn't dropped.
2 days isn't ideal although isn't significant enough to raise as a fault.
|
|
|
The NTE5a's are the standard Openreach branded sockets arent they? The ones that come with bell wire removed as opposed to the BT with piper man logo sockets that still have it? I repeat - the NTE5A is purely and simply the removable faceplate, and in fact so far as I know is no different when supplied with the current NTE5 from that supplied with earlier versions such as the Piper logoed one.
My broadband basic info/help site - www.robertos.me.uk
Domains,website and mail hosting - Tsohost. Connection - Plusnet Extra Fibre (FTTC). Sync ~ 56.0/13.9Mbps @ 600m.
"Where talent is a dwarf, self-esteem is a giant." - Jean-Antoine Petit-Senn.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Allergy information: This post was manufactured in an environment where nuts are present. It may include traces of understatement, litotes and humour.
|
|
|
Agreed, they are only every going to entertain it as a fault if happening multiple times in the same hour
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Are you saying that the dsl link is normally dropped at least once every 48 hours even though you leave the router powered on 24/7?
That seems to be the case going back through my posts here, even when I was capped at 3Mbps.
I've just had the follow up phone call, they said that the line has now been uncapped, it's actually been uncapped since they made the call yesterday. My stats are:
Time Connected: 22:40:56
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
2425
26 | Status:
Configured CurrentLine Status --- SHOWTIME
Link Type --- Fast PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate Information:
Stream Type Actual Data RateUpstream 923 (Kbps.)
Downstream 7291 (Kbps.)
Defect/Failure Indication:Operation Data Upstream Downstream
Noise Margin 7.3 dB 8.8 dBLine Attenuation 19.9 dB 33.5 dB
Indicator Name Near End Indicator Far End Indicator
Output Power 10.1 dBm 0.0 dBmFast Path FEC Correction 0 0
Interleaved Path FEC Correction NA NAFast Path CRC Error 1714 185
Interleaved Path CRC Error NA NALoss of Signal Defect 10 0
Fast Path HEC Error STR 7638 198Interleaved Path HEC Error NA NA
Error Seconds 1371 30 |
I told the guy that I think I should be getting a slightly faster connection ~10Mbps or more. However he said that by line length I can only get 8Mbps, I didn't know whether to take this as; I've been completely uncapped and there's a possibility for my line to automatically sync at a higher speed. Or; We've capped you at 8Mbps because that's the maximum we believe your line can run.
I was told that if I experience a couple of disconnections within the next two or three days I should ring back.
|
|
|
Agreed, they are only every going to entertain it as a fault if happening multiple times in the same hour
It is possible that multiple dsl drops did occur within a very short space of time since the OP said that he has never been connected for longer than 2 days. Further, the OP may have been unaware of such multiple drops if he didn't have access to router logs or other means of recording the connection status.
|
|
|
...I told the guy that I think I should be getting a slightly faster connection ~10Mbps or more. However he said that by line length I can only get 8Mbps, I didn't know whether to take this as; I've been completely uncapped and there's a possibility for my line to automatically sync at a higher speed. Or; We've capped you at 8Mbps because that's the maximum we believe your line can run.
I was told that if I experience a couple of disconnections within the next two or three days I should ring back.
I really don't understand how that guy came to the conclusion that you can only get 8mbps since your downstream adsl2+ attenuation is 33.5dB and SNRM at 8.8dB.
Perhaps others can comment on the error rates etc. but they don't look too bad to me after an up time of more than 22 hours...
Edited by 4M2 (Thu 20-Sep-12 13:17:15)
|
|
|
ES are par for the course; I reckon on 1 ES per min uptime on Fast Path.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
I really don't understand how that guy came to the conclusion that you can only get 8mbps since your downstream adsl2+ attenuation is 33.5dB and SNRM at 8.8dB.
Perhaps others can comment on the error rates etc. but they don't look too bad to me after an up time of more than 22 hours...
Maybe I need to get the phone number for 3rd line support! If my service is uncapped then it may eventually sync at a higher speed. If i don't experience too many disconnections I will leave it for 10 days or so to see what happens, and then decide what to do.
Edited by deleted (Thu 20-Sep-12 13:29:00)
|
|
|
I repeat - the NTE5A is purely and simply the removable faceplate, and in fact so far as I know is no different when supplied with the current NTE5 from that supplied with earlier versions such as the Piper logoed one.
New NTE5's with the "Openreach - a BT Group business - BT" external logo have an externally unmarked NTE5A faceplate that has connections 2,3 and 5 only. Hence a ring wire can still be used
|
|
|
Maybe I need to get the phone number for 3rd line support! If my service is uncapped then it may eventually sync at a higher speed. If i don't experience too many disconnections I will leave it for 10 days or so to see what happens, and then decide what to do.
I believe the sync speed is established when the router syncs to the exchange so just leaving it may not achieve much. During the monitoring period, however, if and when the dsl drops then you may see an increase in sync speed after a reconnection...
|
|
|
It is also possible that I am the queen of sheba
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
Because they are told to be believe the numbers they are told.
When in fact the database is probably putting out garbage due to the logic that populates it, or interprets the data.
Providers have not caught onto attenuation, and the good guide this gives, rather than a distance between two postcodes.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
It is also possible that I am the queen of sheba
|
|
|
Just had a disconnection, was connected for just over 48 hours, my IP profile has gone down to 5.69Mbps
Stats:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
| Line Status --- SHOWTIME
Link Type --- Fast PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate Information:
Stream Type Actual Data RateUpstream 843 (Kbps.)
Downstream 6455 (Kbps.)
Operation Data Upstream DownstreamNoise Margin 8.1 dB 8.2 dB
Line Attenuation 20.1 dB 33.5 dB
Indicator Name Near End Indicator Far End IndicatorOutput Power 10.1 dBm 0.0 dBm
Fast Path FEC Correction 0 0Interleaved Path FEC Correction NA NA
Fast Path CRC Error 14 0Interleaved Path CRC Error NA NA
Loss of Signal Defect 12 0Fast Path HEC Error STR 36 0
Interleaved Path HEC Error NA NAError Seconds 2658 33 |
I hope this isn't a sign that every time I get a disconnection my connection speed will drop slightly, 3070Kbps here I come!
Edited by deleted (Fri 21-Sep-12 15:16:47)
|
|
|
Just had a disconnection, was connected for just over 48 hours, my IP profile has gone down to 5.69Mbps...
...I hope this isn't a sign that every time I get a disconnection my connection speed will drop slightly, 3070Kbps here I come!
Might be almost time to "bit the bullet" and move on
Have Orange themselves offered any more help: e.g. a replacement router, filters and adsl rj11 cable. If you are still connected to the test socket and the sync speed continues to be poor then Orange really do need to thoroughly investigate the problem...
|
|
|
Might be almost time to "bit the bullet" and move on 
Have Orange themselves offered any more help: e.g. a replacement router, filters and adsl rj11 cable. If you are still connected to the test socket and the sync speed continues to be poor then Orange really do need to thoroughly investigate the problem...
They sent me an extra router which I have tried, and I've also tried multiple filters.
I have this feeling that they won't see what's happening as a problem, as far as they're concerned the maximum speed for my connection is 8Mbps and as long as it's above 2Mbps then it's fine.
It's really disappointing that they don't have an online support forum, companies with them seem to have much more knowledgeable staff.
I think I'll wait another couple of days before going through the Indian call centre again
|
|
|
I have this feeling that they won't see what's happening as a problem, as far as they're concerned the maximum speed for my connection is 8Mbps and as long as it's above 2Mbps then it's fine.
That's crazy I would expect throughput, e.g. BT speed tester recorded download speed, to generally be 8Mbps or more on your line...
|
|
|
|
When I pressed the 2nd line support guy about the speed only being 7291Kbps and said I expected more he said that my line was only capable of 8Mbps so I was doing quite well.
|
|
|
When I pressed the 2nd line support guy about the speed only being 7291Kbps and said I expected more he said that my line was only capable of 8Mbps so I was doing quite well.
They keep coming up with this 8Mbps number which might be relevant to an ADSL(1) downstream sync speed but you are on ADSL2+ with an attenuation of 33.5dB and SNRM of 8.2dB and this should give you a downstream sync of ~14500Kbps (~14Mbps)
It may well be that in their view throughput speeds might acceptable between 2Mbps and 8Mbps but I don't know how they can claim between 2Mbps and 8Mbps is acceptable for a sync speed (?) on your adsl2+ line.
|
|
|
They keep coming up with this 8Mbps number which might be relevant to an ADSL(1) downstream sync speed but you are on ADSL2+ with an attenuation of 33.5dB and SNRM of 8.2dB and this should give you a downstream sync of ~14500Kbps (~14Mbps)
It may well be that in their view throughput speeds might acceptable between 2Mbps and 8Mbps but I don't know how they can claim between 2Mbps and 8Mbps is acceptable for a sync speed (?) on your adsl2+ line.
It seems that they're not interested in attenuation at all, I imagine they're following whatever information is on their computer screen, and whatever that says goes.
|
|
|
It seems that they're not interested in attenuation at all, I imagine they're following whatever information is on their computer screen, and whatever that says goes.
I've had similar issues with ISP's in the past (not Orange though) and sent them copies of router stats and BT speed tests in order to convince them that there was a problem.
This was done in the form of "tickets" sent to the ISP which were then escalated to the appropriate level of technical support. Tests were subsequently done on my line by the ISP and it was agreed that there was indeed a problem. In my case an Openreach SFI engineer checked the entire line from my test socket to the exchange and located the fault. In your case it may not be hardware problem but in my opinion they are obliged to fully investigate the poor sync speed and hence the poor service that you are receiving and paying good money for!
Edited by 4M2 (Fri 21-Sep-12 19:10:52)
|
|
|
Hello,
Please send your broadband telephone number in a private message and I will get the issues escalated. One of the team will contact you.
Regards
Gavin
Orange Home Broadband
'Here to help'
|
|
The above post has been made by an ISP REPRESENTATIVE (although not necessarily the ISP being discussed in the post).
|
|
|
It seems that they're not interested in attenuation at all, I imagine they're following whatever information is on their computer screen, and whatever that says goes.
I've had similar issues with ISP's in the past (not Orange though) and sent them copies of router stats and BT speed tests in order to convince them that there was a problem.
This was done in the form of "tickets" sent to the ISP which were then escalated to the appropriate level of technical support. Tests were subsequently done on my line by the ISP and it was agreed that there was indeed a problem. In my case an Openreach SFI engineer checked the entire line from my test socket to the exchange and located the fault. In your case it may not be hardware problem but in my opinion they are obliged to fully investigate the poor sync speed and hence the poor service that you are receiving and paying good money for!
A ticket system is what I would really like, however it doesn't seem like that system exists, at least not for customers. It's quite frustrating.
I have been taking two screenshots per day of my router statistics, but without the sort of system where I could post these they seem fairly useless. I will try to see if I can get 2nd line support to call me, must deal with the 'offshored' call centre first.
|
|
|
Hello,
Please send your broadband telephone number in a private message and I will get the issues escalated. One of the team will contact you.
Regards
Not me doc - perhaps you should offer assistance to the OP
|
|
|
It would appear that the saga is over, not to my satisfaction though.
Time Connected: 2 days 17:51:22
| Text | 1
23
| Line Status --- SHOWTIME
Link Type --- Fast PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+) |
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
| Stream Type Actual Data Rate
Upstream 907 (Kbps.)Downstream 6912 (Kbps.)
Defect/Failure Indication:
Operation Data Upstream DownstreamNoise Margin 6.1 dB 7.8 dB
Line Attenuation 19.7 dB 33.5 dB
Indicator Name Near End Indicator Far End IndicatorOutput Power 10.1 dBm 0.0 dBm
Fast Path FEC Correction 0 0Interleaved Path FEC Correction NA NA
Fast Path CRC Error 4291 49Interleaved Path CRC Error NA NA
Loss of Signal Defect 17 0Fast Path HEC Error STR 12018 50
Interleaved Path HEC Error NA NAError Seconds 6677 62 |
The 3rd line (or whatever they're called) phoned me today, he initially asked about the dropping connection, which for some reason seems to have stopped. I asked why I wasn't getting the higher speeds that my line attenuation indicates I should be getting. He said that line length, interference, line quality and my equipment(!) can all affect the speed. I told him that I thought that the line attenuation reading would reflect any of those problems and would be higher if any of those factors was present. He reiterated that I was achieving my minimum speeds and that's apparently all that they strive to deliver.
I'm pretty fed up with the customer support, I was asked yet again what modem/router I had, whether I was plugged into master socket, any extensions etc. etc. Is the customer support purposefully structured in this way so there's no continuation between separate calls?
I logged into my Orange account and found that this was my predicted speed when I signed up! At least I'm doing better then that.
Hopefully the next 10 months will pass by relatively quickly and I can move providers.
Edited by deleted (Tue 25-Sep-12 13:46:04)
|
|
|
It would appear that the saga is over, not to my satisfaction though.
Is your current downstream throughput speed sufficient for your needs? Even if it is I agree that the situation is far from satisfactory but do you wish to pursue the matter further?
Earlier in the thread you did mention that Orange had detected a problem with the line: "Just spoken to them on the phone, they said that there was a problem with the line test (an exclamation mark) which meant it could be a problem with the line or something in the house. The fault has been escalated to another team who can get in touch with Openreach, so now i have to wait to see if I will get a call."
Maybe if you want to improve the downstream sync and hence throughput speed you will have to push Orange to arrange for an Openreach SFI engineer to thoroughly test your line from the NTE5 test socket to the exchange. You stated earlier that everything is OK on your side of the NTE5 and certainly everything seemed to be in order at the back of the NTE5 as shown in the photo.
|
|
|
Is your current downstream throughput speed sufficient for your needs? Even if it is I agree that the situation is far from satisfactory but do you wish to pursue the matter further?
It is just about enough, I just feel that I am being denied the true speed of my line when other ISPs would try and deal with this problem.
Earlier in the thread you did mention that Orange had detected a problem with the line: "Just spoken to them on the phone, they said that there was a problem with the line test (an exclamation mark) which meant it could be a problem with the line or something in the house. The fault has been escalated to another team who can get in touch with Openreach, so now i have to wait to see if I will get a call."
The escalation team performed a test and didn't find anything wrong with line, each time I have phoned customer support they have performed a line test and it was only one test that showed a fault.
Maybe if you want to improve the downstream sync and hence throughput speed you will have to push Orange to arrange for an Openreach SFI engineer to thoroughly test your line from the NTE5 test socket to the exchange. You stated earlier that everything is OK on your side of the NTE5 and certainly everything seemed to be in order at the back of the NTE5 as shown in the photo.
I very much doubt that they will do this, two members of their escalation team have both insisted that I am getting all that Orange are obliged to deliver and anymore would be a bonus, one which they're not willing to pay for or sort out.
I think the only way they will send an engineer out is if my line starts dropping as it has done previously.
Edited by deleted (Tue 25-Sep-12 15:04:37)
|
|
|
...two members of their escalation team have both insisted that I am getting all that Orange are obliged to deliver and anymore would be a bonus, one which they're not willing to pay for or sort out.
OK
|
|
|
They is actually no obligation to deliver anything, though if zero you would have an easy exit from contract.
You are not dealing with people who understand the technology, just people repeating what another poorly informed person has trained them in.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
|
That reminds me of another story:
A friend bought a motorbike that was supposedly capable of 120 mph from a dealer, when he complained to the dealer that the bike wouldn't do 120 mph the dealer replied that UK roads are limited to a 70 mph speed limit and so we can not verify the validity of your complaint.
If the motorbike wouldn't go at 70 mph (or even perhaps 1 mph!) then I guess the dealer would have had an obligation to correct the problem for my friend�
|
|
|
You are not dealing with people who understand the technology, just people repeating what another poorly informed person has trained them in.
I think that's the crux of the problem, it is a bit annoying when I read a thread on the TalkTalk forum where a user said he didn't think he was getting the correct speed with an attenuation of 33.5dB (~8000Kbps). The admins looked into this and managed to get him up to 11949Kbps in 6 days!
|
|
|
Not sure who to reply to ....
The ONLY thing that is iffy in the back of that socket, is the insulation tape covering the pair above the dropwire sleeve. This smacks of having been cut, and then just twisted back together. Most likely by the builders or decorators. If this a bodged repair, then it's not been done by an Openreach engineer. Why struggle with stripping a pair, twisting and taping when you have a box of crimps in your tool bag.
|
|
|
http://recipes.zzl.org/Socket.jpg - Well spotted, you could have replied to me since I probably mistakenly thought it looked OK
|
|
|
|
Anything I can do about this?
|
|
|
Anything I can do about this?
Officially no!
I believe only an Openreach engineer, or another authorized person would be able to check that out for you.
|
|
|
Best advice, leave well alone. Put the NTE back in place, have the filter in the test jack ......
This way if an engineer does come to site, you can look surprised as discover it. To be fair, it's HIGHLY unlikely that the engineer is raise charges for this.
*If you feel brave*, you might, gently waggle to taped connection, whilst listening on the phone/and looking at the error counter. But if you break this at this point, have to report a no dial tone fault, the engineer will be more than happy to raise charges.
The choice is yours.
There is an awful lot more wire between you and the exchange, the chances of it being the one bit you photographed ..............
|
|
|
|
If the connection starts dropping again I will look into this. I think it's probably best to leave it alone. I put the socket back straight after I took the picture and have been connected to the test socket ever since.
|
|
|
Just had the Openreach engineer round, he checked the wires in the socket and there were no problems. He replaced the socket with a new Openreach one (not filtered). The line checked out fine and he was reading a speed of 11.5Mbps. After plugging the router back in it was running at 10.5Mbps and 1.1Mbps with down attenuation at 32.5 (lowest ever) and NM at 6.2 (lowest ever), and I think output power was 12.? rather than 10.1 which it has always been.
He then phoned in for a reset of the line and now I'm back to pretty much exactly what I had before he changed the socket:
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
24 | Line Status --- SHOWTIME
Link Type --- Fast PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate Information:
Stream Type Actual Data RateUpstream 859 (Kbps.)
Downstream 6711 (Kbps.)
Defect/Failure Indication:Operation Data Upstream Downstream
Noise Margin 7.1 dB 7.6 dBLine Attenuation 19.9 dB 33.5 dB
Indicator Name Near End Indicator Far End Indicator
Output Power 10.1 dBm 0.0 dBmFast Path FEC Correction 0 0
Interleaved Path FEC Correction NA NAFast Path CRC Error 2 0
Interleaved Path CRC Error NA NALoss of Signal Defect 1 0
Fast Path HEC Error STR 2 0Interleaved Path HEC Error NA NA
Error Seconds 17 0 |
I will wait 5 days to see exactly what's happened (although having waited before to see my speed improve I'm not too hopeful), at least I can now say with certainty that my line should be running at least 10Mbps when I talk to Orange CS.
|
|
|
Had a second engineer visit yesterday, I offered him a cup of tea and he went to the green box and replaced the connector there. He also said I was on the best wire to the exchange.
I have installed a filtered faceplate and here are my stats:
| Text | 1
23
| Time Connected: 1 day 00:11:32
Downstream Rate: 15285kbpsUpstream Rate: 888kbps |
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
24 | Line Status --- SHOWTIME
Link Type --- Interleaved PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate Information:
Stream Type Actual Data RateUpstream 888 (Kbps.)
Downstream 15285 (Kbps.)
Defect/Failure Indication:Operation Data Upstream Downstream
Noise Margin 16.7 dB 6.6 dBLine Attenuation 18.4 dB 32.0 dB
Indicator Name Near End Indicator Far End Indicator
Output Power 12.1 dBm 0.0 dBmFast Path FEC Correction NA NA
Interleaved Path FEC Correction 47159 23Fast Path CRC Error NA NA
Interleaved Path CRC Error 210 0Loss of Signal Defect 13 0
Fast Path HEC Error STR NA NAInterleaved Path HEC Error 4275 0
Error Seconds 1375 2 |
Obviously a lot happier with the speeds now, I think they may be doing something to my upload but I should probably quit while I'm ahead
Thanks for your help.
|
|
|
I think they may be doing something to my upload but I should probably quit while I'm ahead  It's BTw's DLM; it only gives 888K Up on Interleaved; Fast Path would be faster but DLM decides.
Good speed tho'; might get faster if DLM chooses 3dB NM.
Notice attn. gone down after eng fiddled
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 19 Meg WBC
|
|
|
I think they may be doing something to my upload but I should probably quit while I'm ahead  It's BTw's DLM; it only gives 888K Up on Interleaved; Fast Path would be faster but DLM decides.
Good speed tho'; might get faster if DLM chooses 3dB NM.
Notice attn. gone down after eng fiddled 
Yes, he said that the connector in the cabinet was mouldy and had probably been there for about 20 years! I think he tried a lot more things out because he was the second engineer to try and fix the problem. I think the filtered faceplate may have helped as well.
EDIT: Forgot to add he also said that I was probably getting too many CRC errors before he changed the connector in the cabinet.
Edited by deleted (Thu 18-Oct-12 18:25:21)
|
|
|
Hello,
I had asked the team to take a second look, so glad we got this resolved for you.
Regards
Gavin
Orange Home Broadband
'Here to help'
|
|
The above post has been made by an ISP REPRESENTATIVE (although not necessarily the ISP being discussed in the post).
|
|
|
Hello,
I had asked the team to take a second look, so glad we got this resolved for you.
Regards
I kept on hassling them after the first engineer visit failed to resolve anything (<4000Kbps sync speed), they reluctantly sent someone else and this rest is in my previous two posts.
Thanks
|
|
|
Got a bump up on the upstream this morning:
| Text | 1
23
| Time Connected: 07:52:11
Downstream Rate: 15285kbpsUpstream Rate: 1264kbps |
| Text | 1
23
45
67
89
1011
1213
1415
1617
1819
2021
2223
24 | Line Status --- SHOWTIME
Link Type --- Interleaved PathOperation Mode G992.5(ADSL2+) G992.5(ADSL2+)
Data Rate Information:
Stream Type Actual Data RateUpstream 1264 (Kbps.)
Downstream 15285 (Kbps.)
Defect/Failure Indication:Operation Data Upstream Downstream
Noise Margin 5.5 dB 6.0 dBLine Attenuation 18.4 dB 31.5 dB
Indicator Name Near End Indicator Far End Indicator
Output Power 12.8 dBm 0.0 dBmFast Path FEC Correction NA NA
Interleaved Path FEC Correction 14863 0Fast Path CRC Error NA NA
Interleaved Path CRC Error 39 11Loss of Signal Defect 14 0
Fast Path HEC Error STR NA NAInterleaved Path HEC Error 716 3
Error Seconds 1497 12 |
Happy Orange BB customer now! I can stream iplayer HD without problems now.
EDIT: Forgot to add; thank you again to everyone here that helped me.
Edited by deleted (Fri 19-Oct-12 19:09:16)
|