07-24-2022, 07:31 AM
The files in ~/.mms/modemmanager/ are MMS messages that are being processed.
My understanding of the process for receving a MMS: ModemManager gets a special SMS. It puts that raw message in a file in ~/.mms/modemmanager/ and then creates a similarly-named ".state" file with metadata for that message. MMSDTNG then attempts to process those messages, which are mostly just a URL where the actual content can be retrieved from the carrier. The MMS data expires after about 5 days (for Verizon) so if MMSDTNG can't get it by then, you'll never get it. I wonder if that's what the 404 might be? Seems like MMSDTNG should be smart enough to quit trying the expired messages, though.
Things to try:
1) You'll see entries in the logs like "Using URI for request: http://63.55.99.247/servlets/mms?message...XXXXXXXXXX". Open a shell and use curl or wget to get the contents of that URL, or see what error happens.
2) do a "ip route get 63.55.99.247" (or whatever IP is appropriate) on the phone to see if it has a viable route to the carrier's server.
My understanding of the process for receving a MMS: ModemManager gets a special SMS. It puts that raw message in a file in ~/.mms/modemmanager/ and then creates a similarly-named ".state" file with metadata for that message. MMSDTNG then attempts to process those messages, which are mostly just a URL where the actual content can be retrieved from the carrier. The MMS data expires after about 5 days (for Verizon) so if MMSDTNG can't get it by then, you'll never get it. I wonder if that's what the 404 might be? Seems like MMSDTNG should be smart enough to quit trying the expired messages, though.
Things to try:
1) You'll see entries in the logs like "Using URI for request: http://63.55.99.247/servlets/mms?message...XXXXXXXXXX". Open a shell and use curl or wget to get the contents of that URL, or see what error happens.
2) do a "ip route get 63.55.99.247" (or whatever IP is appropriate) on the phone to see if it has a viable route to the carrier's server.
