| !! URGENT!! No MM4 Delivery Report! |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | ||||
| Matthieu Unregistered guest |
Hello, I'm receiving MM4 message via VASP account which is then delivered into MMSIN directory. MM_FWD_REQ has the delivery report header set to Yes. I have enabled MM4 Ack under the VAPS account and I do have a MMS route created to sent back the delivery report (I can actually successfully send MMS using this VASP OUT route). Anyway, I have triple checked all the settings, but the nowsms MMSC wont send the MM4_Delivery_Report_req back to the operator MMSC... Any clue? Attached is the mmsdebug.log: looks clean but I dont see any attempt from MMSC to send the delivery report... Help!! Thanks a lot! -Matt PS: I also tried to deliver the incoming MMS to an email recipient (which works fine), but still, no MM4 delivery report from nowMMSC to operator MMSC...
| ||||
| Matthieu Unregistered guest |
I do have "Enable MMS Delivery Receipts" checked under the MMSC config tab. Also the MMS Route matches the "From" number in the MM4_Fwd_Red msg from the operator MMSC. Does the MMSC send Delivery Report only when MMS is actually retrived by MS client over MM1?? | ||||
| Matthieu Unregistered guest |
Hello, Any one can help me here? Thanks! | ||||
| Matthieu Unregistered guest |
Hello Bryce, Did u get a chance to look into my pb? thanks! | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4792 Registered: 10-2002 |
Hi Matthieu, Sorry for the delay. I just replied to your e-mail. I'd probably need to see a longer piece of the log to completely understand. But I think I see enough to be able to explain some things. A delivery report should be generated when the message is actually delivered to the recipient. It is generated when the recipient fetches the MMS message from the MMSC. By contrast, an MM4 ACK happens as soon as the MMSC receives the message. (And I can see the ACK being generated and delivered in the log excerpt.) An MMS delivery report gets routed based upon norrmal routing rules, whereas there are separate routing rules that can be applied for an MM4 ACK. In your log, +8613910778817 is sending to +99977777777. The MM4 ACK is generated immediately. But a delivery report would not be generated until the recipient retrieves the message. When that delivery report is generated will not remember from which route the message originated, and it will route the message to +99977777777 via whichever route has the best match defined (same as if the recipient had replied to the message). Hopefully that will help you figure out what is going on. One other point. It is also possible to disable delivery reports, so make sure that has not been done. If on the "MMSC" page of the configuration dialog, "Enable MMS Delivery Receipts" is not checked, then the MMSC will not generate any delivery reports. Similarly, there is an option that can disable delivery reports from being routed via any given "MMSC Routing" definition ... this option is more difficult to set, but it can be set in the VASPOUT\accountname\VASP.INI file, by putting DisableDeliveryReport=Yes under the [VASP] header. -bn | ||||
| Matthieu Unregistered guest |
Thanks for the reply. This is how I thought it works. I undestand the diff. between the MM4 Ack and the MM4 Delivery Report Request... So unless the recipient fetches the MMS via MM1, the MMSC will not deliver the report, correct? So if I set the VASP account to deliver the MMS into the MMS-IN directory (or to fwd it to an email@), which works fine, MMSC will NOT send the report back to the originator (+66...in my case, and yest, there is a route for that). It there a way to get delivery report from the MMSC when delivery is set to "MMS-IN directory" under the VASP account? We really need to have the MMSC send the delivery (and maybe the read report)... Thanks! -Matthieu | ||||
| matthieu Unregistered guest |
Again, is there a way to get the nowSMS MMSC to send the delivery report when VASP account is set to "deliver to MMS-In directory" thanks | ||||
| Matthieu Unregistered guest |
still trying to get the MMSC to send MM4 Delivery Report... thx | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4972 Registered: 10-2002 |
Hi Matthieu, I haven't forgotten about you. This one is just in the "quick fix" category. It is a very specialised configuration, and not a request that we expect to see a lot of additional demand for. Plus, from a development perspective, it's a bit involved. I wish it were not the case, but it is. We're busy finishing up a number of outstanding feature requests this week, and I'm about 90% sure that this will be included. I will post a follow-up later in the week. -bn | ||||
| Matthieu Unregistered guest |
Thanks for getting back to me on it. I thought it would be fairly straight forward to force the MM4 delivery report when MMS is sent to a local directory instead of fetched by the MS... Anyway, pls let me know if it will be included in the next patch/release. Thanks again for your great support. -Matthieu | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4984 Registered: 10-2002 |
Hi Matthieu, In theory it should be easy. But an MMS delivery report is not triggered until it is delivered to the device. When we receive an MMS message (from a VASP or an MMS client), the message goes into a sort of "inbox" for the recipient. And an MMS notification message gets sent to the recipient. The delivery receipt does not get triggered until the recipient later connects to the server to retrieve the message. So basically, we need to generate a delivery report at an earlier stage in the process. At this point, it looks like it's working, but I have to wait to upload until we finish testing other changes. So I'll follow-up at that point. -bn | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5012 Registered: 10-2002 |
An update for NowSMS v5.51 (any subversion) has been uploaded to address the issue discussed in this thread. The update patch is available at http://www.nowsms.com/download/latestpatch.zip. To install this update, unzip the attached files into the NowSMS program directory, and use them to replace the existing files of the same name. This update is for the v5.51 release of the Now SMS/MMS Gateway product only. Applying these updates to other versions may cause unpredictable results. Remember to stop the NowSMS services before attempting to install these updates. Specific details regarding the issue discussed in this thread: * MMSC: If an "MMSC VASP" is defined with a routing defined to save messages to the "MMS-IN" directory, then generate delivery reports if requested. | ||||
| matthieu Unregistered guest |
Just tested the patch and it is working fine: nowSMS sends the MM4_delivery_report_req once MMS has been received in MMS-IN directory. Your support is greatly appreciated! thanks! -Matt | ||||
MMSCDebug.log
