NowSMS not processing received MMS

NowSMS not processing received MMS SearchSearch
Author Message
Aidan Cope
New member
Username: Acope

Post Number: 1
Registered: 09-2006
Posted on Friday, September 01, 2006 - 09:59 pm:   

I have configured NowSMS to use my Multitech GSM modem on Cingular and have set the MMS configuration under SMSC > Properties > MMS Settings. And have also set the "Process Received MMS Messages" under the 2-Way tab. I also created an MMSC-Route for outbound routing.

I can successfully send an MMS message from NowSMS to a mobile phone via the GSM Modem.

But when I try to send an MMS message from the mobile phone to the GSM Modem, I receive in the SMSIN log an indication that two SMS messages were received:

2006-09-01 00:53:28,1111301000,Binary,4F828A4F8A2370409D4E249C9C97276170706C69636174696F6E2 F766E642E7761702E6D6D732D6D657373616765402F8A0D9C4F348A6F24E45250666D38516F75475 14D414144367541414141424141487341734141414141400D2080E4402B313737383338363738353 12F545950453D504C4D4E40E374647074400A408F24296795829C9D803A409D6874,xxx
2006-09-01 00:53:39,1111301000,Binary,4F828A4F8A2370409D4E242474703A2F2F36362E3130322E31373 12E3135302F5250666D38516F7547514D41414436754141414142414148734173414141414140,xx x

But no further processing gets done to indicate an MMS message was received (ie/ seeing it in MMS-IN).

Any ideas? Thanks in advance!
Aidan Cope
New member
Username: Acope

Post Number: 2
Registered: 09-2006
Posted on Monday, September 11, 2006 - 02:38 am:   

Well, I'm still struggling to receive an MMS on my MultiModem. I put aside the Cingular issue described above for the time being, and am trying on Rogers Wireless in Canada.

The use case is that I'm sending an MMS to myself, and I'm expecting to receive it shortly after sending it.

In this case, I can send/receive an MMS no problem from my phone using the same SIM (tried on both a locked Nokia 6682 and an unlocked Motorola V3x). But when I configure the MultiModem the same way, I can send MMS messages no problem, but I never receive it. I am sending the MMS using the NowSMS Web page for "Send MMS Message". I am including in the first Content File a sample '.mms' file. (I also tried attaching an image in the first Content File, with the same results). I don't get any incoming binary SMS messages. I only get the "Thank you, your picture message
has been sent." text message.

I have attached the MMSCDEBUG.LOG and the MMSCWAPDEBUG.LOG.

application/octet-streamMMSCDEBUG
MMSCDEBUG.LOG (74.9 k)


application/octet-streamMMSWAPDEBUG
MMSWAPDEBUG.LOG (78.5 k)


I am thinking that when I send an MMS using the Multitech Modem, it is indicating to Rogers that it doesn't support MMS viewing, for some reason. I took the identical User-Agent and Profile from the Motorola and included it in the MMSC.INI, but it didn't seem to make much difference.

The reason I think this is that when I remove the SIM and put it into my Nokia, I can leave it sit for 15 minutes and no incoming messages arrive. If I send an MMS to myself, then I receive the MMS plus the others that were 'back-logged' from when they were sent using the Multitech Modem.

For the life of me, I can't figure out why it doesn't work. I'll keep working on it, but any help or ideas would be appreciated! Thanks!

Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6484
Registered: 10-2002
Posted on Monday, September 11, 2006 - 08:11 pm:   

Hi Aidan,

Sorry it has taken me so long to get back to you (and apologies in advance, as my next reply will also likely take at least several days as we work through a backlog).

Go into "Properties" for the modem on the "SMSC" page, and try setting "SMS Message Storage" to "Direct to Modem".

This setting works better with most dedicated modem devices, like the Multitech.

If that doesn't make a difference, then I can't understand why nothing seems to be coming in when you are using the Rogers SIM. With the Cingular SIM, I'd be curious to see the SMSDEBUG.LOG showing the messages being received ... as that might provide some other clue in that instance.

