Mouselike just runs a BT Wholesale speed test on your line and reports the IP Profile to you. I discovered that years ago, when having used it BTW made me wait (IIRC) ten minutes (it used be be longer) before letting me.

Edited by RobertoS (Thu 08-Feb-18 13:13:35)

Hmmmm. This is interesting. I know it can happen (and why) on third-party speed tests, but don't recall it on the BT Wholesale one.

Download speed achieved during the test was - 70.8 Mbps
For your connection, the acceptable range of speeds is 40 Mbps-69.67 Mbps .
Additional Information:
IP Profile for your line is - 69.67 Mbps

Upload speed achieved during the test was - 11.29Mbps
Additional Information:
Upstream Rate IP profile on your line is - 20 Mbps

Speed > IP Profile. Though I did earlier see an oddity in another AAISP log when checking how far back the part of the Radius Log report I can see went. My current sync is in my sig by the way.

This is what I get:

Looks like BT refused to test, possibly because a speed test or BRAS check has been run recently which prevents this tool from working. Try again in a few hours.
Debug: BT no BRAS info

Edited by deleted (Thu 08-Feb-18 13:54:31)

In reply to a post by WilliamGrimsley:

This is what I get:

Looks like BT refused to test, possibly because a speed test or BRAS check has been run recently which prevents this tool from working. Try again in a few hours.
Debug: BT no BRAS info

When i used to be on BTW Backhaul with Zen the IP profile stopped working many months before they put me on TTW backhaul , And following a Fault with the DSLAM port (lift and shift) they following a DLM reset had changed the DLM Policy from SPEED to stable As it had put me on a G.INP re trans High profile for some reason, maybe tt's default

Thats a 4 year old thread you've just resurrected !

I get the same result as BTw checker never work on my G.fast.

But my isp told me that all ip profile will never work on TalkTalkBusiness backhaul ADSL, ADSL2, FTTC & G.fast.

These only work on BTw backhaul ADSL, ADSL2, FTTC & G.fast.

I do believe the ip profile are set below:

IP Profile are 9369% from sync rate 330 = 309 (downstream only) for G.fast (throughput speed 305) BTw Backhaul Profile (low G.INP retransmission Bearer 0 INPRein = 0.00)
IP Profile are 9369% from sync rate 160 = 149 (downstream only) for G.fast (throughput speed 145) BTw Backhaul Profile (low G.INP retransmission Bearer 0 INPRein = 0.00)
IP Profile are 8869% from sync rate 330 = 292 (downstream only) for G.fast (throughput speed 288) BTw Backhaul Profile (high G.INP retransmission Bearer 0 INPRein = 10.00)
IP Profile are 8869% from sync rate 160 = 141 (downstream only) for G.fast (throughput speed 137) BTw Backhaul Profile (high G.INP retransmission Bearer 0 INPRein = 10.00)
IP Profile are 9669% from sync rate 80 = 77 (downstream only) for VDSL (throughput speed 73) BTw Backhaul Profile (low G.INP retransmission Bearer 0 INPRein = 0.00)
IP Profile are 9669% from sync rate 40 = 38 (downstream only) for VDSL (throughput speed 34) BTw Backhual Profile (low G.INP retransmission Bearer 0 INPRein = 0.00)
IP Profile are 9169% from sync rate 80 = 73 (downstream only) for VDSL (throughput speed 69) BTw Backhual Profile (high G.INP retransmission Bearer 0 INPRein = 1.00)
IP Profile are 9169% from sync rate 40 = 36 (downstream only) for VDSL (throughput speed 32) BTw Backhual Profile (high G.INP retransmission Bearer 0 INPRein = 1.00)

Edited by adslmax (Sun 13-Feb-22 10:09:24)

The "IP profile" is something applied by the end ISP on their BRAS, not by the backhaul provider, so that makes no difference.

It is also not the same thing as the line stats that you reported, which are the bit rate on the copper which runs between the cabinet and your property. You certainly cannot view the BRAS profile directly.

However, the ISP does aim to set the BRAS profile at a speed around or just below the line rate; that's to stop the DSLAM being overwhelmed by incoming packets faster than it can send down the copper line (and throwing them away).

In order to learn the line rate, the DSLAM adds some attributes in the PPPoE or DHCP requests that it forwards upstream. Then at the ISP end these get picked up, typically turned into RADIUS attributes, and the RADIUS server selects an IP profile in its RADIUS response.

At least, that's how I understand it works. I'm sure CarlIT will correct me if I'm wrong.

At the moment my ISP Keith agree with me to set the line speed profile at 110% instead of 98% because we both agree that G.fast use SRA and FRA as the speed of sync rate kept changing every half an hour all day as the IP Profile kept changing every 30 minutes but the ISP can't updated to match BRAS IP Profile as it normally updated every 24 - 48 hours.

My current sync now at 244011 - BRAS IP Profile = 228613 ISP IP Profile at 110% = 251474 = throughput speed = 224613 - this throughput speed will stay at all times unless I did soft PPPoE disconnection or a change from DLM force resync.

Edited by adslmax (Sun 13-Feb-22 10:14:27)

In reply to a post by jchamier:

Thats a 4 year old thread you've just resurrected !

Considering the member why are you surprised