| URL to collect MMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Will |
Hi All, I'm trying to collect an MMS message on the NOW SMS/MMS solution by emulating a wap gateway. I've sucessfully sent an MMS message and got the m-send-conf message back. Now I want to collect the message (i've got it's message-id). What is the URL to do this on the NOW MMSC??! On an Ericsson MMSC the HTTP header request looks like this: GET /servlets/mms?message-id=123 HTTP 1.1 I just need to know the URL format. Many thanks W | |||
| Bryce Norwood - NowSMS Support |
Will, If you look at the m-send-conf, I think you'd be able to construct a URL based upon the message-id that is returned. Strip the ID at the "@", and the part before the "@" is the URI to request (just add a "/" to the beginning). | |||
| Bryce Norwood - NowSMS Support |
One note. This id would only be valid if the recipient was a phone number. If the recipient is an e-mail address, the message is dispatched via e-mail and no longer resides on the MMSC. | |||
| will |
Hi again, I tried using the suggestion of Strip the ID at the "@", and the part before the "@" is the URI to request (just add a "/" to the beginning) to gain the URL. Sofor message id 20031009/20/BDFCBE13@<hostname> and the URL would be http://localhost/?Message-ID=/220031009/20/BDFCBE13. Is my thinking right as this is still not working? | |||
| Bryce Norwood - NowSMS Support |
Forget about "?Message-ID=" ... that is specific to the Ericsson MMSC. http://localhost/220031009/20/BDFCBE13.mms would do it. (I didn't mention the ".mms" in my previous message, but I should have.) | |||
| will |
Hi All, That's excellent. Thanks for that I should've guessed the .mms myself. In attempts to retrieve I still get some problems though namely a HTTP/1.0 500 Internal Error stating the message "Unknown request: content type is unknown". Below is the GET I am sending. Any clues? GET /20031010/00/1CA5D7D6.mms HTTP/1.1\r\n Content-Type: /vnd.wap.mms-message\r\n Referer: http://127.0.0.1/\r\n x-wsb-msisdn: 447970482309\r\n Accept: */*;q=0.001\r\n Accept-Language: en\r\n Accept-Charset: UTF-8,*;q=0.001\r\n Accept-Encoding: *;q=0.001\r\n accept-application: 1\r\n accept-application: 2\r\n User-Agent: Nokia-WAP-Toolkit/2.0\r\n Connection: Keep-Alive\r\n Host: 127.0.0.1\r\n This is the MMS I sent successfully: POST / HTTP/1.1\r\n Content-Type: application/vnd.wap.mms-message\r\n Accept: application/vnd.wap.mms-message,*//*;q=0.001\r\n x-wsb-msisdn: 44790482309\r\n Accept-Encoding: *;q=0.001\r\n accept-application: 1\r\n accept-application: 2\r\n User-Agent: Nokia-WAP-Toolkit/2.0\r\n Connection: Keep-Alive\r\n Host: 127.0.0.1\r\n Content-Length: 85\r\n which it seemed to be happy with HTTP/1.0 200 OK\r\n Content-type: application/vnd.wap.mms-message\r\n Content-length: 46\r\n | |||
| Bryce Norwood - NowSMS Support |
I think it the MMSC is confused because you have a "Content-type:" specified in your "GET" request, but there isn't any actual content. Why it cares on a "GET" request, I do not know, but I think if you get rid of that header, you will get further. | |||
