Troubleshooting and Understanding MMS

[epiii2]

I'm trying to figure out what my options might be for handling incoming MMS messages, with the understanding that they're not really supported by most software at the moment but there are some workarounds in use (like jmms for example). When I try out some test messages I can see the encoded data arrive via SMS and I can extract it to a file, but I'm stuck trying to make use of it because it doesn't seem to be formatted like other examples I see online. Does anyone have any experience they can share?

For example, here's what I see for a few MMS messages I sent myself the other day:

Code:

$ mmcli --messaging-list-sms -m 4
    /org/freedesktop/ModemManager1/SMS/2 (received)
    /org/freedesktop/ModemManager1/SMS/1 (received)
$ mmcli --messaging-list-sms -m 4 -s 2
  ----------------------------
  General    |          path: /org/freedesktop/ModemManager1/SMS/2
  ----------------------------
  Content    |        number: XXXXXXXXXX
            |          data: 000603BEAF848C82983046303633443133454142373030303032413630303030313031008D908A808E0278008805810306977F83687474703A2F2F36332E35352E312E38372F736572766C6574732F6D6D733F6D6573736167652D69643D00891680XXXXXXXXXXXXXXXXXXXX2F545950453D504C4D4E00
  ----------------------------
  Properties |      pdu type: cdma-deliver
            |          state: received
            | teleservice id: wap

(Just with the sender and receiver number Xd out.) And I can also dump that data chunk to a file like so and get the binary for that hexadecimal glob:

Code:

mmcli -m 4 -s 2 --create-file-with-data message.sms

...but in any case the contents of the binary don't seem formatted the way tools like jmms expect. For example doing a hexdump on another test message:

Code:

00000000  00 06 03 be af 84 8c 82  98 30 35 30 36 33 44 35  |.........05063D5|
00000010  37 42 45 35 33 30 30 30  30 37 34 35 30 30 30 30  |7BE5300007450000|
00000020  31 30 31 00 8d 90 8a 80  8e 02 78 00 88 05 81 03  |101.......x.....|
00000030  06 97 7f 83 68 74 74 70  3a 2f 2f 36 39 2e 37 38  |....http://69.78|
00000040  2e 38 38 2e 31 30 32 2f  73 65 72 76 6c 65 74 73  |.88.102/servlets|
00000050  2f 6d 6d 73 3f 6d 65 73  73 61 67 65 2d 69 64 3d  |/mms?message-id=|
00000060  00 89 16 80 XX XX XX XX  XX XX XX XX XX XX 2f 54  |....XXXXXXXXXX/T|
00000070  59 50 45 3d 50 4c 4d 4e  00                       |YPE=PLMN.|
00000079

So... what is this weird format? The main thing I see is that URL pointing to a Verizon server where I can hypothetically get the contents of the MMS (I think?) but I don't know what these other mostly-binary chunks are, aside from the sender's phone number and /TYPE=PLMN. The Verizon server never seems to respond to me no matter what I send (via wwan0, too, as I've read about elsewhere) but maybe I don't know what I'm supposed to give for the message ID. Any tips?