Don't receive MMS and MMS delivery report

Don't receive MMS and MMS delivery report SearchSearch

SMS & MMS Technical Forum » NowSMS Lite (Product Support Only) » Don't receive MMS and MMS delivery report « Previous || Next »
Author Message
Igor Grekov
New member
Username: Igor

Post Number: 1
Registered: 06-2015
Posted on Tuesday, June 02, 2015 - 06:34 pm:   

Hi!
I try to receive delivery report from the sent MMS using WebInterface, but it doesn't occur..
Also, MMS aren't accepted.

SMS sent and accepted well, delivery report - ok!
MMS are sent and delivered to the recipient.
I use GSM modem Huawei E392 and NowSms Lite Trial and try to send/receive messages through WebInterface for check and NowSms Lite Trial.
I saw all forum, but didn't find the solution.

The report on delivery of the MMS is very necessary.
application/octet-streamSMSDEBUG
SMSDEBUG.LOG (33.4 k)
application/octet-streamMMSCDEBUG
MMSCDEBUG.LOG (8.9 k)
Igor Grekov
New member
Username: Igor

Post Number: 2
Registered: 06-2015
Posted on Wednesday, June 03, 2015 - 09:51 am:   

On other gsm modem (Novatel Wireless MC935D) I can receive only SMS and can't receive delivery reports. Instead of the delivery report in the SMSDEBUG.LOG writes the following:

13:28:35:559 [17] ReceiveModemCommand: Received New Message Notification

This notice comes also and for MMS.

