| more crap from Bell! Bell is screwing up the profiles of customers who are being upgraded from 5Mb to 6Mb and putting them on Interleave when they are capable of being on fast path and are now refusing to fix it! I was one of the lucky ones to get their profile fixed a few days ago, but support is telling customers that Bell is refusing to fix this for other customers who were upgraded after me.
This looks like Bell just being jerks because they have to upgrade all the 3rd party ISP customers to 6Mb, so they screw them over by putting them on interleave with high pings. My friend had 5ms pings on speed tests before being upgraded and now they're 65ms. I had the same problem when my profile was incorrectly set to interleave but it was fixed, not so lucky for customers who just got upgraded and are now stuck with high pings. |
|
|
|
 HiVoltPremium
join:2000-12-28
Toronto, ON
kudos:12
 ·TekSavvy DSL
 ·TekSavvy Cable
| Not only that, is that they are screwing with the upstream sync rates of those who are on IKNS remotes, because of the consistant poor 6dB SNR on the upstream even if you are sitting on top of the remote.
5056/800 profile before gets turned into a 6016/512 profile after... When you ask to get it fixed, they say it may cost you the $99 DMC.
--
GO LEAFS GO! |
|
grunze510
join:2009-02-14
Cote Saint-Luc, QC
kudos:1 | My profile got bumped from 5056/800 to 6016/800 pretty much when Bell said they'd start transitioning everyone to 6Mbit/s, I think it was the end of October 2011. It was never bumped down to interleave. I guess I'm just lucky. |
|
| reply to HiVolt
That's exactly what my friend was told by support and that's the same profile. It's crap like this that Bell needs to be forced to stop. |
|
 elwoodbluesElwood BluesPremium
join:2006-08-30
HarperLand
·Cybersurf Intern..
| reply to HiVolt
said by HiVolt:Not only that, is that they are screwing with the upstream sync rates of those who are on IKNS remotes, because of the consistant poor 6dB SNR on the upstream even if you are sitting on top of the remote.
5056/800 profile before gets turned into a 6016/512 profile after... When you ask to get it fixed, they say it may cost you the $99 DMC.
Bell makes money coming and going, they cause a problem and then charge to fix it.
The incumbents won't be satisfied till all the IISP's are gone.
--
No, I didn't. Honest... I ran out of gas. I... I had a flat tire. I didn't have enough money for cab fare. My tux didn't come back from the cleaners. An old friend came in from out of town. Someone stole my car. There was an earthquake....... |
|
HiVoltPremium
join:2000-12-28
Toronto, ON
kudos:12 Reviews:
·TekSavvy DSL
·TekSavvy Cable
| reply to grunze510
said by grunze510:My profile got bumped from 5056/800 to 6016/800 pretty much when Bell said they'd start transitioning everyone to 6Mbit/s, I think it was the end of October 2011. It was never bumped down to interleave. I guess I'm just lucky.
The auto profile thing works if you're not on a shit IKNS remote, as they calculate it by line stats... If you've got a 6dB upstream SNR no matter what the sync rate, the thing lowers the sync rate to "attempt" to make the line stable, even though it's a fake stat...
So you're probably not on IKNS.
--
GO LEAFS GO! |
|
grunze510
join:2009-02-14
Cote Saint-Luc, QC
kudos:1 | He didn't mention the IKNS bug in the first post though. And I'm on an old Alcatel remote, unless it got switched since I got a TP-Link modem. I can't check the remote hardware with the TP-Link. |
|
 andybPremium
join:2003-05-29
SW Ontario
kudos:1 | OrbMT works on the tp-link.On the 8840 anyway so may work on other models |
|
HiVoltPremium
join:2000-12-28
Toronto, ON
kudos:12 Reviews:
·TekSavvy DSL
·TekSavvy Cable
| reply to grunze510
said by grunze510:He didn't mention the IKNS bug in the first post though. And I'm on an old Alcatel remote, unless it got switched since I got a TP-Link modem. I can't check the remote hardware with the TP-Link.
I didn't say that was what happened to the OP. I just mentioned the specific upload problem related to the IKNS remotes, and bell reducing the upload profiles on them when asked for 6meg.
--
GO LEAFS GO! |
|
| reply to eots
My line got upgraded from 5/800 to 6/800 with no problems... had 5/800, line reset, came back 6/800, the end.
As for interleave, have you tried an actual ping test to your first hops going out? If you see less than 35ms, you are effectively on fast-path no matter what the modem tool says. |
|
| reply to HiVolt
I don't know if my friend is on a remote, but I'm definitely not and Bell put my profile on interleave when it works perfectly on fast path. I'll be checking my friends modem stats with the DMT tool. |
|
| reply to HiVolt
You're right my friend is on an IKNS remote and it must be right beside the building for the attenuation to be so low. With stats like this shouldn't the connection be perfectly stable on a full 6Mb/800k fastpath profile? |
|
Reviews:
·ELECTRONICBOX
| reply to HiVolt
said by HiVolt:5056/800 profile before gets turned into a 6016/512 profile after... When you ask to get it fixed, they say it may cost you the $99 DMC.
This explains why my already craptastic upload got worse after the "upgrade"
 |
