Microsoft notes 560484 failures may be ignorable when users dial invalid numbers, but can also come from missing SBC configuration in a call transfer scenario (CallType ByotOutUserForwarding).
Checked 2026-10-02
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- Response codes
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- SIP 484 and Microsoft response codes - Microsoft Teams — Microsoft · tier 2 current vendor documentation · Section '560484 ...', suggested actions paragraph 2
Cite this note
APA
WarmTransfer. (2026, October 2). Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-teams-560484-transfer. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-teams-560484-transfer
BibTeX
@misc{warmtransfer-claim-sip-404-484-troubleshooting-teams-560484-transfer,
title = {Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-teams-560484-transfer},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-teams-560484-transfer},
note = {Source note sip-404-484-troubleshooting-teams-560484-transfer, checked 2026-10-02}
}