SMS Queue Hangs

SMS Queue Hangs SearchSearch
Author Message
Doug Macdonell
New member
Username: Doug

Post Number: 1
Registered: 10-2014
Posted on Thursday, October 30, 2014 - 01:56 pm:   

Please could anyone help?
SMS Queue stops processing and I reboot our server to continue the processing.
I have setup alerts when the queue gets to 150 so that is how I know there is a problem
Regards Doug
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5100
Registered: 08-2008
Posted on Thursday, October 30, 2014 - 04:06 pm:   

Hi Doug,

What is your SMSC connection?

What version of NowSMS?

On the service screen, does NowSMS report a modem problem, or is the SMSC status shown as OK?

Does restarting the NowSMS service solve the issue or is a server reboot required?

I'm guessing a USB modem of some type? For some devices, if the USB driver for the device crashes, the only recourse is to either:

1.) Check the modem manufacturer web site for updated drivers.

2.) Try a different USB port, and a different computer if possible, as sometimes these devices can be sensitive to power fluctuations in a USB port.

3.) Under the Properties for the modem in NowSMS, enable the setting to reboot if the modem becomes inaccessible.


To troubleshoot further, enable the SMSDEBUG.LOG (checkbox on the "Serial #" page). When the problem reoccurs, we will want to see the SMSDEBUG.LOG from before you reboot to better understand.

--
Des
NowSMS Support
Doug Macdonell
New member
Username: Doug

Post Number: 2
Registered: 10-2014
Posted on Thursday, October 30, 2014 - 04:46 pm:   

Hi Des,
SMSC = Std 33600bps modem - serial type connected via serial/USB adapter cable
Version 2013.11.15 - however I have applied version 2014.06.30 today
No modem reported problem and all OK status
I have simply been rebooting the server - not tried restarting the gateway service.
I will attach logs the next time this happens - many thanks for prompt reply
Doug
Doug Macdonell
New member
Username: Doug

Post Number: 3
Registered: 10-2014
Posted on Thursday, November 06, 2014 - 03:06 pm:   

Hi Des,
Just to let you know, our issue didn't happen this week.
Perhaps the upgrade to V 2014.06.30 has solved the problem