| Phone does HTTP Post to download MMS and fails. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
| Author | Message | ||||
| Joseph Smith New member Username: Falangjoe Post Number: 25 Registered: 08-2006 |
Union Telephone v2010.04.19 I have an Alcatel phone that is trying to download a MMS by doing a HTTP Post. The body of the post is the messageid that was sent in the notification SMS. The mmsc is not sending back the message in the response, because I guess it is expecting a GET. Have you seen this happen before? I am attaching a trace. Thanks,
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3737 Registered: 08-2008 |
Hi Joseph, That is very odd. The phone is sending back a message indicating that it wishes to reject the message. We have seen this before, but in unusual circumstances. For example, some phones have a setting for whether or not to accept "advertisements" or "anonymous" messages via MMS. In the context of this particular issue, "advertisement" is a possible setting for "message class" associated with a message. This field is optional when submitting a message (assumed to be "personal"), but required when delivering a message. Years ago, we did not set it in the notification if it was not set in the submission, which triggered an issue similar to what you are seeing. But that was only an issue in very old product versions. "Anonymous" refers to a sender address not being present, and was a concept specific to a particular phone manufacturer (I don't recall which one). We do have a configuration setting to shorten the notification by not including the sender address (the spec does not require it), so if you are using either ShortMMSNotification=Yes or MMSNotificationNoSender=Yes, remove those settings. (It is unlikely that you are.) I'm not sure why else an MMS client would see the notification and reject it without even trying to download the message. Size maybe? (If "Dynamic image conversion" is enabled, we always lie in the notification and say 30KB, so that the client doesn't skip it because it thinks the message is too big.) Somewhat of a long shot, but an MMS version misunderstanding could also be an issue. Has this phone ever sent an MMS through the MMSC? When it does, we record its MMS version number for future notifications. I can see this MMS client is v1.2. If it has never sent an MMS message via the MMSC, we would default to v1.0. A v1.2 client should have no problem with a v1.0 notification, but in this case, who knows. Can I see the notification message hex content from SMSOUT-yyyymmdd.LOG for SAR-+19703266674-28-2-1 and SAR-+19703266674-28-2-2? I don't expect it to be anything out of the ordinary, but maybe it will provide a clue. -- Des NowSMS Support | ||||
| Joseph Smith New member Username: Falangjoe Post Number: 26 Registered: 08-2006 |
How did you know that it was rejecting it? I attached the entries from SMSOUT. Thanks, Joseph
| ||||
| Joseph Smith New member Username: Falangjoe Post Number: 27 Registered: 08-2006 |
I think that I found the reason. The phone has a setting to reject MMS messages on the home network. Thanks, Joseph | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3738 Registered: 08-2008 |
Hi Joseph, That would explain it! -- Des NowSMS Support | ||||
TraceOfHttpPost
