MM7 Delivery Reports | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
Author | Message | |||
Latitude De New member Username: Latitudede Post Number: 2 Registered: 07-2009 |
Hi, I am sending MMS from my application via Now SMS/MMS and the device receives the message. I want to get the delivery report. What config changes are required at Now SMS/MMS? What should be added/changed in the MM7 message to enable this feature? Cheers | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1004 Registered: 08-2008 |
Hi, I assume that you are posting MM7 from your application. You would need to include this in the submission to set the delivery report request: <DeliveryReport>true</DeliveryReport> Assuming that your outbound MMS route supports delivery reports, here's what you need to do. Currently you have an "MMSC VASP" definition which is the account that your MM7 application uses to submit messages. Define an "MMSC Routing" to connect back to your MM7 application, and give it the same "Account Name" as the "MMSC VASP". If your outbound MMSC route is a modem, it is also necessary to go into the "Receive MMS Settings" under the modem definition in the "SMSC" list. Under "MMSC Routing for Received Messages", select "Route via MM7" and select the "MMSC Routing" that points to your application here. Alternatively, if your application can't receive MM7 connections ... the default setting is to write them to the MMS-IN directory, and your application could scan for the files there. -- Des NowSMS Support | |||
Latitude De New member Username: Latitudede Post Number: 3 Registered: 07-2009 |
> > > > Thanks for your support. I am not able to get delivery reports. Now the > issue is that Now SMS/MMS is sending me the same report again and again o= f > the same message. Am I supposed to give some ACK to Now SMS/MMS? > > > | |||
Latitude De New member Username: Latitudede Post Number: 4 Registered: 07-2009 |
> > > > It is working now. I get DLR for the sent MMS (in MM7). Now the issue is > that Now SMS/MMS is sending me the same report again and again. Am I > supposed to give some ACK to Now SMS/MMS? > > > | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1006 Registered: 08-2008 |
Your HTTP response to the <DeliveryReportReq> should to be an MM7 <DeliveryReportRsp> with the same <TransactionID> value. Truth be told, however, NowSMS is not that picky, it will be happy as long as it gets an "HTTP/1.0 200 OK" or "HTTP/1.1 200 OK" response. -- Des NowSMS Support | |||
Latitude De New member Username: Latitudede Post Number: 9 Registered: 07-2009 |
So if MM7 <DeliveryReportRsp> or "HTTP/1.0 200 OK"/"HTTP/1.1 200 OK" response is not sent, NowSMS will keep sending MM7 <DeliveryReportReq>? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1014 Registered: 08-2008 |
Correct (at least up to some maximum retry counter). NowSMS will assume that there is something wrong with the MM7 service provider because it is not getting the expected response. -- Des NowSMS Support | |||
Latitude De New member Username: Latitudede Post Number: 12 Registered: 07-2009 |
Where can I set maximum retry counter? | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1019 Registered: 08-2008 |
It'd probably be a better idea to fix the application logic to return the HTTP 200 OK response. But if you want to adjust the retry counters, the settings described in the following link are also followed for MMSC connections: http://blog.nowsms.com/2008/10/sms-retry-error-handling-with-ucpemi.html (The article is all about SMS, but the same parameters are used for MMS retry scheduling.) -- Des NowSMS Support |