Open egloff opened 1 year ago
@egloff , thanks for reporting the issue, do you have the callId for this ? can you explain your scenario - are you using Teams user ( via ACS SDK) as one of the agent behind call queue (CQ ) ? what mode is CQ configured - conf or transfer mode ? if transfer mode, can you try to repro it using a conf mode CQ ? please send callIds in both success/failure case.
Hey @ansrin Thanks for the response. Finally we got a response from our company's Microsoft support (we are waiting there since February, therefore I created this issue because it seems like this is faster). May we pause this issue (or shall I close it?) until our support-case has been successfully processed and update this issue afterwards?
@egloff , sure. we can follow up using the support ticket route and close this.
Describe the bug We use the JavaScript Calling API of the Azure Communication Services in our product to allow the user to accept and initiate Microsoft Teams calls (here is the documentation from Microsoft: https://learn.microsoft.com/en-us/javascript/api/azure-communication-services/@azure/communication-calling/?view=azure-communication-services-js).
When a user receives a call via a call-queue, we get the following object (callerInfo) over the interface:
On the one hand we get the value "unknown" as IdentifierKind and on the other hand the UUID we get is the UUID of the call-queue (without any readable name) which has nothing to do with the caller. So we currently have no possibility to identify the caller before the call is answered.
We expect some information about the caller (PhoneNumberKind with a phone-number or MicrosoftTeamsUserKind with a MicrosoftTeamsUserId) and additionally the information about the call-queue (preferably we could display the same information as the Microsoft Teams Client does: "Call Queue: Support / Caller: John Doe").
To Reproduce
Expected behavior We get information about the actual caller (and the call-queue).
Additional context The information about the caller is essential for our product because a lot of our customers are using call-queues (typically call-centers) and must identify the customer before the call is answered.