-bn
Aidan Cope
New member
Username: Acope

Post Number: 3
Registered: 09-2006
Posted on Monday, September 11, 2006 - 10:09 pm:   

Thanks Bryce, I did find that suggestion of using the Direct To Modem option in one of the threads here, and have that set. But it hasn't seemed to make any difference. I also found that Rogers doesn't support SMS Access via GPRS, so in the SMSC settings instead of setting SMS Access to Default (or GPRS), I have it set to GSM.

Could that have any ramifications?

As for Cingular, I'll be getting back to that in the next few days and will post that log file.

Thanks!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6490
Registered: 10-2002
Posted on Tuesday, September 12, 2006 - 12:20 pm:   

Hi Aidan,

"SMS Access" being set to "GSM" instead of "GPRS" should not be a problem (I have to use this setting myself).

What is puzzling is why no MMS notification is being received via SMS.

The fact that you can send an MMS using the GPRS connection from NowSMS shows that you have a good connection. Maybe you should check to see that if you send an SMS to the phone number associated with the modem in the SIM ... that this SMS is received ok.

Also, I don't expect this to make any difference, but you might want to try adding this to the [Modem - name] section of SMSGW.INI: CommandPostInit1=AT+CGATT=1

That command just forces the modem to do a low level attach to the GPRS network (it doesn't go so far as connecting to an APN and getting an IP address), but it is another level of attachment to the network.

-bn
Aidan Cope
New member
Username: Acope

Post Number: 4
Registered: 09-2006
Posted on Wednesday, September 13, 2006 - 01:15 am:   

The SMS works flawlessly for both incoming and outgoing. I've been sending/receiving quite a few and they all appear almost instantaneous.

For MMS, Rogers also has a web site that you can go to, that automatically includes all MMSs that you receive on your phone # (provided by lightsurf.com). If I send an MMS message from NowSMS via the modem, it appears almost immediately on the site. I only get this following message back:

16:47:20:545 [2] ThreadProcessModem: AT+CGSMS=3
16:47:20:623 [2] ThreadProcessModem:
OK

16:47:20:701 [2] ThreadProcessModem: AT+CGATT=1
16:47:20:779 [2] ThreadProcessModem:
OK

16:47:20:779 [2] ThreadProcessModem: Modem initialization complete: MultiTech Systems USB GSM_GPRS Wireless Modem
16:47:35:170 [2] ReceiveModemCommand: Processing +CMT: Message
16:47:35:170 [2] ReceiveModemCommand: +CMT: ,58
07917150979603F1040680140050400060902161748200305474D8BD06E5DF751628FFAECB41F0F4 985E979741EDF27C1E3E97410A74780E1297CB6ED0BCECA6BB14

+CPMS: (("SM","ME","BM","SR"),("SM","ME"),("SM","ME"))

OK

16:47:35:170 [2] ReceiveModemCommand: AT+CNMA
16:47:35:170 [2] ModemReceiveMessages: 07917150979603F1040680140050400060902161748200305474D8BD06E5DF751628FFAECB41F0F4 985E979741EDF27C1E3E97410A74780E1297CB6ED0BCECA6BB14
16:47:35:170 [2] ModemReceiveMessages: SMSC address len = 7
16:47:35:170 [2] ModemReceiveMessages: SMSC Address = +17057969301
16:47:35:170 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER
16:47:35:170 [2] ModemReceiveMessages: Sender address len = 6
16:47:35:170 [2] ModemReceiveMessages: Sender Address = 410005
16:47:35:170 [2] ModemReceiveMessages: PID = 40
16:47:35:170 [2] ModemReceiveMessages: DCS = 00
16:47:35:170 [2] ModemReceiveMessages: Anticipated user data length = 48
16:47:35:170 [2] ModemReceiveMessages: Message = Thank you, your picture message
has been sent.

16:47:35:483 [5] ThreadProcessInboundSMS: Processing 45074638.in...


ALSO, when I try doing a "Send WAP Push Message" to myself, I get the binary msg back almost immediately... it's just something odd is happening when it's an MMS message:

16:59:38:076 [2] ReceiveModemCommand: Processing +CMT: Message
16:59:38:076 [2] ReceiveModemCommand: +CMT: ,88
07917150979603F1440B917187837658F100F560902161954300450605040B8423F0E20601AE0205 6A0045C60C03736F6D6577617075726C2E636F6D2F6E6F706172746963756C61726D73672E68746D 6C0007010354657374204D7367000101

16:59:38:076 [2] ReceiveModemCommand: AT+CNMA
16:59:38:076 [2] ModemReceiveMessages: 07917150979603F1440B917187837658F100F560902161954300450605040B8423F0E20601AE0205 6A0045C60C03736F6D6577617075726C2E636F6D2F6E6F706172746963756C61726D73672E68746D 6C0007010354657374204D7367000101
16:59:38:076 [2] ModemReceiveMessages: SMSC address len = 7
16:59:38:076 [2] ModemReceiveMessages: SMSC Address = +17057969301
16:59:38:076 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER
16:59:38:076 [2] ModemReceiveMessages: User Data Header is present
16:59:38:076 [2] ModemReceiveMessages: Sender address len = 11
16:59:38:076 [2] ModemReceiveMessages: Sender Address = +17783867851
16:59:38:076 [2] ModemReceiveMessages: PID = 00
16:59:38:076 [2] ModemReceiveMessages: DCS = F5
16:59:38:076 [2] ModemReceiveMessages: Anticipated user data length = 69
16:59:38:076 [2] ModemReceiveMessages: Binary message = 0605040B8423F0E20601AE02056A0045C60C03736F6D6577617075726C2E636F6D2F6E6F70617274 6963756C61726D73672E68746D6C0007010354657374204D7367000101
16:59:38:514 [5] ThreadProcessInboundSMS: Processing 4507463A.in...
16:59:38:514 [5] ThreadProcessInboundSMS: Processing WAP Push Message
16:59:38:514 [5] ThreadProcessInboundSMS: Content type not processed: application/vnd.wap.sic
Aidan Cope
New member
Username: Acope

Post Number: 5
Registered: 09-2006
Posted on Thursday, September 14, 2006 - 07:59 am:   

I bought another USB Multi-tech modem and went back to try out the Cingular problem, and wouldn't you know it, it worked fine! I haven't investigated what exactly is the difference between the two modems; as far as I know they are the same model, s/w version, etc.

So it might be that the problems I am having with Rogers are related to a lemon modem.

I don't physically have the two modems in the same area, but I should in the next week or two, and I will post my findings.

Thanks Bryce for your help!


Adam Block
New member
Username: Ablock

Post Number: 4
Registered: 10-2006
Posted on Friday, October 27, 2006 - 06:23 pm:   

I'm having the exact same problem that the original creator of this thread described. MMS sent to my Cingular SIM generates two incoming binary SMSs and nothing else happens.

I am using a Cingular SIM card in a serial MultiTech GPRS modem. The driver is the MultiTech driver, because when I used the Standard 33,600 bps Modem driver the system reported "Error waiting for initialization response from modem" about once an hour.

I can send and receive SMS and send MMS without any problem. The Cingular SIM has been tested in a phone and receives MMS properly.

I can try a firmware upgrade; that route is suggested by the last post. Otherwise, any further suggestions?

I've also noticed strange behavior with a T-Mobile SIM on MMS receives: sometimes the MMS comes in; other times I get a text message from T-Mobile stating that I have a picture message waiting at t-mobilepictures.com.

MMS is a pain to debug, between the carrier's crummy delivery times and MM7's complexities and POST instead of GET. Sorry for venting. :-)

