Submitting MMS from Command line | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
Author | Message | |||
JvZ |
Hi, I'm trying to submit a MMS direct from the command line (actually HTTP socket) and cannot get the syntax right. I've created the MMS file with MMSCOMP and can send it out using the WEB interface. I can also send out a SMS by telnetting to port 8800 and issueing the following string: GET /?PhoneNumber=0824413903&Text=Message I've tried the following string for MMS: GET /?PhoneNumber=0824413903&MMSText=MMS+Message&MMSFile=&MMSSubject=subject&MMSFrom = and it works file. When I try to add the MMS file as follows: GET /?PhoneNumber=0824413903&MMSText=MMS+Message&MMSFile=gate.MMS&MMSSubject=subject &MMSFrom= I get the following error: HTTP/1.0 500 Internal Error Content-type: text/html Expires: Tue, 01 Jan 1980 1:00:00 GMT Cache-Control: no-cache <html><head><title> Internal Error processing request</title></head> <body> Error: Internal Error </body></html> It seems to be the syntax of the MMSFile option??? Thanks | |||
JvZ |
Realise now I have to do a complex POST. Decided to use smtp command-line client to submit MMS. Works a treat! | |||
Bryce Norwood - NowSMS Support |
Hi Jannie, Sorry for the delay getting back to you. Another option when using the HTTP interface is to specify a complete URL path for the MMSFILE parameter, e.g., MMSFILE=http%2F%3A%3Aweb.server.com/file.ext (I escaped the :// as %2F%3A%3A here which you may or may not have to do depending on the tools you are using to generate the request). -bn | |||
JvZ |
Hi, Must the MMSFile parameter be a URL? CAn it not be a directory? What if I put the file on the nowsms server and give a pathname to it? Jannie | |||
Bryce Norwood - NowSMS Support |
Jannie, No, it has to be in a URL. There *might* be a backdoor, where if you placed a file in the TEMP directory beneath the NowSMS program directory, then NowSMS might find it if you reference such a file in the MMSFILE parameter. (Note that I would expect it to delete the file after it processes it.) This behaviour might vary between releases, so I'd be hesitant to rely on it. -bn |