| Over Size MMS Error |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Leon Bowers Unregistered guest |
Hi, I'm very new to nowsms but have managed to send myself sms and am halfway to successfully sending myself an mms. My problem is when I recieve an mms on my motorola e365 and try to 'load' it, I get an over size limitation for mms error. This happens with jpgs and midis of only a few kb. I'd be happy to hear any theories as to why this isn't working. Leon. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3459 Registered: 10-2002 |
Hi Leon, What is the exact text of the message? (I'm trying to figure out if the message you are seeing is being generated by NowSMS, the handset, or other.) How are you sending the message ... using NowSMS as a direct delivery MMSC, or through the operator MMSC using a GSM/GPRS modem? (The different delivery modes are described at http://www.nowsms.com/howmmsworks.htm.) If you are attempting direct delivery, it is possible that the mobile operator's MMS settings block access to external MMSCs, and then handset is just displaying the wrong error message. | |||
| Leon Bowers Unregistered guest |
G'day Bryce, Thank you for your quick response. The exact text of the error I receive on the handset is "Over MMS Size Limitation". I am sending the MMS message using the Send MMS Message page of the web interface (with one jpg attachment) through my mobile as a modem connected by usb cable to the computer, then receiving it on the same mobile (sending it to myself). I'm guessing that's a direct delivery? I'll tell you what my goal is: my goal is to be able to receive an sms from someone, process the sms text, retrieve a specific image on my computer and send it by mms back to the person. As you can see, I need this to work no matter what phone they're using or whichever network they're on. First of all, is this a realistic expectation of nowsms? What is going to be the safest way for me to ensure this is going to work and that the person is going to be able to see the image everytime? Is it by generating notification mms's through my operator (Optus in oz) and getting them to download the content from there themselves? Are there different cost considerations I should be thinking of? As I said in my previous post, I am very new to everything concerning sms/mms (ie a couple of days) and realise I have a fair bit of research to do for myself, but any help is greatly appreciated. Leon. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3463 Registered: 10-2002 |
Hi Leon, Ok. That's not our error message. So I'm going to go with the theory that the handset is receiving an MMS notification, but it can't retrieve the MMS message content, and the handset is displaying the wrong error message. Let me try to explain about the two different ways that you can configure NowSMS to deliver MMS messages. "Direct Delivery" is when NowSMS is the MMSC. What happens is that NowSMS takes the MMS content and stores it in a file on the NowSMS server. It then sends a special "MMS Notification" message over SMS to the recipient handset. That message contains an HTTP URL pointing back to the MMS message file on the NowSMS server. The receiving device needs to then be able to fetch that URL from the NowSMS server in order to complete the delivery process. A few things can stop this from working: a.) NowSMS server not accessible over the internet. (The receiving device is going to make a data connection, usually over GPRS, to retrieve the MMS message content from the NowSMS server.) b.) "Local Host Name or IP Address" on the "MMSC" page of the NowSMS configuration does not point to a publicly accessible host name or IP address for the NowSMS server. c.) The MMSC HTTP port is a non-standard port that is blocked by a firewall at the mobile operator. (Some mobile operators are very strict about what ports you can connect to through their gateways.) Port 80 is the standard HTTP port, and is always a safe choice ... but it means you cannot run another web server on the same PC. Most operators who employ this type of blocking will let you use port 8080 as an alternative. d.) The MMS settings that are pre-configured on mobile phones for the mobile operator do not allow connections to external MMSCs, blocking the ability to fetch URLs from external MMSCs. "d" is very common (the link that I referred you to above goes into more detail about it). The notification message makes it to the recipient device, but the URL for the MMS message content is basically not accessible from the phone, so an error occurs. The alternative setup is to configure NowSMS to route the message delivery through the operator MMSC. In this case, NowSMS makes a GPRS connection to the operator MMSC over your modem, and the operator MMSC performs the MMS message delivery. To use this approach, you define settings for connecting to the operator MMSC under the "MMSC Routing" tab of NowSMS. More detail can be found here: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/Connecting_to_operator_MMSC.htm Now ... are there cost considerations? Yes. Sending an SMS message (or two) for an MMS notification message is generally cheaper than what an operator will charge you to send an MMS through their MMSC. When NowSMS performs direct delivery as an MMSC, you are charged for the SMS message delivery. When you route messages through the operator MMSC over GPRS, you are charged for the MMS message delivery, which is usually more expensive. However, with many operator setups, routing the MMS message through the operator MMSC is the only solution. And alternative approach that is workable for some types of content is the Multimedia WAP Push function. With it, you are only paying for the SMS message delivery. It's not as pretty as MMS, but for many types of content delivery, the cost differential makes it preferable. -bn | |||
