Slashdot Mirror
A Possible Cause of AT&T's Wireless Clog — Configuration Errors
AT&T customers (iPhone users notably among them) have seen some wireless congestion in recent months; Brough Turner thinks the trouble might be self-inflicted. According to Turner, the poor throughput and connection errors can be chalked up to "configuration errors specifically, congestion collapse induced by misconfigured buffers in their mobile core network." His explanation makes an interesting read.
You see, most blokes, you know, will be buffering at ten. You're on ten here, all the way up, all the way up, all the way up, you're on ten on your buffer. Where can you go from there? Where?
I don't know.
Nowhere. Exactly. What we do is, if we need that extra push over the cliff, you know what we do?
Put it up to eleven.
Eleven. Exactly. One more buffered.
When did you last meet an unfunny penis?
When did you last meet an unfunny penis?
Probably when he met the guy that modded that comment down.
I walk around until I see an incoming arrow. I freeze and
people and cars crash into me
Maybe some PHB equates packet loss with dropped calls, and told the engineers that packet loss would also equate to job loss. Not the first time a person in authority forces a bad configuration choice based on a complete misconception of a situation.
When I saw Cowboy Neal's.
There is actually no standard scale for signal bars on a mobile phone. As such, the mobile phone manufacturer implements a scale pretty much however they want. The upshot of this is that when the signal strength is the same, one model might show 4 bars but another only 2.
Years ago Nokia was notorious for showing a stronger signal than other phones did - meaning that when people sat around and compared the number of bars they had, the Nokias always looked the best - even though the actual strength was the same. I'm not sure if that is still the case.
Avantslash - View Slashdot cleanly on your mobile phone.