| Delivery Report |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 29, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I have written an application that sends MM7 MMS messages. My application requires that delivery reports are received for some messages. How do I configure NowSms to forward delivery reports to a specific IP / port? | |||
| Bryce Norwood - NowSMS Support |
Actually, I'm glad you asked that question. Without the documentation being finished, this is difficult to figure out. We had a lot of design debates on how to handle this. Logically, it would make sense, if when configuring the VASP account, you also configured how to route messages (such as delivery reports) back out to the VASP. But with all of the different protocols, and some of the different routing combinations that are possible. For example, you could talk to us via MM7, and have the gateway use a GPRS modem to talk MM1 ... and you also have to consider how to get delivery reports that come back in the MM1 connection over GPRS back to the MM7 connection. Or NowSMS might be using MM7 to talk to another MMSC. It all gets very confusing. Most of the design choices that we considered seem to rule out different potential combinations that we could think of. So what we decided to do, was to separate inbound message routing from outbound message routing. (By inbound, I am referring to a VASP submitting messages in to the gateway. By outbound, I am referring to the gateway routing messages outbound for delivery.) On the "MMSC VASP" configuration dialog, you define the accounts that can submit messages inbound to NowSMS. On the "MMSC Routing" configuration dialog, you define the routing of messages out from NowSMS for delivery. If you're submitting in a message using MM7, then you've defined an account on the "MMSC VASP" page. That account definition only allows you to submit messages in. You can't receive any replies or delivery reports. If a delivery report is requested, the system will generate a delivery report back to the SenderAddress specified in the MM7 message submission. However, you need to have a path defined to route that address back to your MM7 application. (Or you could make the SenderAddress an e-mail address, in which case the delivery reports would be routed back to you via e-mail.) So if you define an entry on the "MMSC Routing" dialog that points to your MM7 receiver, and give it the SenderAddress that needs to be routed back to your application, then you'll receive the delivery reports. A neat trick that I tried during testing was using MM7 to connect to a NowSMS gateway that was sending all outbound MMS messages via an MM1 connection over GPRS to an operator MMSC. Getting delivery reports proved a little trickier in that environment. When you are receiving messages over a GSM/GPRS modem, there are options for how the received messages should be routed. One of those options is to route the messages via MM7, where you specify a named "MMSC Routing" definition. It was actually a pretty interesting test. I submitted the message via MM7 to the gateway. The gateway initiated the GPRS connection, sent the message over MM1. The MMS delivery notification message came in via SMS, and NowSMS decoded it as an MMS delivery notification, and routed it to my MM7 app. We'll probably need to tweak the way these routings are defined. I do think it is a little difficult to setup, but the flexibility is fantastic. The difficulty will hopefully go away soon as we complete the documentation. We plan to cover different "usage scenarios" to explain how you would configure the settings for different common scenarios as a starting point. I rambled a bit, but hopefully the explanation makes sense. I'll be curious to hear how you get on with this configuration. -bn | |||
