Emulating WAP - MMSC

Emulating WAP - MMSC SearchSearch
Author Message
WillMooney
Posted on Monday, September 29, 2003 - 07:50 pm:   

Hi All,

I'm trying to emulate the HTTP POST request going to an MMSC. I'm doing this with a tool that will emulate any HTTP request (POST for example). If I want to send an MMS to the nowMMS gateway that I've installed as a trial, what would be the URL that I need to POST to:

For example, I've got an Etherial (Network Snoop) log from another MMSC and it looks like this:

POST /servlets/MMS HTTP 1.1
Host: nnn.nnn.nnn.nnn
Pragma: no-cache
etc
etc
content-Length: 55
<data>

I can emulate the HTTP request but I'm not sure what the executable is that will process the POST - i.e. the bit of url after POST! IS there one here or am I parking up the wrong tree!

Many thanks

W
Keith Norris
Posted on Tuesday, September 30, 2003 - 11:21 am:   

Will,

If I understand your question correctly, you should do the POST to the IP address of the machine running the NowSMS gateway.
Bryce Norwood - NowSMS Support
Posted on Tuesday, September 30, 2003 - 09:13 pm:   

Will,

There is no executable.

The URL format is /username=password, where "username" and "password" refer to a defined account in the "MMSC Users" list.

The following link has some more information:

http://www.nowsms.com/documentation/quickstartguide/Configure_Mobile_Phone_Setti ngs.htm

It is not necessary to specify the "/username=password" (and the URI would just be "/") portion of the URL if the device phone number can be retrieved from the network. In your setup it is not going to, put for others I'll go ahead and point out this link:

http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm
will
Posted on Wednesday, October 01, 2003 - 10:10 am:   

Thanks for your replies, I've cleared it up now! I'm using the username=password and also one of my HTTP headers was not right - content-type : application/vnd.wap.mms-message

I'm getting a m-send-conf message back now.

W
Bryce Norwood - NowSMS Support
Posted on Thursday, October 02, 2003 - 06:09 pm:   

Excellent. I should have also mentioned the content-type header requirement.