| MMS Sending works fine but download using WAP2.0/HTTP 1.1 Fails wit... |  Search
|
|
NowSMS Support Forums ⬆ Now.WAP Proxy Support ⬆ Archive through October 01, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| RAVI PRABHU Unregistered guest |
Hi, I am using various Magneto/Smartphone SE based MS mobile device to send/recive MMS to "NowWAP" (Version 5.51b). MMS client sends MMS message using WAP1.0, WAP2.0 and HTTP 1.1 protocol. When WAP1.0 used sending and receiving of MMS message works fine. When WAP 2.0 / HTTP 1.1 protocol used for sending, the sending works fine MMS client receives the "SendConfirmation" from the server. When WAP 2.0/ HTTP 1.1 protocol used for downloading the reserver protocol response is HTTP_OK(200) /WSP_OK (32) but the content it returns is not the MMS message. But it is as follows. -------------------------------------------- Œ HTTP/1.1 200 OK Content-Type: application/vnd.wap.mms-message Content-Length: 54 Œ˜jmms--57436 ’€‹20051018/16/2E0A9973@10.244.43.19 L HTTP/1.1 200 OK Content-Type: */* Content-Length: 0 Connection: close ˜ HTTP/1.1 500 Internal Error Content-Type: text/html Date: Tue, 18 Oct 2005 08:15:26 GMT Expires: Tue, 18 Oct 2005 08:15:26 GMT Connection: close --------------------------------------------- If I switch back client to use "WAP 1.0" then everything works fine and same message can be downloaded also. We request your valuable information on this. The MMS Client on the device is tested against all EUROPE countries agains major operator who provides WAP2.0 and HTTP1.1 service. It is only failing on again "Now WAP" gateway. Any further information required, please inform us and thanks in advance. | |||
| 周平 New member Username: Yoyo_2153 Post Number: 1 Registered: 10-2006 |
could i ask a question? where i used the wap1.1 or wap1.2/http1.1. the wsp lever,the wtp lever,or mms encode,or the connect to geteway | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6881 Registered: 10-2002 |
I'm sorry, but I don't understand the question. (The earlier question in this thread, which didn't get a response previously appears to be about the NowSMS MMSC, not NowWAP. There is not enough detail to diagnose the problem ... but my guess is that a "Content-type:" header is included in the HTTP GET request. This confuses the MMSC in versions prior to v5.51c, and causes an HTTP 500 error to be returned.) | |||
| 周平 New member Username: Yoyo_2153 Post Number: 2 Registered: 10-2006 |
could you please tell me the difference between the wap1.0 and wap2.0/http1.1, I mean the use in mms. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6971 Registered: 10-2002 |
Not without understanding the context in which you are asking the question. From the context of an MMS client connecting to an MMSC, the MMS client is generally not going to connect directly to the MMSC. (The reason for this is because there is usually a proxy which provides additional user authentication and/or identification services on an operator network.) Logically, an MMSC expects to receive HTTP format requests from an MMS client. However, these requests are usually coming via a proxy. That proxy might be a WAP2/HTTP proxy, meaning that the client is actually generating HTTP requests ... or it could be a WAP/WSP proxy meaning that the client is actually generating WSP requests, and the proxy provides translation between WSP and HTTP. -bn | |||
