| Can not send/receive MMS in Europe, but works in China |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through March 23, 2004 ⬆ |
◄ ► |
| Author | Message | ||||
| Frank Xiong New member Username: Chunyunx Post Number: 2 Registered: 01-2004 |
Hi all, I am toasted, I am toasted!!! recently, I developed MMS in cellphone,(the core client module is from Magic4.com), and it works perfectly in my local region(China), but in Europe, it can not send MMS, nor receive MMS. I asked the core client supplier help me log some MMSC side log file by using our cellphone and Panasonic G86(by the way, G86 can send out/receive), when I compared these two log file, I found that the only difference is that in my cellphone's log file, there is no http header info(Accept, content type, etc.). any body can give me any clue about it? one thing confuse me is that how come my cellphone can work perfectly in China as G86 does?? any general tricky thing should I pay attention to?? Many thanks for replying in advance!!
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1536 Registered: 10-2002 |
Hi Frank, At a minimum, you should be including a "Content-type: application/vnd.wap.mms-message" header. Without that, the MMSC doesn't know what you are posting. Perhaps the MMSC used by the Chinese operator just assumes that the content type is MMS. I would also strongly recommend including the "Accept: application/vnd.wap.mms-message" header (or */* as the Panasonic phone uses), otherwise many WAP gateways will block the response coming back from the MMSC and give you a 406 error (or a text variation of this error). Some systems are pickier than others. | ||||
| Frank Xiong New member Username: Chunyunx Post Number: 5 Registered: 01-2004 |
Thanks for replying first. yes, in WSP header, I used */* as to accept any kind of information, and it works perfect in China, but failed in Europe, I am just wondering, in Europe(Vodafone,Orange, O2 etc.), should I explicitly add ""application/vnd.wap.mms-message" in accept header? look forward to hearing reply! Thanks and BRs | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1565 Registered: 10-2002 |
Frank, In the example that you posted as an attachment, there was no "Accept:" or "Content-type:" header included. Of course, you're probably talking WSP, not HTTP. Judging from the goofy way that the "Accept:" header is presented in that log for the Panasonic device, I am guessing that your friends at Magic4 tested the Panasonic client going through a Kannel WAP Gateway (or some other commercial gateway that is a derivative of Kannel). I say this because while in WSP, you specify a separate "Accept:" header for each supported content type, the WAP gateway should convert this over to HTTP with a comma delimited list of content types in a single "Accept:" header. So if you are specifying "Accept: */*" in the WSP header, it is not coming through the WAP gateway to the HTTP world. The "Content-type: application/vnd.wap.mms-message" is also not coming through to the HTTP world, and that is the part that is more concerning. This is particularly odd, because in a WSP POST, the Content-type is a required field ... you can't generate a WSP POST without one. So I'm not sure how the WAP gateway would not include a content-type header. It would be more interesting to see a trace of your packets at the WSP level. We can see that the request that is going to the MMSC does not include the "Content-type:" or "Accept:" headers. But your client is likely talking WSP, and it is a WAP gateway that is translating the request to HTTP. So what do your WSP requests look like? | ||||
| Frank Xiong New member Username: Chunyunx Post Number: 6 Registered: 01-2004 |
Hi there, in my side, for source limitation reason, I can not log WSP packet, what I have is that some API, and I need to fill out in WSP Accept header and content type, I filled with */* and application/vnd.wap.mms-message, the module behind will wrap up data and these fields and send out as standard WSP packet, I don't quite understand what your suggestion, should I change accept header or content type? if yes, to what? Thanks a lot. Frank | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1646 Registered: 10-2002 |
Frank, In your example, the MMSC did not see any "Content-type:" header at all. That's why I think we really need to see the WSP request, because I do not know how that could happen (since Content-type is a required field in a WSP POST PDU). The MMSC also did not see an "Accept:" header. To log WSP packets, I have two suggestions. 1.) Get Ethereal (www.ethereal.com). It is a protocol analyser, and it can be an invaluable debugging tool. 2.) Download the trial of Now.WAP Proxy(www.nowwap.com). Enable the debug log in the proxy (edit WAPGW.INI, and under [WAPGW] section header, add Debug=Yes), and it will log all WSP requests to WAPDEBUG.LOG, so that we can then take a closer look at them. It is possible that your client might work ok when going through Now.WAP, but it would still be good to see the debug log that shows the WSP PDUs that you are generating. (From the log that you posted earlier, it appears that Kannel or a Kannel derivative was being used as the WAP gateway.) -bn | ||||
| charlesk Unregistered guest |
Hi | ||||
| Frank Xiong New member Username: Chunyunx Post Number: 12 Registered: 01-2004 |
Hi all, Tell you all a good news that the MMS works perfectly in Europe by our handset, and not only for Vodafone, but also for all those major operators such O2, T-Mobile, Orange. believe or not, there are some tricky stuff within our test and motification, if you want to kow, we can discuss about it. Thanks Bryce for kindly help during long time testing. Regards | ||||
MMSC log with and without header info
