no change, 1mb unlimited


Where are you located and which central are you connected to? Is your building old? If so, the pre-installed cables are very old and the twisting is low. What you can do is to bring a decent cat3 cable, or buy cat6e cable and connected directly to Ogero's box. You should also make sure that from the RJ11 side, the twisted pair is still twisted inside the connector in order to reduce the external noise. A good electrician can do that!Obviously wroteHey guys,
I was upgraded to the 16 Mbps Sodetel connection, but I am only geting between 8-10 Mbps.
I contacted Sodetel and they said that I have too much noise on my line. She said that my noise level is 9. (whatever that means).
She suggested I contact an electrician to come "clean" my line. I called an electrician and asked, he didn't know what that meant.
So I changed the filters, and nothing happened. Still getting between 8-10 Mbps.
So what am I supposed to do? What does cleaning a line consist of?
ahk40a wrote
Where are you located and which central are you connected to? Is your building old? If so, the pre-installed cables are very old and the twisting is low. What you can do is to bring a decent cat3 cable, or buy cat6e cable and connected directly to Ogero's box. You should also make sure that from the RJ11 side, the twisted pair is still twisted inside the connector in order to reduce the external noise. A good electrician can do that!
The following is the twisted pair:Obviously wrote
Yes I believe the building we live in is around 40-50 years old.
I live right next to the Badaro central.
1- Where do I purchase these cables from? Would the electrician get these cables if I asked him for them?
2- What is twisting?
3- cat3 or cat6e? or doesn't matter?
4- What is the RJ11 side?
they upgraded our connection to 1.5mbs unlimited plan, Chiyah area, BeirutDarkzoon wroteI am on 1.5 Mbps unlimited and no speed update yet !!!!!!!!!
http://www.speedtest.net/result/3665670004.png
If anyone get the speed update on unlimited plan please confirm .
Envoi d_une requête 'ping' sur www.google.com [173.194.35.113] a
données :
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=98 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=95 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=95 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=98 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=95 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=98 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=96 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Réponse de 173.194.35.113 : octets=32 temps=97 ms TTL=54
Statistiques Ping pour 173.194.35.113:
Paquets : envoyés = 20, reçus = 20, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 95ms, Maximum = 98ms, Moyenne = 96ms
Envoi d_une requête 'ping' sur lux.valve.net [146.66.152.1] avec 32 octets de do
nnées :
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=108 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=106 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=107 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=107 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=103 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=105 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=202 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=104 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=106 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=308 ms TTL=52
Réponse de 146.66.152.1 : octets=32 temps=114 ms TTL=52
Statistiques Ping pour 146.66.152.1:
Paquets : envoyés = 20, reçus = 20, perdus = 0 (perte 0%),
Durée approximative des boucles en millisecondes :
Minimum = 103ms, Maximum = 308ms, Moyenne = 120ms
You can ignore the 300ms, someone was probably eating some bandwidth in the house.