Sending MMS notification----failed!

Sending MMS notification----failed! SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through July 14, 2005 » Sending MMS notification----failed! « Previous || Next »
Author Message
Anonymous
 
Posted on Tuesday, May 24, 2005 - 07:19 am:   

I'm sending MMS notification through:
http://nowMMSServer/?PhoneNumber=XXXXXX&MMSURL=hostName/path/XXXX.mms

1. Can this MMSURL server be any server which supports mms data type? or must it be an operator's MMSC?

2. Should there be any special request on NowMMS gateway setting if this mathod is used?

3. What's the difference between this MMS notification way(URL way) and the NowMMS gateway interface way, which means we click on "Send MMS Notification" and fill up the info for:
a) Phone Number:
b) From:
c) MMS URL: (can this URL's server be any web server supporting MMS?)

Best Rgds.

Bochun

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4589
Registered: 10-2002
Posted on Wednesday, May 25, 2005 - 07:47 pm:   

Hi Bochun,

1.) This can be on any server that supports the MMS data type. However, you should refer to http://www.nowsms.com/howmmsworks.htm for more background on how MMS works.

This function simply sends an MMS notification that tells the recipient phone to download the MMS message from the exact URL specified. As detailed in the link above, some mobile operators block MMS delivery from external MMSCs, which is what this would be considered.

2.) Sorry, I do not understand what you are asking.

3.) There is no real difference. The web form just provides an interactive way of building the URL request. When you click on submit, the web browser builds a URL request of that same format.

-bn
Anonymous
 
Posted on Thursday, May 26, 2005 - 09:29 am:   

Hi,Bryce Norwood,

Thank you so much for your reply.

The 2nd question is: since the WAP push way is actually sending SMS through modem phone(handphone used as a modem connecting to nowSMS gateway), not sending MMS, is there any special setting reuqirement on nowSMS gateway, like have to configure it properly so that it can send MMS out?

I don't confiure it according to MMS sending configuration specified in http://www.nowsms.com/howmmsworks.htm, it can send out MMS notification to other mobile phone including the modem phone itself. But other phones which do not belong to the same Telco cannot fetch the MMS.

Is it because that that telco blocks the MMS on other server while my modem phone's telco allows it?

Looking for your advice!

Best Rgds.

Bochun
Anonymous
 
Posted on Thursday, May 26, 2005 - 09:33 am:   

Hi,

Sorry for the mistake, it should be:
The 2nd question is: since Sending MMS Notification way is just sending out SMS.......

Best Rgds.

Bochun


Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4596
Registered: 10-2002
Posted on Thursday, May 26, 2005 - 04:13 pm:   


quote:

Is it because that that telco blocks the MMS on other server while my modem phone's telco allows it?




Yes. That is likely the issue.

Basically when you send an MMS to a mobile phone, the recipient mobile phone receives an MMS notification message over SMS. This MMS notification message contains a URL pointer to the MMS message content.

In the scenario where NowSMS is configured to act as an MMSC (no "MMSC Routing" definitions defined), NowSMS builds a dynamic URL on its own server. This URL is generated using the "Local Host Name or IP Address" and "HTTP Port Number" values on the "MMSC" page of the configuration dialog.

The recipient mobile phone needs to then be able to make a connection back to that host name or IP address, on that port.

If it is working with phones on one operator, but not phones on another, then it sounds like it is being blocked.

Phones are configured with separate connection settings for MMS (different from the settings employed by the phone's browser). These MMS settings often connect to a restrictive GPRS APN and proxy/gateway which limit access to the operator MMSC.

While these restrictive settings are frustrating because they block access, the original motivation by the operator was probably not blocking. But rather, they don't charge for data traffic on this APN connection (only per message at the MMSC), and they don't want other traffic going through a free data connection.

Before concluding that this operator blocks, you should try to configure your MMSC to use port 80, if possible. Some mobile operators block access to non-standard web ports from their proxies.

Converting MMS to a WAP push, or an SMS with a web link, is generally the most cost effective solution for those scenarios.

-bn

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