mms technical question
asked 2018-08-31 04:32:02 +0300
I've seen this - https://together.jolla.com/question/173149/mms-not-working-on-sailfish-x/ - and maybe that's all there is to it, but I'm having a problem with mms, and I wondered about how it actually works technically, because it seems like it doesn't add up...
I'm using Xperia X Compact, community port, v. 2.1.3.7. My mobile provider is Ting, which uses T-Mobile towers, (USA). Mobile data works fine. Sms works fine. When I send mms crom a different phone to this phone, sending is successful from the other phone, and I get a notification on this phone that a message is 'downloading'. Progress spinner goes for about 2 minutes, then stops with 'problrm with downloading' message. If I send mms from this phone, I get the same spinner for the same amount of time, then problem with sending' message. I've tried with default data and mms settings, automatically detected by the phone to be T-Mobile, and also with Ting-specific settings fromtheir support site. Results are the same with both.
It seems to me that if the problem was carrier- or settings-related, there would be no indication of an incoming message, but I don't really understand how mms works. Any ideas?
One thing I wondered about is that Sailfish mms settings include a field for proxy and port, which is auto-filled with T-Mobile default settings, but Ting support site doesn't list that info. I don't know if that would be different, and, if so, how to figure out what it should be...
Reading https://help.ting.com/hc/en-us/articles/205421078-Troubleshooting-GSM-Picture-Video-MMS-Messaging I found that many were helped by setting the MMSC URL to the T-mobile URL, but still using Ting APN. Also I didn't find a reference to proxy either, so I'd try with those fields empty. I don't understand the differences between 7 digits vs 10-11 digits, but have you verified this?
Mohjive ( 2018-08-31 08:55:49 +0300 )editHere's a good tutorial about how MMS works; https://www.nowsms.com/faq/how-mms-works
Your problem is in the message data sending/recaiving part; seems your device cannot make the connection to the mmsc url to push or pull messages
juiceme ( 2018-08-31 09:20:05 +0300 )edit@Mohjive - I just looked into it, and the problem with that solution is that it says "...delete the Ting MMS APN and used the T-Mob MMSC url in the MMSC field of the Ting Data APN.". In Android, all of the information is in one setting, 'apn', but in Sailfish, it's separated into 'data', and 'mms', and there's no place in the data settings to put an mmsc url. Going to keep messing around ...
Levone1 ( 2018-09-01 03:12:27 +0300 )edit@Levone1 that's one persons fix. If you read more comments you can see that more people have had success using the T-mobile MMSC URI, not changing the APN, neither for data nor MMS.
Mohjive ( 2018-09-01 16:33:03 +0300 )editTried multiple different configurations, (Ting data apn and Ting mms apn, with T-Mobile mmsc; Ting data apn with T-Mobile mms apn and mmsc; T- Mobile data apn and mms apn with Ting mmsc; auto-select network, manual-select network, etc...). Still nothing. I alao called Ting and told them the problem, and they were able to send me a sspecific configuration to test, (popup notification 'accept settings?... settings applied'), but still the same. I'll keep messing around... I wondered if connmanctl might offer some help, but I'm not too familiar with it. For example, when setting apn info in Android, there are several more fields to add information than there are in SF, (like MCC, MNC, apn type,), so maybe if I could force those values according to Ting support info...?
Levone1 ( 2018-09-01 22:09:44 +0300 )edit