Thanks for the help.

/adam
Adam Block
New member
Username: Ablock

Post Number: 5
Registered: 10-2006
Posted on Friday, October 27, 2006 - 07:36 pm:   

Follow up: MultiTech lists no firmware updater on their site for the MultiModem GPRS.
Adam Block
New member
Username: Ablock

Post Number: 6
Registered: 10-2006
Posted on Friday, October 27, 2006 - 09:29 pm:   

Okay, things seem to be working.

I think the problem stems from what appear to be bugs in the MMS routing. When I changed the name of a route that was assigned to handle inbound MMS, the name doesn't get properly updated in the MMS Settings dialog of the SMSC configuration dialog. I deleted and recreated my routes (one diagnostic, one to my application), but the old names keep reappearing as phantoms.

Where are the routing profiles saved? There must be a way to clean this up. Right now I see two routes in my MMS Settings dialog, neither of which exists (by name, anyway) in the MMSC Routing list.

Okay, setting the routing type to something other than MM7, closing all dialog boxes (including the main NowSMS config dialog) then reopening and reselecting MM7 routing seems to clear out the phantoms temporarily.

/afb
Adam Block
New member
Username: Ablock

Post Number: 7
Registered: 10-2006
Posted on Monday, October 30, 2006 - 05:48 pm:   

