MMS Receive SAR problem

MMS Receive SAR problem SearchSearch
Author Message
Christian Cerri
Unregistered guest
Posted on Thursday, February 05, 2004 - 12:12 pm:   

Hi Bryce,

I am having a problem with NowSMS v5.01 (b20040120). I have an HTTP send channel and a Siemens TC35 receive channel. MMS reception from the HTTP to the GSM works ok for single SAR. But for multiple SAR, I only get one SAR file in the 'SMS-in' dir, either ending in 1 or 2.

Here is smsdebug.log for an mms send:

06:00:39:468 [9] ThreadProcessConnection: Processing connection from 10.0.0.X...

06:00:41:500 [9] ThreadProcessConnection: Processing connection from 10.0.0.X...

06:00:41:515 [9] ThreadProcessConnection: Processing request /
06:00:41:515 [9] ParseMultipart: POST / HTTP/1.0
Host: 10.0.0.32
Referer: http://10.0.0.X/
User-Agent: ColdFusion
Content-Type: multipart/form-data; boundary=912934959696252642610044
Content-Length: 15162


PhoneNumber=+447769791539&Sender=xxx.com&MMSText=hello dude&MMSFile=18o.gif&MMSSubject=+447816142832&MMSFrom=+447816142835&ContinueURL= none&
06:00:41:515 [9] Debug: 1 recipient entries
06:00:41:515 [9] Debug: +447769791539
06:00:41:546 [9] RetrieveURL: Retrieving http://mms.xxx.com/20040205/06/401F7B8Ea.MMS
06:00:41:562 [9] RetrieveURL: Looking up mms.xxx.com
06:00:41:562 [9] RetrieveURL: Retrieving 20040205/06/401F7B8Ea.MMS
06:00:41:562 [9] RetrieveURL: GET /20040205/06/401F7B8Ea.MMS HTTP/1.0
User-Agent: Now SMS/MMS Gateway v5.01 (b20040120)
Accept: */*
Connection: Close
Host: mms.xxx.com

06:00:43:578 [9] RetrieveURL: got success response
06:00:43:578 [9] RetrieveURL: application/vnd.wap.mms-message
06:00:43:859 [6] ThreadProcessModem: Processing SAR-+447769791539-da-2-1.req...
06:00:43:875 [6] ThreadProcessModem: GET /sms.php?idnr=%2B447769791539&snr=xxx.com&data=01070B05040B8423F00003DA0201/DA06 226170706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676500AF848C82983430 314637423846008D90890F802B34343738313631343238333200962B343437383136313432383332 008A808E0238E688058103093A8083687474703A2F2F6D6D732E746578746D2E636F6D2F32303034 303230352F30 HTTP/1.0
User-Agent: Now SMS/MMS Gateway v5.01 (b20040120)
Host: XXXX
Accept: */*
Connection: Close


06:00:44:031 [6] ThreadProcessModem: HTTP/1.1 200 OK
Date: Thu, 05 Feb 2004 05:59:10 GMT
Server: Apache
X-Powered-By: PHP/4.0.6
Connection: close
Content-Type: text/html

+OK 01 message queued (dest=+447769791539).

06:00:44:031 [6] ThreadProcessModem: Processing SAR-+447769791539-da-2-2.req...
06:00:44:046 [6] ThreadProcessModem: GET /sms.php?dnr=%2B447769791539&snr=xxx.com&data=01070B05040B8423F00003DA0202/362F3 430314637423845612E4D4D5300 HTTP/1.0
User-Agent: Now SMS/MMS Gateway v5.01 (b20040120)
Host: xxxx
Accept: */*
Connection: Close


06:00:44:203 [6] ThreadProcessModem: HTTP/1.1 200 OK
Date: Thu, 05 Feb 2004 05:59:10 GMT
Server: Apache
X-Powered-By: PHP/4.0.6
Connection: close
Content-Type: text/html

+OK 01 message queued (dest=+447769791539).

06:00:56:781 [4] ModemReceiveMessages:
+CMGL: 1,0,,49
07914477581093874410D0D4329EDE748DDF6D00F5402050509571001C0B05040B8423F00003DA02 02362F3430314637423845612E4D4D5300

OK

06:00:56:781 [4] ModemReceiveMessages: Decoding received message index 1 from message storage ME
06:00:56:781 [4] ModemReceiveMessages: 07914477581093874410D0D4329EDE748DDF6D00F5402050509571001C0B05040B8423F00003DA02 02362F3430314637423845612E4D4D5300
06:00:56:781 [4] ModemReceiveMessages: SMSC address len = 7
06:00:56:781 [4] ModemReceiveMessages: SMSC Address = +447785013978
06:00:56:781 [4] ModemReceiveMessages: SMS Message Type = SMS-DELIVER
06:00:56:781 [4] ModemReceiveMessages: User Data Header is present
06:00:56:781 [4] ModemReceiveMessages: Sender address len = 16
06:00:56:781 [4] ModemReceiveMessages: D4329EDE748DDF6D
06:00:56:781 [4] ModemReceiveMessages: xxx.com
06:00:56:781 [4] ModemReceiveMessages: Sender Address = TextM.com
06:00:56:781 [4] ModemReceiveMessages: PID = 00
06:00:56:781 [4] ModemReceiveMessages: DCS = F5
06:00:56:781 [4] ModemReceiveMessages: Anticipated user data length = 28
06:00:56:781 [4] ModemReceiveMessages: Binary message = 0B05040B8423F00003DA0202362F3430314637423845612E4D4D5300
06:00:56:781 [4] ModemReceiveMessages: AT+CMGD=1

06:00:56:859 [7] ThreadProcessInboundSMS: Processing 401F7B90.in...
06:00:56:859 [7] ThreadProcessInboundSMS: SAR Segment Reference = DA, Count = 2, Current = 2
06:00:57:218 [4] ModemReceiveMessages:
OK

Sorry I have blanked sensitive info.

Any ideas? I saw on one support page that there were issues with segmentation in sending?

Thanks in advance,

Christian
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1859
Registered: 10-2002
Posted on Thursday, February 12, 2004 - 05:57 am:   

Hi Christian,

Apologies again for the delay.

The problem with segmentation in sending that was mentioned in another thread was that if you had multiple SMSCs defined, one segment might be sent via one SMSC, and one segment through another. This was mainly a problem with GSM modems as the SMSC, because the receiving end, when reassembling, looks at the sender address, and the segment reference number in order to reassemble. With GSM modems, the sender address could be different for the different segments, which is a definite problem. (And we have since addressed that.)

Anyway, I don't think that is at all related to the problem that you are seeing.

It appears that your modem is simply not receiving all SMS messages.

What if you fire off 20 regular text messages to the modem in rapid succession ... does it receive them all?

Assuming it does ... how about this ...

Instead of connecting the modem to NowSMS, connect it to HyperTerminal. (Send an ATZ command out, and make sure that you get an OK back to know that you're talking to the modem.)

Issue the following commands:

AT+CSMS=0
AT+CMGF=0

Send an MMS to the modem, and wait a bit.

Issue the command AT+CMGL=0 ... do you now see one message or two? (+CMGL: header appears once for each message)

-bn