Yes, I had found that and looked up what allow_inactive vs allow_active meant and that was my impression. And by running chatty from the terminal instead of from a remote session, I got different output which you will see in the other post I just made.
1 Like
I also get the error “Couldn’t delete SMS - error: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: Couldn’t delete 2 parts from this SMS” but that does not prevent me from receiving MMS messages.
Looking back at the mmsd output you posted earlier and comparing to what I get, I think now I see a difference that could be important.
You posted this:
For me the corresponding part of mmsd output looks like this:
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:mms_parse_headers() saw header of type 11
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:mms_parse_headers() running handler for type 11
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:decode_text() claimed len: 18
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:decode_text() val: 717500249@mmscse1
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:mms_parse_headers() handler for type 11 was success
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:mms_parse_headers() saw header of type 25
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:mms_parse_headers() type isn't a part of the standard? Skipping 26
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:extract_content_id() extracted content-id <FOT4928.jpg>
Apr 16 00:04:51 pureos mmsd[590]: src/mmsutil.c:extract_content_id() extracted content-id <Smil.txt>
Apr 16 00:04:51 pureos mmsd[590]: src/service.c:activate_bearer() service 0xaaaae13a4b30 setup 0 active 1
So for me it says “extracted content-id <FOT4928.jpg>” which looks good, that .jpg is probably the image I received in the MMS.
But for you it instead says “extracted content-id” and nothing more, as if the content-id is nonexistent/empty.
What do you think @kop316 – could this be something, to find out why there is no content-id there? That could be figured out by adding some extra debug output in mmsd, perhaps?
I’m sorry at this point, I tried to read the thread a couple of times and I am not sure what I am trying to answer. Is it still this:
" I never get anything in ~/mms just in /.mms/modemmanager."
“extracted content-id” alone should be okay? but I am not as familiar with that part of the code. It looks to be here:
EDIT: Does this look familiar for the issue?:
@kop316 I see that you found a possible fix for the MMS issue I was seeing, so I started over with all the steps from https://source.puri.sm/Librem5/chatty/-/issues/30#note_151962. Unfortunately, I am unable to build mmsd anymore. If I do these steps:
mkdir mmsd
cd mmsd
git clone https://source.puri.sm/kop316/mmsd.git
cd mmsd/
git checkout debian/modemmanager/latest
sudo apt-get -y build-dep .
dpkg-buildpackage -us -uc -b
I get this error:
The following packages have unmet dependencies:
builddeps:. : Depends: debhelper-compat (= 13)
If I try to follow the instructions that you put at your git page for mmsd I can’t build because the version of meson I have is 0.51.1 but 0.56.0 or later is required.
Can you tell me how I can build your mmsd on librem 5 amber? Is it possible?
Thanks.
Good! Was it the SMIL issue? That turned out to be a silly mistake on my end, a pmOS dev was very nice in helping be figure it out. Everyone so far who has reported the issue says it is fixed.
HOWEVER, that was a purple-mm-sms bug, NOT an mmsd bug. You need to rebuild purple-mm-sms for the fix.
The following packages have unmet dependencies:
builddeps:. : Depends: debhelper-compat (= 13)
Mobian is on Bullseye, and Amber Phone is on Buster, so you need to change “Depends: debhelper-compat (= 13)” to “debhelper-compat (= 12)” :
If I try to follow the instructions that you put at your git page for mmsd I can’t build because the version of meson I have is 0.51.1 but 0.56.0 or later is required.
This is probably not an issue. This is what Mobian/pmOS had as their version…so I just stuck that number. Change this line:
to “0.51.1” instead of “0.56.0”
If you want to use the deb package, you can change it here:
So, I had already tried changing the debian control file, but that didn’t work.
So I tried changing meson.version in meson.build and that did seem to work, except that instead of:
meson compile -C _build
I had to do just:
meson compile
I verified that the change from Commit afffbef0 (changing a guint to a guint64 on line 1035) was there. I verified that the built mmsd was the one running but I am still not getting the MMS message, although it does show up in ~/.mms/modemanager (but nothing in ~/mms) and if I send it a regular text it goes through so things aren’t blocked. I will try getting further debug information later.
Thanks for all your help.
Hello,
The bug was in purple-mm-sms, NOT mmsd. Please redownload/compile/install purple-mm-sms.
Unfortunately I cannot do much without logs.
@kop316, sorry I guess I wasn’t clear. I needed to rebuild mmsd along with everything else because I had put on updates. I did rebuild the purple-mm-sms with this fix. I have verified that I have the newly built mm-sms.so in /usr/lib/purple-2 and that it is the one referenced by the running chatty.
No worries, just didn’t want you to be confused if a bug showed up again when it was fixed.
OK, here is the excerpt from mmsd with debugging on:
mmsd[2062]: …/src/mmsutil.c:mms_message_decode() about to check well known
mmsd[2062]: …/src/mmsutil.c:mms_message_decode() about to extract short
mmsd[2062]: …/src/mmsutil.c:mms_message_decode() octet 132
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 24
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() running handler for type 24
mmsd[2062]: …/src/mmsutil.c:decode_text() claimed len: 34
mmsd[2062]: …/src/mmsutil.c:decode_text() val: DLLB01030419205126521203000100000
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() handler for type 24 was success
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 13
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() running handler for type 13
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() handler for type 13 was success
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 23
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() running handler for type 23
mmsd[2062]: …/src/mmsutil.c:extract_text_array_element()
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() handler for type 23 was success
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 16
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 2
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 9
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() running handler for type 9
mmsd[2062]: …/src/mmsutil.c:extract_from() trying to decode text of length 22: +15612062856/TYPE=PLMN
mmsd[2062]: …/src/mmsutil.c:extract_from() text="+1[…]/TYPE=PLMN"
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() handler for type 9 was success
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 11
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() running handler for type 11
mmsd[2062]: …/src/mmsutil.c:decode_text() claimed len: 37
mmsd[2062]: …/src/mmsutil.c:decode_text() val: 139d4b85-4baa-49dc-8da4-7285144be58e
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() handler for type 11 was success
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 5
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() running handler for type 5
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() handler for type 5 was success
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 6
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() saw header of type 25
mmsd[2062]: …/src/mmsutil.c:mms_parse_headers() type isn’t a part of the standard? Skipping 26
mmsd[2062]: …/src/mmsutil.c:extract_content_id() extracted content-id
Note it does mention attachment this time, but again nothing in ~/mms.
And here is the debug output from chatty:
16:51:25) mm-sms: New SMS at ‘/org/freedesktop/ModemManager1/SMS/4’(sm.puri.Chatty:2094): mm-sms-DEBUG: 16:51:25.650: cb_dbus_signal_sms_added: New SMS at /org/freedesktop/ModemManager1/SMS/4
(sm.puri.Chatty:2094): mm-sms-DEBUG: 16:51:25.659: pur_mm_check_pdu_type: pdu type deliver
(sm.puri.Chatty:2094): mm-sms-DEBUG: 16:51:25.659: cb_sms_list_new_ready
(sm.puri.Chatty:2094): mm-sms-DEBUG: 16:51:26.408: Received SMS WAP! Sending proxy call to mmsd
(sm.puri.Chatty:2094): mm-sms-DEBUG: 16:51:26.409: cb_sms_state_change: state received
(sm.puri.Chatty:2094): mm-sms-DEBUG: 16:51:26.483: cb_pur_mmsd_push_notify
(sm.puri.Chatty:2094): mm-sms-DEBUG: 16:51:26.511: Couldn’t delete SMS - error: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Failed: Couldn’t delete 2 parts from this SMS
Do you think the issue is in the purple-mm-sms code or the mmsd code? I could try to put in some additional debug code in my copy if I knew the appropriate place.
Thanks.
On concerned about seeing the header 26…but maybe that’s a red herring.
Do you ever see a “MessageAdded” over the dbus? It looks like purple-mm-sms never sees the message.
No, the only thing I see monitoring the dbus is:
method call time=1618867920.222238 sender=:1.53 -> destination=:1.3 serial=126 path=/org/ofono/mms; interface=org.ofono.mms.ModemManager; member=PushNotify
array of bytes [
2d 06 22 61 70 70 6c 69 63 61 74 69 6f 6e 2f 76 6e 64 2e 77 61 70 2e 6d
6d 73 2d 6d 65 73 73 61 67 65 00 af 84 8c 82 98 44 4c 4c 42 30 32 30 33
30 34 31 39 32 31 33 31 35 39 35 32 32 32 30 33 30 30 30 30 38 30 30 30
30 00 8d 91 89 18 80 2b 31 35 36 31 32 30 36 32 38 35 36 2f 54 59 50 45
3d 50 4c 4d 4e 00 96 02 ea 00 86 81 8a 80 8e 02 4e 82 88 05 81 03 03 f4
80 83 68 74 74 70 3a 2f 2f 31 30 37 2e 31 32 35 2e 36 33 2e 32 31 33 3a
38 30 30 35 2f 59 2f 30 34 31 39 32 31 33 31 35 39 35 32 32 32 30 33 30
30 30 30 38 30 30 30 30 00
]
Hmmm…that sounds like the parser is erroring out.
I’ll try to make a debug build for you to try tonight or tomorrow to figure out what’s happening.
Please do the following things for me:
- Delete (or move out of the folder) any MMSes in $HOME/.mms/ModemManager
- Start mmsd
- Recieve an MMS
- close mmsd
- Post the FULL log of the events here.
This will help me figure out the issue and where to put the debug messages.
Looking through the code again, I suspect mmsd is silently erroring out somewhere, but without the full log, it is hard for me to tell where.
Edit: Actually if you could, please file an issue here: https://source.puri.sm/kop316/mmsd/
Part of my problem is it was hard to parse through the logs here on what’s happening, and that’s why I got confused.
I have the log, but unfortunately I tried to register for source.puri.sm last week but I am still waiting for approval. Is there another way I can get the log to you?
Hmm,
That is worrying if that’s happening (though I guess I’m not surprised that they want to give approvals now).
You can post it here then and I can cross post it.
MMS daemon version 0.1-4
mmsd[2861]: …/src/service.c:__mms_service_init()
mmsd[2861]: …/src/plugin.c:__mms_plugin_init()
mmsd[2861]: …/src/service.c:mms_service_create() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:mms_service_set_identity() service 0xaaaae5e59f30 identity modemmanager
mmsd[2861]: …/src/plugin.c:add_plugin() Plugin modemmanager loaded
mmsd[2861]: …/src/plugin.c:add_plugin() Plugin ofono loaded
mmsd[2861]: …/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_MANAGER_FOUND
mmsd[2861]: …/plugins/modemmanager.c:cb_mm_manager_new() ModemManager found: :1.10
mmsd[2861]: …/plugins/modemmanager.c:mmsd_mm_add_object() Added device at: /org/freedesktop/ModemManager1/Modem/0
mmsd[2861]: …/plugins/modemmanager.c:mmsd_mm_init_modem() Not autoprocessing SMS WAPs
mmsd[2861]: …/plugins/modemmanager.c:mmsd_mm_init_modem() mmsd_mm_init_modem
mmsd[2861]: …/plugins/modemmanager.c:mmsd_mm_get_modem_state() MM_MODEM_GOOD_STATE: 11
mmsd[2861]: …/plugins/modemmanager.c:mmsd_mm_state() MMSD_MM_STATE_READY
mmsd[2861]: …/plugins/modemmanager.c:mmsd_plugin_connect() Registering Modem Manager MMS Service
mmsd[2861]: …/src/service.c:mms_service_register() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:emit_service_added() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:mms_load_settings() Maximum Attachment Total Size (in bytes): 1400000
mmsd[2861]: src/service.c:load_message_from_store() There is no date stamp!
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to check well known
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to extract short
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() octet 132
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 24
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 24
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 34
mmsd[2861]: …/src/mmsutil.c:decode_text() val: ATNB04050419211907424005000190000
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 24 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 13 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 11
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 11
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 37
mmsd[2861]: …/src/mmsutil.c:decode_text() val: 1c4b30fb-c6ef-44fd-9cec-2d97b1912aab
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 11 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 23
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 23
mmsd[2861]: …/src/mmsutil.c:extract_text_array_element()
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 23 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 9
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 9
mmsd[2861]: …/src/mmsutil.c:extract_from() trying to decode text of length 22: +1[…]/TYPE=PLMN
mmsd[2861]: …/src/mmsutil.c:extract_from() text="+1[…]/TYPE=PLMN"
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 9 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 16
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 5 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 6
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 25
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() type isn’t a part of the standard? Skipping 26
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 setup 0 active 0
mmsd[2861]: src/service.c:load_message_from_store() There is no date stamp!
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to check well known
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to extract short
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() octet 132
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 24
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 24
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 34
mmsd[2861]: …/src/mmsutil.c:decode_text() val: DLLB02030419213159522203000080000
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 24 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 13 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 23
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 23
mmsd[2861]: …/src/mmsutil.c:extract_text_array_element()
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 23 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 16
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 2
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 9
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 9
mmsd[2861]: …/src/mmsutil.c:extract_from() trying to decode text of length 22: +1[…]/TYPE=PLMN
mmsd[2861]: …/src/mmsutil.c:extract_from() text="+1[…]/TYPE=PLMN"
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 9 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 11
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 11
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 37
mmsd[2861]: …/src/mmsutil.c:decode_text() val: 8905eb20-98d2-4b16-821e-923408f96bda
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 11 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 5 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 6
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 25
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() type isn’t a part of the standard? Skipping 26
mmsd[2861]: …/src/mmsutil.c:extract_content_id() extracted content-id
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 setup 0 active 0
mmsd[2861]: src/service.c:load_message_from_store() There is no date stamp!
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to check well known
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to extract short
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() octet 132
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 24
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 24
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 34
mmsd[2861]: …/src/mmsutil.c:decode_text() val: DLLA04020419211654524202000230000
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 24 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 13 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 11
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 11
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 37
mmsd[2861]: …/src/mmsutil.c:decode_text() val: 366b63d2-c63c-42c1-9c84-60de95f0c57f
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 11 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 23
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 23
mmsd[2861]: …/src/mmsutil.c:extract_text_array_element()
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 23 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 9
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 9
mmsd[2861]: …/src/mmsutil.c:extract_from() trying to decode text of length 22: +1[…]/TYPE=PLMN
mmsd[2861]: …/src/mmsutil.c:extract_from() text="+1[…]/TYPE=PLMN"
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 9 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 16
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 5 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 6
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 25
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() type isn’t a part of the standard? Skipping 26
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 setup 0 active 0
mmsd[2861]: src/service.c:load_message_from_store() There is no date stamp!
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to check well known
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to extract short
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() octet 132
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 24
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 24
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 34
mmsd[2861]: …/src/mmsutil.c:decode_text() val: ATNA03020419213023413002000120000
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 24 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 13 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 23
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 23
mmsd[2861]: …/src/mmsutil.c:extract_text_array_element()
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 23 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 16
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 2
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 9
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 9
mmsd[2861]: …/src/mmsutil.c:extract_from() trying to decode text of length 22: +1[…]/TYPE=PLMN
mmsd[2861]: …/src/mmsutil.c:extract_from() text="+1[…]/TYPE=PLMN"
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 9 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 11
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 11
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 37
mmsd[2861]: …/src/mmsutil.c:decode_text() val: 08523da1-849d-4510-ba6f-8fe85172c09e
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 11 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 5 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 6
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 25
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() type isn’t a part of the standard? Skipping 26
mmsd[2861]: …/src/mmsutil.c:extract_content_id() extracted content-id
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 setup 0 active 0
mmsd[2861]: …/plugins/modemmanager.c:mmsd_plugin_connect() Setting Bearer Handler
mmsd[2861]: …/src/service.c:mms_service_set_bearer_handler() service 0xaaaae5e59f30 handler 0xaaaaac67044c
mmsd[2861]: …/plugins/modemmanager.c:mmsd_mm_state() Not checking SMS WAPs
mmsd[2861]: …/plugins/modemmanager.c:mmsd_mm_get_modem_state() Auto processing unsent/unrecieved messages per settings.
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 setup 0 active 0
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 waiting for 20 seconds
mmsd[2861]: …/plugins/modemmanager.c:set_context() Setting Context…
mmsd[2861]: …/src/service.c:mms_service_set_mmsc() service 0xaaaae5e59f30 mmsc https://mmsc.mobile.att.net
mmsd[2861]: …/plugins/modemmanager.c:set_context() Max number of bearers: 1
mmsd[2861]: …/plugins/modemmanager.c:set_context() Current Context APN: reseller, mmsd settings MMS APN: reseller
mmsd[2861]: …/plugins/modemmanager.c:set_context() You are connected to the correct APN! Enabling context…
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/0 active 1 context_active 1
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() active and context_active, bearer_notify
mmsd[2861]: …/src/service.c:mms_service_bearer_notify() service=0xaaaae5e59f30 active=1 iface=wwan0 proxy:80=proxy.mobile.att.net
mmsd[2861]: …/src/service.c:mms_service_bearer_notify() interface wwan0 proxy proxy.mobile.att.net:80
mmsd[2861]: …/src/service.c:process_request_queue() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:process_request_queue() location (null)
mmsd[2861]: Cannot process request (request type: 2)
mmsd[2861]: …/src/service.c:process_request_queue() location (null)
mmsd[2861]: Cannot process request (request type: 2)
mmsd[2861]: …/src/service.c:process_request_queue() location (null)
mmsd[2861]: Cannot process request (request type: 2)
mmsd[2861]: …/src/service.c:process_request_queue() location (null)
mmsd[2861]: Cannot process request (request type: 2)
mmsd[2861]: …/src/service.c:get_messages()
mmsd[2861]: …/plugins/modemmanager.c:cb_get_sim_ready() Got SIM Path: /org/freedesktop/ModemManager1/SIM/0 Identifier: 89014104279702124090, imsi: 310410970212409
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 setup 0 active 1
mmsd[2861]: …/src/service.c:process_request_queue() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:bearer_idle_timeout() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:deactivate_bearer() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:deactivate_bearer() service 0xaaaae5e59f30
mmsd[2861]: …/plugins/modemmanager.c:set_context() Setting Context…
mmsd[2861]: …/src/service.c:mms_service_set_mmsc() service 0xaaaae5e59f30 mmsc https://mmsc.mobile.att.net
mmsd[2861]: …/plugins/modemmanager.c:set_context() Max number of bearers: 1
mmsd[2861]: …/plugins/modemmanager.c:set_context() Current Context APN: reseller, mmsd settings MMS APN: reseller
mmsd[2861]: …/plugins/modemmanager.c:set_context() You are connected to the correct APN! Enabling context…
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/0 active 0 context_active 1
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() checking for failure
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() No failures
mmsd[2861]: …/src/service.c:mms_service_bearer_notify() service=0xaaaae5e59f30 active=0 iface=wwan0 proxy:80=proxy.mobile.att.net
mmsd[2861]: …/plugins/modemmanager.c:handle_method_call() handle_method_call
mmsd[2861]: …/src/service.c:mms_service_push_notify() service 0xaaaae5e59f30 data 0xffff94011400 len 177
mmsd[2861]: …/src/service.c:mms_service_push_notify() about to push notify
mmsd[2861]: …/src/push.c:mms_push_notify() pdu 0xffff94011400 len 177
mmsd[2861]: …/src/push.c:mms_push_notify() 2D06226170706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676500AF848C8298444C4C413033303330343139323233333331353233323033303030303030303030008D918918802B31353631323036323835362F545950453D504C4D4E009602EA0086818A808E024E828805810303F48083687474703A2F2F3130372E3132352E36332E3130303A383030352F592F3034313932323333333135323332303330303030303030303000
mmsd[2861]: Body Length: 140
mmsd[2861]: …/src/service.c:mms_service_push_notify() did push notify; about to store
mmsd[2861]: …/src/store.c:generate_uuid_from_pdu() pdu 0xffff94011425 len 140
mmsd[2861]: …/src/store.c:mms_store() pathname /home/purism/.mms/modemmanager/EBBD68242206333C8793B30116F19F65B43EE09A
mmsd[2861]: …/src/service.c:mms_service_push_notify() did store; about to decode
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to check well known
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to extract short
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() octet 130
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 24
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 24
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 34
mmsd[2861]: …/src/mmsutil.c:decode_text() val: DLLA03030419223331523203000000000
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 24 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 13 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 9
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 9
mmsd[2861]: …/src/mmsutil.c:extract_from() trying to decode text of length 22: +1YPE=PLMN
mmsd[2861]: …/src/mmsutil.c:extract_from() text="+1[…]/TYPE=PLMN"
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 9 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 22
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 22
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 22 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 6
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 10
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 10
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 10 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 14
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 14
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 14 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 8
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 8
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 8 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 3
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 3
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 55
mmsd[2861]: …/src/mmsutil.c:decode_text() val: http://107.125.63.100:8005/Y/0419223331523203000000000
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 3 was success
mmsd[2861]: …/src/service.c:mms_service_push_notify() did decode message
mmsd[2861]: …/src/service.c:mms_service_push_notify() is type NI?
mmsd[2861]: …/src/service.c:mms_service_push_notify() type is NI
mmsd[2861]: MMS transaction id: DLLA03030419223331523203000000000
mmsd[2861]: MMS version: 1.1
mmsd[2861]: From: +1[…]/TYPE=PLMN
mmsd[2861]: Subject:
mmsd[2861]: Class: Personal
mmsd[2861]: Size: 20098
mmsd[2861]: Expiry: 2021-04-22T18:33:33-0400
mmsd[2861]: Location: http://107.125.63.100:8005/Y/0419223331523203000000000
mmsd[2861]: …/src/service.c:mms_service_push_notify() about to store_meta_open 2
mmsd[2861]: …/src/service.c:mms_service_push_notify() did store_meta_open 2
mmsd[2861]: …/src/service.c:mms_service_push_notify() did create_request
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 setup 0 active 0
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 waiting for 20 seconds
mmsd[2861]: …/plugins/modemmanager.c:set_context() Setting Context…
mmsd[2861]: …/src/service.c:mms_service_set_mmsc() service 0xaaaae5e59f30 mmsc https://mmsc.mobile.att.net
mmsd[2861]: …/plugins/modemmanager.c:set_context() Max number of bearers: 1
mmsd[2861]: …/plugins/modemmanager.c:set_context() Current Context APN: reseller, mmsd settings MMS APN: reseller
mmsd[2861]: …/plugins/modemmanager.c:set_context() You are connected to the correct APN! Enabling context…
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/0 active 1 context_active 1
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() active and context_active, bearer_notify
mmsd[2861]: …/src/service.c:mms_service_bearer_notify() service=0xaaaae5e59f30 active=1 iface=wwan0 proxy:80=proxy.mobile.att.net
mmsd[2861]: …/src/service.c:mms_service_bearer_notify() interface wwan0 proxy proxy.mobile.att.net:80
mmsd[2861]: …/src/service.c:process_request_queue() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:process_request_queue() location http://107.125.63.100:8005/Y/0419223331523203000000000
mmsd[2861]: …/src/service.c:web_get_cb() status: 200
mmsd[2861]: …/src/service.c:web_get_cb() data size = 20137
mmsd[2861]: …/src/service.c:web_get_cb() request->result_cb=0xaaaaac661694 vs. retrieve_conf=0xaaaaac661694/send_conf=0xaaaaac65e32c/notify_resp=0xaaaaac661510
mmsd[2861]: …/src/store.c:generate_uuid_from_pdu() pdu 0xffffa0edb000 len 20137
mmsd[2861]: …/src/store.c:mms_store_file() pathname /home/purism/.mms/modemmanager/1EA8E994B64C60A5825E18AEE69E100D1F411470
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to check well known
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() about to extract short
mmsd[2861]: …/src/mmsutil.c:mms_message_decode() octet 132
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 24
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 24
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 34
mmsd[2861]: …/src/mmsutil.c:decode_text() val: DLLA03030419223331523203000000000
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 24 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 13
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 13 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 23
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 23
mmsd[2861]: …/src/mmsutil.c:extract_text_array_element()
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 23 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 16
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 2
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 9
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 9
mmsd[2861]: …/src/mmsutil.c:extract_from() trying to decode text of length 22: +1[…]/TYPE=PLMN
mmsd[2861]: …/src/mmsutil.c:extract_from() text="+1[…]/TYPE=PLMN"
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 9 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 11
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 11
mmsd[2861]: …/src/mmsutil.c:decode_text() claimed len: 37
mmsd[2861]: …/src/mmsutil.c:decode_text() val: 12a69e28-0a1c-4943-83ac-a094bc551de4
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 11 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() running handler for type 5
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() handler for type 5 was success
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 6
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() saw header of type 25
mmsd[2861]: …/src/mmsutil.c:mms_parse_headers() type isn’t a part of the standard? Skipping 26
mmsd[2861]: …/src/mmsutil.c:extract_content_id() extracted content-id
mmsd[2861]: …/src/service.c:activate_bearer() service 0xaaaae5e59f30 setup 0 active 1
mmsd[2861]: …/src/service.c:process_request_queue() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:process_request_queue() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:process_request_queue() location (null)
mmsd[2861]: Cannot process request (request type: 2)
mmsd[2861]: …/src/service.c:bearer_idle_timeout() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:deactivate_bearer() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:deactivate_bearer() service 0xaaaae5e59f30
mmsd[2861]: …/plugins/modemmanager.c:set_context() Setting Context…
mmsd[2861]: …/src/service.c:mms_service_set_mmsc() service 0xaaaae5e59f30 mmsc https://mmsc.mobile.att.net
mmsd[2861]: …/plugins/modemmanager.c:set_context() Max number of bearers: 1
mmsd[2861]: …/plugins/modemmanager.c:set_context() Current Context APN: reseller, mmsd settings MMS APN: reseller
mmsd[2861]: …/plugins/modemmanager.c:set_context() You are connected to the correct APN! Enabling context…
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() At Bearer Handler: path /org/freedesktop/ModemManager1/Modem/0 active 0 context_active 1
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() checking for failure
mmsd[2861]: …/plugins/modemmanager.c:bearer_handler() No failures
mmsd[2861]: …/src/service.c:mms_service_bearer_notify() service=0xaaaae5e59f30 active=0 iface=wwan0 proxy:80=proxy.mobile.att.net
mmsd[2861]: Terminating
mmsd[2861]: …/src/plugin.c:__mms_plugin_cleanup()
mmsd[2861]: …/src/service.c:mms_service_unregister() service 0xaaaae5e59f30
mmsd[2861]: …/src/service.c:emit_service_removed() service 0xaaaae5e59f30
mmsd[2861]: …/plugins/modemmanager.c:mmsd_plugin_disconnect() Disabling Bearer Handler
mmsd[2861]: …/src/service.c:mms_service_set_bearer_handler() service 0xaaaae5e59f30 handler (nil)
mmsd[2861]: …/src/service.c:__mms_service_cleanup()
mmsd[2861]: Exit
setting proxy proxy.mobile.att.net:80
request https://mmsc.mobile.att.net
address proxy.mobile.att.net
port 80
host mmsc.mobile.att.net
flags 1
request https://mmsc.mobile.att.net
content-type application/vnd.wap.mms-message
binding wwan0
using TLS encryption
channel missing
request https://mmsc.mobile.att.net
address proxy.mobile.att.net
port 80
host mmsc.mobile.att.net
flags 1
request https://mmsc.mobile.att.net
content-type application/vnd.wap.mms-message
binding wwan0
using TLS encryption
channel missing
request https://mmsc.mobile.att.net
address proxy.mobile.att.net
port 80
host mmsc.mobile.att.net
flags 1
request https://mmsc.mobile.att.net
content-type application/vnd.wap.mms-message
binding wwan0
using TLS encryption
channel missing
request https://mmsc.mobile.att.net
address proxy.mobile.att.net
port 80
host mmsc.mobile.att.net
flags 1
request https://mmsc.mobile.att.net
content-type application/vnd.wap.mms-message
binding wwan0
using TLS encryption
channel missing
setting proxy proxy.mobile.att.net:80
request http://107.125.63.100:8005/Y/0419223331523203000000000
address proxy.mobile.att.net
port 80
host 107.125.63.100:8005
flags 0
request http://107.125.63.100:8005/Y/0419223331523203000000000
binding wwan0
no encryption
creating session proxy.mobile.att.net:80
request http://107.125.63.100:8005/Y/0419223331523203000000000 from 107.125.63.100:8005
status 1 bytes to write 154 bytes written 154
bytes read 185
[header] HTTP/1.1 200 OK
[header] Date: Mon, 19 Apr 2021 22:33:35 GMT
[header] Content-Length: 20137
[header] Content-Type: application/vnd.wap.mms-message
[header] Via: 1.1 proxy.mobile (HPM/14.09.0099)
[header] Connection: close
[body] length 0
bytes read 1392
[body] length 1392
bytes read 2047
[body] length 2047
bytes read 737
[body] length 737
bytes read 1392
[body] length 1392
bytes read 1392
[body] length 1392
bytes read 1392
[body] length 1392
bytes read 2047
[body] length 2047
bytes read 2047
[body] length 2047
bytes read 2047
[body] length 2047
bytes read 819
[body] length 819
bytes read 1392
[body] length 1392
bytes read 1392
[body] length 1392
bytes read 2041
[body] length 2041
bytes read 0
request https://mmsc.mobile.att.net
address proxy.mobile.att.net
port 80
host mmsc.mobile.att.net
flags 1
request https://mmsc.mobile.att.net
content-type application/vnd.wap.mms-message
binding wwan0
using TLS encryption
channel missing
Ok, I may see where it is. I will try to make a debug version to try.
By the way, i fyou have matrix, I am also on the comunity/librem-5 channel. That may be easier to find me and work with me.
Ok, here is the debug branch:
Please compile and run it.
2 Likes
As a Heads up, there is an issue with mmsd. The payload does not have expected headers so mmsd errors out.
I need to fix it, and @francepat has been kind enough to help me with it.
EDIT:
@francepat: I think I fixed the issue.
Please test: https://source.puri.sm/kop316/mmsd/-/tree/debug-francepat
and let me know if it worked.
As a note for anyone else, if it works I will merge it, and it is only for specific use cases, so don’t try to compile/use this unless you have a good reason to (like you are francepat, or have the same problems).
2 Likes