Consultative transfer of phone calls not possible anymore

%3CLINGO-SUB%20id%3D%22lingo-sub-2457179%22%20slang%3D%22en-US%22%3EConsultative%20transfer%20of%20phone%20calls%20not%20possible%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2457179%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20community!%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3CP%3EWe%20are%20facing%20the%20following%20issue%20since%208th%20June.%20When%20our%20app%20is%20doing%20a%20consultative%20transfer%20of%20an%20audio%20call%2C%20we%20receive%20the%20%22tranferAccepted%22%20commsNotification%2C%20but%20the%20call%20is%2C%20in%20fact%2C%20not%20transfered%20or%20is%20automatically%20terminated%20after%20a%20short%20moment.%3C%2FP%3E%3CP%3EThe%20call%20objects%20(checked%20via%20Graph%20API)%20are%20still%20in%20the%20state%20of%20before%20the%20transfer%2C%20which%20does%20not%20make%20any%20sense%2C%20because%20we%20received%20the%20transferAccepted%20and%20onHold%20messages%20for%20the%20respective%20calls.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWith%20consultative%20transfer%20I%20mean%3A%20I%20call%20the%20transfer-target%20person%20before%20the%20transfer%20and%2C%20if%20accepted%2C%20the%20original%20call%20is%20then%20transfered%20to%20that%20target%20user%20with%20option%20%22replacesCallId%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20reproducing%20this%20process%20with%20standard%20auto%20attendants%2C%20we%20get%20the%20same%20issue.%20Especially%20strange%3A%20the%20transfer-target%20user%20needs%20to%20accept%20the%20transfered%20call%20twice%20to%20actually%20accept%20the%20transfer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20MS%20support%20is%20not%20reacting%20to%20the%20ticket%20I%20opened%20for%20three%20days%20now.%20%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2F%40FE3C8A5543DEF164D4C09E9B7F45E1A4%2Fimages%2Femoticons%2Ffacepalm_40x40.gif%22%20alt%3D%22%3Afacepalm%3A%22%20title%3D%22%3Afacepalm%3A%22%20%2F%3E%20This%20is%20a%20big%20issue%20for%20us%2C%20though.%20Do%20you%20understand%20what%20might%20have%20changed%20around%20the%208th%20June%3F%20This%20process%20was%20working%20flawlessly%20before.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20This%20only%20happens%20when%20the%20initially%2C%20to-be-transfered%20call%20is%20via%20phone.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2457179%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECalling%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2462280%22%20slang%3D%22en-US%22%3ERe%3A%20Consultative%20transfer%20of%20phone%20calls%20not%20possible%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2462280%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1011388%22%20target%3D%22_blank%22%3E%40andreasjm%3C%2FA%3E%26nbsp%3B-%20Thanks%20for%20reaching%20out%20to%20us%2C%20let%20me%20check%20this%20issue%20with%20internal%20team%20and%20will%20get%20back%20to%20you.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2469261%22%20slang%3D%22en-US%22%3ERe%3A%20Consultative%20transfer%20of%20phone%20calls%20not%20possible%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2469261%22%20slang%3D%22en-US%22%3E%3CP%3ELet%20me%20add%20a%20detail.%3CBR%20%2F%3EIf%20you%20transfer%20a%20call%20coming%20from%20a%20regular%20Teams%20client%2C%20it%20works%2C%20as%20I%20said.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20transfer%20a%20call%20coming%20from%20a%20telephone%20(associated%20with%20an%20application%20instance)%2C%20then%20the%20attached%20commsNotification%20is%20received%20after%20the%20transferAccepted%20notification.%20The%20referenced%20call%20is%20the%20transfered%20one.%3C%2FP%3E%3CP%3EThis%20does%20not%20come%2C%20when%20using%20a%20Teams%20client%20instead%20of%20a%20phone.%3C%2FP%3E%3CP%3EThis%20message%20is%20not%20documented%20and%20new%20since%20the%208th%20June.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-javascript%22%3E%3CCODE%3E%40odata.type%3A%20%22%23microsoft.graph.commsNotifications%22%0A%20%20%20%20value%3A%20%5B%0A%20%20%20%20%20%20%7B%0A%20%20%20%20%20%20%20%20%22%40odata.type%22%3A%20%22%23microsoft.graph.commsNotification%22%2C%0A%20%20%20%20%20%20%20%20%22changeType%22%3A%20%22updated%22%2C%0A%20%20%20%20%20%20%20%20%22resource%22%3A%20%22%2Fapp%2Fcalls%2F7c1f5c00-1d34-42a4-9a3f-0d77b1d9baf1%22%2C%0A%20%20%20%20%20%20%20%20%22resourceUrl%22%3A%20%22%2Fcommunications%2Fcalls%2F7c1f5c00-1d34-42a4-9a3f-0d77b1d9baf1%22%2C%0A%20%20%20%20%20%20%20%20%22resourceData%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%22%40odata.type%22%3A%20%22%23microsoft.graph.call%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22state%22%3A%20%22established%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22resultInfo%22%3A%20%7B%0A%20%20%20%20%20%20%20%20%20%20%20%20%22%40odata.type%22%3A%20%22%23microsoft.graph.resultInfo%22%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22code%22%3A%20400%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22subcode%22%3A%208538%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%22message%22%3A%20%22CallEndReasonLocalUserInitiated.%20DiagCode%3A%20603%230%22%0A%20%20%20%20%20%20%20%20%20%20%7D%2C%0A%20%20%20%20%20%20%20%20%20%20%22callChainId%22%3A%20%2295f09401-721e-4751-bde6-8e34d61e5d23%22%2C%0A%20%20%20%20%20%20%20%20%20%20%22replacesContext%22%3A%20%22aHR0cHM6Ly9jYy1mcmNlLTA2LmNjLnNreXBlLmNvbS9jYy92MS9jYWxsUGFydGljaXBhbnQvNTgyNTc3OTctNjMxOC00NWQwLWE0ZWItYmJiYjQ2Mzg4NDFjLzEwL2szLzI1Mi9yZXBsYWNlbWVudD9ydD0yN2ExYzY1ZTIwZjE0MDUwYjFhYjVlYWJjNzA5ZGM2MiZyYz1leUp5ZEd4aWNtTWlPbnNpYVhCa2FYUmpJanBtWVd4elpTd2ljSE4wSWpvaVEyRnNiR2x1WjFCc1lXNXpJbjBzSW5KMGFXUWlPaUkwT2lzME9URTFOelU0TkRneE16WTFJbjAlMjUzZCZpPTE0NSZlPTYzNzU3NTcyOTYwNDE0OTI2Mg%3D%3D%22%0A%20%20%20%20%20%20%20%20%7D%0A%20%20%20%20%20%20%7D%0A%20%20%20%20%5D%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2496773%22%20slang%3D%22en-US%22%3ERe%3A%20Consultative%20transfer%20of%20phone%20calls%20not%20possible%20anymore%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2496773%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1011388%22%20target%3D%22_blank%22%3E%40andreasjm%3C%2FA%3E%26nbsp%3B-%20Could%20you%20please%20check%20this%20%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FOfficeDev%2FMicrosoft-Teams-Samples%2Ftree%2Fmain%2Fsamples%2Fbot-calling-meeting%2Fcsharp%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Esample%3C%2FA%3E%20for%20reference%20and%20try%20this%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi community!

