Skip to content
New issue

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

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

Already on GitHub? # to your account

Rejecting a call doesn't send 'm.call.reject' event #1967

Closed
2 tasks done
coder-with-a-bushido opened this issue Dec 6, 2024 · 0 comments · Fixed by #1968
Closed
2 tasks done

Rejecting a call doesn't send 'm.call.reject' event #1967

coder-with-a-bushido opened this issue Dec 6, 2024 · 0 comments · Fixed by #1968
Assignees
Labels
bug Something isn't working

Comments

@coder-with-a-bushido
Copy link
Contributor

Checklist

  • I could not find a solution in the documentation, the existing issues or discussions.
  • I already asked for help in the chat

In which Project did the bug appear?

Famedly App

If you selected "Other" as Project, please enter in which project the bug occurred.

No response

On which platform did the bug appear?

Android, iOS, Chrome

SDK Version

0.35.0

Describe the problem caused by this bug

When a user calls reject from CallSession for an incoming call, it should end the call and ideally send an 'm.call.reject' event. But with the current implementation 'm.call.reject' event is not sent.

Steps To Reproduce

  1. Call from device A
  2. Reject the call from device B
  3. You should not get the 'm.call.reject' event, so the UI shows you that the call was not rejected but is actually a missed call

Screenshots or Logs

No response

Security related

No response

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant