<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font color="#CC0000"><font size="3"><font face="Arial"><font
color="#000000">Hi All,<br>
Hopefully someone out there has had a similar problem,
or can advise how best to guide the suppliers as they can't
seem to think out-side the box or flow-chart.<br>
<br>
I had a client churn from Telstra (had been with them for
many years all fine and dandy) to Exetel (Optus Infra) for
both Voice and Data (ADSL2). <br>
<br>
Services worked fine for approx 6 weeks after churn, no
issues, client very happy with service speeds etc on the ADSL2.<br>
<br>
Suddenly, a few weeks ago, the ADSL2 started continually
dropping out, and Voice calls could no longer be made to
non-local numbers (Long Distance call routing failing).<br>
<br>
Tickets logged with provider (Exetel) for the issues and the
tickets promptly closed, and the reasons given were;<br>
<br>
1. Customer chosen Telstra as LD provider, so must get
Telstra to sort it (Not the case, Exetel/Optus is the LD
provider).<br>
2. Customer is 5Km from Exchange, so tough luck, ADSL2
won't work, we will not investigate!<br>
<br>
Residents up and down the same street all have ADSL2 working
fine, as did my client, but even that does not explain why
suddenly, same day, same time, Voice calls to non-local also
don't route.<br>
<br>
Does anyone know what the issue may be, or come across it
before?<br>
<br>
In my mind, it seems there is NO LD provider in the switch
hence any-non-local call fails to be routed. But why did
that interfere with the ADSL? I remember from my old
ARE/ARM days a reload of the switch port data would cure
many ills, but they won't even do any investigation!<br>
<br>
Cheers,<br>
<br>
Mal<br>
<br>
<br>
<br>
</font><b></b></font></font></font>
</body>
</html>