| No delivery report for MMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | ||||
| Low New member Username: Javabeanz Post Number: 7 Registered: 12-2014 |
Hi, We are using Android Modem to send out MMS. 1) We tested using the web interface and selected Yes for Delivery Report. We can receive the MMS, however, we are not getting the Delivery Report. 2) We also tried the DeliveryReportEnroute=Yes setting in case the Operator is not returning the Delivery Report. However, we are also not getting the Enroute delivery report. There is no problem getting the Delivery Report for SMS. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5911 Registered: 08-2008 |
Hi, Apologies for the delay in response. The short answer is that not all mobile operators support these delivery reports. The longer answer is that it can be difficult to confirm whether the issue is a lack of mobile operator support or some other issue. So here are a few things that should be checked. Can you receive MMS into NowSMS via the Android device? In the SMSIN-yyyymmdd.LOG, are you seeing any binary SMS received? (Receiving an MMS will also show a binary SMS being received. I'm curious if there is any extra activity that might be attributable to missing delivery reports.) -- Des NowSMS Support | ||||
| Low New member Username: Javabeanz Post Number: 8 Registered: 12-2014 |
Yes we can receive MMS via the Android device. Below is the MMSCDEBUG.LOG extract Actual sender is replaced with +1111111111 Actual recipient is replaced with +2222222222 **** 01:03:08:128 [14] HttpResponseWait: Received 340 bytes 01:03:08:128 [14] HttpResponseWait: Ok 01:03:08:128 [14] ThreadProcessVASPQ: MM1 - got http ok response 01:03:08:128 [14] ThreadProcessVASPQ: MM1 - invalid content type in response 01:03:08:195 [14] WaitForSocketClose: WinSock reported ioctlsocket complete 01:03:08:195 [14] SaveIniData: 01:03:08:195 [14] ThreadProcessVASPQ: Delete: C:\PROGRA~2\NowSMS\VASPQ\509F30FF.MMS 01:03:09:038 [9] ThreadRouteSMTPIn: A6F5C9BD.RFC 01:03:09:038 [9] ThreadRouteSMTPIn: X-Mms-Message-Type: MM4_delivery_report.REQ 01:03:09:038 [9] ThreadRouteSMTPIN: X-Mms-Message-Type: m-delivery-ind 01:03:09:038 [9] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: +1111111111/TYPE=PLMN 01:03:09:038 [9] ThreadRouteSMTPIn: BCC: +1111111111/TYPE=PLMN 01:03:09:038 [9] ThreadRouteSMTPIn: To: +1111111111/TYPE=PLMN@nowsms 01:03:09:038 [9] ThreadRouteSMTPIn: TO: +1111111111/TYPE=PLMN 01:03:09:038 [9] ThreadRouteSMTPIn: X-Mms-Message-ID: "20180510-01-1AE58CC0@nowsms" 01:03:09:038 [9] ThreadRouteSMTPIn: X-Mms-Status: Rejected 01:03:09:038 [9] ThreadRouteSMTPIn: X-Mms-MM-Status-Code: Rejected 01:03:09:038 [9] ThreadRouteSMTPIn: X-MMSC-Auth-User: localsystem 01:03:09:038 [9] ThreadRouteSMTPIn: Sender: system-user@ 01:03:09:038 [9] ThreadRouteSMTPIn: From: +2222222222/TYPE=PLMN 01:03:09:038 [9] ThreadRouteSMTPIn: Subject: Not Delivered: mms test 01:03:09:039 [9] ThreadRouteSMTPIn: C:\PROGRA~2\NowSMS\MMSCIN\DECODE\A6F5C9BD.HDR 01:03:09:051 [9] ThreadRouteSMTPIn: Parsing Attachments 01:03:09:123 [9] ThreadRouteSMTPIn: C:\PROGRA~2\NowSMS\MMSCIN\DECODE\A6F5C9BD.MMS 01:03:09:123 [9] MMSRoutingCallback: +1111111111/TYPE=PLMN 01:03:09:123 [9] CheckBlackList: +1111111111 01:03:09:124 [9] CheckBlackList: 01:03:09:124 [9] MMSRoutingCallback: +1111111111/TYPE=VASP:contestmms 01:03:09:130 [9] DeliverMMSMessage: TO: +1111111111/TYPE=VASP:contestmms 01:03:09:130 [9] DeliverMMSMessage: Processing delivery report or read report 01:03:09:130 [9] DeliverMMSMessage: 20180510-01-1AE58CC0@nowsms 01:03:09:130 [9] DeliverMMSMessage: Message ID 20180510-01-1AE58CC0@nowsms, receipt should go to +1111111111, not TO: +1111111111 01:03:09:130 [9] MMSRoutingCallback: +1111111111/TYPE=PLMN 01:03:09:130 [9] CheckBlackList: +1111111111 01:03:09:130 [9] CheckBlackList: SMS:localsystem 01:03:09:130 [9] MMSRoutingCallback: +1111111111/TYPE=VASP:contestmms 01:03:09:130 [9] DeliverMMSMessage: TO: +1111111111/TYPE=VASP:contestmms 01:03:09:130 [9] DeliverMMSMessage: Found VASP Recip - contestmms 01:03:09:131 [14] Debug: Signaled 01:03:09:131 [9] DeliverMMSMessage-VASP: +1111111111 01:03:09:131 [9] DeliverMMSMessage-VASP: Closing Queued Message Files 01:03:09:159 [9] DeliverMMSMessage-VASP: Complete 01:03:10:140 [14] ThreadProcessVASPQ: C:\PROGRA~2\NowSMS\VASPQ\5C850D7B.INI 01:03:10:140 [14] ThreadProcessVASPQ: 5C850D7B.MMS 01:03:10:140 [14] ThreadProcessVASPQ: Message size = 65 01:03:10:140 [14] ThreadProcessVASPQ: recipArray count = 1 01:03:10:141 [14] SaveIniData: 01:03:10:141 [14] ThreadProcessVASPQ: Delete: C:\PROGRA~2\NowSMS\VASPQ\5C850D7B.MMS **** | ||||
| Low New member Username: Javabeanz Post Number: 9 Registered: 12-2014 |
Hi, We also see below in MMSC-20180510.LOG **** 2018-05-10 01:03:06,MMSIN,127.0.0.1,+1111111111,+2222222222,20180510-01-1AE58CC0@nowsms,VASP:contestmms,498 2018-05-10 01:03:08,MMSOUT,VASP:contestmms,+1111111111,+2222222222,FAILED,20180510-01-1AE58CC0@nowsms,512 2018-05-10 01:03:09,MMSIN-DeliveryReport,,SMS:localsystem,+1111111111,20180510-01-1AE58CC0@nowsms,VASP:contestmms,85 2018-05-10 01:03:10,MMSOUT-DeliveryReport,VASP:contestmms,+2222222222,+1111111111,FAILED,20180510-01-1AE58CC0@nowsms,16 **** Does above mean there was a delivery report? But it does not appear in the SMSIN log and it does not get processed in the 2-way, which we have defined the "id:*" keyword for processing delivery reports. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5913 Registered: 08-2008 |
Hi, Sorry for the delay again... The case above is kind of an odd one. Was the MMS in question actually received? It appears to have received an unusual response on submission, which NowSMS generates a non-delivery report for. However, this locally generated non-delivery is not considering that the report should go to the 2-way queue. I need to have our engineering team investigate this more fully...because this is not right. An actual MMS delivery report follows a different path, and in my tests, can go to the 2-way queue. The question still remains if your operator supports them. -- Des NowSMS Support | ||||
| Low New member Username: Javabeanz Post Number: 10 Registered: 12-2014 |
Hi, Yes, the MMS is actually received. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5916 Registered: 08-2008 |
Hi, I've got an update for you to try. The download is at https://www.nowsms.com/download/nowsms20180511.zip I do not expect its to fix the problem, but it will help us understand what is happening. I will need another MMSCDEBUG.LOG... We are expecting a couple differences with this update... 1.) Your 2-way command should receive a non-delivery report. 2.) Additional info should be in MMSCDEBUG.LOG after 01:03:08:128 [14] ThreadProcessVASPQ: MM1 - got http ok response 01:03:08:128 [14] ThreadProcessVASPQ: MM1 - invalid content type in response This "invalid content type in response" is a problem. The MMSC should be responding with an acknowledgment that it has accepted the MMS message, and should report the message id that has been assigned. We do not seem to be receiving that info...so we need to see what information is in the response. -- Des NowSMS Support | ||||
| Low New member Username: Javabeanz Post Number: 11 Registered: 12-2014 |
hi, Attached new MMSCDEBUG.LOG
but we are still not getting any DR | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5923 Registered: 08-2008 |
The MM1 response looks valid, so the non-delivery report is not triggered like it was before. I have no solution for why you are not receiving MMS delivery reports...assuming that MMS messages sent to the phone are received in NowSMS. An MMS message can request a delivery report, but there is no guarantee that one will be generated. We have noticed that some (very few) operators do not generate them. When an MMS delivery report is received by NowSMS from an Android device, it is first processed as a binary SMS, and would appear in a raw format in the SMSIN-yyyymmdd.LOG, like this: 2018-05-23 15:43:48:813,1,NowSMSModem - VZW,Binary=1;DCS=4;UDH=0605040B8423F0;Data=EE0603BEAF848c868d908b3036393331383334463744463030303039383330303030330097383433323930393135392f 545950453d504c4d4e0085045b05c4709581;SMSCRouteName=VZW;Recip=xxxxxxxx An inbound MMS is similar and would appear like this: 2018-05-23 15:51:22:071,1,NowSMSModem - VZW,Binary=1;DCS=4;UDH=0605040B8423F0;Data=EE0603BEAF848c82983035393331383530344538443030303037453430303030333031008d908a808e02780088058103 06977f83687474703a2f2f36392e37382e38382e3130322f736572766c6574732f6d6d733f6d6573 736167652d69643d3035393331383530344538443030303037453430303030333031008916803834 33323930393135392f545950453d504c4d4e00;SMSCRouteName=VZW;Recip=xxxxxxxx The party highlighted in blue indicates whether it is a delivery report or inbound MMS. I mention all this, to make sure we are not overlooking a problem that can be solved. If you are seeing raw MMS delivery reports in the SMSIN-yyyymmdd.LOG, or inbound MMS are not arriving, then there are potential solutions. -- Des NowSMS Support } | ||||
MMSCDEBUG.LOG
