FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
281 views 1 comments
by anonymous
Hi there,

on an old raspian os with modemmanager 1.10 installed, the TRM240 is successfully working configured via the network manager.

Now I had to update to the lastest raspian for some reasons. The modemmanager now is version 1.14.12-0.2.

Everything seems fine, but if an call is received, the modem is instantly lost in modemmanager (no modem found) and therefore network access via network manager is also lost. This was working on the old setup with modemmanager 1.10.

I testet it with different installations - all the same. As soon as I call the modem, before I even get an ringing tone, the modem drops. And it does not recover until reboot.

I tried to downgrade and upgrade the modem-manager manually, but there are so many dependancies and I did not get it to work.

Anyone has an idea?

Thank you.

1 Answer

0 votes
by anonymous

Hello,

I have followed instructions on setting up TRM240 following this link for modem manager and this for network manager in combination with raspberry pi400, but did not encounter any issue, when connection was established, while I tried to make a call to the number of SIM used by the modem.

  • mmcli version 1.14.12
  • Linux raspberrypi 5.15.84-v7l

Could you try configuration, provided in this link, to interface between TRM240 and your raspberry? 

Best regards,

by anonymous

This is really wierd. 

Finally I changed the modem to another TRM240 and there was no problem - everything works.

So this modem is generally working until a call comes in. If this problem occurs again on a different modem - is there anything I could do? Like reduce the serial baud rate? 

By the way, the modem firmware is the same.

Thank you.

Here the error again in modemmanager:

---

Feb 06 08:23:51 raspberrypi ModemManager[472]: <info>  [modem0/call0] call state changed: unknown -> ringing-in (incoming-new)
Feb 06 08:23:53 raspberrypi ModemManager[472]: <warn>  [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
Feb 06 08:23:55 raspberrypi ModemManager[472]: <warn>  [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
Feb 06 08:23:57 raspberrypi ModemManager[472]: <warn>  [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
Feb 06 08:24:04 raspberrypi ModemManager[472]: <warn>  [modem0] couldn't load call list: Serial command timed out
Feb 06 08:24:06 raspberrypi ModemManager[472]: <warn>  [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
Feb 06 08:24:13 raspberrypi ModemManager[472]: <warn>  [modem0] couldn't load call list: Serial command timed out
Feb 06 08:24:15 raspberrypi ModemManager[472]: <warn>  [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
Feb 06 08:24:17 raspberrypi ModemManager[472]: <warn>  [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
Feb 06 08:24:24 raspberrypi ModemManager[472]: <warn>  [modem0] couldn't load call list: Serial command timed out
Feb 06 08:24:26 raspberrypi ModemManager[472]: <warn>  [modem0] couldn't load call list: Unknown error
Feb 06 08:24:28 raspberrypi ModemManager[472]: <warn>  [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
Feb 06 08:24:30 raspberrypi ModemManager[472]: <warn>  [modem0] couldn't load call list: Unknown error
Feb 06 08:24:32 raspberrypi ModemManager[472]: <warn>  [modem0] couldn't load call list: No carrier
Feb 06 08:24:35 raspberrypi ModemManager[472]: <info>  [modem0/call0] call state changed: ringing-in -> terminated (unknown)
Feb 06 08:24:35 raspberrypi ModemManager[472]: <warn>  [modem0] unexpected incoming call to number 'n/a' reported in call list: state active
Feb 06 08:24:44 raspberrypi ModemManager[472]: <info>  [modem0/call1] call state changed: unknown -> ringing-in (incoming-new)
Feb 06 08:24:48 raspberrypi ModemManager[472]: Cannot read from istream: connection broken
Feb 06 08:24:48 raspberrypi ModemManager[472]: [/dev/cdc-wdm0] QMI endpoint hangup: removed
Feb 06 08:24:48 raspberrypi ModemManager[472]: <info>  [modem0] connection to qmi-proxy for /dev/cdc-wdm0 lost, reprobing