IP profile lowered after placing fault call :-(

[bikefright]

Hi forum,

I have 2 x phone lines, 2 x total broadband (2 x HH3).  I should be able to get 20Mbit as distance wise I'm close the the exchange, but due to congestion in the big green box and the love of aluminium core cable from the days of the copper crisis, I normally sync at around the 8Mbit mark on both lines.

Line 2 is fine has been for ages.  Line 1 has just started playing up in the last week.

BB speed has dropped (which was the reason for me placing a fault call) from around 7-8Mbit to around 4-5Mbit.It has been consistently at the high end of my connection speed for more than 12 months.

SNR has changed in the last week.  It was 30dB up and 15dB down, before placing the fault call today it was 17dB up and 15dB down however after placing the call and going through some diagnostics over the phone (all the usual stuff like plug into the test socket etc, which required a reboot of the HH3) it is 29dB up and 15dB down.

I note that my IP profile has been lowered to 2 point something which means the maximum DL speed I get is around the 2.4Mbit mark   How can this be changed back to 7.15 which is where I think it was prior to the problems starting a week ago?

26th July, speedtest.net recorded 7.15Mbit, today before placing the call, 4.5Mbit, now after placing the call it's recording 2.45Mbit 😞

Could someone explain (be however technical you like) what has happend since placing the fault call to change my IP profile other than the reboot of the HH3?

Below are the two sets of output from both HH3's.  Bad first, then the good one for comparison:

Before placing the fault call today:

17:47:57, 01 Sep.	(269058.610000) DSL is up
17:47:55, 01 Sep.	(269056.540000) DSL noise margin: 17.00 dB upstream, 15.10 dB downstream
17:47:54, 01 Sep.	(269056.480000) DSL line rate: 448 Kbps upstream, 5856 Kbps downstrea

After placing the fault call today:

10:02:06, 06 Sep.	( 56.410000) PPPoA is up
10:02:06, 06 Sep.	( 55.890000) CHAP authentication successful
10:02:05, 06 Sep.	( 55.830000) Starting CHAP authentication with peer
10:02:00, 06 Sep.	( 50.700000) DSL is up
10:01:58, 06 Sep.	( 48.590000) DSL noise margin: 29.00 dB upstream, 15.40 dB downstream
10:01:58, 06 Sep.	( 48.520000) DSL line rate: 448 Kbps upstream, 7072 Kbps downstream
10:01:54, 06 Sep.	( 44.540000) New GUI session from IP 171.16.0.65
10:01:54, 06 Sep.	( 44.480000) New GUI session from IP 171.16.0.65
10:01:43, 06 Sep.	( 33.700000) Lease for IP 171.16.0.65 renewed by host Vigor2930Vn(00-50-7f-c4-a9-95) (MAC 00:50:7f:c4:a9:95). Lease duration: 1440 min
10:01:43, 06 Sep.	( 33.620000) Lease requested
10:01:41, 06 Sep.	( 31.330000) Server URL: https://pbthdm.bt.motive.com; Connecting as user: ACS username
10:01:41, 06 Sep.	( 30.970000) Initializing transaction for event code 1 BOOT
10:01:26, 06 Sep.	( 16.240000) Booting firmware 4.7.5.1.83.8.57.1.3 (Type A)

1. Product name:	BT Home Hub
2. Serial number:	+058720+1109038476
3. Firmware version:	Software version 4.7.5.1.83.8.57.1.3 (Type A) Last updated 19/05/11
4. Board version:	BT Home Hub 3.0A
5. ADSL uptime:	0 days, 00:52:27
6. Bandwidth:	448 / 7072
7. Data sent/received:	0.0 / 0.0
8. Broadband username:	bthomehub@btbroadband.com
9. BT FON:	No
10. Wireless network/SSID:	Spongebob
11. Wireless connections:	Disabled
12. Wireless security:	WPA and WPA2
13. Wireless channel:	Automatic / 1
14. Firewall:	Default
15. MAC Address:	94:fe:f4:2f:c6:4e
16. VPI/VCI:	0 / 38
17. Line profile:	Interleaved

The good, well behaved HH3

15:06:35, 29 Aug.	( 53.540000) DSL is up
15:06:33, 29 Aug.	( 51.460000) DSL noise margin: 31.00 dB upstream, 13.50 dB downstream
15:06:33, 29 Aug.	( 51.390000) DSL line rate: 448 Kbps upstream, 8128 Kbps downstream

1. Product name:	BT Home Hub
2. Serial number:	+058720+1108004721
3. Firmware version:	Software version 4.7.5.1.83.8.57.1.3 (Type A) Last updated 09/11/11
4. Board version:	BT Home Hub 3.0A
5. ADSL uptime:	7 days, 19:48:47
6. Bandwidth:	448 / 8128
7. Data sent/received:	0.5 / 1.5
8. Broadband username:	bthomehub@btbroadband.com
9. BT FON:	No
10. Wireless network/SSID:	BTHub3-ZP2K
11. Wireless connections:	Disabled
12. Wireless security:	WPA and WPA2
13. Wireless channel:	Automatic / 1
14. Firewall:	Default
15. MAC Address:	94:fe:f4:27:45:d6
16. VPI/VCI:	0 / 38
17. Line profile:	Interleaved

Best regards,

Rowland.

[john46]

Hi Welcome to the forums

Here is a basic guide to getting help from the community members done by CL Keith http://forumhelp.dyndns.info/speed/first_steps.html

Have you tried the quiet line test? - dial 17070 option 2 - should hear nothing - best done with a corded phone. if cordless phone you may hear a 'dull hum' which is normal

once you have posted the information asked for then the community members can help you more

Thank You

This is a customer to customer self help forum the only BT presence here are the forum moderators

[bikefright]

Thanks for the welcome John.

My haste to understand what had happend made me skip the basics and I have posted what I *thought* was needed as opposed to what is actually needed 😉

Hopefully here is what is required:

ADSL Line Status

Connection Information Line state: Connected Connection time: 0 days, 01:41:11 Downstream: 6.906 Mbps Upstream: 448 Kbps

ADSL Settings VPI/VCI: 0/38 Type: PPPoA Modulation: G.992.1 Annex A Latency type: Interleaved Noise margin (Down/Up): 15.3 dB / 29.0 dB Line attenuation (Down/Up): 14.6 dB / 6.0 dB Output power (Down/Up): 19.9 dBm / 12.0 dBm FEC Events (Down/Up): 126 / 1 CRC Events (Down/Up): 1 / 0 Loss of Framing (Local/Remote): 0 / 0 Loss of Signal (Local/Remote): 0 / 0 Loss of Power (Local/Remote): 0 / 0 HEC Events (Down/Up): 0 / 0 Error Seconds (Local/Remote): 1 / 0

This is a HH3

BT Speedtester results:

 Download speedachieved during the test was - 2.31 Mbps
 For your connection, the acceptable range of speeds is 0.6 Mbps-7.15 Mbps.
 Additional Information:
 Your DSL Connection Rate :6.94 Mbps(DOWN-STREAM), 0.45 Mbps(UP-STREAM)
 IP Profile for your line is - 2.5 Mbps

Quiet line test with a corded phone: There is some hissing and occasional crackle.

I already have a bt fault logged I can provide the BT refrence number if needed.

I have the first type of master socket with the split faceplate.

ADSL stats when plugged into the test socket after 10 minutes:

ADSL Line Status

Connection Information Line state: Connected Connection time: 0 days, 00:12:22 Downstream: 6.781 Mbps Upstream: 448 Kbps

ADSL Settings VPI/VCI: 0/38 Type: PPPoA Modulation: G.992.1 Annex A Latency type: Interleaved Noise margin (Down/Up): 15.4 dB / 30.0 dB Line attenuation (Down/Up): 14.6 dB / 6.0 dB Output power (Down/Up): 19.9 dBm / 12.1 dBm FEC Events (Down/Up): 0 / 0 CRC Events (Down/Up): 1 / 0 Loss of Framing (Local/Remote): 0 / 0 Loss of Signal (Local/Remote): 0 / 0 Loss of Power (Local/Remote): 0 / 0 HEC Events (Down/Up): 0 / 0 Error Seconds (Local/Remote): 1 / 0

BT Speedtester results when plugged into the test socket:

 Download speedachieved during the test was - 2.32 Mbps
 For your connection, the acceptable range of speeds is 0.6 Mbps-7.15 Mbps.
 Additional Information:
 Your DSL Connection Rate :6.94 Mbps(DOWN-STREAM), 0.45 Mbps(UP-STREAM)
 IP Profile for your line is - 2.5 Mbps

ATB,

Rowland.

[john46]

could you first check the noise can be heard when you connect a phone to the test socket this will eliminate any internal wiring issues
once the line noise is resolved you then need the hub to be left powered up 24/7 for 5 days and your IP Profile will rise automatically as will your download speed but the noise needs fixing first

[bikefright]

Thanks for the reply John.

The line test was done from the test socket.  I have just repeated the test for a couple of minutes and the line is quiet.  I have checked the fault logged against my line and BT have closed the fault as fixed.

I understand why the profile will increase over time as the line proves stable.  I suppose it was a shock that two or three reboots of the HH3 resulted in a jump in IP profile from 7Mbit to 2Mbit.

I will sit tight and see what happens over the next week.

Thanks again,

Rowland.

[john46 · Accepted solution]

there may have been more than just two or three restarts as only the hub stats would show the noise may have caused more than you realise

[bikefright]

A week down the line and things are pretty much back to where they were 🙂

Thanks for your helpful advice John - in this instance, sitting back and waiting for the re-profiling to take place after whatever was done to sort the noise on the line last week was what was needed.

ATB,

Rowland.

[john46]

Please post back any time you want any help or advice there is always some one around