From: Babyack, Sharon (SEN)
Sent: Monday, 22 December 2003 5:53 PM
To: ECITA, Committee (SEN)
Subject: FW: Follow up to Senate Inquiry session

-----Original Message-----
From: Brian Beckor [mailto:brianb@callpoint.com.au]
Sent: Thursday, 13 November 2003 14:03
To: 'Sinclair, Rosemary'
Subject: Follow up to Senate Inquiry session



Hi Rosemary 
 
Thanks again for the opportunity to participate.  
 
I've become increasingly aware of regional deployment issues as a result of recent discussions with a carrier that plans to deploy its own DSL infrastructure into these areas.  To summarise:
 
A. EXCHANGE AND RIM BOUNDARIES
Firstly, as discussed, there is the need for Telstra to offer exchange and RIM boundaries that cover ALL exchanges, not just those that are DSL enabled. This is particularly important for regional/ rural where exchange service areas are much greater than in metro.
 
This information, and all boundary information, needs to be supplemented
with:
* A list of Telstra exchange addresses (so that exchange-customer distance etc computations can be performed),
* And a list of sub-exchange addresses
I understand Telstra's sensitivities regarding security of its assets but believe that this can be adequately accommodated with appropriate NDA etc.  In any event, the location of many of its metro exchanges is identified in street directories (though not in a conveniant electronic form and does not cover sub-exchanges)
 
B. EXCHANGE PREFIX LISTS
Secondly, there is a need for Telstra to publish telephone prefix lists that cover ALL exchanges, not just those that are DSL enabled.
 
The prefix list aspect is even more intruiging when one considers that early this year, Telstra removed access to its "Neighbourhood Call" exchange prefix list.  This list covered all 5,000 exchanges and was accessible from Telstra's web site.
 
Accordingly, and to better support the needs of innovative regional carriers and providers, I believe that Telstra should provide industry
with:
* A regularly maintained prefix list for non-DSL enabled exchanges
* That this prefix list should contain critical fields such as ESA code, CCA and State for each prefix as per the DSL-enabled prefix list available from: http://telstrawholesale.com/products/access_broadband_reports.htm
 
 
Please let me know if you need further clarification.
 
Kind regards
Brian