On 20 March 2017 at 17:01, Mike Jenkins <mike.jenk...@poundbury.com> wrote:
>> > Why not have the copper SFP as a default,
>>
>> Why not have fibre as default? - Seriously though, this is document in the 
>> SIN
>> documents, so for future reference, RTFM.
>>
>> "The client interface consists of a RJ-45 type socket for 10 Mbit/s and 100
>> Mbit/s EAD services or dual LC sockets for 1000 Mbit/s EAD services." -
>> http://www.btplc.com/sinet/SINs/pdf/492v1p8.pdf - Section
>> 4.2 Connector.
>>
>
> But the OP ordered his service from SSE - so there's a definite possibility 
> that their ordering process let him (incorrectly) order a copper gig 
> presentation....

If the OP is informed when quoting/ordering the circuit with the
carrier that the tail is coming from OR > read the SIN doc.

When ordering a circuit with a carrier and the B end is off-net for
the carrier (which it sounds like it was), ask the carrier "Who's
providing the tails for this service? OR you say!" > read the SIN doc.

When ordering a circuit with a carrier and it is not explicity stated
that the circuit is on-net or that existing fibre will be used, ask
the carrier "Who's providing the tails for this service? OR you say!"
> read the SIN doc.

Cheers,
James.

Reply via email to