Sending MMS to Mogreet shortcode fails every time

34 views
Skip to first unread message

mpoyt...@gmail.com

unread,
May 15, 2014, 1:30:52 AM5/15/14
to mogre...@googlegroups.com
Hi there - I'm trying to test Mogreet to process inbound MMS.  Sending a plain text (SMS) works fine, but any time I try to send a photo message (MMS) the message fails to send (no joke - the phone actually says "the message to 343-434 failed to send".  You can't make this stuff up.)

I'm using an iPhone 5, and see that another user testing with an iPhone 5S had a similar problem a few months ago.  I would try the same fix / workaround that was given to him, but....well, there isn't one.  No reply to that post whatsoever.  So, I'm optimistic that someone will see and reply to THIS message.


mpoyt...@gmail.com

unread,
May 15, 2014, 1:33:46 AM5/15/14
to mogre...@googlegroups.com, mpoyt...@gmail.com

Here's a screenshot showing SMS working and MMS failing





Anthony Rossano

unread,
May 15, 2014, 12:46:11 PM5/15/14
to mpoyt...@gmail.com, mogre...@googlegroups.com
Hi There - 
So, that message on the phone indicates that the MMS couldn't be sent from the phone itself. If you CAN send MMS with images to longcodes, then its possible that your service has MMS to shortcodes disabled.  

Sometimes this can happen because the Service is set up incorrectly or shortcode sending is blocked by the carrier - you can call your carrier customer service and ask about that. 

You should also check your MMS settings in the iphone (Settings/Messages) to make sure that MMS is enabled. 

Hope that helps!
ATR


Anthony Rossano, Technologist



On May 14, 2014, at 10:33 PM, mpoyt...@gmail.com wrote:

Here's a screenshot showing SMS working and MMS failing






--
You received this message because you are subscribed to the Google Groups "Mogreet API" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mogreetapi+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

mpoyt...@gmail.com

unread,
May 15, 2014, 6:58:01 PM5/15/14
to mogre...@googlegroups.com, mpoyt...@gmail.com, anthony...@outspoken.com
Anthony -
Thank you for the reply!

My carrier is AT&T, and my service is just one of their normal plain-vanilla accounts, with unlimited voice and text.  Nothing special.

I did go into the Settings -> Messages on my phone and found a setting turned off ("Send as SMS when iMessage is unavailable").  So I turned that On and tried again, and it seems to be working now.

I'm evaluating this for a consumer-facing application, so my question now is this:  Is what I had to do normal, and what most AT&T iPhone subscribers would have to do?  (I don't know if I turned that setting off at some point or not, but it's entirely possible that I changed it from the default of "On")

A related, and perhaps more relevant question:  Do you have a lot of iPhone traffic using Mogreet's system without issues?  Do you have any metrics on problem reports vs. your traffic?

I'm trying to figure out if this API is ready for prime-time on a public application that requires users to text photos in, or if trying to develop a product with it will leave us wishing we had never been born.

Thanks!

mpoyt...@gmail.com

unread,
May 15, 2014, 7:04:18 PM5/15/14
to mogre...@googlegroups.com, mpoyt...@gmail.com, anthony...@outspoken.com
Revision to my last email:
I looked at the settings on another iPhone that I know has default settings, and the "Send as SMS" setting was also off.
So I turned mine off again, and tried to send another photo MMS.  This time it worked!

That causes some concern, but for now I will chalk it up to some kind of temporary network glitch.

My other questions still stand, though, regarding how common or representative my issue is.

Anthony Rossano

unread,
May 19, 2014, 2:47:30 PM5/19/14
to mpoyt...@gmail.com, mogre...@googlegroups.com
Hi there - 
Your experience was very unusual.  I've heard of setting confusion messing up MMS maybe two or three times in the last year.  Very rare. 
The screenshot pointed in that direction though - the device just was unable to deliver the message to the upstream MMSC. 
ATR


Anthony Rossano, Technologist



Reply all
Reply to author
Forward
0 new messages