I had a similar problem. My phone line is on Home Highway and was rerouted
to a fairly distant exchange. Having spoken to a few people decided to get a
second line installed as my exchange was due to go broadband on 15/6/2005. I
did specify that as the line was for broadband it had to be on the local
exchange and that it was a non dacs line...BT seemed ok with these
specifications. I kep on the second line until I was sure that the broadband
connection would be ok. This was just as well as the RFS date on my local
exchange was delayed from 15/6 to 6/7and later to 20/7. These delays seem to
be increasingly common with "remote" exchanges.
Hope this helps,
Alan
"Rev Adrian Kennard" <`@o.gg> wrote in message
news:42d23d0d$0$38039$(E-Mail Removed).. .
> Ron Lowe wrote:
>> Hi, all.
>>
>> A work colleague has the following dilemma:
>>
>> He lives in a remote rural location.
>> The exchange is literally at the bottom of his garden, and has an RFS
>> date
>> Real Soon Now, so he's looking to get ADSL installed. So far, so good.
>>
>> Here's the problem.
>> His existing phone line does not come from that exchange.
>> It comes from a distant ( 10 miles++) exchange.
>> The reason for this is historical, perhaps due to the fact the previous
>> occupant had ISDN installed, and the local exchange wasn't up to it.
>>
>> So, what's the solution?
>>
>> I don't think a Managed Conversion will work: the BT engineer will just
>> look
>> at the ADSL possibility of the existing line.
>>
>> I doubt BT would move the line to the local exchange 'just for the
>> asking'.
>>
>> The only solution I can suggest it for him to order a new line, to be
>> provisioned from the local exchange, and then cease the old one.
>> Perhaps a
>> so-called 'Combined Order' would be the most appropriate?
>
> Sounds like probably the best bet and minimum risk.
>
>> Any comments or suggestions?
>
>
> --
> Rev Adrian Kennard
> Andrews & Arnold Ltd
> Broadband internet, fixed IPs, VoIP equipment, FireBricks and more.
> http://aa.gg/