07-23-2022, 11:58 AM
I've been following this post for some time now and am having the same problems. Thank you all for hashing this out so far. I can add a little more info I think.
I have been on the Matrix chat with kop316 (the author of mmsd-tng) trying to fix this also but he's at a loss too. He did tell me that these are not necessarily HTTP error codes but libsoup error codes.
I see the same types of files but I think these are test mms files that I try to send. I'm not positive because there are two files that are named similarly, one with what seems like a hash file name and the other with the same hash file name but also with a '.status' extension. The .status file shows that the message is unread and also lists the expiration. I think these are mms that I'm sending because I don't get a new file when someone tries to send me an mms; only when I send a test message to myself but this could be wrong.
This is interesting to me. I have seen messages received in Chatty that do not respect my current timezone so they are timestamped in the past by my GMT offset. I know that the time on my phone is right but the modem time may be wrong. I know that in ssl traffic your time skew can only be 5 minutes or messages will be discarded. That said, it seems like the message protocol is unencrypted (http) so this shouldn't matter but I don't know. It's definitely something else that I never considered until now.
(07-22-2022, 09:01 PM)pikurasa Wrote: As for the logs, if I have mmsc=http://mms.vtext.com/servlets/mms and apn=vzwinternet (in both chatty and gnome settings), I get http 7 errors. If I have mmsc=http://mms.vtext.com/servlets/mms and apn=vzwapp (in both chatty and gnome settings), I get http 404 errors.
I have been on the Matrix chat with kop316 (the author of mmsd-tng) trying to fix this also but he's at a loss too. He did tell me that these are not necessarily HTTP error codes but libsoup error codes.
(07-22-2022, 09:01 PM)pikurasa Wrote: Oddly enough, I seem to be able to send text with images (presumably mms) when set to mmsc=http://mms.vtext.com/servlets/mms and apn=vzwapp (in both chatty and gnome settings), but not able to receive them (I know I have missed group MMS texts b/c I am in constant communication with another person who I am in the group with). Also, oddly enough, I see some files in .mms/modenmanager that look suspiciously like MMS data (but not entirely human readable). This makes me wonder if I am receiving the MMS, but maybe chatty is not correctly adding them to the database. Or maybe, those files are a list of MMS that are suppose to be retrieved, but are failing to be retrieved. I have no idea, but curiosity is overwhelming me at the moment.
I see the same types of files but I think these are test mms files that I try to send. I'm not positive because there are two files that are named similarly, one with what seems like a hash file name and the other with the same hash file name but also with a '.status' extension. The .status file shows that the message is unread and also lists the expiration. I think these are mms that I'm sending because I don't get a new file when someone tries to send me an mms; only when I send a test message to myself but this could be wrong.
(07-22-2022, 09:01 PM)pikurasa Wrote: Also, another weird thing is, when I run: `mmcli -m any --time` it prints 2024-06-06 (but the timestamp on the debugger is the correct time).
This is interesting to me. I have seen messages received in Chatty that do not respect my current timezone so they are timestamped in the past by my GMT offset. I know that the time on my phone is right but the modem time may be wrong. I know that in ssl traffic your time skew can only be 5 minutes or messages will be discarded. That said, it seems like the message protocol is unencrypted (http) so this shouldn't matter but I don't know. It's definitely something else that I never considered until now.