|
| reply to eots
said by eots:With stats like this shouldn't the connection be perfectly stable on a full 6Mb/800k fastpath profile? Try adding 100m of cat3 wiring between the modem and phone jack... there has been posts in the past about sync/stability/interoperability problems on excessively short loops and in at least one of those, the Bell tech did indeed resolve the problem by adding 100m to the line. |
|
HiVoltPremium
join:2000-12-28
Toronto, ON
kudos:12 Reviews:
·TekSavvy DSL
·TekSavvy Cable
| said by InvalidError:Try adding 100m of cat3 wiring between the modem and phone jack... there has been posts in the past about sync/stability/interoperability problems on excessively short loops and in at least one of those, the Bell tech did indeed resolve the problem by adding 100m to the line.
Interesting... I can play with that at work, just wire up a spool of CAT5 in between the modem and the splitter...
--
GO LEAFS GO! |
|
 Talon88 The One
join:2003-08-13
Toronto
3 edits | reply to eots
:::
Yes, I am now One of the Victim....
TekSavvy Support is still working on my issue with Bell.
Bell even put me on 3M & 512K Interleave....
See the Prove.... Fu?K Bell..!!
::: |
|
HarawayPremium
join:2008-07-19
Montreal, QC | reply to eots
I posted in the Direct Forum, requested the 5m to 6M upgrade. Was told:
quote:
The downstream could come up for sure but they may lower the upstream to 512k as its using 100% of the capacity to attain 800. Could cause some errors and generally they will lower it.
Line Status: In Service UpTime: 5720940
Line Profile Name: al1_d5056-5056-384_u800-800-256 Last State Change: 12/05 19:39:19
DLM State: DISABLED Equipment Type: OSLAM
Operational Status Speed (Kbs) Relative Capacity Occupation (%) Noise Margin (0..31 dB) Signal Power (0..20 dBm) Attenuation (0..60 dB) Block count
UpStream 800.0 101.0 5.0 12.0 0.0 945707392.0
DownStream 5056.0 44.0 25.0 8.0 4.0 1232542336.0
What that means is your upstream is running on a 101% at 800kbps, but you downstream is 5056kbps at 44%, so if we request raising your line bell will automatically lower you upstream to 512kbps since it is overloading at 800kbps.
These are my DSL details on my ST516:
quote:
Uptime:67 days, 2:00:45
Modulation:G.992.1 annex A
Bandwidth (Up/Down) [kbps/kbps]:800 / 5.056
Data Transferred (Sent/Received) [KB/KB]:0,00 / 0,00
Output Power (Up/Down) [dBm]:12,5 / 5,5
Line Attenuation (Up/Down) [dB]:17,5 / 4,0
SN Margin (Up/Down) [dB]:6,0 / 25,5
Vendor ID (Local/Remote):TMMB / IKNS
Loss of Framing (Local/Remote):0 / 0
Loss of Signal (Local/Remote):0 / 0
Loss of Power (Local/Remote):0 / 0
Loss of Link (Remote):0
Error Seconds (Local/Remote):0 / 0
FEC Errors (Up/Down):0 / 0
CRC Errors (Up/Down):0 / 0
HEC Errors (Up/Down):0 / 0
I've been following the Official thread on the 5M to 6M upgrade, and feel very hesitant to let TSI go ahead with my request right now. It's looking more and more like Bell is doing this intentionally and TSI shouldn't be letting them get away with it. We shouldn't be required to buy 100m of cat3 wiring to get this promised upgrade to work. So many are reporting having their downstream lowered, and/or their upstream lowered to 512k. Jeesh. I'm only 3 blocks from a CO, fwiw. |
|
andybPremium
join:2003-05-29
SW Ontario
kudos:1 | Ikns remote.Just tell TSI_Martin and he will fix it.Those remotes always show 6db on the upstream and max occupancy |
|
HarawayPremium
join:2008-07-19
Montreal, QC | andyb, do you think it would be better doing that in the Official upgrade thread, or in the Direct Forum where I have a upgrade request pending with 2 other staff members? |
|
| reply to andyb
When I got the line stats right from the modem it was sufficient proof that my friend was practically on top of the IKNS remote, I also had to explain to the Teksavvy support rep that the IKNS remotes always show low SNRM and that Bell should know this and raise the profile. The next day the profile was put back on fastpath and the upload was increased from 512 to 768. I'm not sure why they didn't just increase it to 800, I guess just Bell being jerks as usual. |
|