We are facing the following issue since 8th June. When our app is doing a consultative transfer of an audio call, we receive the "tranferAccepted" commsNotification, but the call is, in fact, not transfered or is automatically terminated after a short moment.

The call objects (checked via Graph API) are still in the state of before the transfer, which does not make any sense, because we received the transferAccepted and onHold messages for the respective calls.

 

With consultative transfer I mean: I call the transfer-target person before the transfer and, if accepted, the original call is then transfered to that target user with option "replacesCallId".

 

When reproducing this process with standard auto attendants, we get the same issue. Especially strange: the transfer-target user needs to accept the transfered call twice to actually accept the transfer.

 

The MS support is not reacting to the ticket I opened three days ago. :facepalm: This is a big issue for us, though. Do you understand what might have changed around the 8th June? This process was working flawlessly before.

 

Edit: This only happens when the initially, to-be-transfered call is via phone. 

 

Kind regards

3 Replies

@andreasjm - Thanks for reaching out to us, let me check this issue with internal team and will get back to you. 

Let me add a detail.
If you transfer a call coming from a regular Teams client, it works, as I said.

 

If you transfer a call coming from a telephone (associated with an application instance), then the attached commsNotification is received after the transferAccepted notification. The referenced call is the transfered one.

This does not come, when using a Teams client instead of a phone.

This message is not documented and new since the 8th June. 

 

@odata.type: "#microsoft.graph.commsNotifications"
    value: [
      {
        "@odata.type": "#microsoft.graph.commsNotification",
        "changeType": "updated",
        "resource": "/app/calls/7c1f5c00-1d34-42a4-9a3f-0d77b1d9baf1",
        "resourceUrl": "/communications/calls/7c1f5c00-1d34-42a4-9a3f-0d77b1d9baf1",
        "resourceData": {
          "@odata.type": "#microsoft.graph.call",
          "state": "established",
          "resultInfo": {
            "@odata.type": "#microsoft.graph.resultInfo",
            "code": 400,
            "subcode": 8538,
            "message": "CallEndReasonLocalUserInitiated. DiagCode: 603#0"
          },
          "callChainId": "95f09401-721e-4751-bde6-8e34d61e5d23",
          "replacesContext": "aHR0cHM6Ly9jYy1mcmNlLTA2LmNjLnNreXBlLmNvbS9jYy92MS9jYWxsUGFydGljaXBhbnQvNTgyNTc3OTctNjMxOC00NWQwLWE0ZWItYmJiYjQ2Mzg4NDFjLzEwL2szLzI1Mi9yZXBsYWNlbWVudD9ydD0yN2ExYzY1ZTIwZjE0MDUwYjFhYjVlYWJjNzA5ZGM2MiZyYz1leUp5ZEd4aWNtTWlPbnNpYVhCa2FYUmpJanBtWVd4elpTd2ljSE4wSWpvaVEyRnNiR2x1WjFCc1lXNXpJbjBzSW5KMGFXUWlPaUkwT2lzME9URTFOelU0TkRneE16WTFJbjAlMjUzZCZpPTE0NSZlPTYzNzU3NTcyOTYwNDE0OTI2Mg=="
        }
      }
    ]

 

@andreasjm - Could you please check this sample for reference and try this out.