Transfer Call continuously results in failed state with Teams Call Agent

Question

While following the Azure Communications Calling documentation for transfers, the example goes over how this can be achieved with a Call Agent. The teams Call Agent seems to be quite similar but the transfer to participant functionality always results in a state of failed. The example uses an Azure Communication id as the target participant, is there another format for the teams call agent (ie transfer to another teams id)?

Answer 1

@Hunter Arndorfer Thanks for reaching here! To elaborate-

There is already an active call between the person initiating the transfer (the transferor) and the recipient of the call (the transferee). The transferor decides to redirect the call to another individual (the transfer target).

The transferor initiates this process by making use of the transfer API. The transferee then has the option to either accept or decline the transfer request, and this decision is communicated through a transferRequested event.

The call is only redirected to the transfer target if the transferee agrees to the transfer. To execute the call transfer, the transfer API can be employed. In case any issues or errors arise during the transfer process, you have the option to utilize the transfer API to subscribe to events such as transferStateChanged and transferRequested.

A transferRequested event originates from the ongoing call instance, while transferStateChanged events, along with details about the transfer's state and error, are linked to a transfer instance.

Could you please use below to narrow down on why its failed-

// transfer state
const transferState = transfer.state; // None | Transferring | Transferred | Failed

// to check the transfer failure reason
const transferError = transfer.error; // transfer error code that describes the failure if a transfer request failed

Reference- https://learn.microsoft.com/en-us/azure/communication-services/how-tos/calling-sdk/transfer-calls

Let us know.