Source note · Troubleshooting Teams call queues and auto attendants
For consultative transfers over Direct Routing, calls drop early if the SIP proxy does not get a 202 Accepted and NOTIFY progress from the SBC or the SBC sends BYE too early; the SBC must send 202 and NOTIFY so the proxy can end the original call after a NOTIFY carrying 200 OK.
Checked 2026-09-25
- Vendor
- Microsoft
- Product
- Microsoft Teams Phone Direct Routing
- Subsystem
- transfer
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Issues with call transfers - Microsoft Teams — Microsoft · tier 2 current vendor documentation · Calls drop before the transfer is completed
Cite this note
APA
WarmTransfer. (2026, September 25). Troubleshooting Teams call queues and auto attendants: source note teams-call-queue-troubleshooting-consult-xfer-202-notify. WarmTransfer. https://warmtransfer.net/knowledge/claims/teams-call-queue-troubleshooting-consult-xfer-202-notify
BibTeX
@misc{warmtransfer-claim-teams-call-queue-troubleshooting-consult-xfer-202-notify,
title = {Troubleshooting Teams call queues and auto attendants: source note teams-call-queue-troubleshooting-consult-xfer-202-notify},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/teams-call-queue-troubleshooting-consult-xfer-202-notify},
note = {Source note teams-call-queue-troubleshooting-consult-xfer-202-notify, checked 2026-09-25}
}