Sending peer 2 peer MMS

Sending peer 2 peer MMS SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Archive through July 14, 2004 » Sending peer 2 peer MMS « Previous || Next »
Author Message
Posted on Thursday, February 26, 2004 - 07:21 pm:   

We just set up v5 of the NOW SMS/MMS gateway. We can send MMS from the NOW MMSC to mms capable handsets. That works fine. But we can't send an MMS from one handset to another. The handset reports "MMS Message Sending Failed" and when we look at our TCP/IP traffic logs we see:
WTP+WSP WSP Reply: "0x40 400 Bad Request"
The debug log shows no problems.
Any help will be appreciated.
Posted on Friday, February 27, 2004 - 12:29 pm:   


I got it to work thanks.
Posted on Tuesday, March 09, 2004 - 07:54 am:   

can u explain how u get it to work as I been tying thanks
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2019
Registered: 10-2002
Posted on Tuesday, March 09, 2004 - 06:04 pm:   

The "400 Bad Request" error is usually triggered when you configure the phone to connect to the wrong web service.

There are two web servers that are built into the NowSMS product. On the "Web" page of the NowSMS configuration dialog, you configure the port that is used for the web interface from which you can connect with a browser to send messages. This same port is also used for submitting URL requests to send SMS messages, and the proprietary URL format for submitting MMS messages: g_text_messages.htm rameters_for_sending_messages.htm ontent/Submitting_MMS_Messages_URL.htm

Then there is another web server for the MMSC. This port number gets configured on the "MMSC" page of the NowSMS configuration.

When you configure a phone to use NowSMS as the MMSC, you need to configure the phone to connect to the HTTP port configured for the MMSC.

If you try to connect to the SMS gateway web interface port, you will get a "400 bad request" error.

You also need to include the "/username=password" in the MMSC URL (unless NowSMS is getting the user identification from a RADIUS feed to the WAP gateway). This configuration is described in the following link: ontent/MMSC_Messaging_Server.htm

If you are still not getting anywhere, enabling the debug logs can help us understand what is occurring.

Manually edit SMSGW.INI, and under the [SMSGW] section header, add Debug=Yes. Also edit MMSC.INI and under the [MMSC] section header, add Debug=Yes. Then restart the NowSMS services. NowSMS will create an SMSDEBUG.LOG and MMSCDEBUG.LOG as it runs.

If you provide some more details about what exactly you are trying, and attach those logs as a ZIP file, then we can better answer questions of what you need to do in order to get things working.


Login Login / Register Logout Logout Search Last 30 Days Topics Topics