Verify the modem connection status

Verify the modem connection status SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through June 24, 2009 » Verify the modem connection status « Previous || Next »
Author Message
yzhou
New member
Username: Zy_sakura

Post Number: 9
Registered: 02-2009
Posted on Thursday, June 04, 2009 - 09:49 am:   

Hi,sorry to bother you again.
I meet some problems while doing the test with NowSMS, I want to verify the modem connection status all the time in our website, which is the interface connceted to NowSMS for sending messages.I searched the relative information, and the member here seems to have the same question http://support.nowsms.com/discus/messages/1/8390.html

In our case, we don't use the bluetooth, but the serial to ethernet software which create some vitual ports to connect the equipements distant,that might cause some problems if the connection is not stable. (This software can't provide any api neither...)

I'm wandering is it possible to get the API nowadays or any other solutions we can check the modems connection status such as the option (SMSC- Test) in the client side? Coz we try to not display the Log file which might contain too much informations on our website.

Thank you so much!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 898
Registered: 08-2008
Posted on Thursday, June 04, 2009 - 04:47 pm:   

Hi,

One of the problem with having several years worth of messages here is that some things that were not possible in the past with older versions of NowSMS are possible now with newer versions.

There is an XML/HTTP based query interface for this information.

Enable the "Web Account Administration" on the "Web" page of the NowSMS configuration dialog, and assign an account name and password.

Connect to the NowSMS server with the following URL:

http://127.0.0.1:8800/admin/xmlstatus?user=adminuser&password=adminpass

Substitute in your appropriate IP address and port ... and the appropriate "adminuser" and "adminpass" values.

The XML formatted information is quite readable, so to get started you might want to make the request via a web browser to see what information is returned.

For more details on the XML format, see the following:

http://support.nowsms.com/discus/messages/1/23704.html

The example in the thread above only shows SMPP SMSC connections, but the <SMSCStatus> response also includes modems and current status information regarding the modem connection.

--
Des
NowSMS Support
yzhou
New member
Username: Zy_sakura

Post Number: 10
Registered: 02-2009
Posted on Friday, June 05, 2009 - 09:02 am:   

Thank you Des, I try the method this morning, output it on our site, the informations are clear,but unfortunately, when i Unplug the mobile, all the informations seem to have nothing changed. Even when i try to use this mobile to send messages which blocked in the queue,all the status keep "OK"
yzhou
New member
Username: Zy_sakura

Post Number: 11
Registered: 02-2009
Posted on Friday, June 05, 2009 - 12:29 pm:   

I think the problem is the NowSMS tries several times to make sure that the modem is reliable or not. Is there any configuration can reduice this period? To get the output as "XXX Mobile USB WMC Modem,Modem Failure -- Unable to access modem, ensure that it is powered on and passes diagnostic tests." as soon as possible.

I find some comments about SMSGW.INI configurations. Something like
RetryDelay=
RetryDelayMultiplier=
RetryDelayAfterAttempts=
RetryDelayMax=
I'm wondering is it for this usage? Thank you!
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 905
Registered: 08-2008
Posted on Friday, June 05, 2009 - 05:36 pm:   

Occasional modem blips are normal ... so we do perform some retries before reporting an error ... and we perform a variety of attempts to recover a "hung" modem.

However, I agree ... currently the time delay is far too long.

It appears that the logic to try to recover a "hung" modem takes too long when there is no device connected.

I'm going to have to take this back to our engineering team. Obviously if there is a modem that is "hung", we want to take steps to try to recover it. But it shouldn't take 10 to 15 minutes to do this. I'm thinking that it should take no more than 2 to 3 minutes. Do you agree that 2 to 3 minutes would be acceptable?

--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics