| SMS Not Send Out |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 03, 2020 ⬆ |
◄ ► |
| Author | Message | |||
| gensupport New member Username: Gensupport Post Number: 17 Registered: 12-2017 |
Hi Support, May I know what the meaning of below error? Found in smsdebug log. I try to test send sms after add modem connection but it stuck in queue and did not send out. FindNowSMSModemInAddressRange: 0.0.0.0 - DISCOVER_NOWSMSMODEM_RESPONSE=xxxx:8990 | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5945 Registered: 08-2008 |
That is not an error. It is debug information about locating an Android modem over WiFi...if it actually says 0.0.0.0, that is a problem, but otherwise this is normal. What does SMSOUT-yyyymmdd.LOG report? Is there only one modem connected? | |||
| gensupport New member Username: Gensupport Post Number: 18 Registered: 12-2017 |
There is no record in SMSOUT.log since the sms still in queue. We already connected with 9 modems (can send sms), then we upgrade to 14 modems. The debug log that I provided before when I want test send sms after add the modem connection. From android phone can see the status is Connected. But when I want send test sms it stuck in queue. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5946 Registered: 08-2008 |
There would be an entry in the SMSOUT log if the server could not see the modem. Also, if there was an attempt that failed. I would need to see a more complete SMSDEBUG.LOG to diagnose. The entry you mentioned before is normal. My best guess would be that there is a restriction on the connection in the routing section of the modem definition. I would suggest sending SMSDEBUG.LOG and SMSGW.INI to me via email. Send to nowsms@nowsms.com. In the subject line, include Attention: Des. Post a short reply here so I know to look for the message. -- Des NowSMS Support | |||
| gensupport New member Username: Gensupport Post Number: 19 Registered: 12-2017 |
Hi Des, Issue has been solved after I restart the service in nowsms software. Thanks for you help. | |||