Since applying the latest Now2006 patch I seem to be having problems again.

Looking at the logs with debugging turned on, I see the two binary SMSs come in, and then in SMSDEBUG.LOG the modem makes the MM1 connection and fetches the MMS content and appears to be calling the proper route:

09:15:59:298 [7] ThreadProcessInboundMMS: mm1 - got http ok response
09:15:59:298 [7] RouteInboundMMSToVASP: Routing inbound MMS to VASP: Dummy Inbound

"Dummy Inbound" is my test routing. It calls a Web server that simply dumps the POST request contents to a file for examination.

However, despite the RouteInboundMMSToVASP line, no call is ever made to the Web server. I have tested manually that the server running NowSMS can connect to the dummy Web server.

Where should I look next for further diagnosis?

Thanks!

/afb
Adam Block
New member
Username: Ablock

Post Number: 8
Registered: 10-2006
Posted on Monday, October 30, 2006 - 06:53 pm:   

Followup: Setting up MMSC to route message to MMS-IN works. The information in my last post is still correct.

/afb
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6769
Registered: 10-2002
Posted on Wednesday, November 01, 2006 - 05:50 pm:   

Hi Adam,

I'm sorry, but I'm confused.

It sounds like you've worked through the initial issues, and now you're having a problem getting the MMS message routed to your application.

I assume that "Dummy Inbound" is an MM7 connection defined under "MMSC Routing".

Is the MMSC service enabled?

It is a little confusing, but the MMSC service handles all of the MM7 interfacing, and outbound MMS delivery.

As I read the above, it looks like at this point you are receiving only ... not sending. So maybe the MMSC service is not enabled.

If it is enabled, let's take a look at the MMSCDEBUG.LOG to see what's going on.

-bn
Adam Block
New member
Username: Ablock

Post Number: 9
Registered: 10-2006
Posted on Thursday, November 02, 2006 - 05:30 am:   

Sorry if I was confusing. The opposite is true; I can send MMS (using the Web interface, for example) but not receive.

When I send an MMS, the SMSIN log shows the arrival of two binary files. However, nothing happens after that. MMSCDEBUG shows no activity beyond the startup entries (see attachment).

The MMSC service is definitely running. All .INI files are the defaults (no customization).

/afb

application/octet-streamMMSCDEBUG.LOG
MMSCDEBUG.LOG (1.0 k)
Adam Block
New member
Username: Ablock

Post Number: 10
Registered: 10-2006
Posted on Thursday, November 02, 2006 - 05:31 am:   

Sorry, to clarify the last entry: When I send an MMS to the modem SIM using my mobile, the SMSIN log shows the arrival of two binary files. However, nothing happens after that.
Adam Block
New member
Username: Ablock

Post Number: 11
Registered: 10-2006
Posted on Saturday, November 04, 2006 - 03:32 am:   

I found where the incoming binary SMS that aren't being processed are going: the SMS-IN directory. They're being dumped in there in binary form, but no MMS processing is ever done. MMSCDEBUG has no new entries except the hourly "XX days remaining in trial version" warning.

