From 041980e7d325e31235d2a86a602fd28717460f82 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=A9bastien=20Blin?=
<sebastien.blin@savoirfairelinux.com>
Date: Thu, 5 Mar 2020 14:57:57 -0500
Subject: [PATCH] sipcall: no need to execute setState on Main Thread
This causes the incoming state to come after the current state sometimes and
there is no need to run onPeerRinging on the main thread
Change-Id: I0d98c22b298b1bc5a2e1797ecae4855fa767fec8
Gitlab: #209
---
src/sip/sipcall.cpp | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/src/sip/sipcall.cpp b/src/sip/sipcall.cpp
index d2a046d40b..174b149d4f 100644
--- a/src/sip/sipcall.cpp
+++ b/src/sip/sipcall.cpp
@@ -825,10 +825,7 @@ SIPCall::sendKeyframe()
void
SIPCall::onPeerRinging()
{
- runOnMainThread([w = weak()] {
- if (auto shared = w.lock())
- shared->setState(ConnectionState::RINGING);
- });
+ setState(ConnectionState::RINGING);
}
void
--
GitLab