Beta support: MMS on chatty/mmsd on Modem Manager - help/testing wanted!

[kop316]

So I have been able to get mmsd to handle suspending and waking up a lot better! There is some weirdness involving the dbus though for it, and I am not quite sure why. Essentially purple-mm-sms will always register a new dbus interface from mmsd in unsuspending, even though I never disabled the dbus interface.

If anyone knows what cuases that, their help would be appreciated!

[cyp]

Thank for your work, i manage to get some results with Free Mobile (french mobile operator)



Two weird things...

The Provider's documentation say to use an APN (mmsfree) for MMS which is different from the one used for data (free) but mmsd give an error

Code:

mmsd[9491]: ModemManagerPlugin(): Setting Context...
mmsd[9491]: src/service.c:mms_service_set_mmsc() service 0x557ac86b90 mmsc http://mms.free.fr
mmsd[9491]: ModemManagerPlugin(): Max number of bearers: 1
mmsd[9491]: ModemManagerPlugin(): Current Context APN: free, mmsd settings MMS APN: mmsfree
mmsd[9491]: ModemManagerPlugin(): The modem is not connected to the correct APN!
mmsd[9491]: ModemManagerPlugin(): Set MMSC: http://mms.free.fr, Set Proxy: (null), Set MMS APN: mmsfree
mmsd[9491]: ModemManagerPlugin(): At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/2 active 1 context_active 0
mmsd[9491]: ModemManagerPlugin(): Error activating context!

And mmsd do not succeed to resole CarrierMMSC=http://212.27.40.225

Code:

mmsd[11089]: src/service.c:process_request_queue() location (null)
request http://mms.free.fr
address (null)
port 80
host mms.free.fr
flags 0
request /
content-type application/vnd.wap.mms-message
lookup hostname mms.free.fr
g_resolv_lookup_hostname: nameserver_list NULL
g_resolv_lookup_hostname: nscount=3
adding nameserver 192.168.1.1
addr = 10.180.240.233
setting nameserver 192.168.1.1
fam 2 != expected 10
bind failed: Invalid argument
connect_udp_channel failed!
mmsd[11089]: src/service.c:web_post_result_cb() Send </home/mobian/.mms/send.FZ8QX0.mms> complete

So at the end I try with this content into my ModemManagerSettings file

Code:

[Modem Manager]
CarrierMMSC=http://212.27.40.225
MMS_APN=free
CarrierMMSProxy=NULL

And it works...

For people who want to try a more complete howto for fresh Mobian install

Install ssh on your (if you prefer to use ssh from your computer)

Code:

sudo  apt install ssh

Once connected, install git clone all repo compile, and install.

Code:

sudo apt install git make build-essential build-dep
mkdir ~/src
cd ~/src
git clone https://source.puri.sm/kop316/purple-mm-sms.git
cd purple-mm-sms/
sudo apt install libebook-contacts1.2-dev
sudo apt install libpurple-dev libmm-glib-dev modemmanager
make
sudo make install
cd ~/src
git clone https://source.puri.sm/kop316/mmsd.git
cd mmsd
sudo apt install autotools-dev automake libtool
./bootstrap-configure --prefix=/usr/
make
sudo make install
cd ~/src
git clone https://source.puri.sm/Librem5/chatty.git
cd chatty
sudo apt -y build-dep .
meson build # or for debug mode: meson build -Db_sanitize=address -Dbuildtype=debug
ninja -C build
sudo ninja -C build install # if you want to replace regular install
sudo mv /etc/xdg/autostart/sm.puri.Chatty-daemon.desktop ~/ # or rm if you do not want to keep the file

To launch (or relaunch)

Code:

sudo killall mmsd
sudo killall chatty
~/src/mmsd/src/mmsd # or to debug: ~/src/mmsd/src/mmsd -n -d 'src/*'
~/src/chatty/build/run & # or to debug: G_MESSAGES_DEBUG=all ~/src/chatty/build/run --debug --verbose

[kop316]

Thank for your work, i manage to get some results with Free Mobile (french mobile operator)



Two weird things...

The Provider's documentation say to use an APN (mmsfree) for MMS which is different from the one used for data (free) but mmsd give an error

Code:

mmsd[9491]: ModemManagerPlugin(): Setting Context...
mmsd[9491]: src/service.c:mms_service_set_mmsc() service 0x557ac86b90 mmsc http://mms.free.fr
mmsd[9491]: ModemManagerPlugin(): Max number of bearers: 1
mmsd[9491]: ModemManagerPlugin(): Current Context APN: free, mmsd settings MMS APN: mmsfree
mmsd[9491]: ModemManagerPlugin(): The modem is not connected to the correct APN!
mmsd[9491]: ModemManagerPlugin(): Set MMSC: http://mms.free.fr, Set Proxy: (null), Set MMS APN: mmsfree
mmsd[9491]: ModemManagerPlugin(): At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/2 active 1 context_active 0
mmsd[9491]: ModemManagerPlugin(): Error activating context!

