Skip to content

record-store: Don't crash on unexpected call state changes

Evangelos Ribeiro Tzaras requested to merge devrtz/calls:dont-assert-record-store into main

It has been reported that the BM818 sometimes unexpectedly changes the call state from "active" back to "ringing-in" (as reported by ModemManager) shortly after accepting an incoming call.

ModemManager[734]: [modem1/call1] user request to accept call ModemManager[734]: [modem1/call1] call is accepted ModemManager[734]: [modem1/call1] call state changed: ringing-in -> active (accepted) ModemManager[734]: [modem1/call1] call state changed: active -> ringing-in (unknown)

This leads to a failed assertion and program termination. Instead of crashing raising a critical warning is more appropriate and may allow the user to pick up the call after all.

Closes: #547 (closed)

Merge request reports