(01-10-2021, 10:37 AM)antiX-Dave Wrote: 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.
I just fixed the segfault issue, that was in purple-mm-sms. There are still some sync issues in purple-mm-sms that I need to fix though, so if weird things happen, load mmsd then load chatty. EDIT: I fixed that issue, you can load chatty and mmsd in any order now.
Without seeing the mmsd debug output, I couldn't tell you what the issue is unfortunately. Kent was the one who figured out how to navigate the mmsproxy, T-Mobile doesn't have it. His repo is here, and it may provide clues as to how to solve this: https://source.puri.sm/Kent/mmsd
I know what I have works if the mmsproxy is a domain name vs. an ip address (It was tested on H2O), so it may have to do with the mmsproxy being a raw ip address? See what happens if you uncomment this line:
https://source.puri.sm/kop316/mmsd/-/blo...eb.c#L1313
Kent, do you have any ideas?
