You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've seen an instance of a client placing two calls to a peer in fairly quick succession. It's not 100% clear how, but presumably the member state event processor function must have got run again and we're not smart enough to realise we're already placing a call. The fix is probably to check for an existing call before placing another.
Outcome
What did you expect?
What happened instead?
Operating system
No response
Browser information
No response
URL for webapp
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered:
dbkr
added
the
T-Defect
Something isn't working: bugs, crashes, hangs, vulnerabilities, or other reported problems
label
Sep 8, 2022
Steps to reproduce
We've seen an instance of a client placing two calls to a peer in fairly quick succession. It's not 100% clear how, but presumably the member state event processor function must have got run again and we're not smart enough to realise we're already placing a call. The fix is probably to check for an existing call before placing another.
Outcome
What did you expect?
What happened instead?
Operating system
No response
Browser information
No response
URL for webapp
No response
Will you send logs?
Yes
The text was updated successfully, but these errors were encountered: