Sending SMS carrier: O² Germany
#1
Has anyone gotten chatty to send sms over O2 network in Germany? If so how?
  Reply
#2
I'm on a Telefónica Moviles MVNO (same carrier as O2) and can confirm that sending text messages with chatty only seems to work (chatty marks them as sent, but they're never received on the other end). Receiving text messages works OK, but at this moment I wanted to check this and it seems to have lost the messages database: zilch!
This definitely worked when I started to use the phone as daily driver ...
  Reply
#3
Sadly, yes, I can confirm, that SMS messages are not received, if sent via Chatty/O2Germany - it worked some weeks ago though.

But thanks for pointing that out. I will try to get some logs and open an issue on gitlab(?).

Cheers
  Reply
#4
Has anyone tried this?
https://gitlab.com/mobian1/issues/-/issues/254
  Reply
#5
If Chatty is the standard, preinstalled & bookmarked SMS client: I don't seem to have any problems sending or receiving messages via O2 Germany.
  Reply
#6
(05-11-2021, 01:51 PM)sfb Wrote: Has anyone tried this?
https://gitlab.com/mobian1/issues/-/issues/254

I tried this, intending to switch off IMS for some time in the running configuration of the modem, using mmcli to poke the modem's configuration directly. It didn't work. Sending text messages directly via mmcli also does not work any more, which tells me it isn't a Chatty problem, but with the middleware (ModemManager or eg25-manager).

Code:
root@pine:~# mmcli -m any --messaging-create-sms="text='Hello world test',number='+44123456789'"
Successfully created new SMS: /org/freedesktop/ModemManager1/SMS/6
root@pine:~# mmcli -s 6 --send
error: couldn't find SMS at '/org/freedesktop/ModemManager1/SMS/6': 'not found in any modem'

journalctl tells this after some seconds:

Code:
ModemManager[583]: transaction 0xd aborted, but message is not abortable
  Reply
#7
(05-12-2021, 01:45 PM)Maus Wrote:
(05-11-2021, 01:51 PM)sfb Wrote: Has anyone tried this?
https://gitlab.com/mobian1/issues/-/issues/254

I tried this, intending to switch off IMS for some time in the running configuration of the modem, using mmcli to poke the modem's configuration directly. It didn't work. Sending text messages directly via mmcli also does not work any more, which tells me it isn't a Chatty problem, but with the middleware (ModemManager or eg25-manager).

Code:
root@pine:~# mmcli -m any --messaging-create-sms="text='Hello world test',number='+44123456789'"
Successfully created new SMS: /org/freedesktop/ModemManager1/SMS/6
root@pine:~# mmcli -s 6 --send
error: couldn't find SMS at '/org/freedesktop/ModemManager1/SMS/6': 'not found in any modem'

journalctl tells this after some seconds:

Code:
ModemManager[583]: transaction 0xd aborted, but message is not abortable

Thanks for testing and eliminating Chatty as the culprit... So it looks like a ModemManager thing, isn't it?

(05-12-2021, 07:45 AM)Anna Wrote: If Chatty is the standard, preinstalled & bookmarked SMS client: I don't seem to have any problems sending or receiving messages via O2 Germany.

That's good! Is your Mobian up-to-date?
  Reply
#8
(05-12-2021, 01:55 PM)arno_nuehm Wrote: That's good! Is your Mobian up-to-date?

Pretty much -- except for these:

Code:
at-spi2-core/testing 2.38.0-4 arm64 [upgradable from: 2.38.0-2]
file-roller/testing 3.38.1-1 arm64 [upgradable from: 3.38.0-1]
libatspi2.0-0/testing 2.38.0-4 arm64 [upgradable from: 2.38.0-2]
libsmbclient/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]
libwbclient0/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]
libxml2/testing 2.9.10+dfsg-6.6 arm64 [upgradable from: 2.9.10+dfsg-6.3+b1]
samba-libs/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]
  Reply
#9
[quote pid='94594' dateline='1620850684']
Code:
at-spi2-core/testing 2.38.0-4 arm64 [upgradable from: 2.38.0-2]
file-roller/testing 3.38.1-1 arm64 [upgradable from: 3.38.0-1]
libatspi2.0-0/testing 2.38.0-4 arm64 [upgradable from: 2.38.0-2]
libsmbclient/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]
libwbclient0/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]
libxml2/testing 2.9.10+dfsg-6.6 arm64 [upgradable from: 2.9.10+dfsg-6.3+b1]
samba-libs/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]

[/quote]

Do you guys think any of those could be at fault?
  Reply
#10
(05-13-2021, 10:53 PM)Anna Wrote: [quote pid='94594' dateline='1620850684']
Code:
at-spi2-core/testing 2.38.0-4 arm64 [upgradable from: 2.38.0-2]
file-roller/testing 3.38.1-1 arm64 [upgradable from: 3.38.0-1]
libatspi2.0-0/testing 2.38.0-4 arm64 [upgradable from: 2.38.0-2]
libsmbclient/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]
libwbclient0/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]
libxml2/testing 2.9.10+dfsg-6.6 arm64 [upgradable from: 2.9.10+dfsg-6.3+b1]
samba-libs/testing 2:4.13.5+dfsg-2 arm64 [upgradable from: 2:4.13.5+dfsg-1]

Do you guys think any of those could be at fault?
[/quote]

As far as I see, there is nothing related to this problem - no risk regarding the updates.
  Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  WIRED-PROPERTIES.CARRIER: off --- 1 771 09-24-2020, 05:03 AM
Last Post: ---

Forum Jump:


Users browsing this thread: 1 Guest(s)