[Linphone-developers] Call in wrong state if caller hangs up between accept and stream on

[matteo.fortini]

I have a system which can, in some situations, HANGUP a call briefly after
sending INVITE.

The callee is auto ACCEPTing the call right after receiving
the/LinphoneCallIncomingReceived/ event, so linphone starts setting up the
rtp stream.

Before receiving the /LinphoneCallStreamsRunning/ event, I receive the
/LinphoneCallEnd/ event, so I terminate the call (actually, I use
terminate_all() just to make sure I cleanup) and go back to my idle state.

What I see is that for some reason the call is not terminated correctly,
and there is a runaway rtp stream going on, which I cannot terminate in any
way. The debug output of ortp is:

ortp-warning-call_terminated: ignoring.
ortp-warning-cannot set noise gate mode to [0] because no volume send
ortp-error-Fail to build answer for call: err=-3
ortp-warning-Spurious call state change from LinphoneCallEnd to
LinphoneCallConnected, ignored.
ortp-warning-Spurious call state change from LinphoneCallEnd to
LinphoneCallStreamsRunning, ignored.
ortp-warning-alsa_set_params: periodsize:256 Using 256
ortp-warning-alsa_set_params: period:8 Using 8

You can see that there is a spurious transition to
LinphoneCallStreamsRunning, which I suspect triggers the event.

What can I do to debug/avoid the issue?

Thank you,
Matteo