SMS Server Tools 3
This site is hosted by Kekekasvi.com
 Menu
Basic information:
Additional information:
Support:
Get SMS Server Tools 3:
Additional Options

 Sponsored links

 Search
Custom Search

 Visitor locations
 
 SMS Server Tools 3 Community
Welcome, Guest. Please login or register. Sun May 19, 2024 20:04
SMSTools3 Community » Help and support Bottom

[solved] "No Destination" in log?

  This topic is locked

Page:  1

Author Post
Member
Registered:
Jul 2009
Location: Paris, France
Hi All,

Apologies if this is answered elsewhere, but a quick search didn't reveal anything directly relevant.

Having installed smstools, it works great, and I'm very happy with it. However, I have encountered an issue when trying to create outgoing SMS messages using either an in-house script or even simply with a text file.

If I create the message using the included 'sendsms' it works fine.
If I copy/modify one of the included examples, it works fine.

If I (programmatically, or using just a text file) create a new SMS file from scratch and place it in the outgoing spool, the server reports:

smsd: No destination in file /var/spool/sms/outgoing/<filename>

However, the format of the file is exactly as described in the documentation, and even creating (manually) an exact copy of one of the examples (and comparing with 'diff' to be sure it's exactly the same), it still fails with this error.

Example format of output file (excluding the '-----' lines)
-------------------------------------
To: 336XXXXXXXX
Flash: yes

This is a test message.
-------------------------------------

Am I missing something obvious?

Thanks in advance

Leland

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
Very strange... :o

Can you show what hexdump -C < filename says?

Member
Registered:
Jul 2009
Location: Paris, France
Topic owner
keke wrote
Very strange... :o

Can you show what hexdump -C < filename says?

(obfuscating the actual destination telephone number)



Looks okay to me .. hmm..

Administrator
Registered:
May 2009
Location: Jyväskylä, Finland
There was no any other messages in the log?

Is you hexdump surely from the failed file? The dump is ok and should work.

When you create a file, what are the permissions?

And you are not using any checkhandler which modifies message headers?

You could mkdir /var/spool/sms/failed and define failed = /var/spool/sms/failed in the smsd.conf, then restart smsd and try once more. Show the hexdump of unaltered failed message, use private tag to protect it.

Member
Registered:
Jul 2009
Location: Paris, France
Topic owner
Think I found the problem...

The daemon was slurping from the spool directory before the file was completely released during creation...

Writing to a temporary file elsewhere first, and then moving the temp file into the spool seems to have resolved the issue.

Will do some more tests and let you know to be sure.

Thanks,

Leland

  This topic is locked

Page:  1

SMSTools3 Community » Help and support Top

 
Time in this board is UTC.  

Privacy Policy   SMS Server Tools 3 Copyright © Keijo Kasvi.