From 3096f859ac15703e8106f6e09ecb47fc8127e4ad Mon Sep 17 00:00:00 2001
From: Peter Cai <peter@typeblog.net>
Date: Thu, 21 Apr 2022 21:28:38 -0400
Subject: [PATCH] Call setActive anyway in CONNECTED state

There is no code that guarantees the state must go through CONNECTING
before being CONNECTED. To avoid potential bugs, call setActive anyway
here.
---
 src/cheogram/java/com/cheogram/android/ConnectionService.java | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/cheogram/java/com/cheogram/android/ConnectionService.java b/src/cheogram/java/com/cheogram/android/ConnectionService.java
index 8bc429dcf83c4fee2bb477d0ee121fffb3199c1c..0f5dfa172654e67504fb25cbb1be971adb5c2b16 100644
--- a/src/cheogram/java/com/cheogram/android/ConnectionService.java
+++ b/src/cheogram/java/com/cheogram/android/ConnectionService.java
@@ -251,6 +251,8 @@ public class ConnectionService extends android.telecom.ConnectionService {
 				setActive();
 				statusLabel = getString(R.string.rtp_state_connecting);
 			} else if (state == RtpEndUserState.CONNECTED) {
+				xmppConnectionService.setDiallerIntegrationActive(true);
+				setActive();
 				postDial();
 			} else if (state == RtpEndUserState.DECLINED_OR_BUSY) {
 				close(new DisconnectCause(DisconnectCause.BUSY));