Sending MMS Using Private MMSC

Sending MMS Using Private MMSC SearchSearch
Author Message
Rich Flores
New member
Username: G3rich

Post Number: 4
Registered: 07-2010
Posted on Monday, July 26, 2010 - 07:59 pm:   

Hello,
I am currently running into another issue sending MMS messages to another phone. My current setup is pretty much the same, I am running NOW SMS and have configured MMSC Tab with proper IP Address, MMSC Routing to Direct Delivery(internal MMSC). I am using a private network that allows for GPRS Data connections.
When I Use NowSMS and a mobile device as a modem, the MMS Message shows that it is being sent. The message is sent in 2 parts, and my network displays that the message was successfully delivered.
Next, my test network also shows that the recipient phone is receiving the message and begins to attach so that it can download the MMS. The Recipient phone receives an alert that it has received the message and it displays that it includes an MMS so it prompts me if i'd like to receive the message. Once i've started to download the message within a couple of minutes it fails.

Is there certain MMSC user or configuration settings that I need in order to get my network to use NOW SMS internal MMSC?
Thanks in advance for all your help.

I've also attached a log file MMSCDEBUG.LOG for my last test which may help solve this issue.
Thank You
application/octet-stream
MMSCDEBUG.LOG (120.3 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2366
Registered: 08-2008
Posted on Tuesday, July 27, 2010 - 01:19 am:   

Hi Rich,

Please read How MMS Works at http://www.nowsms.com/howmmsworks.htm.

The quick answer is that many mobile operators block the use of private/external MMSCs. The link that I referenced above explains more of the how and why. It also offers explanations of alternatives:

1.) Configure NowSMS to send MMS messages via the operator MMSC.

2.) Use an alternate delivery method that is not "real MMS" (e.g., convert to WAP push or SMS link with web page).

3.) For a closed environment, change the configuration settings on the mobile phones to allow access to the NowSMS MMSC.

If you want to do #3, you need to make sure that the "Local Host Name or IP Address" setting for the MMSC is an externally accessible host name or IP address that can be used for a direct connection to the NowSMS MMSC. (This can be a tough one to verify ... you can try connecting from a mobile phone to http://ipaddr:port/testurl and see if you get a resulting MMSRETRIEVE FAILED entry in the MMSC-yyyymmdd.LOG referencing "testurl". However, the browser/WAP APN settings in your phone may be different from the MMS APN, so you may want to try reconfiguring a phone to use the NowSMS MMSC as its MMS Server URL and try sending an MMS message from the phone to verify that the MMS client can retrieve the message.)

Hopefully this helps explain things.

If I can add more clarification, tell me more about your configuration settings.

--
Des
NowSMS Support
Rich Flores
New member
Username: G3rich

Post Number: 5
Registered: 07-2010
Posted on Wednesday, July 28, 2010 - 09:53 pm:   

Hello,
Currently we are trying to do # 3. We are attempting to set the NowSMS as the MMSC. We are using Nokia E71 and Samsung SGH-L760 phones.
Our current status is the following:
Using the Samsung, we have been able to connect it to our PC running NowSMS and set it as a modem. We've configured the Modem, MMSC, MMSC Users, etc and we are successfully able to send SMS, Multimedia SMS&WAP, and MMS messages to our recipient phones using our Private Network.
Everything there works great!

However, now we are trying to send an MMS from one Nokia to another Nokia or a Samsung to Samsung and it does not go through. Our network shows that the sending phone is making a data connection but it seems as if it doesn't know where to go from there. We have our phones configured where they are able to talk with the NowSMS Machine. We've validated that we do get the MMSRETRIEVE FAILED error in the LOG when going to that URL.

Is there anything that we are missing here?
Has this been done before where One phone sends to another phone both on a private network and using NowSMS as the MMSC?
What other suggestions do you have?

I appreciate all your help and thanks in advance.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 2381
Registered: 08-2008
Posted on Thursday, July 29, 2010 - 06:11 pm:   

Hi Rich,

It sounds like the Nokia phone is simply not connecting to the correct APN or MMS Server URL.

Manually configuring settings on Nokia phones tends to be confusing. Here's a link that goes through all of the steps: http://www.blog.roniphone.com/nokia-e71-mms-settings.html ... you just need to substitute in your values.

Specifically, you need to change the "Access Point Name" (APN) as appropriate.

