How to send or receive one MMS via NowSMS from one mobile to the ot...

How to send or receive one MMS via NowSMS from one mobile to the ot... SearchSearch
Author Message
wenjingyuan
New member
Username: Wenjingyuan

Post Number: 3
Registered: 08-2006
Posted on Sunday, September 10, 2006 - 11:29 am:   

Hi Bryce Norwood,

I am setting up MMSC via NowSMS.WAPGateway is NowWAP.But I can not send one MMS to the other mobile.Mobile display "Error". I want to know how to configure MMS setting at the mobile?Below is my configure:
MMSC Address: http://nowsms IP address
Port:9201
IP:nowwap IP
APN:cmnet
that is right?

Thank you very much.

Wen Jing Yuan
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6486
Registered: 10-2002
Posted on Monday, September 11, 2006 - 08:28 pm:   

Hi Wen Jing Yuan,

What you have described would be correct ... as long as the APN that you are using allows you to connect to "nowwap IP".

Most mobile operators have multiple APNs ... some APNs can only be used to connect to the operator WAP gateway, some APNs can only be used to connect to the operator MMSC, and some APNs allow full internet access. You would need to use an APN that allows full internet access.

Next, there is the issue of whether or not there are any firewalls that might block the path to "nowwap IP".

Next is the question of "port". Port 9201 (UDP) is the standard port for WAP/WSP connections. NowWAP automatically listens on this port, and this port number cannot be changed. However, many newer phones use WAP2/HTTP instead. The port number on which NowWAP accepts these connections is configured on the "HTTP" page of the configuration. So perhaps the device you are using supports only WAP2/HTTP?

I would suggest that you enable the WAPDEBUG.LOG in NowWAP. You can do this by editing WAPGW.INI, and adding Debug=Yes under the [WAPGW] header in that file.

If NowWAP receives any connection attempts or data packets, they will be logged to WAPDEBUG.LOG. This way you can see if there is any data making it as far as "nowwap IP".

Another suggestion for troubleshooting is Ethereal (www.ethereal.com) with the WinPCap filter. This tool can be used to determine if any data is making it from the phone to your server.

-bn
周平
New member
Username: Yoyo_2153

Post Number: 3
Registered: 10-2006
Posted on Monday, March 12, 2007 - 03:33 am:   

if my device only support WAP2/HTTP,so what different things should i do? i know if my device support wap/wsp, i need connect to the mmsc, then send wtp and wsp connect info to mmsc,then what should i do if my device just support wap2/http?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6967
Registered: 10-2002
Posted on Monday, March 12, 2007 - 07:23 pm:   

The setup procedure varies by device ... but generally you set the "port" number to the WAP2/HTTP on the proxy (e.g, "nowwap ip" above).

Some devices will also allow you to leave the proxy fields blank, and connect directly. This usually doesn't happen in the real world, as in the real world, proxies add value by integrating in with the network to help identify the MSISDN of connected clients.

In fact, that brings up a related point. My advice above may have been incomplete. If you are configuring NowSMS as an MMSC in a lab environment, then the proxy generally does not know MSISDN information, and cannot forward this information to the MMSC. In these cases, you need to include user account information in the MMS Server URL (MMSC Address) ... http://server:port/username=password ... where "username" and "password" correspond to an account defined in the "MMSC Users" list.

Manual user account provisioning is required in lab environments. Mobile operators can use automatic user account provisioning (described here http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm), but that is not an option for most other environments.

-bn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6968
Registered: 10-2002
Posted on Monday, March 12, 2007 - 07:26 pm:   

P.S. - The above discussion was all about configuring NowSMS for use as an MMSC. The follow-up question is 6 months later, so it might not be related to the original question.

If you are trying to configure NowSMS to send/receive MMS messages via an operator MMSC over a GPRS/EDGE/UMTS modem, then by default NowSMS assumes a WSP proxy. To use a WAP2/HTTP proxy, in the "WAP Gateway IP Address" field, specify "http://ip.address:port" instead of just "ip.address". This tells NowSMS to use a WAP2/HTTP proxy on "port" at "ip.address".