SIP 486: Busy Here
SIP 486 is the CallEndReason for a failed Teams Direct Routing call. The recipient or bot was busy. A mismatch between the gateway's cause code and the carrier's expected mapping can also trigger repeated missed calls. Read it together with CallEndSubReason to narrow down the cause.
What to check
- Find the call in the Teams admin centre or the PSTN Quality of Experience report. Copy the Microsoft response code and reason phrase as well as the SIP response.
- Compare the Microsoft response with 10321. The same SIP response can have different causes.
- For repeated missed calls from the same caller, ask the gateway vendor to review the Q.850 mapping. Microsoft documents cause
17for the Direct Routing mapping, while some carriers use cause34for the same SIP response.