microsoftgraph / microsoftgraph/microsoft-graph-comms-samples
Bot webhook data `callChainId` no longer persists on transfers
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 253
- Forks
- 275
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 1
Description
Describe the issue
Recently (around 2022-01-05) the json data we receive on our bot webhook has changed. A call flow such as:
- pstn calls a teams user
- teams user transfers to another user
- both legs would have a matching
resourceData.callChainId
Now when transferring the resourceData.callChainId is different and we get resourceData.incomingContext.transferor instead
Expected behavior
We would expect the resourceData.callChainId to persist across a transfer, is this not the purpose of that id?
Graph SDK (please complete the following information):
Not an SDK issue, this the bot webhook configured in Azure.
Additional context
Is this the intended behaviour now? If so is there anywhere we can subscribe to future changes as this is a breaking change.
Also please let me know if there is a more appropriate place to log this issue, it is not clear where this should be reported.
Many thanks!
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
The issue identifies an Azure bot webhook and the transfer fields resourceData.callChainId and incomingContext.transferor, but names no repository files, tests, or entry points. Start by checking the webhook behavior around transferred calls; this is done only when the intended persistence behavior and an appropriate reporting or subscription path are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100