SAR Problems

SAR Problems SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through February 02, 2006 » SAR Problems « Previous || Next »
Author Message
Anonymous
 
Posted on Wednesday, October 19, 2005 - 06:57 am:   

Everyday, my NowSMS installation encounters SAR files left in my Windows folder being processed incompletely.
application/octet-streamSAR_1
+1602xxxxxxx-3A-2-1.SAR (0.4 k)
application/octet-streamSAR_2
+1602xxxxxxx-3D-2-2.SAR (0.4 k)


My question is, how do I solve this so that I don't miss any files that need to be sent to my customer. My program is checking for .SMS files every 3 seconds so if these files remain with .SAR extension, my customer complains that their msg was not sent. For customer's privacy, cellnumber has been changed to xxx.

Question #2: Are picture msgs being represented as SAR files? How do I know if the file is a picture msg? Right now, I only processes SMS msgs. How do I begin processing picture msgs?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5151
Registered: 10-2002
Posted on Wednesday, October 19, 2005 - 02:22 pm:   

Hi,

These messages are not being received completely. In each case, the modem is only delivering one part of the message to NowSMS. So we are waiting for the other parts to arrive.

The naming convention that we use on the "SAR" file tells us some details about it.

+1602xxxxxxx-3A-2-1.SAR indicates that this is a message received from +1602xxxxxxx, it has a SAR reference (assigned by the sender) of 3A, it is a 2 part message, and this is part 1.

The problem in this case is that we never receive part 2.

And in the other example, we never received part 1 of SAR reference 3D from the sender.

However, I'm wondering if there is more to this.

In both of your examples, the received message indicates "dcs=3" and "pid=3B". Those are very unusual values.

dcs=3 indicates that it is a class 3 message which is terminal specific. And pid=3B indicates a value that is SMSC specific.

This is telling me that the message is probably not being interpreted correctly.

Is your customer sending these messages from a mobile phone, or are they using some software to generate these messages?

I'm suspecting that maybe there is a problem with that modem, or at least something very unusual.

A couple of things to try:

1.) Under "Properties" for the modem in the "SMSC" list, try changing "SMS Message Storage" to "Direct to Modem". (This might make a difference if the modem is somehow corrupting the message when it stores it, and we might avoid such corruption with this setting.)

2.) Send a long text message to the modem yourself. Is it received correctly? If not, then enable the SMSDEBUG.LOG in NowSMS, and let's take a look at what comes in when you send a long message. Let me know what the text is of the long message that you sent, and then show me the details of the message being received in the SMSDEBUG.LOG. That way, we can try to determine what is going on. If it is a modem bug, we might be able to put in a setting to work-around it if we can understand the problem. Or if it is a message attribute that we are not parsing correctly, we can try to fix it.

On the second question, this doesn't look like a picture message. I'd expect different UDH from a picture message. If you want to have a 2-way script receiving binary messages (so that you might reply back and indicate that a message was received that you do not understand), see the following thread: http://support.nowsms.com/discus/messages/485/624.html
Anonymous
 
Posted on Thursday, October 20, 2005 - 02:19 am:   

Hello,

This is exactly the problem: Part of the messages that is supposed to be received doesn't go through. The part 1 or part 2 of the attached files didn't arrive as I wrote this email.

Is your customer sending these messages from a mobile phone, or are they using some software to generate these messages? --Yes they are sending messages from a mobile phone (Cingular, T-Mobile, Verizon, etc, even local carriers)

My NowSMS is configured to store SMS msgs "Direct to Modem" ever since.

I have customers who are sending long SMS (300-500 chars) and there's no problem.

My question thus is, how do I fix these incomplete SAR files. I'm using SonyEricsson GC79 PC Card under T-Mobile USA. Is there a particular problem with this modem, or is there something that NowSMS is failing to do?

Your response will be highly appreciated.

Thanks.
Anonymous
 
Posted on Tuesday, October 25, 2005 - 01:54 am:   

Bryce,

I need your input re this problem.

Thanks,

NowSMS Customer
SN: 00002604, 2605
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5178
Registered: 10-2002
Posted on Tuesday, October 25, 2005 - 01:56 pm:   

That's the problem. I don't know how to fix your problem.

If the messages are not actually being received by the modem, there is no way for us to guess what the rest of the message contains.

My suggestions would be:

1.) Try setting "SMS Access" to "GPRS", and see if that makes a difference. I'm wondering if maybe the modem is receiving too many messages and that is causing it to lose messages. If that is the case, this "GPRS" setting might make a difference because it should enable the modem to receive messages faster. (As long as T-Mobile supports SMS over GPRS, which I understand that it does in most areas of the USA.)

2.) Try different settings for "SMS Message Storage", and see if another setting is more reliable with that modem.

3.) Try a different modem. Sierra Wireless Aircard for the PC card format, and Multitech as an external would be my suggestions for the US.


-bn

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