| HELP! Problem on getting MM message |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| ylcp97 |
I have developed a tiny wap client stack on a Dragonball-based PDA with a GSM-modem. Now I could post MM messages to GSM users,but when I was to retrieve MM with my WAP stack,(the MM URI was taken from sms-based MM-NOTIFICATION_IND packet) I failed--time out,no message from WAPGATEWAY/MMSC.When I using a wrong MM URI in WSP_GET,the return message from MMSC is "404,requested object not found". I have set up "Profile" in the WSP_CONNECT(the uaprof RDF file's URI is OK), and I have added headers("Accept = application/vnd.wap.mms-message" and "User-Agent= WBMMsClient/1.0") to the wsp_get packet. Where do I did wrong? Any advices would be appeciated. | |||
| Bryce Norwood - NowSMS Support |
When you post an MMS message, you're performing a WSP POST through the same WAP gateway that you're later trying to retrieve the MMS message from, correct? I can't imagine what would cause that problem. Take a closer look at the URL in the notification to see if maybe you could be decoding something incorrectly. Try variations on that URL to see what changes you have to make in order to get an error response back. (Maybe there is a parameter with strange encoding that is causing confusion.) Also look closely at the GET PDU that you generate. I really can't imagine what this could be. | |||
| ylcp97 |
Mr. Bryce Norwood: Thank you for the answer. At now the mobile carrier's wapgateway has been changed. When I connected to this new wapgateway using WSP_CONNECT with client SDU>8K(2000h in hex), I got a WSP_ConnectReply with a client SDU=8K. So when I went to retrieve an MM message larger than 8K in size, I got an TR_ABORT with wtp_user error code: "e6", i.e. MRUEXCEEDED.When I went to retrieve a "small" MM message, I succeeded. I have tested the client SDU size in WSP_CONNECT from 0 to 65535, but the WSP_CONNECTREPLY was the same at client SDU size each time. How can I circumvent this barrier? Thanks a lot in advance. | |||
| Ooze |
i wanna know how too | |||
| Bryce Norwood - NowSMS Support |
If it's a limitation of their gateway, I don't know of any way around it other than using a different gateway. (You might need to use a different GPRS APN with open internet connectivity to connect to an external WAP gateway, such as the one at 213.48.20.10.) Certainly the responses generated by the operator's gateway are suggesting that there is a fixed 8KB limit on that gateway. If you want to work with that operator's system ... I'd suggest getting a contract for an MMS compatible phone from the operator. And then try using that phone to send/receive larger messages. Maybe the operator has another gateway that they use for their actual MMS deployment? I would think that 8KB is too small for any real world MMS deployment. -bn | |||
| ylcp97 |
Mr.Bryce, I have tested your wapgateway at 213.48.20.10 and our mobile operator's W/G. When I wanted to get a big page,e.g.,"http://winwap.org/press_agil.wml",the "Get" process failed at IP transportation. I tested WSP_GET with WINWAP PRO 3.1( and I monitored the packets with ethereal), the result was the same. W/Gs did not start WTP-SAR, and SAR processing was taken at IP layer. I think the mobile's MMS client should has the ability to retrieve MM messages about 30k big in size. I have tested a Panasonic GD88 with the same configuration(APN,W/G,MMSC,et al.),it can send and retrieve MM messages 30k big in size.That is said, there is a way to retrieve "big" MM messages from wap/mms client via this "8K" W/G. I have tried "Range" and "Accept-Ranges" headers(like http/1.1) in the WSP_Get packet header, but I did not get any right result. Thanks a lot, ylcp97 | |||
