| Unable to Dispatch SMS - Beta Version |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through December 09, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Steven Quek |
I submited the message but does not see the GW dispatching the SMS. Please help ... 16:31:11:567 [0] main: Now SMS/MMS Gateway Web server started on port number 8800 16:31:13:640 [0] main: 31 Days remaining in trial version 16:31:13:740 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:31:13:740 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:31:13:740 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:31:13:740 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:31:13:740 [2] ThreadProcessModem: After ModemRelease - COM3: 16:31:33:739 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:31:33:739 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:31:33:739 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:31:33:739 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:31:33:739 [2] ThreadProcessModem: After ModemRelease - COM3: 16:32:13:766 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:32:13:766 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:32:13:766 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:32:13:766 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:32:13:766 [2] ThreadProcessModem: After ModemRelease - COM3: 16:33:00:363 [5] ThreadProcessConnection: Processing connection from 10.92.28.100... 16:33:00:363 [5] ThreadProcessConnection: Processing request /?WAPURL=http%3A%2F%2Fwww%2Ee%2Dbizsupport%2Ecom%2Fmobileportal%2FMobileDL%2Easp %3FMobile%3D94882260%26RequestType%3DGame%26ItemID%3D1&PhoneNumber=94882260&Send er=8811&Text=MobilePortal(10001)&ContinueURL=http%3A%2F%2F127%2E0%2E0%2E1%5CMobi lePortal%2FReqGame2DL%5FOK%2Easp 16:33:00:363 [5] Debug: 1 recipient entries 16:33:00:363 [5] Debug: 94882260 16:35:13:895 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:35:13:895 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:35:13:895 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:35:13:895 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:35:13:895 [2] ThreadProcessModem: After ModemRelease - COM3: 16:39:13:149 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:39:13:149 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:39:13:149 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:39:13:149 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:39:13:149 [2] ThreadProcessModem: After ModemRelease - COM3: | |||
| Bryce Norwood - NowSMS Support |
Hi Steven, I need more information about your configuration. Could you post the content of the SMSGW.INI file? Is there a file sitting in your "Q" directory that appears to have been created around the same time as your message submission to the gateway? My best guess is that there is an issue related to the "Routing" "Properties" for the SMSC defined as "COM3". I suspect that "Support any outbound message traffic" is not checked. -bn | |||
| Steven Quek |
[SMSGW] WebAuth=No WebMenu=Yes WebPort=8800 Modem1=COM3: Debug=1 The "Support any outbound message traffic" is checked. May i ask, 16:35:13:895 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:35:13:895 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:35:13:895 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:35:13:895 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:35:13:895 [2] ThreadProcessModem: After ModemRelease - COM3: 16:39:13:149 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:39:13:149 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:39:13:149 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:39:13:149 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:39:13:149 [2] ThreadProcessModem: After ModemRelease - COM3: What does the abovementioned means ? i am using a COM to USB converter does this causes any problem ? | |||
| Bryce Norwood - NowSMS Support |
Steven, I'm sorry. I got tied up in some other issues, and I was away from the discussion board for a few days. It looks to me like an error condition is occurring, but it is not getting written to the log file. Doing some more investigation, it looks like the only way that this would occur is if Windows refused to allow the gateway to open COM3. Like perhaps another application has grabbed the port ... and the operating system will only allow one application to have a port open at a time. Stop the service. Go back into the configuration program, highlight the COM3 entry on the "SMSC" page, and press "Test". Does this return an error? Go to Programs/Accessories/Communications, and load Windows Hyperterminal. Can it open COM3: successfully? | |||
| Steven |
I can open the COM3 via hyperterminal. Do u suspect USB 2 Serial having problem. OK, i just need some confirmation that the Demo version does not have any restriction except the msg/minute and i will setup the server for DEMO using Serial interface. | |||
| Bryce Norwood - NowSMS Support |
Right, the only restriction on the trial version is limits on the number of messages per minute (30). Maybe there is some issue that is USB specific, but I actually use a USB cable to connect my phone to my PC for use with NowSMS. From the NowSMS config program, does it "Test" the modem ok? | |||
| Steven |
The "test" is OK. Based on the debug log, what does the following meant ? 16:35:13:895 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:35:13:895 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:35:13:895 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:35:13:895 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:35:13:895 [2] ThreadProcessModem: After ModemRelease - COM3: 16:39:13:149 [2] ThreadProcessModem: Before ModemAllocate - COM3: 16:39:13:149 [2] ThreadProcessModem: After ModemAllocate - COM3: - OK 16:39:13:149 [2] ThreadProcessModem: Re-initializing modem: COM3: ... 16:39:13:149 [2] ThreadProcessModem: Before ModemRelease - COM3: 16:39:13:149 [2] ThreadProcessModem: After ModemRelease - COM3: Beside logging to window events, can its log into a file when its having problem with the modem ? When will be the beta version into production ? One suggestion, its will be nice u gateway able to process files in the directory example with certain format : example : In the queue directory we can dump file : xxxxxx.que (Inside the file consists of some define parameters) Upon completion, its will rename as xxxxx.done . In these way its able 3rd application can interface easy with u application. | |||
| Bryce Norwood - NowSMS Support |
Steven, What that sequence means is that the gateway is trying to re-initialise the modem over and over again. Normally I would expect to see an error message that would indicate why it is trying to re-initialise the modem. That's why I did some investigation, and I found that if the modem port was in use by another application, an error message is not properly logged. Let's try this. Based upon the fact that we found some error messages that were not properly logged, we updated SMSGWS.EXE to log the error messages. I've uploaded a ZIP at http://www.nowsms.com/download/steven.zip with an updated SMSGWS.EXE. Try that and let's see if the log text changes. A file API could be interesting. Right now, we do internally use a similar type of interface, but we expect the actual file in the Q to be pre-formatted, so it is awkward to interface to it directly with anything but very simple messages. We expect the v5.0 version to be released this coming week. | |||
| Steven |
Thanks. I downloaded and will try. Can we have some information of Q, these could be very helpful to 3rd party. There few SMS GW does that. | |||
| Bryce Norwood - NowSMS Support |
Steven, Probably the best thing to do is to submit some messages and let them queue up (turn the modem off or disconnect it ... or actually it sounds like its not working so well at present ... so this should not be a problem). Look at the files in the Q directory, and you'll see that they are a simple INI file format. The only catch is that they are pre-formatted. So for example, if the gateway determines that the message text requires Unicode, the Unicode encoding is performed before the message is written to the queue and the message is in binary format. If the gateway determines that a message requires encoding as a long message, it converts the message to binary format and submits multiple messages. It would probably be more helpful to interact with this type of Q if this type of formatting was done after a message is q'd instead of before. | |||