And mmsd do not succeed to resole CarrierMMSC=http://212.27.40.225

Code:

mmsd[11089]: src/service.c:process_request_queue() location (null)
request http://mms.free.fr
address (null)
port 80
host mms.free.fr
flags 0
request /
content-type application/vnd.wap.mms-message
lookup hostname mms.free.fr
g_resolv_lookup_hostname: nameserver_list NULL
g_resolv_lookup_hostname: nscount=3
adding nameserver 192.168.1.1
addr = 10.180.240.233
setting nameserver 192.168.1.1
fam 2 != expected 10
bind failed: Invalid argument
connect_udp_channel failed!
mmsd[11089]: src/service.c:web_post_result_cb() Send </home/mobian/.mms/send.FZ8QX0.mms> complete

So at the end I try with this content into my ModemManagerSettings file

Code:

[Modem Manager]
CarrierMMSC=http://212.27.40.225
MMS_APN=free
CarrierMMSProxy=NULL

And it works...

For people who want to try a more complete howto for fresh Mobian install

Install ssh on your (if you prefer to use ssh from your computer)

Code:

sudo  apt install ssh

Once connected, install git clone all repo compile, and install.

Code:

sudo apt install git make build-essential build-dep
mkdir ~/src
cd ~/src
git clone https://source.puri.sm/kop316/purple-mm-sms.git
cd purple-mm-sms/
sudo apt install libebook-contacts1.2-dev
sudo apt install libpurple-dev libmm-glib-dev modemmanager
make
sudo make install
cd ~/src
git clone https://source.puri.sm/kop316/mmsd.git
cd mmsd
sudo apt install autotools-dev automake libtool
./bootstrap-configure --prefix=/usr/
make
sudo make install
cd ~/src
git clone https://source.puri.sm/Librem5/chatty.git
cd chatty
sudo apt -y build-dep .
meson build # or for debug mode: meson build -Db_sanitize=address -Dbuildtype=debug
ninja -C build
sudo ninja -C build install # if you want to replace regular install
sudo mv /etc/xdg/autostart/sm.puri.Chatty-daemon.desktop ~/ # or rm if you do not want to keep the file

To launch (or relaunch)

Code:

sudo killall mmsd
sudo killall chatty
~/src/mmsd/src/mmsd # or to debug: ~/src/mmsd/src/mmsd -n -d 'src/*'
~/src/chatty/build/run & # or to debug: G_MESSAGES_DEBUG=all ~/src/chatty/build/run --debug --verbose

Great! I am glad it works!

---

Thanks,
Looks like it is compiled and able to run. However when trying to run chatty via
G_MESSAGES_DEBUG=all chatty --debug --verbose
I receive a segmentation fault
(sm.puri.Chatty:1239): mm-sms-DEBUG: 11:34:57.681: got mmsd Manager
(sm.puri.Chatty:1239): mm-sms-DEBUG: 11:34:57.687: got service
(sm.puri.Chatty:1239): mm-sms-DEBUG: 11:34:57.687: Listening for new messages
(sm.puri.Chatty:1239): mm-sms-DEBUG: 11:34:57.688: Connected to mmsd ModemManager Plugin
(sm.puri.Chatty:1239): mm-sms-DEBUG: 11:34:57.745: pur_mmsd_get_all_mms_cb
Segmentation fault

Nothing is returned / printed via the mmsd -n output.

Opps, had a typo with the apn configuration.

Now with the programs working mms fails to download.
I suspect this is because the download is being attempted directly without the mms proxy as there is a 404 error. It does appear to be using the correct ip / wwan0 connection.

APN settings:
[Modem Manager]
CarrierMMSC=http://aliasredirect.net/proxy/mmsc
MMS_APN=sp.telus.com
CarrierMMSProxy=74.49.0.18:80

Manually downloading using
curl --interface wwan0 --proxy 74.49.0.18:80 Download_URL_from_sms_in_mmsd_output -o test.mms;
recoverjpeg -b1 test.mms -o ./ -f test.jpg;
retrieved the test picture.

Hello!

The latest mmsd may have solved the Telus issue. Do you mind testing?

[kop316]

I seem to have figured out the earlier dbus issue! It looks like I have mmsd/purple-mm-sms supporting MMS even from suspend! I can send myself an MMS while Mobian suspends and it recieves!

[FutureBucket]

I seem to have figured out the earlier dbus issue! It looks like I have mmsd/purple-mm-sms supporting MMS even from suspend! I can send myself an MMS while Mobian suspends and it recieves!

Nice! So that's pretty much done eh? Just have to wait for it to get put into chatty?

