General Discussion
  >> Fibre Broadband


Register (or login) on our website and you will not see this ad.


Pages in this thread: 1 | 2 | (show all)   Print Thread
Standard User philjohn
(newbie) Mon 25-Jul-16 13:09:34
Print Post

Query about a Cab status - 29 connected to Dunchurch


[link to this post]
 
As per the subject, we've just moved to this area and having had Infinity 2 previously, 3.5Mbps is hurting badly right now! It's Cabinet 29 connected to the Dunchurch exchange (CV22 7FA is the postcode)

Wondering if it's just a case of more ports, or if the cab is actually full and will need a 2nd one installing. Any help gratefully received.

Phil.
Standard User Ribble
(fountain of knowledge) Mon 25-Jul-16 14:14:52
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: philjohn] [link to this post]
 
Cabinet is full. A 2nd cabinet is being planned
Standard User philjohn
(newbie) Mon 25-Jul-16 14:19:23
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: Ribble] [link to this post]
 
Thanks for the response, that's something then ... do you know the new cabinet number by any chance? Out of interest ... where do you get your info from?

As for the waiting list ... is BT Retail able to place you on it in case a subscriber currently on the cab ceases their service? They don't seem to know anything about the waiting list ...


Register (or login) on our website and you will not see this ad.

Standard User lee111s
(experienced) Mon 25-Jul-16 14:39:49
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: philjohn] [link to this post]
 
BT Retail don't use the waiting list feature. I'm not aware of any ISP's that do.
Standard User philjohn
(newbie) Mon 25-Jul-16 14:52:50
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: lee111s] [link to this post]
 
Interesting, that seems to contradict some of the info elsewhere on the forum (see the poor person who had their infinity disconnected when they re-contracted and had to be added to the waiting list ... discussion about whether they should be bumped up to the top of it).
Administrator MrSaffron
(staff) Mon 25-Jul-16 15:16:33
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: philjohn] [link to this post]
 
You will remain on cabinet 29, just that it will have two fibre twins

The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
Standard User lee111s
(experienced) Mon 25-Jul-16 15:45:33
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: philjohn] [link to this post]
 
As a one off perhaps, but they don't have the functionality built into their ordering system so that it allows an order to be placed when there's no capacity.
Standard User Ribble
(fountain of knowledge) Mon 25-Jul-16 16:21:40
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: lee111s] [link to this post]
 
From experience the availability checker goes to waiters as soon as the cab is out of capacity, regardless if there is actually a waiting list.
Standard User philjohn
(newbie) Mon 25-Jul-16 17:22:10
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: MrSaffron] [link to this post]
 
Hi,

Sorry, I meant the number of the new fibre twin - when I used code check I see that there are several cabs in the planning/design phase (numbered E then a number) whereas the FTTC Cab is P29 ... wanting to find out if it's in the tranche they expect to install by Jan 2017 or June 2017 - if it's the latter it makes sense for me to get a 4G mobile broadband contract for working from home, if the earlier I can suffer for 6 months.
Standard User BatBoy
(sensei) Mon 25-Jul-16 17:26:22
Print Post

Re: Query about a Cab status - 29 connected to Dunchurch


[re: philjohn] [link to this post]
 
The current fibre twin "number" is NMBZAS. The PCP is number 29. The E number you refer to is simply a bundle of cables from the exchange.
Pages in this thread: 1 | 2 | (show all)   Print Thread

Jump to