This project aims to eventually have equivalent functionality to mmsd. instead of relying on ofono it will support using ModemManager to talk to the modem. ideally it will use modular approach, so as to support both ModemManager and ofono.
- Parse mms push notifications
- Fetch messages when passed a binary message, for example from ModemManager
with
mmcli -s n --create-file-with-data="mms1.bin"- Handle multi-part messages. Often a message will contain multiple files in the body field, for example a smil section, and an image.
- Encode messages + cli to send messages (the user must use mmcli to send any data which needs to be encoded as sms messages)
- Integrate with ModemManager through a generic interface (wrapper around ModemManager DBus interface) to interact with messages without manually running mmcli.
- Service - run in the background and download messages as they arrive
- DBus interface - have a dbus interface for listening for new messages, retrieving message data, sending messages... etc. This will be necessary to integrate into messaging apps.
Dependencies:
On postmarketos I had to install openssl-dev to get it to build. I'm not sure
about others.
cargo build should work, cargo build --release takes longer, but will
produce a smaller binary which should run faster.
copy target/release/mmsutil or target/debug/mmsutil to a directory in your
$path, ie. /usr/local/bin/.
use cargo run -- --help or rust-mmsd --help if you installed using the
previous step to get usage information.
To send or receive a message you must connect to the MMSC through the mode, which is the typically wwan0 interface on the PinePhone. It is sometimes also necessary to perform DNS lookups using your carriers DNS servers.
The MMSC is your carriers server that handle MMS messages. The easiest method to find it is by searching for apn settings for your carrier, and looking for the MMSC entry.
Use mmcli -s <Message ID> --create-file-with-data=<Notification> to save the
push notification to a file that can be passed to mmsutil.
Run mmsutil fetch <Notification> <Output File> to download the message. You
may also need to use the --dns and --interface flags to download messages.
See mmsutil fetch --help for more information, and Troubleshooting / Dns
queiries.
To send a message you'll need to a smil display section. This will be generated
in the near future. It is probably easiest to copy one from a message you've
received and decoded, and adapt it to the message you're sending.
The smil section should be the first file specified to the --file option, after
that specify any content files you'd like to send, such as text or images.
Messages can be encoded using mmsutil encode see mmsutil encode --help for
more information about encoding messages.
Once you have an encoded message it can be sent using something like curl -vv --interface wwan0 --data-binary "@encoded-message.bin" -H "Content-Type: application/vnd.wap.mms-message" -H "Expect:" "${mmsc}" -o response.bin
In some cases dns queries must be handled by the carrier. If they are not it will often result in inentelligable errors.
The most robust solution to this currently is to disable all network connections
except for the connection which goes through the modem. It should also be
possible to edit /etc/resolv.conf and remove all entries except for the
carriers dns servers, or to pass the dns servers to curl / mmsutil.
TLDR: If you get errors try disabling every network interface except the modem.
Note: In the future this software will automatically handle selecting the right dns server. I need to make sure dns queries are sent over the modem's interface.
I've used information from the oma Multi Media Messaging specs: http://www.openmobilealliance.org/release/MMS/ and parts of the OMA Wireless Application Protocal spec: http://www.openmobilealliance.org/wp/Affiliates/WAP.html