Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Teams presence status is not updated during a call via Azure Communication Services #26169

Closed
1 task done
egloff opened this issue Jun 12, 2023 · 2 comments
Closed
1 task done

Teams presence status is not updated during a call via Azure Communication Services #26169

egloff opened this issue Jun 12, 2023 · 2 comments
Assignees
@cn0151
Labels
Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@egloff
Copy link

egloff commented Jun 12, 2023

  • Package Name: @azure/communication-calling
  • Package Version: 1.14.2-alpha.20230606.1 (and also current stable: 1.13.1)
  • Operating system:
  • browser
    • name/version: Google Chrome/113.0.5672.126

Describe the bug
Teams presence status is not updated ("available" -> "in a call") when a call is accepted or initiated via Azure Communication Calling in Teams interoperability mode. Are we doing something wrong or is this really not working at the moment?

To Reproduce

  1. Implement an Azure Communication Calling client with Teams interoperability (https://learn.microsoft.com/en-us/azure/communication-services/concepts/interop/calling-chat)
  2. Initiate or receive a call (does not matter if its to/form another Teams user or a phone number)
  3. Status of my Teams user (in Microsoft Teams Client) remains "available"

Expected behavior
The status in Microsoft Teams client should switch to "in a call".
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-triage Workflow: This issue needs the team to triage. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jun 12, 2023
@xirzec xirzec removed the needs-team-triage Workflow: This issue needs the team to triage. label Jun 13, 2023
@github-actions github-actions bot added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jun 13, 2023
@cn0151
Copy link
Member

cn0151 commented Jun 16, 2023

@egloff

The current status is that it is not supported at this point in time. I hope this helps clarify things for you. Let me know if you have any other questions.

@egloff
Copy link
Author

egloff commented Jun 19, 2023 •
edited
Loading

@cn0151

Thanks for the reply.
Are there any plans to implement this in the near future?
Or is there a workaround which we can implement on our side?

azure-sdk pushed a commit to azure-sdk/azure-sdk-for-js that referenced this issue Nov 2, 2023
@dishantmunjal @chandrasekarendran
@soumyapattnaik @nickpacificomsft @asmitt
CodeGen from PR 25967 in Azure/azure-rest-api-specs
9751ecf 
[Hub Generated] Review request for Microsoft.DataProtection to add version preview/2023-08-01-preview (Azure#25967)

* Adds base for updating Microsoft.DataProtection from version preview/2023-06-01-preview to version 2023-08-01-preview

* Updates readme

* Updates API version in new specs and examples

* Re-Validate API Swagger Changes

* JobCancel & Job InProgress changes

* vault tier changes aks (Azure#25972)

* Add is isPartialRP boolean to AzureBackupDiscreteRecoveryPoint and examples (Azure#25974)

* Add is ispartialrp to AzureBackupDiscreteRecoveryPoint and examples

* Fix prettier issues in examples

* Including ValidateForModifyBackupRequest Defn.

* resolved comments (Azure#26064)

* Revert IsPartialRP changes (Azure#26070)

* Using Restricted Pattern for Vault Name (Azure#26169)

* Handling Validation Errors (Azure#26186)

* removing 200 status code

* LintDiff fix - using common types error response (Azure#26187)

* whitespace handling

* Editing where clause

* Removing Where Condition

---------

Co-authored-by: Dishant Munjal <dishantmunjal@users.noreply.github.com>
Co-authored-by: chandrasekarendran <59728024+chandrasekarendran@users.noreply.github.com>
Co-authored-by: soumyapattnaik <33341338+soumyapattnaik@users.noreply.github.com>
Co-authored-by: nickpacificomsft <144935783+nickpacificomsft@users.noreply.github.com>
Co-authored-by: asmitt <62243673+asmitt@users.noreply.github.com>
@fizampou fizampou assigned cn0151 and unassigned akania May 20, 2024
@cn0151 cn0151 closed this as not planned Won't fix, can't repro, duplicate, stale May 22, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Aug 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@cn0151 cn0151

Labels
Client This issue points to a problem in the data-plane of the library. Communication customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@akania @xirzec @egloff @cn0151