Remove use of legacy hangup in sending flow.

This commit is contained in:
Cody Henthorne
2023-09-13 12:07:54 -04:00
committed by Alex Hart
parent ff5b024074
commit 11e0dd18d3
6 changed files with 12 additions and 29 deletions

View File

@@ -39,7 +39,7 @@ object CallMessageProcessor {
callMessage.iceUpdateList.isNotEmpty() -> handleCallIceUpdateMessage(envelope, metadata, callMessage.iceUpdateList, senderRecipient.id)
callMessage.hasHangup() || callMessage.hasLegacyHangup() -> {
val hangup = if (callMessage.hasHangup()) callMessage.hangup else callMessage.legacyHangup
handleCallHangupMessage(envelope, metadata, hangup, senderRecipient.id, callMessage.hasLegacyHangup())
handleCallHangupMessage(envelope, metadata, hangup, senderRecipient.id)
}
callMessage.hasBusy() -> handleCallBusyMessage(envelope, metadata, callMessage.busy, senderRecipient.id)
callMessage.hasOpaque() -> handleCallOpaqueMessage(envelope, metadata, callMessage.opaque, senderRecipient.requireAci(), serverDeliveredTimestamp)
@@ -115,8 +115,7 @@ object CallMessageProcessor {
envelope: Envelope,
metadata: EnvelopeMetadata,
hangup: SignalServiceProtos.CallMessage.Hangup,
senderRecipientId: RecipientId,
isLegacyHangup: Boolean
senderRecipientId: RecipientId
) {
log(envelope.timestamp, "handleCallHangupMessage")
@@ -124,7 +123,7 @@ object CallMessageProcessor {
ApplicationDependencies.getSignalCallManager()
.receivedCallHangup(
CallMetadata(remotePeer, metadata.sourceDeviceId),
HangupMetadata(HangupMessage.Type.fromProto(hangup.type), isLegacyHangup, hangup.deviceId)
HangupMetadata(HangupMessage.Type.fromProto(hangup.type), hangup.deviceId)
)
}