IPC6023 Error

[mcgall05]

I've had IPC error on tv since i got ee broadband and tv in November, spoke to EE multiple times, spoke to TMC multiple times, replaced tv box. On weekend had 3 engineers out which broke my broadband. Broadband is back up today and get the same error code IPC6023. All channels work fine for a minute or 2 then freeze and then the error comes back on. Broadband and equipment is all EE, router is a couple of meters away from tv box, no aerial so it's all through multicast, which appears to be the problem. Is there anything else to try or, given its been 2 months and nobody can fix, do I have to admit defeat and seek a different option for live TV?

[CustardCreams]

Have either of you had a resolution as yet to the ipc6023 issue? I'm now on day 119 and it is still 'under investigation'. 

[Emma7577]

No we pulled out of the contract in the cooling off period. However that gave me a load of new issues, where despite accepting the cancellation at day 9 of the cooling off period and trying to convince us to stay for the remainder of the time, they didn't process it for a further 5 days and then tried to take us for £227 cancellation fee, outside of the 14 days! That took a further 5wks for them to remove from the account, despite telling us they knew it was their error and it still being forwarded to debt collectors.

And all this when we are still EE customers with phones with them! You couldn't write how terrible the service has been if you were the most fantastic story teller ever! In total I've racked up 8hrs of my time on the phone to them (mainly being put on hold listening to their awful hold music of 3 songs on repeat,)!

I hope you get this sorted but I think you're in for a lot more inconvenience along the way. 

[mcgall05]

I moved to the apple tv box, worked fine since the change however I still get the standard text messages advising ee are still looking into the Ipc6023 error so it's fairly obvious that the various departments don't communicate and as I can't contact the department that is apparently looking into the error I can't advise them myself. Your far more patient than I am, 119 days to wait is shocking. 

[CustardCreams]

Update: Day 139 of the error message IPC6023 unresolved.

After telephoning 150 I now found out after all of this time I am NOT entitled to the auto compensation offered for issues with EE. I have been wrongly advised on more than one occasion by EE Guides that I would be entitled and this offered some small comfort to this whole saga of endurance and extreme patience. I will now have to go through the manual compensatory route for whenever this issue is finally resolved. I have no idea as to when that will be as the sms messages from TMC dept are generic and word for word the same every fortnight or so. For a communications company this is extremely poor. I would like to speak to someone within EE about this , other than a guide, but this seems near on impossible.

[Midnight_Voice]

@CustardCreams 

As per Mandy Rice-Davies “Well, they would say that, wouldn’t they?”

If Multicast isn’t working on your broadband, then you have a broadband fault.

Unless EE (not EETV) are somehow trying to claim otherwise?

I suggest you get on to Ofcom and see what they have to say.

[CustardCreams]

Thanks MV, I was advised that auto comp payment is for 'total loss of service' only, it could be argued this is only partial maybe? May well be worth a visit to Ofcom. Received a call today which it was nice to talk through the issue with a human being however there remains no timeframe for a fix and no mention of any appropriate compensation until this is (if ever) resolved. An Apple TV box was suggested as a possible alternative should I so wish.

ps I had to google who Mandy Rice-Davies is, I thought you meant she had replied that to my post and I couldn't see it!! 🙂 🙂

[John3181]

Has anyone had this issue resolved yet, everything was working fine until yesterday, then I had this new full fibre  fitted and bang this stupid code appears, been on phone with EE for hours and still not resolved