Re: 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.jimene...@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]:  [1679560149.943734] [modem0/ttyUSB2/at] -->
'AT+CLCC'
ModemManager[4908]:  [1679560150.110892] [modem0/ttyUSB2/at] <--
'CONNECT '
ModemManager[4908]:  [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

Re: ublox SARA does not connect

[Aleksander Morgado]

Hey!

On Mon, Mar 27, 2023 at 11:00 AM ron  wrote:
>
> Hi
>
> Im running a ublox SARA modem in an embedded system on ubuntu.
>
> It is connecting fine on ubuntu 20.04, but remains in “registered” state when 
> setup in ubuntu 22.04.
>
> It seems that NM doesn’t run pppd for some reason, or is it MM issue?
>
>
>
> root@ubuntu:~# mmcli -m 0
>
>   
>
>   General  | path: /org/freedesktop/ModemManager1/Modem/0
>
>|device id: d4174b3552de7d45f5b0268aec1350664f7273c6
>
>   
>
>   Hardware | manufacturer: u-blox
>
>|model: SARA-R510M8S
>
>|firmware revision: 03.15
>
>|supported: gsm-umts
>
>|  current: gsm-umts
>
>| equipment id: 352709570223149
>
>   
>
>   System   |   device: 
> /sys/devices/platform/soc@0/3080.bus/3086.serial
>
>|  drivers: imx-uart
>
>|   plugin: generic
>
>| primary port: ttymxc0
>
>|ports: ttymxc0 (at)
>
>   
>
>   Status   |   unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), 
> sim-puk2 (10)
>
>|state: registered
>
>|  power state: on
>
>|  access tech: lte
>
>|   signal quality: 41% (recent)
>
>   
>
>   Modes|supported: allowed: any; preferred: none
>
>|  current: allowed: any; preferred: none
>
>   
>
>   IP   |supported: ipv4, ipv6, ipv4v6
>
>   
>
>   3GPP | imei: 352709570223149
>
>|operator name: Partner ISR
>
>| registration: home-sms-only
>
>| packet service state: detached

These two previous lines are a bit suspicious. The home-sms-only could
indicate that you are not allowed to setup a data connection, but that
would collide with your previous statement that it worked fine in
20.04.
Then, the packet service detached thing could indicate that we're not
correctly handling that, but a bit unsure without looking at the logs.
Could you gather MM debug logs (see
https://modemmanager.org/docs/modemmanager/debugging/) with both
Ubuntu 20.04 and Ubuntu 22.04 and open a new issue in gitlab?
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/issues


>
>   
>
>   SIM  | primary sim path: /org/freedesktop/ModemManager1/SIM/0
>
>
>
> NM connection file:
>
>
>
> id=ttymxc0
>
> uuid=c0a7c307-2657-4cf1-8913-b5a826594338
>
> type=gsm
>
>
>
> [gsm]
>
> #apn=uinternet
>
> auto-config=TRUE
>
>
>
> [ppp]
>
> baud=921600
>
> crtscts=true
>
> lcp-echo-failure=5
>
> lcp-echo-interval=30
>
>
>
> [ipv4]
>
> dns-search=
>
> method=auto
>
>
>
> [ipv6]
>
> addr-gen-mode=stable-privacy
>
> dns-search=
>
> method=ignore



-- 
Aleksander