modem terminates call when accepted remotely

[Aleksander Morgado]

Hey Héctor,


On Thu, Mar 23, 2023 at 2:03 PM Héctor Jiménez Méndez <
hector.jimenez.m at gmv.com> wrote:

> Hi, Alex, thanks for your quick answer.
>
> Nice to know you worked at Elecnor/Deimos Space 😊
>
> This is definitely a bug to fix. That transition to "terminated"
> shouldn't happen when the callee picks up the call. Can you get MM debug
> logs while reproducing the issue? Also, is this using AT or QMI?
>
> Two logs are attached: one with transition from ringing-out to active and
> another with the wrong state transition (ringing-out -> terminated).
>
> At first sight I couldn’t find any significative trace to explain this
> behavior, I hope you can get some related info in them.
>
>
>
I think this "CONNECT" URC is getting in the middle of the +CLCC? polling
and it's breaking the logic:

ModemManager[4908]: <debug> [1679560149.943734] [modem0/ttyUSB2/at] -->
'AT+CLCC<CR>'
ModemManager[4908]: <debug> [1679560150.110892] [modem0/ttyUSB2/at] <--
'<CR><LF>CONNECT <CR><LF>'
ModemManager[4908]: <debug> [1679560150.111267] [modem0] reported 0 ongoing
calls

Your device is QMI capable and we do see certain Voice events reported in
the log via QMI. Full QMI based voice support was introduced in MM 1.18, I
definitely suggest you switch to that so that AT-based management is
completely skipped.

-- 
Aleksander
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20230330/0552847f/attachment.htm>