| Using NowSMS - EAIF and MMS delivery reports |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Chia Siow Tong New member Username: Siow_tong Post Number: 1 Registered: 01-2007 |
Hi, I have a question regarding NowSMS gateway used in the following configuration. Basically I have an application that sends MMS to NowSMS gateway through the web interface and NowSMS routes the MMS through EAIF to an external MMSC. My questions are as follows. 1. Is it possible for us to configure NowSMS to send delivery reports back to our application? 2. Is it possible for us to correlate the outgoing MMS to the delivery report using some form of transaction ids? Thanks | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6896 Registered: 10-2002 |
Hi, Currently the answer is no when the external MMSC connection is EAIF. There is currently some support for this when the external MMSC connection is MM7, or MM1 over GPRS. We could look at adding EAIF support in this area, but we would probably need to see some debug logs from someone like you that can provide log snapshots of real world EAIF delivery reports. If you would like to pursue this, enable the MMSCDEBUG.LOG in NowSMS. Submit one or more messages with a delivery report requested. Assuming that the delivery reports do get routed back to you correctly via EAIF, I'd expect to see an MMSCDEBUG.LOG entry like this: ThreadProcessConnection: Got m-delivery-ind (illegal PDU) I'd like to see MMSCDEBUG.LOG details that show the message submission, and this delivery report coming back. Then we could look at adding support for delivery reports in the EAIF environment. Either post the MMSCDEBUG.LOG here, or e-mail it to nowsms@now.co.uk with "Attention: Bryce" in the subject line. If you e-mail it, please include some text to remind me why I asked for the log file. -bn | |||
| Chia Siow Tong New member Username: Siow_tong Post Number: 2 Registered: 01-2007 |
Hi Bryce, Thanks for the reply. Based on what I read about the EIAF specifications, we will need to create a terminating application listening to a particular IP/port in order to receive delivery reports from MMSC. From the nokia forums, seems like this URL is preconfigured in MMSC as part of agreement. See link below. http://discussion.forum.nokia.com/forum/archive/index.php/t-31437.html Therefore in this case, may I know what URL I should specify in the MMSC to route the delivery back to nowSMS? Thanks again | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6902 Registered: 10-2002 |
Yes, that is correct. I had assumed that you were already setup to receive messages via the EAIF connection, in addition to sending. To receive messages, you need to define an "MMSC VASP" account. Then, tell the provider to post to a URL of http://server:mmscHttpPort/eaif/account=password (mmscHttpPort is the HTTP Port Number configured for the MMSC on the "MMSC" page of the NowSMS configuration.) When you enable this, the delivery reports are currently going to be rejected by NowSMS. But regular delivered messages would come in through this path. The raw delivery report packets would still get logged in the MMSCDEBUG.LOG. I would be interested in seeing a sequence where you send an MMS message with delivery report requested ... and then this delivery report packet comes back in. I've been wrong before, but I don't think it would take much for us to add support for this. (The question would remain though, how do we route this back to your application. Currently, we do route delivery reports back for clients that submit to NowSMS via MM7. I assume you are using HTTP??) -bn | |||