APN settings:
[Modem Manager]
CarrierMMSC=http://aliasredirect.net/proxy/mmsc
MMS_APN=sp.telus.com
CarrierMMSProxy=74.49.0.18:80

Manually downloading using
curl --interface wwan0 --proxy 74.49.0.18:80 Download_URL_from_sms_in_mmsd_output -o test.mms;
recoverjpeg -b1 test.mms -o ./ -f test.jpg;
retrieved the test picture.

I was able to get it working with different proxy. https://www.telus.com/en/on/support/arti...oid-device

Though, I see above mmsd just has a problem downloading the image. My tests worked after the change from kop316

Code:

mobian@mobian:~$ cat ~/.mms/modemmanager/ModemManagerSettings
[Modem Manager]
CarrierMMSC=http://aliasredirect.net/proxy/mmsc
MMS_APN=sp.telus.com
CarrierMMSProxy=mmscproxy.mobility.ca:8799
mobian@mobian:~$ host mmscproxy.mobility.ca
mmscproxy.mobility.ca is an alias for mmscproxy.glb.mobility.ca.
mmscproxy.glb.mobility.ca has address 209.202.119.4
mmscproxy.glb.mobility.ca has IPv6 address 2001:568:202:b::1
mobian@mobian:~$

[kop316]

I seem to have figured out the earlier dbus issue! It looks like I have mmsd/purple-mm-sms supporting MMS even from suspend! I can send myself an MMS while Mobian suspends and it recieves!

Nice! So that's pretty much done eh? Just have to wait for it to get put into chatty?

APN settings:
[Modem Manager]
CarrierMMSC=http://aliasredirect.net/proxy/mmsc
MMS_APN=sp.telus.com
CarrierMMSProxy=74.49.0.18:80

Manually downloading using
curl --interface wwan0 --proxy 74.49.0.18:80 Download_URL_from_sms_in_mmsd_output -o test.mms;
recoverjpeg -b1 test.mms -o ./ -f test.jpg;
retrieved the test picture.

I was able to get it working with different proxy. https://www.telus.com/en/on/support/arti...oid-device

Though, I see above mmsd just has a problem downloading the image. My tests worked after the change from kop316

Code:

mobian@mobian:~$ cat ~/.mms/modemmanager/ModemManagerSettings
[Modem Manager]
CarrierMMSC=http://aliasredirect.net/proxy/mmsc
MMS_APN=sp.telus.com
CarrierMMSProxy=mmscproxy.mobility.ca:8799
mobian@mobian:~$ host mmscproxy.mobility.ca
mmscproxy.mobility.ca is an alias for mmscproxy.glb.mobility.ca.
mmscproxy.glb.mobility.ca has address 209.202.119.4
mmscproxy.glb.mobility.ca has IPv6 address 2001:568:202:b::1
mobian@mobian:~$

What I will say is mmsd needs some "real world" testing. The more I test it, the more I have found these sorts of bugs so I can fix it. At the present moment, i am not aware of issues in mmsd (though every time i have said that, i have discovered an issue i need to fix). I also want to go through the mmsd plugin a bit to make sure the code is clean/well commented as well, so it is easier for folks to dive into it. I also want to make sure the documentation is good as well too.

As for chatty, I am still waiting for the upgraded chatty to work with, so I can integrate MMS into it.

[kop316]

It seems that mmsd is still on the buggy side for supporting receiving MMS from suspend. From what I can tell, the issue stems from it trying to reattached to the modem too fast after suspend, and the modem isn't ready. If anyone has experience in how to handle this, some help would be appreciated!

EDIT: I seemed to have fixed this on the mmsd side....but purple-mm-sms seems to still have issues. I will have to look into this to figure out what is going on.

[Elias]

Thanks for doing this, great work!

I also got it working, on a PinePhone running Mobian, using more or less the instructions that @cyp wrote above. There was a problem building chatty just as @patrickmollohan said. Anyway I did receive an mms message that was properly received and resulted in a beautiful jpg image in the ~/mms directory.

My ~/.mms/modemmanager/ModemManagerSettings file that turned out to work looks like this, for a "Comviq kontant" SIM card in Sweden:

[Modem Manager]
CarrierMMSC=http://mmsc.tele2.se
MMS_APN=4g.tele2.se
CarrierMMSProxy=130.244.202.30:8080

The ":8080" for the CarrierMMSProxy was needed because without that it tries to use port 80 which does not work.
2.12.0.0

[kop316]

So good news, I think mmsd is in really good shape, and unless someone finds something to be a show stopper, it is at a point release!

I still am looking for help packaging it, and I still need to track down an underlying issue with Telus. But telus so far works, I just want a better solution for the bug that's been found.

[kop316]

So good news! I think I have the Telus issue resolved. Thank you Futurebucket for your help resolving it.