You are correct, loads of mention on this forum of this error, but a denial from BT of an issue, and subsequently no cure.
Fundamentally, we need to know what protocol BT use to generate this message in the first place, then we can see how to avoid it. It's a pro forma message so obviously BT had some conditions in mind that it would be generated if it met, 'certain rules', but no one can tell us, hence it keeps happening...
