I just can't believe my eyes we are seeing the same situation acting out again this time on the ECI cabinets most people seeing great results and others seeing negative results.
You would have thought Openreach got their fingers burnt with G.INP Mk1 on huawei cabinets in May 2015 and the ECI G.INP rollout would go very smooth this time with the knowledge they gained.
It looks like ECI issue 2 those bloody ECI modems and HH5a but seeing not much activity on BT forums yet the source seems to be coming from the Plusnet Forums
Sorry NS, Ive read your post about 6 times and cant make out what you are trying to say here.
What do you mean about ECI and HH5a and issue 2 and BT and Plusnet forums? Im confused?
This is a totally different issue to what happened with G.INP Mk1. What has happened this time is that a number of users have been unable to obtain PPP. The modem syncs up, but doesn't connect to the ISP.
ie the
ECI Issue 1 problem.
They have identified which lines this problem could to happen to... and for those lines only they have ceased the roll-out regardless if the EU has a problem or not.
I suspect that its the 206 cabs. 206 cabs had some type of new firmware rolled out about 2 months ago.
Those of us on 204 seem ok, but then again anyone on here is most likely to have fully g.inped modems anyhow.
As I mentioned in my earlier post I am speculating about it being 206, it certainly looks like the 206 change could somehow affected something to do with g.inp.. and whatever it is, it causes problems for some people to establish a PPP session.
So it looks like what Openreach is doing is removing g.inp for people on those cabinets so that the affected users can at least get online.
I have a niggle about 206 FEC/EMP whatever number it was, that I cant quite put my finger on... but I wont speculate further and make out 2+2 equals 5
I dont have much more info other than appx how many lines have the potential to be affected but I have absolutely no idea of how many actually are affected - TBH Im not even sure if all ISPs are aware yet.. or even if its filtered down to the OR engineers yet, because its was less than a week ago that they identified the problem.