| MMS delivery reports using NowSMS |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through November 21, 2009 ⬆ |
◄ ► |
| Author | Message | ||||
| Deepak Kumar Khantwal New member Username: Deepu111 Post Number: 4 Registered: 02-2009 |
I am investigation about MMS delivery reports using NowSMS. I am looking for various MMS headers and delivery reports in log files and to major extend I can find the values of MMS headers in log file. Our Test Environment set up is as per the attached image, is having two Anritsu (Wireless Network Simulator) , HUB and NowSMS server [192.168.1.50].Please refer the attachment.. With the set up I performed the below steps. [ IDEAL SCENERIO to Deliver MMS ] 1.Phone 1 send MMS to Phone 2 via NowSMS. 2.MMS received on Phone 2 3.Delivery report comes on Phone 1 via NowSMS 4.MMS retrieved and read on Phone 2 5.Read Report comes to Phone 1. It is Working fine But the particular scenario I am looking for : [ SCENERIO NOT to Deliver MMS] PROBLEM 1.Phone 1 send MMS to a fake Phone number other than Phone 2, so that it could not get delivered. 2.MMS not received as it a fake phone number, No phone exist with this number. But I did not receive any delivery report as “MMS rejected” neither on Phone 1 nor in NowSMS log files. Please suggest how can I test for [ SCENERIO NOT to Deliver MMS] so that I can get Delivery report as MMS rejected in NowSMS log files. Regards Deepak Kumar
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 777 Registered: 08-2008 |
Hi Deepak, There are two relevant scenarios. One scenario is when the MMSC knows that the recipient address is bad and the MMSC refuses to accept the message. The easy way to test this is to go to the "MMSC Routing" page of the NowSMS configuration, and make "Block/Reject Message" the default route. When that configuration is set, the MMSC will only accept messages addressed to recipients that are in the "MMSC Users" list. (The MMSC will also accept messages to recipients that match other defined MMSC routes.) Other recipients will be rejected with an error response to the submit attempt. The other scenario more closely matches your description above. In this scenario, the MMSC does not know that the recipient address is bad. It tries to send the notification, but the recipient never retrieves the message. In this scenario, a non-delivery notification is returned after a timeout elapses. By default, the NowSMS MMSC does not generate these non-delivery notifications, but they can be enabled with the following setting: The MMSC can generate MMS non-delivery notifications when a message expires without being delivered/retrieved by the recipient. To enable this, edit MMSC.INI, and under the [MMSC] header, add NonDeliveryNotificationTimeout=####, where #### is the number of minutes after which to consider a message as being expired. -- Des NowSMS Support | ||||
Test Environment set up diagram
