| Incoming MMS looks weird |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
I dont know if we have discussed the problem before. I have a Siemens MC35 GPRS modem. A grps/mms enabled simcard. When i send a mms to the modem, it leaves the message in the SMS-IN folder and calls it; 3F016D13.in The data in this file is this; [SMS-IN] Sender=55555 UDH=0605040B8423F0 pid=39 dcs=F5 Binary=1 Data=EA06226170706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676500AF848 C8298507746745373436F385849414148526F41414141417741414E4F494141414141008D9189178 02B343536313330343035302F545950453D504C4D4E0096736B6F76008A808E025AF18805810303F 47F83687474703A2F2F3139322E3136382E3234312E3131343A383030322F507746745373436F385 849414148526F41414141417741414E4F49414141414100 of which i dont undestand a thing. Is it because the modem tries to download the file via http and the mmsc-server is firewalled ? Or is it the modem itself that is wrongly configured? | |||
| Anonymous |
his is the smsdebug.log data: 13:11:49:580 [2] TestModemSpeed: Initialised modem at 57600 bps 13:11:50:090 [2] ThreadProcessModem: AT+CPMS? 13:11:50:251 [2] ThreadProcessModem: +CPMS: "MT",2,60,"MT",2,60,"MT",2,60 OK 13:11:50:251 [2] ThreadProcessModem: Modem initialization complete: COM1: 13:14:25:834 [2] ModemReceiveMessages: +CMGL: 3,0,,156 069154049390994005855555F539F5307010314164408C0B05040B8423F00003F10201EA06226170 706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676500AF848C82985077467453 73436F385849414148526F41414141417741414E4F494141414141008D918917802B343536313330 343035302F545950453D504C4D4E0096736B6F76008A808E025AF18805810303F47F83687474703A 2F2F31 OK 13:14:25:834 [2] ModemReceiveMessages: Decoding received message index 3 from message storage ME 13:14:25:834 [2] ModemReceiveMessages: SMSC address len = 6 13:14:25:834 [2] ModemReceiveMessages: SMSC Address = +4540390999 13:14:25:834 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 13:14:25:834 [2] ModemReceiveMessages: User Data Header is present 13:14:25:834 [2] ModemReceiveMessages: Sender address len = 5 13:14:25:834 [2] ModemReceiveMessages: Sender Address = 55555 13:14:25:834 [2] ModemReceiveMessages: PID = 39 13:14:25:834 [2] ModemReceiveMessages: DCS = F5 13:14:25:834 [2] ModemReceiveMessages: Anticipated user data length = 140 13:14:25:834 [2] ModemReceiveMessages: Binary message = 0B05040B8423F00003F10201EA06226170706C69636174696F6E2F766E642E7761702E6D6D732D6D 65737361676500AF848C8298507746745373436F385849414148526F41414141417741414E4F4941 41414141008D918917802B343536313330343035302F545950453D504C4D4E0096736B6F76008A80 8E025AF18805810303F47F83687474703A2F2F31 13:14:25:834 [2] ModemReceiveMessages: AT+CMGD=3 13:14:26:045 [3] ThreadProcessInboundSMS: Processing 3F016D11.in... 13:14:26:045 [3] ThreadProcessInboundSMS: SAR Segment Reference = F1, Count = 2, Current = 1 13:14:29:199 [2] ModemReceiveMessages: OK 13:14:31:913 [2] ModemReceiveMessages: +CMGL: 4,0,,81 069154049390994405855555F539F530701031417440410B05040B8423F00003F1020239322E3136 382E3234312E3131343A383030322F507746745373436F385849414148526F41414141417741414E 4F49414141414100 OK 13:14:31:913 [2] ModemReceiveMessages: Decoding received message index 4 from message storage ME 13:14:31:913 [2] ModemReceiveMessages: SMSC address len = 6 13:14:31:913 [2] ModemReceiveMessages: SMSC Address = +4540390999 13:14:31:913 [2] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 13:14:31:913 [2] ModemReceiveMessages: User Data Header is present 13:14:31:913 [2] ModemReceiveMessages: Sender address len = 5 13:14:31:913 [2] ModemReceiveMessages: Sender Address = 55555 13:14:31:913 [2] ModemReceiveMessages: PID = 39 13:14:31:913 [2] ModemReceiveMessages: DCS = F5 13:14:31:913 [2] ModemReceiveMessages: Anticipated user data length = 65 13:14:31:913 [2] ModemReceiveMessages: Binary message = 0B05040B8423F00003F1020239322E3136382E3234312E3131343A383030322F507746745373436F 385849414148526F41414141417741414E4F49414141414100 13:14:31:913 [2] ModemReceiveMessages: AT+CMGD=4 13:14:32:063 [3] ThreadProcessInboundSMS: Processing 3F016D12.in... 13:14:32:063 [3] ThreadProcessInboundSMS: SAR Segment Reference = F1, Count = 2, Current = 2 13:14:33:075 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:14:33:075 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:14:33:075 [3] ThreadProcessInboundSMS: Processing MMS message 13:14:33:075 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:14:33:075 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:14:34:357 [2] ModemReceiveMessages: OK 13:14:55:086 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:14:55:086 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:14:55:096 [3] ThreadProcessInboundSMS: Processing MMS message 13:14:55:096 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:14:55:096 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:15:17:188 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:15:17:308 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:15:17:308 [3] ThreadProcessInboundSMS: Processing MMS message 13:15:17:308 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:15:17:308 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:15:39:320 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:15:39:320 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:15:39:320 [3] ThreadProcessInboundSMS: Processing MMS message 13:15:39:320 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:15:39:320 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:16:01:282 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:16:01:282 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:16:01:292 [3] ThreadProcessInboundSMS: Processing MMS message 13:16:01:292 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:16:01:292 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:16:23:253 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:16:23:253 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:16:23:253 [3] ThreadProcessInboundSMS: Processing MMS message 13:16:23:253 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:16:23:253 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:16:45:225 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:16:45:225 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:16:45:225 [3] ThreadProcessInboundSMS: Processing MMS message 13:16:45:225 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:16:45:225 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:17:07:196 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:17:07:196 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:17:07:196 [3] ThreadProcessInboundSMS: Processing MMS message 13:17:07:196 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:17:07:196 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:17:29:168 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:17:29:168 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:17:29:168 [3] ThreadProcessInboundSMS: Processing MMS message 13:17:29:168 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:17:29:168 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:17:51:140 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:17:51:140 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:17:51:140 [3] ThreadProcessInboundSMS: Processing MMS message 13:17:51:140 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:17:51:140 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:18:13:111 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:18:13:111 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:18:13:111 [3] ThreadProcessInboundSMS: Processing MMS message 13:18:13:111 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:18:13:111 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:18:35:073 [3] ThreadProcessInboundSMS: Processing 3F016D13.in... 13:18:35:073 [3] ThreadProcessInboundSMS: Processing WAP Push Message 13:18:35:073 [3] ThreadProcessInboundSMS: Processing MMS message 13:18:35:073 [3] ThreadProcessInboundSMS: MMS Content-location: http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA 13:18:35:073 [3] RetrieveURL: Retrieving http://192.168.241.114:8002/PwFtSsCo8XIAAHRoAAAAAwAANOIAAAAA | |||
| Bryce Norwood - NowSMS Support |
Hi, It's because the MMSC is firewalled. Actually, the MMSC is configured on a private IP address which is not accessible via the internet. Basically, anything on a "192.168" range, or a "10." range is a good indication that it is a private IP address. In the v5.0 release, in addition to adding the ability to configure things so that these messages can be retrieved over WAP via a GPRS modem ... we're changing the process of how we store the received messages that are awaiting MMS download so that you won't have to dig through the smsdebug.log to see what is going on. -bn | |||
