MMS success and failure
-
@rik
Ugh... some simple tasks are so complicated... After copying gprs to my home folder, if i tried to open it, the OS only offered going to the Open Store. I tried Document Viewer, but it won't open anything not in the Documents folder. So i moved gprs to Documents, but then i couldn't find a way to copy the text. And after trying to download a couple text editors, none of those seemed to have a way to search folders for me to open the file.There must be an easier way, or i'm missing something.
So i'm manually typing out the results here. gprs contains the following:
[Settings] Powered=1 RoamingAllowed=1 [context1] Name=Bell internet AccessPointName=pda2.bell.ca Username= Password= AuthenticationMethod=chap Type=internet Protocal=ip Preferred=true MessageProxy= MessageCenter= [context2] Name=Virgin mms AccessPointName=pda.bell.ca Username= Password= AuthenticationMethod=chap Type=mms Protocal=ip Preferred=true MessageProxy=web.wireless.bell.ca:80 MessageCenter=http://mms.bell.ca/mms/wapenc -
@fizz you can install "Seabass" from the Open Store to better view and edit text files.
Looking at your entries, the different things that stand out from mine are:
AuthenticationMethod=chap(mine isany)- I do not need any proxy settings for USA T-Mobile, so my MessageProxy is empty.... but it seems you do need it according to guides on the internet. I guess it wouldn't hurt to try without it?
For reference here is my gprs file when using separate APNs for Internet and MMS (the
IMSone comes back each time if I manually remove it, but it also doesn't even show in the GUI so I think we can ignore it?):[Settings] Powered=1 RoamingAllowed=false [context3] Name=IMS AccessPointName=ims Username= Password= AuthenticationMethod=none Type=ims Protocol=dual Preferred=false [context4] Name=Internet/WebConnect AccessPointName=epc.tmobile.com Username= Password= AuthenticationMethod=none Type=internet Protocol=ip Preferred=true [context6] Name=US Mobile MMS AccessPointName=pwg Username= Password= AuthenticationMethod=any Type=mms Protocol=ip Preferred=true MessageProxy= MessageCenter=http://pwg.mmsmvno.com/mms/wapenc -
@rik said in MMS success and failure:
Can you try a receive MMS image? Other Canadian users reported they had trouble sending MMS but could receive. It doesn't solve your issue but helps identify where the problem may be?
All the errors i have included are for when i try to receive. I can send images no problem, but i can't receive. The only thing i can receive are ordinary text messages.
Mine also fails for group messages. That is, if someone sends out a mass message on which i am included, i get the same error message.
-
@rik
I've installed Seabass2 and it looks promising. Thanks for that.I tried removing the MessageProxy entry, and that doesn't seem to make a difference.
In comparing to your settings: you have Roaming as false, while mine is true. Might this do something?
Is it possible for me to change the AuthenticaionMethod? It doesn't seem so via Settings, so i guess i'd have to manually edit the file. (Does Seabass2 have a sudo mode where i can see and modify the gprs file?)
I'm not sure what else i can try.
-
@ronbillock said in MMS success and failure:
the message that continued to fail was from iMessage/IOS
Apple has a feature that detects if the contact is an iOS user or not and then decide to send a MMS or an iMessage.
Maybe switching from iOS to Ubuntu Touch lead to iOS sending an iMessage when it is not compatible with Ubuntu Touch.Checking and sharing the logs migh help to figure this out.
I doubt Apple took into account people switching from iOS to something different from Android. -
@fizz said in MMS success and failure:
@rik said in MMS success and failure:
Can you try a receive MMS image? Other Canadian users reported they had trouble sending MMS but could receive. It doesn't solve your issue but helps identify where the problem may be?
All the errors i have included are for when i try to receive. I can send images no problem, but i can't receive. The only thing i can receive are ordinary text messages.
Mine also fails for group messages. That is, if someone sends out a mass message on which i am included, i get the same error message.
OK that is good progress: were you previously able to receive MMS or is that relatively recent? Anyway, it seems like you are in a similar situation as @StandUpMobile now, is that right @StandUpMobile ?
Can you try creating the MMS group (with the people icon to the right of the "TO" field, not just by clicking + and adding individuals) with multiple people then see if you can receive to it? It of course takes a bit of cooperation from willing friends
If you can receive those, then it seems the only / main issue is when you send it doesn't have a URL of where to send the messages. Why is this? Not sure but again I think that is the same that @StandUpMobile is seeing, we will wait for him to confirm.
-
@rik said in MMS success and failure:
@fizz said in MMS success and failure:
@rik said in MMS success and failure:
Can you try a receive MMS image? Other Canadian users reported they had trouble sending MMS but could receive. It doesn't solve your issue but helps identify where the problem may be?
All the errors i have included are for when i try to receive. I can send images no problem, but i can't receive. The only thing i can receive are ordinary text messages.
Mine also fails for group messages. That is, if someone sends out a mass message on which i am included, i get the same error message.
OK that is good progress: were you previously able to receive MMS or is that relatively recent? Anyway, it seems like you are in a similar situation as @StandUpMobile now, is that right @StandUpMobile ?
No, ever since i installed Ubuntu Touch, i've been able to send / receive ordinary texts, and send MMS (images) to others. But i have never been able to receive MMS (images or group messages).
So apologies if i gave the wrong impression, but from my perspective nothing has changed ever since i got Ubuntu Touch. It's always been this way.
Can you try creating the MMS group (with the people icon to the right of the "TO" field, not just by clicking + and adding individuals) with multiple people then see if you can receive to it? It of course takes a bit of cooperation from willing friends
I've learned i can text myself (tried sending an image over text to myself, which still fails). So perhaps i can include myself in a group. Let me try...
OK, i successfully sent a group message (to myself and the wifey), and i successfully received the message. So perhaps it's not considered a MMS. I know others have included me on group messages and they have given the same kind of error as when they try to send me an image.
So perhaps saying "group message" is a misnomer on my part, and we should just focus on my inability to receive MMS (any time someone tries to include an image in their text to me, it fails).
-
@ronbillock Yes, I switched providers, from Google Fi to Red Pocket.
-
@fizz said in MMS success and failure:
So perhaps saying "group message" is a misnomer on my part, and we should just focus on my inability to receive MMS (any time someone tries to include an image in their text to me, it fails).
OK sorry I was mixed up previously on if you could send or receive. So for failed incoming MMS, can you get them with wget? Then we could confirm it is NOT a group MMS. If it IS a group MMS, then if you manually create the group with the members, then re-attempt download it may work. Additionally, for failed MMS due to wifi being connected, you need to wait at least 1 minute after failure (and disconnect wifi) before re-trying.
Anyway, getting with wget would be informative if possible. Your older logs indicated no ril context (that was when trying the wrong APN entries), then your later log was when attempting to send, so I don't think we have an example here at least of the log when attempting to receive.
-
@rik is this what the output should look like?
phablet@ubuntu-phablet:~$ wget http://mt.t-mobile.com/mm?T=m-6-2a6-1-8690c1-9b
--2022-01-19 17:10:00-- http://mt.t-mobile.com/mm?T=m-6-2a6-1-8690c1-9b
Resolving mt.t-mobile.com (mt.t-mobile.com)... 10.188.75.137, 64:ff9b:
4b89
Connecting to mt.t-mobile.com (mt.t-mobile.com)|10.188.75.137|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 268410 (262K) [application/vnd.wap.mms-message]
Saving to: ‘mm?T=m-6-2a6-1-8690c1-9b’mm?T= 0% 0 --.-KB/s mm?T=m 12% 32.96K 121KB/s mm?T=m- 61% 161.97K 284KB/s mm?T=m-6-2a 100% 262.12K 421KB/s in 0.6s2022-01-19 17:10:01 (421 KB/s) - ‘mm?T=m-6-2a6-1-8690c1-9b’ saved [268410/268410]
This is greek to me. If this says nothing, is there a way to clear the log and then I can send a message from my wife and then after it 'oops' try and get the log again?
-
@applee which log(s)?
-
@ronbillock said in MMS success and failure:
Saving to: ‘mm?T=m-6-2a6-1-8690c1-9b’
Your output shows that you successfully downloaded the MMS message with wget. You will find a file in your home directory named
mm?T=m-6-2a6-1-8690c1-9b. Don't you love those filenames? Open the file with "Seabass" so you can read it, again I suspect the reason the download in the messaging app failed is because this is a group message. The first few lines of the message will list the phone numbers part of the group. Use them to manually create the MMS group. Then try download again from messaging app. Hopefully it completes.NO this isn't a solution, but it will hopefully show that the reason for the failure is the "known bug" that the MMS group must exist or else when downloading it fails. Please do report back so we can confirm or deny that we are on the right path.
-
@rik I downloaded Seabass2. I have never used it before but am familiar with nano. Unless I am doing something wrong, it appears the file is completely empty. Do I have to type anything in the Seabass window to get it to read the file or should it just open up when I select it?
-
@rik said in MMS success and failure:
OK sorry I was mixed up previously on if you could send or receive. So for failed incoming MMS, can you get them with wget? Then we could confirm it is NOT a group MMS. If it IS a group MMS, then if you manually create the group with the members, then re-attempt download it may work. Additionally, for failed MMS due to wifi being connected, you need to wait at least 1 minute after failure (and disconnect wifi) before re-trying.
I am happy to try. But i know little about wget other than it retrieves files. I see that i need the address of of the nuntium.log file, what would that address be?
-
@ronbillock said in MMS success and failure:
@applee which log(s)?
Nuntium, Ofono and maybe the messaging app
You can copy them to a pastebin (e.g. https://pastebin.ubuntu.com/) so we can read them.
The fresher the logs the better after receiving an MMS.I don't know how to analyze them but I know it will be helful to those who understand the inner mechanism of the MMS stack.
Best of luck
-
@applee well I am willing to do what I can to help but I will be on the road the next couple of days. Maybe I can re-engage when I have fresh 'failures'.
-
@ronbillock
Sure we cannot force you to swap phone/OS again
We're here to help those willing to give UT a try. -
@fizz said in MMS success and failure:
I am happy to try. But i know little about wget other than it retrieves files. I see that i need the address of of the nuntium.log file, what would that address be?
nuntium.logcan be found using "Log Viewer" app, or to directly find the file go to~/.cache/upstart/nuntium.log(you can also find compressed older versions in that upstart folder) -
@rik
Oh, i had provided details from nuntium.log in earlier messages, and i thought you said you wanted it retrieved from a server using wget.nuntium.log seems to get cleared every day (it's not listed as an available log file in Log Viewer currently). So i'll have to send myself a test or two. One moment...
-
@rik
And here is the output on nuntium after my failed attempt to receive (sending works) an image:2022/01/21 10:58:00 Encoding M-Send.Req 2022/01/21 10:58:00 Unhandled optional field Subject 2022/01/21 10:58:00 Unhandled optional field DeliveryTime 2022/01/21 10:58:00 Unhandled optional field Priority 2022/01/21 10:58:00 Unhandled optional field SenderVisibility 2022/01/21 10:58:00 Created /home/phablet/.cache/nuntium/store/f2d3e644112faeb31fa7a453f9b7c334.m-send.req to handle m-send.req for f2d3e644112faeb31fa7a453f9b7c334 2022/01/21 10:58:00 Trying to set Active property to true for context on true /ril_0/context2 2022/01/21 10:58:00 Starting upload of /home/phablet/.cache/nuntium/store/f2d3e644112faeb31fa7a453f9b7c334.m-send.req to http://mms.bell.ca/mms/wapenc with proxy 207.164.79.130:80 2022/01/21 10:58:00 Progress:302809 16384 2022/01/21 10:58:00 Progress:302809 98304 2022/01/21 10:58:00 Progress:302809 196608 2022/01/21 10:58:00 Progress:302809 302809 2022/01/21 10:58:01 File /home/phablet/.local/share/ubuntu-upload-manager/Downloads/f2d3e644112faeb31fa7a453f9b7c334.m-send.req.response returned in upload 2022/01/21 10:58:01 Trying to set Active property to false for context on false /ril_0/context2 2022/01/21 10:58:01 m-send.conf ResponseStatus for f2d3e644112faeb31fa7a453f9b7c334 is 128 2022/01/21 10:58:01 Status changed for /org/ofono/mms/302610917674682/f2d3e644112faeb31fa7a453f9b7c334 to Sent 2022/01/21 10:58:02 Received ReceiveNotification() method call from 44600 2022/01/21 10:58:02 Push data 00000000 00 06 29 1f 22 61 70 70 6c 69 63 61 74 69 6f 6e |..)."application| 00000010 2f 76 6e 64 2e 77 61 70 2e 6d 6d 73 2d 6d 65 73 |/vnd.wap.mms-mes| 00000020 73 61 67 65 00 81 84 af 84 8d 01 00 8c 82 98 66 |sage...........f| 00000030 39 35 63 34 66 35 64 62 64 63 32 38 66 34 39 39 |95c4f5dbdc28f499| 00000040 66 36 31 39 64 34 34 2d 31 00 8d 92 89 1a 80 18 |f619d44-1.......| 00000050 ea 2b 31 35 31 39 38 35 37 32 31 38 33 2f 54 59 |.+15198572183/TY| 00000060 50 45 3d 50 4c 4d 4e 00 96 00 8a 80 88 05 81 03 |PE=PLMN.........| 00000070 09 3a 7f 86 81 83 68 74 74 70 3a 2f 2f 6d 6d 73 |.:....http://mms| 00000080 63 32 2e 67 65 74 2e 62 65 6c 6c 2e 63 61 2f 63 |c2.get.bell.ca/c| 00000090 6c 6f 75 64 6d 6d 73 63 3f 6c 3d 66 39 35 63 34 |loudmmsc?l=f95c4| 000000a0 66 35 64 62 64 63 32 38 66 34 39 39 66 36 31 39 |f5dbdc28f499f619| 000000b0 64 34 34 2d 31 00 8e 03 04 5e 51 |d44-1....^Q| 2022/01/21 10:58:02 Trying to set Active property to true for context on true /ril_0/context2 2022/01/21 10:58:02 Download issues: org.freedesktop.DBus.Error.InvalidArgs: Invalid URL: '' 2022/01/21 10:58:02 Trying to set Active property to false for context on false /ril_0/context2 2022/01/21 10:58:03 Received unknown method call on org.ofono.mms.Message MarkRead 2022/01/21 10:58:03 Message /org/ofono/mms/302610917674682/a501466511fcc6e523913ca837fd7a0e is not responded and not expired, not deleted.
