Device prompts: Message Failed

Device prompts: Message Failed SearchSearch
Author Message
Latitude De
New member
Username: Latitudede

Post Number: 26
Registered: 07-2009
Posted on Friday, August 28, 2009 - 11:29 am:   

Hi,

I am sending MO MMS from SE K800i which is received by Now SMS/MMS and routed to the appropriate Servlet. All fine uptill now. But the device prompts: Message Failed. Its a system message. I believe that the device expects some ACK from the MMSC. Is that right? How to do this?

Regards.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1178
Registered: 08-2008
Posted on Friday, August 28, 2009 - 01:33 pm:   

Hi,

I'd have to see an MMSCDEBUG.LOG that shows the transaction in order to understand.

The only ACK is the HTTP response back to the client when the message is submitted.

If the message is getting accepted, then I can't see why the ACK would be negative.

But I can't really make any guesses without an MMSCDEBUG.LOG.

--
Des
NowSMS Support
Latitude De
New member
Username: Latitudede

Post Number: 27
Registered: 07-2009
Posted on Friday, August 28, 2009 - 04:47 pm:   

application/octet-streamLog attached.
MO-MMS-K800.log (14.8 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1185
Registered: 08-2008
Posted on Friday, August 28, 2009 - 05:16 pm:   

Thanks. That clarifies things.

It's a non-delivery report that is being sent back.

I think I gave you some bad (or incomplete) info awhile back.

Earlier, I think I told you that you needed to return an "HTTP/1.x 200 OK" response in order to stop NowSMS from resending the message.

That is true.

But, if it's not a minimally valid MM7 response, NowSMS will simply assume that the message delivery failed. And this is what is triggering a non-delivery notification to be sent back to the sender.

NowSMS wants to see a SubmitRsp or DeliverRsp.

For a SubmitRsp, it will assume the message submission was successful if a <MessageID> element is returned, or a <StatusCode> value of 1000 is returned.

For a DeliverRsp, it expects to see a <StatusCode> value of 1000 to indicate success.

If you just return the HTTP 200 OK response, NowSMS won't retry, but it will assume that the delivery failed.

--
Des
NowSMS Support
Latitude De
New member
Username: Latitudede

Post Number: 29
Registered: 07-2009
Posted on Thursday, September 03, 2009 - 01:04 pm:   

Hi,

Quoting you: Earlier, I think I told you that you needed to return an "HTTP/1.x 200 OK" response in order to stop NowSMS from resending the message.

Are you refering to your post number: 1006 ?

Just want to clerify.

Thanks.
Latitude De
New member
Username: Latitudede

Post Number: 30
Registered: 07-2009
Posted on Thursday, September 03, 2009 - 02:27 pm:   

When I send MO from Nokia phones, I do not get Message Failed response. It only happens with SE K800. In both cases, I send "HTTP/1.1 200 OK" to MMSC. Is this expected?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 1197
Registered: 08-2008
Posted on Friday, September 04, 2009 - 10:46 am:   

The message failed response is a separate delivery report notification. When you return an HTTP OK response, but don't include the SubmitRsp or DeliverRsp XML, NowSMS considers the delivery to be a failure. In most instances
this results in a separate non-delivery notification transaction.

--
Des
NowSMS Support
Latitude De
New member
Username: Latitudede

Post Number: 33
Registered: 07-2009
Posted on Wednesday, September 09, 2009 - 02:54 pm:   

Thanks. Working fine now.