<StatusText>Rejected</StatusText> | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
Author | Message | ||||
Latitude De New member Username: Latitudede Post Number: 32 Registered: 07-2009 |
Please check the attached log. Now SMS/MMS is not delivering MMS to the device.
| ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1216 Registered: 08-2008 |
Same issue as http://support.nowsms.com/discus/messages/485/41694.html | ||||
Latitude De New member Username: Latitudede Post Number: 34 Registered: 07-2009 |
The following issue is for MO http://support.nowsms.com/discus/messages/485/41694.html Where as the current issue is with MT. Please advise. | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1220 Registered: 08-2008 |
The message flow may be different, but the underlying issue is the same. A SubmitReq goes to your MM7 application, but the HTTP response does not include a SubmitRsp. NowSMS wants to see a SubmitRsp or DeliverRsp (depending on which transaction you were sent). 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 will assume that the delivery failed. (I know that I told you at one time that an HTTP 200 OK response was sufficient, but I was wrong.) -- Des NowSMS Support | ||||
Latitude De New member Username: Latitudede Post Number: 35 Registered: 07-2009 |
To understand: I am sending MM7 SubmitReq to MMSC from my applciation. In return, MMSC sends me a SOAP message. Now am I supposed to ACK MMSC with SubmitRsp? | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1225 Registered: 08-2008 |
Then you're sending the message to yourself? When you submit the message, it looks like the routing that is defined is to route the message back to you. I wish all of our discussions were on a single thread ... ... Because I think the following should explain it: http://support.nowsms.com/discus/messages/485/41722.html What I see in the log is that an "MMSC VASP" named "test" is submitting the message to NowSMS via MM7. NowSMS looks at the routing for that "MMSC VASP" account and/or the recipient address, and determines that the message should be routed to the outbound "MMSC Routing" named "test1". This would mean that either the "MMSC VASP" account is set to route via "test1" ... or the recipient phone number is in the recipient address pattern list for the "test1" account. -- Des NowSMS Support | ||||
Latitude De New member Username: Latitudede Post Number: 36 Registered: 07-2009 |
Thanks for looking into this. I agree that my settings are some how to route the message via "test1". Under 'MMSC Routing' tab, I can see 'test1' selected under 'Default Route:' drop down menu. May be this is the reason? I cannot unselect it, I mean some account has to be selected there. Can this be disabled? | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1228 Registered: 08-2008 |
Yeah ... You need to have some sort of outbound path for sending MMS messages. With all of the messages you've posted, I kind of assumed that the basics were all in place. You need to have some sort of outbound path for sending MMS messages. For test environments, you can change the MMS settings on your mobile phone to use NowSMS as the MMSC. And then you can use direct delivery as the outbound path ... but for that, you need to have and outbound SMS path. Do you even have that? I guess I'm just confused. What are you planning to use for your outbound SMS and/or MMS connectivity? (Background info ... "How MMS Works" at http://www.nowsms.com/howmmsworks.htm) -- Des NowSMS Support |