I had approximately 97 hours of solid connection with:
connection rate 19544 Kbps SNR 5 or 6 dB and Loop Att 23 dB
no interleaving.
At that time ATM stats were:
more than 367000000 RX cells and approx 17100 RX Errors
Then for no apparent reason the exchange dropped the connection and resynched with:
18182 Kbps SNR 5 dB ant Loop Att 23 dB
Interleaving ON.
Now with 97 hours of uptime it must have been a stable connection, and surely 17100 RX Errors out of more than 367000000 RX cells isn't a high error rate, so why did the BT equipment decide to resynch with interleaving on?
Sean
It suddenly did this for me too about a year ago. I asked IDNet to ask BT to turn the interleaving off again and it was done within a day. The mysteries of BT algorithms are unknown to all. Especially BT.
Smoke and mirrors, eh? :)
for customer in customerlist:
customer.dsl.interleave = math.random()
Hell, they could be right *up to* 50% of the time!
;D
Quote from: esh on Sep 25, 2010, 11:53:21
for customer in customerlist:
customer.dsl.interleave = math.random()
Hell, they could be right *up to* 50% of the time!
Nah, I think they have a drinking bird wired up to the exchange, one on each line. If it stops dipping, you get interleaving turned on! :eek4:
Quote from: Technical Ben on Sep 27, 2010, 21:37:11
Nah, I think they have a drinking bird wired up to the exchange...
Funny you should say that. I'm sure the last one I spoke to had had a few... ;D
The BT algorithms are indeed esoteric...
Yesterday morning, after about 140 hours uptime and again for no apparent reason, there was a resynch by the exchange (coincidentally giving me higher sych rate) and this time interleaving was turned OFF again.
This is how I would prefer it, but I thought that once it was automatically turned on it wouldn't automatically turn off again?
Sean
Hi SSK,
If your interleave is set to auto it "should" be activated and then deactivated when BT's systems deem fit.
ie...randomly!