| MMS data from the gateway |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | ||||
| David Thijm New member Username: Daverunt Post Number: 3 Registered: 01-2004 |
Hi Can you tell me what the following two bitstreams represent. My phone receives an MMS if the content only has text. If there is an image I get the new message sound but no message in the inbox. Any detail on the above might help. Thanks, Dave 2004-01-23 11:06:56,SAR-+445856-76-2-1.req,MMS user +441324567890 (Jo),+445856,OK -- HTTP - hamlet:80,Binary=1;DCS=F5;UDH=0B05040B8423F00003760201;Data=7606226170706C696361 74696F6E2F766E642E7761702E6D6D732D6D65737361676500AF848C82983443384134463332008D 908919802B3434313332343536373839302F545950453D504C4D4E008A808E0204FD88058103093A 8083687474703A2F2F6E65696C2D7661696F2F32303034303132332F31312F34433841344633 2004-01-23 11:07:27,SAR-+445856-76-2-2.req,MMS user +441324567890 (Jo),+445856,OK -- HTTP - hamlet:80,Binary=1;DCS=F5;UDH=0B05040B8423F00003760202;Data=322E4D4D533F69643D35 38353600 | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1714 Registered: 10-2002 |
David, There is no difference in the MMS notification format whether or not the MMS contains just text or also includes an image. So I'm not going to decode that data here ... suffice it to say that it is an MMS notification. The most common situation that causes the type of problem that you describe (text only MMS is fine, but images fail), is if the MMSC does not have a direct internet connection (i.e., it needs to connect external via a proxy server). The reason for this problem is related to the content conversion capabilities in the MMSC. The content conversion engine tries to fetch the user-agent profile for the device over the internet, and by the time this request times out, the phone has given up attempting to retrieve the message. The solution is to disable content conversion. Go to the "MMSC" page of the configuration dialog, end uncheck "Enable Dynamic Image + Audio Conversion". (If you want to enable that setting, it does require that the PC be able to connect to the internet without going through a proxy server.) If that is not the problem, another problem can be the WAP configuration setting in the mobile phone. Some phones allow you to configure the connection type or port for connecting to the WAP gateway. The terminology varies from phone to phone, but you should use the "Connection-oriented" protocol, also known as "permanent" on Nokia phones, and port 9201 on many other phones. Avoid using the "connection-less", "temporary" or port 9200 type of connection, as this will usually only work for very small MMS messages (hence the text only support working). It could also be a problem with the WAP gateway itself. This is unlikely, but not knowing your configuration, it is also worth mentioning that many older WAP gateways had support for very limited size transactions. If the answer is not in one of the above suggestions, then please enable the debug mode in the MMSC. This is done by manually editing MMSC.INI, and under the [MMSC] section header, add Debug=Yes. Then restart the MMSC service. Repeat your attempts, and e-mail the MMSCDEBUG.LOG to nowsms@now.co.uk, or post it as an attachment in a reply here. -bn | ||||
| David Thijm New member Username: Daverunt Post Number: 4 Registered: 01-2004 |
Hi Bryce tried those suggestions. Still the same though. However looking at the attached debug log it appears the phone received the message? It doesn't show up in the inbox though. The test setup I am using has the phone sending the message to itself. I have tried sending from another phone with the same result. A text only MMS is ok but a message with image fails. I am using a Kannel WAP gateway. Cheers, Dave
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1724 Registered: 10-2002 |
Hi Dave, We also exchanged some e-mail about this. I can see in the MMSCDEBUG.LOG that the phone made an attempt to retrieve the MMS message. However, the "m-notifyresp-ind" packet that comes from the phone after the retrieval attempt indicates that the MMS message retrieval has been "deferred". This likely means that an error occurred downloading the message. I also see that from your e-mail message follow-up that you downloaded Now.WAP, and it worked properly with that gateway. You also mentioned that you were using Kannel v1.2. My understanding is that Kannel v1.2 does not support segmentation and re-assembly (SAR), which most MMS clients require. So I suspect that you are having a problem when messages exceed a certain size. -bn | ||||
MMSdebug zip
