The called party is busy everywhere it could be reached, not just at this one endpoint (Busy Everywhere) -- distinct from 486, which is only busy at this one location.
In the status line of a SIP response, often with Reason and Warning headers that say more.
Got a trace with SIP 600 Busy Everywhere? Drop it in the analyzer: it finds the step that really failed first, which node sent the code and what to ask the other side. Captures, test-system PDFs and vendor exports. 5 free analyses a month, no sign-up.
Analyze a trace free