| SMS-in |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 14, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| alex New member Username: Alexc Post Number: 2 Registered: 08-2010 |
We have just downloaded the trial version of SMS now and had a few questions. We are connected via a GPRS modem with T-Mobile. 1. How are the .SMS files given their names? For instance 4C6C2E9D.SMS Thanks in advance. 2. Is there a key to decipher the naming convention? 3 I noticed that there is no time stamp in the inbound sms, is there a way to include this in the file or must we reference the SMSIN.log? 4.Is there any other network information that can be captured in the .sms file or the log? Like the senders SMSC, I know there ae many steps between sending an SMS and then receiving one, I am surprised there isn't more routing information in the .SMS or the log. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2445 Registered: 08-2008 |
Hi Alex, Apologies for the delay in reply. 1 & 2. There is no significance to the name, the names are randomly generated. If you are processing received messages via the file based interface, you would scan for *.SMS to find messages to process. (When messages are received, they are initially stored with a .IN extension. However, if it is a multipart message, NowSMS may need to recombine the message parts before renaming to .SMS extension.) 3. That's a good point. We probably should add a timestamp to the file. Our assumption is that people are going to use the 2-way command interface instead of the file-based interface. The 2-way command interface extracts the timestamp from the creation date/time of the file (@@MSGDATE@@ & @@MSGTIME@@). 4. There's not that much information available. SMS is pretty primitive. In fact, the SMSC from which the message was received is an attribute that is only available when using modems ... it is not available in other interfaces. -- Des NowSMS Support | |||
| alex New member Username: Alexc Post Number: 3 Registered: 08-2010 |
Hi Des- Thanks for the reply. A stupid question: When you say "Our assumption is that people are going to use the 2-way command interface instead of the file-based interface." Do you mean using an API to connect to NowSMS? Or is there another method? If there is ever a vote I say add the timestamp to the .sms file. Regards, Alex | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2449 Registered: 08-2008 |
Hi Alex, Normally the way that people interface with NowSMS to process received SMS messages is the 2-way command facility. That facility spawns an executable or issues an HTTP request for every received message. These links explain it in more detail: http://www.nowsms.com/documentation/ProductDocumentation/2_way_sms_support.htm http://support.nowsms.com/discus/messages/1/4520.html Although not mentioned on those pages (the manual PDF is more up-to-date than the web site), there are @@MSGDATE@@ and @@MSGTIME@@ parameters that can be passed in the command line or URL. (The logic in NowSMS determines these values from the file creation date/time stamp.) For direct file processing, I do agree that it would be helpful if we added a field. I will put in an enhancement request. However, in the meantime, I would recommend using the Windows API GetFileTime if you are accessing the file directly. Or, use the replaceable command line or URL parameters for the 2-way command interface. -- Des NowSMS Support | |||
| alex New member Username: Alexc Post Number: 4 Registered: 08-2010 |
Thanks Des, I will go through the manual this weekend. One last thing, do you think that a SMPP will have more routing information in their SMS's than a what we get from our modem? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2452 Registered: 08-2008 |
Hi Alex, No, SMPP doesn't have any additional routing information. -- Des NowSMS Support | |||
