Strange happenings on incoming SMS

Strange happenings on incoming SMS SearchSearch
Author Message
Anonymous
 
Posted on Thursday, February 12, 2004 - 02:54 pm:   

Hi,

Im using a Nokia 30 Modem to receive SMS via NowSMS. Every now and then the Data section in the SMS file has been cut short. Heres an example:

[SMS-IN]
ModemName=Nokia 30 (Cable)
Sender=+44xxxxxxx
PhoneNumber=xxxxxx
Data=this is a message that is very long indeed this is a message that is very long indeed this is a message that is veB
Binary=0

The same message was sent 5 mins later and was received correctly:

[SMS-IN]
ModemName=Nokia 30 (Cable)
Sender=+44xxxxx
PhoneNumber=xxxxxxxxx
Data=this is a message that is very long indeed this is a message that is very long indeed this is a message that is very long indeed this is a message that is very
Binary=0

Is there some known issues with NowSMS that may be causing this?

Thanks in advance


Mark Little
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1872
Registered: 10-2002
Posted on Thursday, February 12, 2004 - 03:18 pm:   

Mark,

That's a new one by me.

If this happens with somewhat regular frequency, I'd suggest enabling the debug log. (Manually edit SMSGW.INI, and under the [SMSGW] section header, add Debug=Yes. Then restart the SMS service.)

Then we can look at the SMSDEBUG.LOG, and see what is coming in with the modem.

I do recall a bizarre problem, maybe a year ago, where someone was occasionally getting completely corrupt messages. In that case, it turned out to be the modem cable dropping bytes, and the cable had to be replaced.

Let's get a look at the SMSDEBUG.LOG when this happens, and we should be able to give better insight with that information.

-bn
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1929
Registered: 10-2002
Posted on Saturday, February 21, 2004 - 01:07 am:   

Just a follow-up ... we had someone else posting almost exactly the same problem on another thread:

http://support.nowsms.com/discus/messages/1/2832.html

Their problem turned out to be either a problem with the modem or the cable.