I have been having ongoing connection issues with my VFX service for over 6 months. Was initially advised that my first router, less than 6 months old, was broken and needed a new one. Brought a new cisco SRP527W which did not improve the situation: continued dropoffs of up to an hour. Over the past month the dropoffs have become more regular and for longer periods. After ringing the help desk several times a linecheck was done and a "fault" fixed by telecom....yeh right. Drop offs have continued. Rung the helpdesk again and was told that "yes you are having alot of dropoffs and your download speed is pitifull, I will investigate this further. You (me) should ring back on tuseday for an update". Which I did. And was told by some amature that I should expect at least 2 dropoffs a day and I would be lucky to be getting 2Mbs download speed Max. And that Xnet would not investigate further untill I was getting "at least 10 dropoffs a day for a week". So the following week the line gets worse untill no connection at all. Several phone calls to xnet later and a fault is finally registered with Telecom again. After having no internet for 3 days I recieve an email saying the fault has been fixed by Telecom. Yes I do now have a connection but it still drops off as you can see via the Router Log:
Log List
Summary
Apr 19 13:54:10 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 13:54:16 SRP527W daemon.notice cmd_server: handle_wan_done: PVC 1 is up
Apr 19 14:07:35 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:08:05 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:08:48 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:09:07 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:18:40 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:19:09 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:19:34 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:19:49 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:20:05 SRP527W daemon.notice cmd_server: handle_wan_down: PVC 1 is down
Apr 19 14:20:14 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:20:58 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:21:23 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:22:01 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:22:26 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:23:10 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:23:14 SRP527W daemon.notice cmd_server: handle_wan_done: PVC 1 is up
Apr 19 02:23:51 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 02:24:21 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 02:24:41 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 02:25:02 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 02:25:12 SRP527W daemon.notice cmd_server: handle_wan_down: PVC 1 is down
Apr 19 02:25:25 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 02:25:54 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 02:26:06 SRP527W daemon.notice cmd_server: handle_wan_done: PVC 1 is up
Apr 19 02:26:07 SRP527W daemon.notice cmd_server: handle_wan_done: PVC 1 is up
Apr 19 14:26:34 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:26:53 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:27:18 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 14:27:32 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 14:27:57 SRP527W daemon.notice cmd_server: handle_wan_down: PVC 1 is down
Apr 19 14:28:04 SRP527W daemon.notice cmd_server: handle_wan_done: PVC 1 is up
Apr 19 15:25:37 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 15:26:06 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 15:26:43 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 15:27:02 SRP527W daemon.notice cmd_server: handle_wan_down: PVC 1 is down
Apr 19 15:27:29 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 15:27:40 SRP527W daemon.notice cmd_server: handle_wan_done: PVC 1 is up
Apr 19 15:28:38 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 15:29:07 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 15:34:42 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 15:35:32 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 15:35:53 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 15:36:08 SRP527W daemon.notice cmd_server: handle_wan_down: PVC 1 is down
Apr 19 15:36:22 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 15:36:47 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 15:37:10 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 15:37:16 SRP527W daemon.notice cmd_server: handle_wan_done: PVC 1 is up
Apr 19 15:38:58 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 15:39:27 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 15:56:02 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 15:56:21 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 16:12:04 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 16:12:46 SRP527W daemon.notice cmd_server: DSL is UP
Apr 19 16:14:19 SRP527W daemon.notice cmd_server: DSL is DOWN
Apr 19 16:14:36 SRP527W daemon.notice cmd_server: DSL is UP
And thats just since I've been home from work.
Anyways back to my original question: How long does it take to get Xnet to make Telecom to properly fix a fault on its network?