| BUG in NowSMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 26, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Alexandre New member Username: Alexd Post Number: 18 Registered: 01-2008 |
Hello! Today i saw what NowSMS rebooting every 7 second, i stop service and start looking in Queue dir, and i found what someone sent sms with: PhoneNumber=+7122711423473512312267735123126067351231415873512317454735123302287 35123310707351233204173512353333 Have NowSMS any length check of destination address ? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1243 Registered: 08-2008 |
Hi Alexandre, I'm struggling to recreate this problem. What is the NowSMS version? What outbound SMSC connections do you have defined? The recipient string does get truncated, but it is truncated at 100 characters (like in your example above). I've tried a variety of tests, but I haven't been able to trigger a problem yet. Obviously, this sounds like a critical problem, and we need to get to the bottom of it. There just must be something different with my attempts to recreate. -- Des NowSMS Support | |||
| GSM TEST New member Username: Gsmtest Post Number: 9 Registered: 04-2006 |
I had a very similar issue. [SMS-IN] ModemName=Samsung Mobile USB Modem II 1.0 Sender=B7360000080260A5D6E93D9DB653551031860000080200005800600000005500B73600000 802A000000002 UDH=200007916163838408F6000000000B8191274793 dcs=12 Data= Binary=1 ReceivedSMSC=FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF My system did not reboot but is was very very slow since i have a "*" 2-way wild card that will launch the mailto command. By the time i caught it 30,000 emails were sent out. I was sending concatenated messages that started with the echo command. I tried to reproduce it but was not successful. | |||
| GSM TEST New member Username: Gsmtest Post Number: 10 Registered: 04-2006 |
verison 2009.07.09 Also wanted to clarify that i was directing the concatenated special character messages to Nowsms from another mobile. | |||
| Alexandre New member Username: Alexd Post Number: 19 Registered: 01-2008 |
Version is 2009.07.09 it`s full .req file: Sender=Bon-Bon ReceiptRequested=Yes Data=042304320430043604300435043C044B043500200433043E044104420438002100200420043 00434044B00200441043E043E0431044904380442044C002004120430043C002C002004470442043 E0020043E0442043A0440044B043B04300441044C0020041004320442043E04400441043A0430044 F0020043A043E043D0434043804420435 UDH=050003270301 dcs=08 Binary=1 PhoneNumber=+7122711423473512312267735123126067351231415873512317454735123302287 35123310707351233204173512353333 | |||
| Alexandre New member Username: Alexd Post Number: 20 Registered: 01-2008 |
I think maybe truble in file nime coz it very long: SAR-+712271142347351231226773512312606735123141587351231745473512330228735123310 707351233204173512353333-576e058f-3-1.req | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1247 Registered: 08-2008 |
Hi Alexandre, Thank you for the follow-up. We have successfully recreated the problem and identified the source of the problem. In order to recreate the problem, we needed to have multiple outbound SMSC connections with one or more of the connections having this phone number in a recipient pattern mask. There also needed to be at least one other message in the queue destined for a particular outbound connection. Indeed, it was related to the filename length. A fix should be available shortly. However, I'm not sure about the "GSM TEST" 2-way "mailto:" scenario. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1253 Registered: 08-2008 |
An update to fix the problem with restarts related to long messages being sent to recipients with extra long addresses can be downloaded at: http://www.nowsms.com/download/nowsms20090915.zip | |||
