[Bug] Missing "released" call state on newer SDK versions

[safakesberk]

Hello,

1. Describe the bug

We access the Asterisks server via linphone.
We are currently using version 5.1.73 minimal and minimal-debug.
When we initiate an outgoing call, in this version, after a certain period of time, if the other party does not answer the call, we receive “end” and “release” call state events from linphone.
Now we have upgraded our SDK version to 5.3.9. In the same scenario we get “end” but not “release” event.
Here we have some scenarios where we follow the “release” call state. Is the behavior change here a bug or is it a change that we need to adapt?
Attached are the SDK logs where we do and do not get the “release” call_state.
Note -> Only SDK version change makes this difference, regardless of device and OS. That's why I don't share device information.

2. To Reproduce

Start an outgoing call that the other party does not answer

4. Expected behavior

At the end of a long phone ringing time, a “release” call state event should occur when the call is automatically closed.

5. SDK Versions

Correctly Running SDK Version

• Device: [Samsung Galaxy A33]
• OS: [Android 13]
• Version of the SDK [minimal & minimal-debug 5.1.73]

Different Running SDK Version

• Device: [Samsung Galaxy A33]
• OS: [Android 13]
• Version of the SDK [minimal & minimal-debug 5.3.90]

7. SDK logs

Shared in two different files

Thank you in advance

5.1.73.txt
5.3.90.txt

[JonathanWilbur]

I think this explains why I do not see BYE messages sent when I hang up. I feel like this is a recent problem, because I was doing Wireshark captures a few weeks ago and I am pretty sure I saw BYE messages being sent.

[JonathanWilbur]

This seems to have started with Linphone Android 5.1.0 / Linphone SDK 5.2.96.

[safakesberk]

@Viish Hello Sylvain, have you had a chance to review it? Thank you very much in advance 🙏 🙏

[Viish]

Sorry but that's not my area of expertise.

[safakesberk]

I apologize if I tagged you irrelevantly, maybe you have a relevant opinion on this topic?
@AndreaGianarda @Ledjlale @Mickhopes @jeannotlapin