I have created a support ticket with the Ticket ID: 4495130 .
amx wrote:Today the subcontractors came. They spent more than four hours going from pit to pit and to the pillar.
I was with them most of the time, as couldn't work anyway (working from home).
The problem was with a short (not a complete short more like a leakage) through the line. It happened to be from the cables in one of the pits.
The cable had water in it, and despite all effort, apparently the cable enclosure had been breached. Cleaning it up and repatching didn't help, and they were saying that this could be due to the gels in the cable, which overtime can harden and cause trouble.
The line could not be repaired without cutting up the cable, and they said that they are not allowed to do that. So they had to find a good spare cable and swap the line pit by pit, and at each point ask optus to run the tests and pass it.
At a couple of points the line resistance was 800 Ohm and optus did not pass. Aparently it has to about 1000.
The credit should go to the contractors with persisting with it and not taking shortcuts.
The guys that worked on this issue should really be commended.
The line is back up now. I will monitor and report back in a couple of weeks as of the stability.
amx wrote:Unfortunately, it happened again. Today when I came back home, I noticed the speed had dropped to below 3mbps, with all high speed tones missing. I tried several reboots to finally get a 10mbps speed.
I am really running out of things to test here. What I think is happening is this:
For some reason the ATU-C goes into a low power mode, or maybe as a result of an event (a shock, high voltage interference, some solar storm or ET phenomenon) decides to change the profile to a low speed one, and holds onto this profile.
If this is a power mode issue, the first thing to ask is "does exetel support power mode switching?".
If no, then is there a log that indicates something disruptive has happened, or any reason why a new lower speed profile has been used?
If there is no log, can this be set up to monitor the line behavior over some period?
If exetel uses power state switching, then can this be the cause?
Could this be a fault at the exchange?
Users browsing this forum: Google [Bot] and 1 guest