Do not confuse an answer to a SIP response. 3CX is telling the SIP provider that it cannot process the call, so there is no "answer" (no ack, no ring, etc.).
The issue is that "busy here" (486) is somewhat ambiguous. It leaves open the possibility that there "MAY" indeed be alternate routes available (SIP Proxy). The disaster recovery option being employed by the SIP provider may be how they interpret the alternate route reaction to the 486 response code. It may be possible to work with them to handle the 486 response as shown below instead.
Instead, the alternative response code of 600 could be employed which is essentially a "busy everywhere" (meaning no alternatives). This is reportedly a supported response code within 3CX, but I am not clear as to the conditions by which the response would be engaged. You might want to contact 3CX support or your reseller for more clarity.
I suppose there could be some settings that allow for its use, but a glance at the advanced, custom parameters did not reveal anything that just stood out to me.