Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
10,515 questions
Teams Direct Routing - Call Queue timeout redirection splits call across multiple callRecords
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 92%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERG%3C/text%3E%3C/svg%3E)
Ronan Gibney
1
Reputation point
We have an application that subscribes to change notifications on the /communications/callRecords endpoint subsequently retrieves callRecord data.
We are seeing unexpected behaviour in the following scenario
- We receive an incoming call to an auto attendant via direct routing
- This is then transferred to a call queue that has "conference mode" turned on
- The call timeout threshold is reached and the call is redirected to a specific teams user
- The user does not answer and the call eventually goes to voicemail
In this scenario we get notifications for two distinct call records rather than a single call as anticipated. The first callRecord contains all the call details up to the point when the call queue timeout is reached, the second callRecord just contains the redirection to the teams user.
I would have expected all call details to be contained in a single callRecord.
Is this a known issue or expected behaviour?