Microsoft does not support a third-party SIP proxy or UAS between the Microsoft SIP proxy and the paired SBC that might modify the Request-URI created by the SBC.
Checked 2026-10-02
- Vendor
- Microsoft
- Product
- Teams Phone Direct Routing
- Subsystem
- Inbound call processing
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-10-02
- Checked
- 2026-10-02
Sources
- Teams Phone System Direct Routing: SIP protocol — Microsoft · tier 2 current vendor documentation · Section 'Processing the incoming request: finding the tenant and user', step 5
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-no-ruri-rewriter. WarmTransfer. https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-teams-no-ruri-rewriter
BibTeX
@misc{warmtransfer-claim-sip-404-484-troubleshooting-teams-no-ruri-rewriter,
title = {Troubleshooting SIP 404 Not Found and 484 Address Incomplete call failures: source note sip-404-484-troubleshooting-teams-no-ruri-rewriter},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/sip-404-484-troubleshooting-teams-no-ruri-rewriter},
note = {Source note sip-404-484-troubleshooting-teams-no-ruri-rewriter, checked 2026-10-02}
}