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.

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

select answer should be used for outgoing calls. #4625

Merged
merged 8 commits into from
Dec 3, 2021

Conversation

langleyd
Copy link
Member

@langleyd langleyd commented Dec 3, 2021

Fixes #4621

Use case is:

  • alice calls bob
  • bob answers alice
  • alice selects bob's answer

The reason being that if bob tries to accept on two devices, it's clear which one alice is actually trying to connect to.

I believe this problem might have just surfaced recently due to changes at the sip bridge adding a timeout for the selectAnswer

@langleyd langleyd requested review from ganfra and bmarty December 3, 2021 11:32
@@ -203,8 +203,10 @@ internal class MxCallImpl(

override fun selectAnswer() {
Timber.tag(loggerTag.value).v("select answer $callId")
if (isOutgoing) return
state = CallState.Answering
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we still set this state somewhere else or does CallState.Answering no longer need to exist?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It still exists and is set for incoming calls here as described in it's definition here.

This selectAnswer function is actually used for outgoing calls the current state at this point is Dialing and stays as that until the Connected state.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for explaining

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@ouchadam ouchadam left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small question around removing the state, otherwise looking good! 💯

Copy link
Member

@ganfra ganfra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix, my fault for that :/

Copy link
Member

@bmarty bmarty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@@ -203,8 +203,10 @@ internal class MxCallImpl(

override fun selectAnswer() {
Timber.tag(loggerTag.value).v("select answer $callId")
if (isOutgoing) return
state = CallState.Answering
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@github-actions
Copy link

github-actions bot commented Dec 3, 2021

Unit Test Results

  66 files  ±0    66 suites  ±0   56s ⏱️ -1s
135 tests ±0  135 ✔️ ±0  0 💤 ±0  0 ±0 
418 runs  ±0  418 ✔️ ±0  0 💤 ±0  0 ±0 

Results for commit 767ead0. ± Comparison against base commit 1aa5321.

♻️ This comment has been updated with latest results.

@bmarty bmarty merged commit 9f4f15a into develop Dec 3, 2021
@bmarty bmarty deleted the feature/dla/outgoing_pstn_call_fails branch December 3, 2021 15:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Outgoing voip call through sip bridge fails
5 participants