"Process incoming MMS" is checked on the 2-Way tab. "Receive MMS" is checked in the SMSC modem properties dialog box.

Any further thoughts? I'm pretty sure this worked before I applied the patch.

Thanks!

/afb
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6794
Registered: 10-2002
Posted on Tuesday, November 07, 2006 - 06:02 pm:   

Adam,

Sorry for the delay in response.

In the "Properties" for the modem on the "SMSC" page, do you have "SMS Message Storage" set to "Direct to Modem".

I'd be interested in seeing the SMSDEBUG.LOG showing these MMS notifications coming in, so that I can determine what is wrong with them.

All I can think of is the "Direct to Modem" issue.

Or we've also seen issues of flaky cables dropping random bytes and corrupting the received data. Although I've generally only seen this issue in serial connections, not USB ... but maybe there is an issue of a problem with a USB port, and try connecting to a different USB port to try to rule out issues there.

The cable issue is a long shot ... I think we're going to need to look at SMSDEBUG.LOG to see the raw messages that are coming in.

-bn
Adam Block
New member
Username: Ablock

Post Number: 12
Registered: 10-2006
Posted on Tuesday, November 07, 2006 - 06:29 pm:   

Bryce, thanks for the response.

Should or should not the SMS Message Store be set to Direct to Modem? At the moment it is.

This is a serial modem, not a USB. I see the exact same problem on two different machines running NowSMS. One is an XP home machine with a serial port PCI card. The other is a Win2K machine with legacy ports.

But I think that if this were a cable issue the binary files saved in the MMS-IN directory would be corrupted, but they're fine.

Anything else you can think of that would affect routing? I will post SMSDEBUG when I get to the office.

Thanks!

/afb
Adam Block
New member
Username: Ablock

Post Number: 13
Registered: 10-2006
Posted on Tuesday, November 07, 2006 - 09:12 pm:   

Nope, I was wrong. SMS Message Store was "Default". Changing this appeared to fix the problem. I am confirming, but things look good right now. Thanks again.

/afb
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6799
Registered: 10-2002
Posted on Tuesday, November 07, 2006 - 09:16 pm:   


quote:

Should or should not the SMS Message Store be set to Direct to Modem? At the moment it is.




Should (at least that is what I'd recommend).


quote:

This is a serial modem, not a USB.




Ok. I wouldn't rule out the cable then. But then again, I might be confused about what the current problem is.


quote:

But I think that if this were a cable issue the binary files saved in the MMS-IN directory would be corrupted, but they're fine.




I thought you weren't getting any files there. I thought you were getting binary SMS files into the SMS-IN directory, and no files to MMS-IN.

But I guess I'm confused. If I read back earlier in the thread, you are getting the messages into MMS-IN. Or at least you are sometimes?

I'm sorry, I know a big part of the problem here is that I haven't been on-line to respond back for follow-up quickly enough.

I see that earlier in this thread, the problem is that the MMS message is being received, but it is not getting routed to the "Dummy Inbound" "MMSC Routing" definition.

So we might need to look at both SMSDEBUG.LOG and MMSCDEBUG.LOG in order to see what is going on.

Let me explain the flow that the message processing is going to take, and this might help.

The binary SMS notification is going to come in to SMS-IN. It should be recognised as an MMS notification, and get moved to MMSINQ.

When the MMS is retrieved, if it is being routed to an MM7 connection, a message file should be created in the VASPQ directory. VASPQ holds messages that are destined for an outbound MM7 connection.

I might not be back again for follow-up today, but I should finally be back to a regular schedule to improve the response time here.

-bn
Adam Block
New member
Username: Ablock

Post Number: 15
Registered: 10-2006
Posted on Wednesday, November 08, 2006 - 01:18 am:   

That's okay. It looks like the Direct To Modem setting was the problem. Things are working well now.

And I successfully shortened my app code a lot using your new multipart POST tool; though I have a question that I posted on that thread.

Thanks again!

/afb