The whole point of IPSC is that it allows connection of a customer on a non-WBC-enabled exchange into the WBC backhaul at a later stage in the BT Cloud. As a result of that the ISP can pick get the traffic handed over at one of the 10 IPSC nodes and integrate it into their own backhaul WB(M)C from whatever WBC nodes they are using.
So the fact that your exchange hasn't been enabled doesn't matter.
What does matter,
and I don't know the answer, is whether Plusnet are using IPSC yet - in order to reduce the load on Centrals and either avoid having to add to those or be able to decommission some as their contracts expire. That would still leave the question of whether your exchange was being routed that way.
Which brings us to the other question - so what if you are on IPSC? To which the answer is that the symptoms you are getting are exactly those experienced by many Entanet customers when they introduced these types of connection, and I believe AAISP and BT Total customers have done so as well. For example, see
this AAISP blog.
The BT Wholesale systems and/or DLM on WB(M)C and IPSC still seem to be less than robust, to put it mildly.
As a minor issue, you are right in saying interleaving should not have this effect. The latest BT descriptions of the products say 20-40ms additional latency.
Bob's broadband basic info/help site:
www.robertos.me.uk
ISP history: Demon dialup >> Freeserve dialup >> BT Broadband >> Prodigynet >> Newnet >> O2 Standard.
Purple Cloud for
domain,
email and
web space.
Edited by RobertoS (Tue 09-Feb-10 09:31:02)
Print Thread
c0dec
