| ModemReceiveMessages: ERROR |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Ian Fitchet New member Username: Idf Post Number: 7 Registered: 12-2003 |
Hi, I can receive SMS messages through v20031006 with an MMSWAP patch, however I can't receive incoming MMSs. I do see the following in SMSDEBUG.LOG, repeated every 30-90 minutes (or longer), which makes me a bit suspicious: 13:28:11:037 [1] ModemReceiveMessages: ERROR 13:28:17:037 [1] ThreadProcessModem: Before ModemRelease - Standard 19200 bps Modem 13:28:17:037 [1] ThreadProcessModem: After ModemRelease - Standard 19200 bps Modem 13:28:23:037 [1] ThreadProcessModem: Before ModemAllocate - Standard 19200 bps Modem 13:28:23:037 [1] ThreadProcessModem: After ModemAllocate - Standard 19200 bps Modem - OK 13:28:23:037 [1] ThreadProcessModem: Re-initializing modem: Standard 19200 bps Modem ... 13:28:23:991 [1] ThreadProcessModem: AT+CPMS? 13:28:24:147 [1] ThreadProcessModem: +CPMS: "MT",5,45,"MT",5,45,"MT",5,45 OK 13:28:24:147 [1] ThreadProcessModem: Modem initialization complete: Standard 19200 bps Modem Naively, I would interpret this as meaning it saw in incoming m-retrieve-conf or at least the start of the exchange but something went wrong very quickly. The "Test Connection" button in MMS Receive Messages reports that all is well. Nothing shows up in any other logs I have to hand (MMSWAPDEBUG.LOG anyway!). I haven't seen anything in other threads but I won't deny that I haven't read them all! Cheers, Ian | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1377 Registered: 10-2002 |
Ian, I wouldn't be worried about that appearing every 30 to 90 minutes. Basically, we're polling the modem for messages, and for some unknown reason, it seems normal to occasionally receive some "ERROR" responses from some modems. So I suspect that something else is the root of the problem. What type of modem is this? If it is a phone, then most of those intercept MMS notifications themselves, and will not route them to a connected device. We were recently alerted to a problem where we could not receive notifications about binary SMS (including MMS notifications) on a Nokia 30. If you have a Nokia 30, that is likely the problem. If it is not a Nokia 30, I'd be curious what the model is (and the patch might still help you). I had planned to upload the patch today, but it's looking more like Monday at this point. -bn | |||
| Ian Fitchet New member Username: Idf Post Number: 8 Registered: 12-2003 |
It's a Siemens MC35T. I have received incoming MMSs before. Indeed before the MMSWAP.DLL patch you gave me to correct the Gateway redirect problem in the other thread. I couldn't tell you if it had stopped working before that patch (if I'd tweaked a setting, say) as I didn't do any rigorous testing. Cheers, Ian | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1400 Registered: 10-2002 |
Ian, I haven't seen any problems with the Siemens MC35T. So I don't think it would be the same problem as with the Nokia 30. Also the MMSWAP.DLL wouldn't have anything to do with this. Verify that text SMS messages are actually being received. You could also use the web interface of NowSMS and send a WAP push to the phone number of the modem. Does this generate any activity in the SMSDEBUG.LOG? -bn | |||
| Ian Fitchet New member Username: Idf Post Number: 9 Registered: 12-2003 |
Bryce, Inbound SMS' are fine. When I tried to send a WAP Push, I got the following: 17:08:53:388 [5] ThreadProcessConnection: Processing connection from 127.0.0.1... 17:08:53:388 [5] ThreadProcessConnection: Processing request /Send%20WAP%20Push%20Message.htm?WAPSL=&PhoneNumber=%2B447730611xxx&WAPURL=http% 3A%2F%2Fwap.mobitastic.com&Text=WAP+Push%21&WAPSIACTION=signal-medium&WAPSIID=&W APSICREATED=&WAPSIEXPIRES= 17:08:53:388 [5] Debug: 1 recipient entries 17:08:53:388 [5] Debug: +447730611xxx 17:08:54:263 [2] ThreadProcessModem: Processing 3FDDD8A3.req... 17:08:54:263 [2] ThreadProcessModem: OUT: AT+CMGS=66 17:08:54:388 [2] ThreadProcessModem: IN: > 17:08:54:388 [2] ThreadProcessModem: OUT: 0041000C9144770316414400F5350605040B8423F0E20601AE02056A0045C60C037761702E6D6F62 697461737469632E636F6D00070103574150205075736821000101 17:08:58:826 [2] ThreadProcessModem: +CMGS: 163 OK 17:09:04:326 [2] ModemReceiveMessages: +CMGL: 2,0,,72 0791448720003023440C9144770316414400F530217171808500350605040B8423F0E20601AE0205 6A0045C60C037761702E6D6F62697461737469632E636F6D00070103574150205075736821000101 OK 17:09:04:326 [2] ModemReceiveMessages: Decoding received message index 2 from message storage ME 17:09:04:326 [2] ModemReceiveMessages: SMSC address len = 7 17:09:04:326 [2] ModemReceiveMessages: SMSC Address = +447802000332 17:09:04:326 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 17:09:04:326 [2] ModemReceiveMessages: User Data Header is present 17:09:04:326 [2] ModemReceiveMessages: Sender address len = 12 17:09:04:326 [2] ModemReceiveMessages: Sender Address = +447730611xxx 17:09:04:326 [2] ModemReceiveMessages: PID = 00 17:09:04:326 [2] ModemReceiveMessages: DCS = F5 17:09:04:326 [2] ModemReceiveMessages: Anticipated user data length = 53 17:09:04:326 [2] ModemReceiveMessages: Binary message = 0605040B8423F0E20601AE02056A0045C60C037761702E6D6F62697461737469632E636F6D000701 03574150205075736821000101 17:09:04:326 [2] ModemReceiveMessages: AT+CMGD=2 17:09:04:654 [3] ThreadProcessInboundSMS: Processing 3FDDD8A4.in... 17:09:04:654 [3] ThreadProcessInboundSMS: Processing WAP Push Message 17:09:04:654 [3] ThreadProcessInboundSMS: Content type not processed: application/vnd.wap.sic 17:09:06:529 [2] ModemReceiveMessages: OK and the corresponding SMS-IN file looks like: [SMS-IN] ModemName=Standard 19200 bps Modem Sender=+447730611xxx PhoneNumber=+447930611xxx UDH=0605040B8423F0 dcs=F5 Data=E20601AE02056A0045C60C037761702E6D6F62697461737469632E636F6D000701035741502 05075736821000101 Binary=1 The message about not supporting application/vnd.wap.sic seems unrelated, the key issue to my mind being that the phone happily reacts to SMS' but doesn't react at all to MMS notifications. That smacks of an operator misconfiguration but, on the other hand, I can send outbound MMS'. Is that a likely scenario? Cheers, Ian | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1404 Registered: 10-2002 |
Ian, It does sound like some sort of operator issue. Let me explain why I had you do the bit about the WAP push. The MMS receiving process starts with an MMS notification that arrives via WAP push in an SMS. Instead of content type "application/vnd.wap.sic", it is a content type specific to MMS. So what I wanted to do was make sure that there was not a general problem receiving these binary SMS messages. (The problem that I mentioned earlier about the Nokia 30 is that we have to use a different approach for receiving binary SMS messages on that modem. You wouldn't even see a WAP push being received in the log without an update.) It might be time to pop the SIM into a phone and verify that you can send/receive MMS using that SIM in a phone. -bn | |||
| Ian Fitchet New member Username: Idf Post Number: 10 Registered: 12-2003 |
The SIM in a phone works just fine for sending and receiving. :-( The only difference I can see between the MMSC Routing settings and the MMS Receive settings is that in the MMS Receive settings the MMS Server URL is mmsc.mms.o2.co.uk:8002/ whereas the MMSC Routing setting has http:// at the start. If I add http:// at the start of the MMS Receive settings the Gateway strips it off again next time I look at it. "Test Connection" works fine. Cheers, Ian | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1423 Registered: 10-2002 |
Ian, The MMSC setting wouldn't be an issue at this stage of things. (And we assume the "http://" part.) The problem seems to be that the MMS notification is not arriving over SMS. I'm really stumped by that. Let's try this. Using the web interface of NowSMS, try sending yourself an MMS notification message. For the URL that contains the MMS message, specify http://www.nowsms.com/download/btmms.mms Does that come back in the modem interface? | |||
| Ian Fitchet New member Username: Idf Post Number: 11 Registered: 12-2003 |
Yes. Presumably in your logs too. Naturally, I've just tried sending again from my T-mobile SIM & 3650 and no joy (15 minutes later). The same SIM & phone combo worked fine yesterday when the O2 SIM (used in the Gateway) was in a P800. That's wierd. The only thing I can think of are those SMS' when you first put a SIM in a phone (at least I see an SMS in the 3650's log -- can't remember offhand which way they go). Could it be that the operator is sending/expecting an SMS when you change a phone-SIM tuple and the MC35 isn't playing ball? Cheers, Ian | |||
| Ian Fitchet New member Username: Idf Post Number: 12 Registered: 12-2003 |
Bryce, Apologies for the delay, here's my current status: O2 SIM #1 ("Online" contract) O2 SIM #2 (standard contract bought with P800) T-mob SIM (standard contract bought with 3650) The T-mob SIM works as advertised, SMS in/out, MMS in/out. No known problems. Both O2 SIMs SMS in/out, MMS out, then we have the problem of MMS inbound. Neither will receive an inbound MMS except both will receive an inbound MMS sent from themselves. Naturally, both work perfectly in the P800 (MMS in/out). I considered that my O2 settings may be at fault (no matter how many times I've looked at them) but that they both receive inbound MMS' sent by themselves suggests the settings are OK. The smsgw.ini settings are: [SMSGW] Debug=yes Modem1=Standard 19200 bps Modem WebAuth=No WebMenu=Yes WebPort=8800 ReceiveSMS=No ReceiveMMS=No [Modem - Standard 19200 bps Modem] MMSURL=mmsc.mms.o2.co.uk:8002/ UseDial=Yes WAPGatewayIP=193.113.200.195 DialUpProfile=Modem: Standard 19200 bps Modem UseModem=Standard 19200 bps Modem APN=wap.o2.co.uk APNLogin=o2wap APNPass=password PhoneNumber=+44xxxxxxxxxx ReceiveSMS=Yes ReceiveMMS=Yes The problem appears to be that when the O2 SIMs are in the MC35T either the (externally sourced) MMS Notification isn't sent or the modem doesn't react to it. Referring to my previous post, maybe there is a registration issue but that wouldn't explain why they can send MMS' to themselves (and are allowed to send MMS' to others). Cheers, Ian | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1722 Registered: 10-2002 |
Ian, I don't think your settings are an issue. If it was a settings issue, you'd at least be seeing the SMS part of the MMS notification be received. As fate would have it, I've only tried the MC35 in the UK with Vodafone and Orange SIMs. I'll have to try scheduling some time to run tests with an O2 SIM, and see if I can figure out what type of handshake there could possibly be. -bn | |||
| Ian Fitchet New member Username: Idf Post Number: 13 Registered: 12-2003 |
As luck would have it, perhaps :-) Thanks, Bryce, I look forward to the results of your experiments. Cheers, Ian | |||
