The price is about 1 month of my brother income, So it's a lot.
the bad news is the Mikrotik is only brand which is accepted by my country ISPs.
Which seems to be related, other vendors may be prohibitively expensive or embargoed. And they don't support NV2 of course.
They already have connected me to another radio but problem still exist, we also tested both protocol, 802.11 and nv2, on both of ISP radios, but it didn't change anything. The solution that is mentioned before, also worked on the new destination radio(Disabling other clients). About changing MAC, they(ISP) said that they already had this problem with one of their customers and problem fixed by changing connection into PTP, So it means even changing MAC may not solve the problem.
If replacement of the whole device hasn't helped, it seems logical that replacing a MAC address will not help either.
The way you describe it, it sounds as an issue with the wireless protocol where some of the other clients on the same AP is sending when it is not supposed to, interfering with the signal from your LHG5, or the AP not allowing your STA to send for quite a long period of time. This is something that can only be debugged the way I've described before, i.e. using a third radio to passively listen to the wireless traffic and then analysing the captured communication, and it needs an experienced WiFi specialist to find the issue and identify the guilty piece of equipment.
I am afraid no tools capable of analysing NV2 traffic exist outside Mikrotik's lab, so such an analysis can only be done when the whole cell runs 802.11.
What surprises me most is that those other clients (companies) connected to the same AP don't complain, as this issue should affect every client on the same AP, not just a single one. Do they use LHG5 as well? Can the ISP eventually switch them off temporarily in the afternoon one by one (which can be done remotely using the delay
command), to possibly identify a single client device that misbehaves?