microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Cannot transfer call from bot in Teams client
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Hi,
During some time now we (and our customers) are unable to transfer an established call (between a bot and a Teams user) to another Teams user using the Transfer button in the Teams client. This did work in the past. Only recently we were notified about this problem by one of our customers.
Scenario:
- Bot calls Teams-User1
- Teams-User1 answers call and talks to bot.
- Teams-User1 transfers call to Teams-User2. (this is what fails now)
- Teams-User2 answers call and talks to bot.
In step 3 you get a 'Transfer failed' message in the Teams client (see screen shot). On the bot side there seems to be no indication that something goes wrong. Both a direct transfer as well as a consultative transfer fail.
An example of a call which could not be transferred:
Teams-CallId = 45003980-53f7-40d4-8182-04ef23282313
Time-of-transfer = 2025-12-29 13:24:50 UTC
Library versions:
- Microsoft.Skype.Bots.Media 1.31.0.226
- Microsoft.Graph.Communications.Calls.Media 1.2.0.15533
- Microsoft.Graph 5.94.0
- Microsoft.Graph.Core 3.2.4
Hopefully you can give us some insight in what goes wrong, because this is a use-case that is used by multiple customers of our SaaS-service.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the transfer scenario against the listed Microsoft.Skype.Bots.Media, Microsoft.Graph.Communications.Calls.Media, and Microsoft.Graph versions. Reproduce both direct and consultative transfers using the provided Teams-CallId and UTC timestamp, then compare the Teams “Transfer failed” result with the bot-side behavior; done means identifying a confirmed cause or actionable guidance.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100