The "Homepage" setting is the MMS Server URL. (e.g., http://ip:port/number=password)

The proxy server IP address and port also needs to be configured as appropriate. (Although I believe Nokia will allow it to be configured blank to mean not to use a proxy.)

Rather than creating a new access point like described in the link, I would start with step 23 and check to see what the current MMS access point settings are. View them and make sure that they are correct.

If the phone can't send or receive, it sounds like its requests are not making it as far as the MMSC ... probably because of something incorrect in these settings.

--
Des
NowSMS Support
Rich Flores
New member
Username: G3rich

Post Number: 6
Registered: 07-2010
Posted on Thursday, July 29, 2010 - 06:14 pm:   

Hi,
thank you very very much for all your help. We actually got it working early this morning and the entire issue was that we needed to set the "homepage" as you described in your last post. everything is working perfect now and we are able to send MMS's between various phones using NowSMS as the MMSC.
I appreciate all your help and your time.
John O'Brien
Posted on Sunday, March 27, 2011 - 05:58 am:   

Hello,

I’m building a home grown MMSC so I can do some neat things sending MMS to my friends.

I have the basic system working pretty well. Sending M-notification.ind’s to handsets and having the content retrieved by sending M-retrieve.conf with the included media.

Have an issue sending error messages to the handset MMS client.

The use case is that some handsets don’t seem to expire messages even when the notification.ind has a valid X-Mms-Expiry value. So the handset continues to periodically issue a WSP/HTTP Get.req well after the content has expired and no longer available.

I have immersed myself in the standards but can’t seem to understand what needs to be done.
It seems I need to respond with an M-retrieve.conf that indicated that the content has expired.
The format for M-retrieve.conf is different between release 1.0 and 1.1 of the standards.

It looks like release 1.0 assumes the MMSC constructs a M-retrieve-conf message containing a plain text error message in the PDU body. If that is the case how do I encode this?
I’m only guessing how the Content-Type should be encoded.
Blow is what I have been trying

; MMS Version 1.0
0x84 ; M-retrieve-conf
0x8D ; X-MMS-Version
0x90 ; MMS 1.0
0x85 ; Date
0x04 0x4D 0x8E 0xB8 0xCC
0x84 ; Content-Type
0x83 ; "text/plain"
0x32 ; length of error string
“The content has expired and is no longer available”

Some handsets get so confused they crash and reboot themselves.
Would really appreciate some so suggestions with this.

; MMS Version 1.1
0x84 ; M-retrieve-conf
0x8D ; X-MMS-Version
0x90 ; MMS 1.0
0x85 ; Date
0x04 0x4D 0x8E 0xB8 0xCC
0x99 ; X-Mms-Retrieve-Status
0xE0 ; Permanent Error
0x9A ; X-Mms-Retrieve-Text
"Error Retrieving from MMSC"
0x00
0x84 ; Content-Type
0x83 ; "text/plain"
0x32 ; length of error string
“The content has expired and is no longer available”

John
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3057
Registered: 08-2008
Posted on Monday, March 28, 2011 - 08:57 pm:   

Hi John,

I think you might be over complicating it ... I'd suggest returning a standard HTTP 404 Not Found response.

Granted, there is an X-Mms-Retrieve-Status field in post MMS 1.0 releases, but if you use this you need to have a message body. And a client is going to expect this message body to be a standard MMS message (maybe with just one text part that says "Message Expired", but it needs to be in the standard MMS message wrapper).

--
Des
NowSMS Support
Ranjani K R
New member
Username: Ranjani14krgmailcom

Post Number: 2
Registered: 03-2011
Posted on Monday, April 11, 2011 - 07:49 am:   

Hi,

I'm sending MMS to different numbers using send mms message option. But I'm not able to download. I tried sending both pre-compiled MMS file and one with with out that. Unable to download both. Can you please help me with this problem

Thank you,
Ranjani
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 3092
Registered: 08-2008
Posted on Monday, April 11, 2011 - 09:05 pm:   

Hi Ranjani,

Many mobile operators block MMS message delivery from a private MMSC, and require that you send MMS messages via their MMSC.

For more information about this, please see the "How MMS Works" article at http://www.nowsms.com/faq/how-mms-works

To configure NowSMS to send MMS messages via an operator MMSC using a GSM modem, please see:

http://www.nowsms.com/doc/mmsc-messaging-server/connecting-to-an-operator-mmsc/u sing-a-gprs-modem

Alternatively, you might want to look at the following quick start guide that walks through this configuration process: http://www.nowsms.com/documentation/quickstartguide/NowSMSQuickStart3.pdf

--
Des
NowSMS Support