application/octet-streamSMSDEBUG.LOG
SMSDEBUG.LOG (7.8 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5309
Registered: 08-2008
Posted on Wednesday, June 03, 2015 - 02:25 pm:   

Hi Igor,


For the second issue (no delivery reports on Novatel modem), it is interesting that "Received New Message" is triggered, but on message is found. My suggestion would be to edit SMSGW.INI and add the following under the [Modem - Novatel Wireless Modem] header:

PollMemorySR=Yes
DebugModemPoll=Yes

PollMemorySR may fix the problem (although based on the debug log, this setting should have been enabled automatically). DebugModemPoll will increase the logging and hopefully give us a better idea.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5310
Registered: 08-2008
Posted on Wednesday, June 03, 2015 - 03:05 pm:   

Hi Igor,

For problem #1...my first suggestion is to use an Android phone as a modem over WiFi.

There are few reasons for this.

* Better performance (avoids mode shifting between SMS and MMS).

* Avoids issue where many mobile operators do not enable MMS capability on modem SIMs, because they assume the device cannot send MMS.

The only downside of using an Android device is that special SMS (message class, flash, WAP Push) cannot be supported. Long text and Unicode are OK.

Now to actually troubleshoot the problem. Seeing the MMSWAPDEBUG.LOG and the MMS settings in use would be helpful.

Is the MMS actually being sent? The response from the MMSC appears to be generic, as normally one would expect an MMS specific response with an MMS message-id. I would expect that the MMS is not actually being sent.

Try moving the SIM from the device to a phone and verify that the phone can send/receive MMS for that SIM. As I state above, if the device is on a modem plan, the operator will assume the device is being used as an internet modem, and MMS may not be enabled. We've even seen one US operator that detects the device is a modem and blocks MMS, even if the SIM was originally activated in a phone. That's why my first recommendation was to use an Android device instead. The mobile operator sees that device as a phone, not as a modem.

All this said MMS delivery reports are a problem. Our experience is that only around 50% of mobile operators support them. MMS delivery reports arrive as a standard SMS with MMS content in the payload, so it is different from what you are experiencing with SMS delivery reports and the second modem. (Side note: We use the stock Android messaging app, not Hangouts, as a test to determine whether or not the operator supports MMS delivery reports. If that app can't see MMS delivery reports either, we know it is not a NowSMS specific issue.)

--
Des
NowSMS Support
Igor Grekov
New member
Username: Igor

Post Number: 3
Registered: 06-2015
Posted on Thursday, June 04, 2015 - 07:55 am:   

I Tried the second modem of Novatel (MC990D) firm, the same history. I sent SMS, but delivery report again got lost. In SMSGW.INI added
PollMemorySR=Yes
DebugModemPoll=Yes

SMSDEBUG.log attached
application/octet-stream
SMSDEBUG.LOG (20.7 k)


I will add that SMS and MMS via the modem are perfectly sent.
Igor Grekov
New member
Username: Igor

Post Number: 4
Registered: 06-2015
Posted on Thursday, June 04, 2015 - 08:19 am:   

Hi!
And again to the GSM modem Huawei..Probably, the reason in the device. I tried to send messages via another Huawei model - E3272 (previous E392) and I сould receive MMS and MMS delivery report.
But...Perhaps, I don't understand something. How I can read the binary message (delivery report MMS)? SMS delivery report is simple.
ModemTextMode didn't solve my problem. What I do wrong and how I have to do?

Logs attached
application/octet-stream
SMSDEBUG.LOG (15.9 k)
application/octet-stream
MMSWAPDEBUG.LOG (4.9 k)
application/octet-stream
MMSCDEBUG.LOG (4.4 k)
Igor Grekov
New member
Username: Igor

Post Number: 5
Registered: 06-2015
Posted on Thursday, June 04, 2015 - 12:31 pm:   

Hi Des
Perhaps I wasn't attentive.
My configuration is : 2-Way -> Process received MMS Messages -> Receive to MMS-IN Directory.
in this directory really there is a report:

X-NowMMS-RCPT-TO: +7999999999
X-NowMMS-Modem-Name: HUAWEI Mobile Connect - Modem
Message-type: m-delivery-ind
MMS-version: 1.2
Message-id: 20150604-16-E3995361@nowsms
Date: Thu, 04 Jun 2015 13:04:40 GMT
To: +79999999999/TYPE=PLMN
Status: Retrieved

I correctly understand, what it is the MMS delivery report?
What else "status" happen?

Thanks for your answers.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5312
Registered: 08-2008
Posted on Thursday, June 04, 2015 - 03:26 pm:   

Hi Igor,

Sorry, I made a mistake. The extra modem debug is not present in your logs, because I gave the wrong instruction.

Under [Modem - Novatel Wireless Modem], add PollMemorySR=Yes

Under [SMSGW], add DebugModemPoll=Yes

The MMS delivery report looks good. If you would like to receive them in a simple format, (id:xxxxx like with SMS), on the 2-way page, enable "Use SMS 2-Way Commands" under "Process Received MMS". Note that MMS delivery reports are only processed via 2-way commands in version 2014.08.11 or later. This is a later version than our current official release. Scroll down to the interim development releases at http://www.nowsms.com/download-free-trial and use the latest version on that page.

--
Des
NowSMS Support
Igor Grekov
New member
Username: Igor

Post Number: 6
Registered: 06-2015
Posted on Tuesday, June 30, 2015 - 09:41 am:   

Hi Des,
Thanks for your previous answers.
I couldn't solve a problem with the NOVATEL modem, it is seen their design feature and it doesn't interest me any more.

But, not to create a new subject I will ask the following question here.

May I receive modem errors from the NowSMS in my programm by means of any inquiries? For example, I need to know, whether the modem is connected or not?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5348
Registered: 08-2008
Posted on Tuesday, June 30, 2015 - 12:59 pm:   

Hi Igor,

There is an XML Status query, where you can check the modem status.

See http://www.nowsms.com/xml-status-query-for-smsc-connection-status-and-statistics

--
Des
NowSMS Support
Igor Grekov
New member
Username: Igor

Post Number: 7
Registered: 06-2015
Posted on Wednesday, July 08, 2015 - 09:03 am:   

Hi Des,

I try receive delivery report from NowSMS to my application via 2-way.
In Received SMS command table:
Keyword: *
Run HTTP: http://127.0.0.1:5555/?message=@@FULLSMS@@ or
httppost://127.0.0.1:5555/?message=@@FULLSMS@@

Input SMS has status "queued".
My app receives http query and process it, but NowSMS send query again.

What reply I should send to NowSMS?

I want receive simply the message from the NowSMS and process it, without sending answers to somebody.
Igor Grekov
New member
Username: Igor

Post Number: 8
Registered: 06-2015
Posted on Wednesday, July 08, 2015 - 03:05 pm:   

In SMSDEBUG.LOG:
18:51:26:006 [17] ModemTest: HUAWEI Mobile Connect - Modem
18:51:26:346 [17] ModemTest: OK
18:52:19:525 [8] HttpResponseWait: ioctlsocket indicates end of request
18:52:19:525 [8] HttpResponseWait: Expected 0 bytes, got 0 bytes
18:52:19:525 [8] HttpResponseWait:
18:52:19:525 [8] RetrieveURL: HTTP timeout error or invalid server response
18:52:19:525 [8] ThreadProcessInboundSMS: Processing incomplete 556FBA9F.in...
18:52:21:531 [8] ThreadProcessInboundSMS: Processing 556FBA9F.in...
18:52:21:531 [8] GetProgramToExecute: Found 2-way command prefix match id:*
18:52:21:531 [8] GetProgramToExecute: Best match so far for 2-way command prefix id:*
18:52:21:531 [8] GetProgramToExecute: http://127.0.0.1:5555/?message=@@FULLSMS@@
18:52:21:532 [8] GetProgramToExecute: http://127.0.0.1:5555/?message=id%3A55555%0AIP%3A62.16.108.130
18:52:21:532 [8] ThreadProcessInboundSMS: Executing http://127.0.0.1:5555/?message=id%3A55555%0AIP%3A62.16.108.130
18:52:21:532 [8] RetrieveURL: Retrieving http://127.0.0.1:5555/?message=id%3A55555%0AIP%3A62.16.108.130
18:52:21:532 [8] InetServerConnect: Connected to 127.0.0.1 (127.0.0.1:5555)
18:52:21:532 [8] RetrieveURL: Retrieving ?message=id%3A55555%0AIP%3A62.16.108.130
18:52:21:532 [8] RetrieveURL: GET /?message=id%3A55555%0AIP%3A62.16.108.130 HTTP/1.1
User-Agent: Now SMS/MMS Gateway v2015.06.24
Accept: */*
Host: 127.0.0.1:5555
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5359
Registered: 08-2008
Posted on Wednesday, July 08, 2015 - 04:59 pm:   

Hi Igor,

You need to send a normal HTTP OK response to acknowledge the message. The content can be blank to ensure no reply is sent.

At a raw protocol level, it would look like this:

HTTP/1.1 200 OK
Content-Length: 0
Content-Type: text/plain


To ensure no reply is accidentally generated, in the 2-way command definition, uncheck "Command returns response text" or "Reply to sender with command output". (There is different wording for this option in different versions of NowSMS.

--
Des
NowSMS Support
mrprakash
New member
Username: Mrprakash

Post Number: 1
Registered: 08-2015
Posted on Monday, October 05, 2015 - 11:13 am:   

Hi I'm Getting the Same Response While Processing the 2-Way SMS.
The Issue I face is My Command Running Successfully & return the Required Output.
But
There is No any response when I Process a Long result which takes approx 3 minutes to return the result.
The Message Response are always shows in Queue/Retries. The View Button on 2-Way SMS Shows the Following:
[SMS-IN]
ModemName=Mobile Connector #4
Sender=xxxxxxx
SCTS=20151005173013
Data=MYKEYWORD
ReceivedSMSC=xxxxxx
[ErrorDetail]
RetryCount=2
LastRetryTime=##########

Pl. advice
regds
mrprakash
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5467
Registered: 08-2008
Posted on Monday, October 05, 2015 - 01:09 pm:   

Hi,

Does this happen with all messages or only some (or most) messages?

For example, if you restart the NowSMS server is the first message processed OK, but the next messages have retry/delay? If this is the case the web server running the 2-way script may have a problem with keep-alive sockets. To disable NowSMS from using keep-alive sockets, edit SMSGW.INI and under the [SMSGW] header add 2WayKeepAlive=No

The above problem/solution would be a rare case, so I do not expect this to resolve your problem unless it matches my description (if you restart the NowSMS server is the first message processed OK, but the next messages have retry/delay?)

For other cases, it suggests the 2-way command is sending an incomplete HTTP response or taking a long time to reply.

What is the command type? PHP?

Enable the SMSDEBUG.LOG (option on "Serial # page of configuration).

Do you see statements like this?


quote:

18:52:19:525 [8] HttpResponseWait: ioctlsocket indicates end of request
18:52:19:525 [8] HttpResponseWait: Expected 0 bytes, got 0 bytes
18:52:19:525 [8] HttpResponseWait:
18:52:19:525 [8] RetrieveURL: HTTP timeout error or invalid server response




If so, look in the SMSDEBUG.LOG to find the 2-way command URL NowSMS is trying to process...copy + paste it to try from a web browser. Does that work?


--
Des
NowSMS Support
mrprakash
New member
Username: Mrprakash

Post Number: 2
Registered: 08-2015
Posted on Tuesday, October 06, 2015 - 09:24 am:   

Hi,
Thanks for Reply.
This happens to Particular this message Only.
Actually the HTTP response is taking approx 3-4 minutes.
and this URL is running Fine on Browser.

Only during the 2-way processing it goes on Queue..

Below is the SMSDEBUG.LOG
------------------------------

15:29:01:406 [33] ModemReceiveMessages: Decoding received message index 0 from message storage SM
15:29:01:406 [33] ModemReceiveMessages: 0791198989509141240C911989399456000000510160513393220349A715
15:29:01:406 [33] ModemReceiveMessages: SMSC address len = 7
15:29:01:406 [33] ModemReceiveMessages: SMSC Address = +xxxxxxxx
15:29:01:406 [33] ModemReceiveMessages: SMS Message Type = SMS-DELIVER
15:29:01:406 [33] ModemReceiveMessages: Sender address len = 12
15:29:01:406 [33] ModemReceiveMessages: Sender Address = +xxxxxxxx
15:29:01:406 [33] ModemReceiveMessages: PID = 00
15:29:01:406 [33] ModemReceiveMessages: DCS = 00
15:29:01:406 [33] ModemReceiveMessages: Anticipated user data length = 3
15:29:01:406 [33] ModemReceiveMessages: Message = XXX
15:29:01:437 [15] ThreadProcessInboundSMS: Processing 4C386666.in...
15:29:01:453 [15] GetProgramToExecute: http://xxx.xxxx.xxx/xxx.asp?txtweb-message=@@SMS@@&txtweb-mobile=@@SENDER@@&MSG-ID=@@MESSAGEID@@&MSG-Date=@@MSGDATE@@&Msg-T ime=@@MSGTIME@@&txtsms=@@FULLSMS@@&txtprefix=@@SMSPREFIX@@
15:29:01:453 [15] GetProgramToExecute: http://xxx.xxxxx.xxx/xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C 386666.in&MSG-Date=20151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
15:29:01:453 [15] ThreadProcessInboundSMS: Executing http://xxx.xxxxx.xxx/xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C 386666.in&MSG-Date=20151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
15:29:01:453 [15] RetrieveURL: Retrieving http://xxx.xxxxx.xxx/xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C 386666.in&MSG-Date=20151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
15:29:01:453 [15] RetrieveURL: Looking up xxx.xxxxx.xxx
15:29:01:453 [33] ModemReceiveMessages: AT+CMGD=0

15:29:01:468 [15] RetrieveURL: Retrieving /xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C386666.in&MSG-Date=2 0151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
15:29:01:468 [15] RetrieveURL: GET /xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C386666.in&MSG-Date=2 0151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
User-Agent: Now SMS/MMS Gateway v2012.06.28
Accept: */*
Connection: close
Host: xxx.xxxxx.xxx


15:29:02:781 [33] ModemReceiveMessages:
OK

15:30:11:468 [15] HttpResponseWait: ioctlsocket indicates end of request
15:30:11:468 [15] HttpResponseWait: Expected 0 bytes, got 0 bytes
15:30:11:468 [15] HttpResponseWait:
15:30:11:468 [15] RetrieveURL: HTTP timeout error or invalid server response
15:30:11:468 [15] ThreadProcessInboundSMS: Processing incomplete 4C386666.in...
15:30:11:562 [12] ThreadProcessInboundSMS: Processing 4C386666.in...
15:30:11:562 [12] GetProgramToExecute: http://xxx.xxxx.xxx/xxx.asp?txtweb-message=@@SMS@@&txtweb-mobile=@@SENDER@@&MSG-ID=@@MESSAGEID@@&MSG-Date=@@MSGDATE@@&Msg-T ime=@@MSGTIME@@&txtsms=@@FULLSMS@@&txtprefix=@@SMSPREFIX@@
15:30:11:562 [12] GetProgramToExecute: http://xxx.xxxxx.xxx/xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C 386666.in&MSG-Date=20151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
15:30:11:562 [12] ThreadProcessInboundSMS: Executing http://xxx.xxxxx.xxx/xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C 386666.in&MSG-Date=20151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
15:30:11:562 [12] RetrieveURL: Retrieving http://xxx.xxxxx.xxx/xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C 386666.in&MSG-Date=20151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
15:30:11:562 [12] RetrieveURL: Looking up xxx.xxxxx.xxx
15:30:11:562 [12] RetrieveURL: Retrieving /xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C386666.in&MSG-Date=2 0151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
15:30:11:578 [12] RetrieveURL: GET /xxx.asp?txtweb-message=&txtweb-mobile=%2Bxxxxxxxx&MSG-ID=4C386666.in&MSG-Date=2 0151006&Msg-Time=153339&txtsms=XXX&txtprefix=XXX
User-Agent: Now SMS/MMS Gateway v2012.06.28
Accept: */*
Connection: close
Host: xxx.xxxxx.xxx

---------------------------------------------------------

Pl. advice.
mrPrakash

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

Login Login / Register Logout Logout Search Last 30 Days Topics Topics