Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
853 questions
ACS Client (using Teams Identity) fails to terminate replaced call with Teams Calling Bot
![](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(134.4, 4%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
Dr Dave H
150
Reputation points
We are using the Azure Communication Calling client library for JavaScript (latest stable (v1.28.4)) to build a web-based softphone for voice calling. The client is using the Teams interoperability option of having the identity as a Teams user (rather than the BYOI model).
We have identified a small issue when interoperating with a Teams Calling Bot where the ACS client is being adding into an existing call and having a separate 1-2-1 call with the Bot being replaced. In this situation the ACS client library is not terminating the replaced call, which we believe it should be.
This situation is similar to a consultation transfer, with the ACS client being the "transfer target"; in this case the ACS client library does terminate the replaced call, which leads us to believe there is a bug in the library for handling the Bot scenario previously explained.
From the ACS logging we can see that the incoming call is correctly identified as a "replaces" call. Our code accepts the call but it appears that the stack doesn't terminate the replaced call.
`10:04:09.157 useAcs.js:118 azure:ACS-calling:info 2024-09-19T09:04:09.157Z CallClient1:CallStack:PluginlessStack:CallRegistry/ace44ee6:IncomingCallMessageHandler Incoming transfer paylod,{`
` "body": {`
` "evt": 107`
` },`
` "callerId": "28:u18",`
` "groupId": null,`
` "conversationId": null,`
` "convoCallId": "2101c865-f1ec-4e5c-888f-c12b5c11da67",`
` "isMultiParty": true,`
` "fromMixer": true,`
` "ngcCall": true,`
` "participantId": "e9877acc-3d6e-4a4d-8362-56ac3426db63",`
` "callType": "replaces",`
` "consultativeCallId": "d5540b61-c678-42bf-ac9f-062b646bf47f",`
` "messageId": null,`
` "transferorId": null`
` }`
` 10:04:09.158 useAcs.js:118 azure:ACS-calling:verbose 2024-09-19T09:04:09.158Z CallClient1:CallStack:PluginlessStack:CallRegistry/ace44ee6:IncomingCallMessageHandler:[350ece73][handleIncomingCall] replacementCall=true`
Steps to Reproduce;
1. Make call (#1) from ACS client (Teams user 1) to Teams Calling Bot
2. Teams Calling Bot answers the call and makes a new 1-2-1 call (#2) to another ACS client (Teams user 2)
3. ACS client (Teams user 2) answers call (#2)
4. Teams Calling Bot adds ACS client (Teams user 2) into call #1, replacing call #2
As mentioned, at this point the ACS client (Teams User 2) accepts the new call but call #2 does not get terminated
Note, if a Teams Desktop Client is used in place of the ACS client, then everything occurs as expected with the replaced call being dropped.
We believe we are handling the incoming replaces call correctly but we were unable to find any documentation on how best to handle the incoming call as a "transfer target".
We have full ACS logs for this call if required.
Any help in this matter will be gratefully received. Many thanks in advance, cheers Dave
{count} votes
-
![](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(185.6, 59%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESM%3C/text%3E%3C/svg%3E)
SnehaAgrawal-MSFT 21,506 Reputation points2024-09-23T06:02:19.22+00:00 @Dr Dave H Thanks for asking question! Clarifying questions-
- You say this is similar to 'consultative transfer' - to me it sounds exactly the same, question is, why are you not doing the consult transfer ?
- Is this "Teams bot" a graph bot ? Graph supports transfer, so the bot should be able to transfer Teams user 2 to Teams user 1.
- Ideally, transferor ( in this case bot) hangs up the call with transferee (#2) when the transfer is successfully completed - you can follow the 'transfer to call a.k.a consult transfer' quickstart here on how to handle this from ACS SDK https://video2.skills-academy.com/en-us/azure/communication-services/how-tos/calling-sdk/transfer-calls#transfer-to-call
-
Dr Dave H 150 Reputation points
2024-09-23T09:26:54.48+00:00 Hi @SnehaAgrawal-MSFT , many thanks for your response. In answer to your questions;
- We are not using a consultative transfer as we need the Bot to remain in the call.
- Yes, the Teams Bot is using the Graph Cloud Communications API. As mentioned above, if we use a Transfer operation then the Bot will drop out of the call but we require it to remain a participant. [As an aside, we did try the consultative transfer scenario to see if that had a similar issue, however, that failed with the ACS client acting as the transferee generating the error "Connected:TransferFeature::Call(id='f71a5c93-9a94-4144-bc1c-f9e3a9799110', state='3') Transfer to target failed at call start"]
- Agreed, the transferor should drop the call with the transferee but in this case the ACS client is essentially the transfer target, so it should drop the replaced call with the Bot. When we use a Teams desktop client, we see it drop the call to the Bot.
Sign in to comment
Sign in to answer