Modem Failure -- Error waiting for SMS initialization response from...

Modem Failure -- Error waiting for SMS initialization response from... SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through May 19, 2016 » Modem Failure -- Error waiting for SMS initialization response from modem « Previous || Next »
Author Message
Ansar V M
New member
Username: Ansarvm

Post Number: 15
Registered: 06-2014
Posted on Wednesday, November 25, 2015 - 11:18 am:   

Hi Des,

Is it possible to configure nowssms in a virtual machine residing in VMware ESxi host?

What i did is

I have installed nowsms software in a virtual machine which is running on VMware Esxi 5.5 host and enabled USB controller in it, then connected the wavecom fastrack modem in one of the USB port of ESXi Server, which is accessible through the VM.

In the VM i have installed the modem driver. Issue is that, when i am configuring nowsms gateway i can able to configure the modem connection but after apply ok, i am getting error saying "Modem Failure -- Error waiting for SMS initialization response from modem" . Attaching the log file.

Strange thing is that two messages i was able to send successfully, after that this error is coming. Could you please help.
application/octet-stream
SMSOUT-20151125.LOG (4.6 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5513
Registered: 08-2008
Posted on Wednesday, November 25, 2015 - 04:06 pm:   

Hi Ansar,

Those errors suggest the USB virtualization is not working well. Very frequently NowSMS is simply not seeing any response from the modem.

VMware installations are generally not a problem, but when there are problems with USB, they are very difficult to troubleshoot.

Here are some suggestions:

1. If possible, use an Android device as a modem over WiFi instead. The VM itself does not need to be on WiFi, it just needs to be accessible on the same IP network.

2. For the USB modem, install a Windows modem driver to associate with the COM port. “Standard 33600 bps Modem” is the driver recommended for Wavecom modems.

Once this modem driver is installed, go into the Windows Control Panel, and select the “Modems” or “Phone and Modem Options” applet. In the diagnostics section, ensure that you are able to use “Query Modem” to interface with your modem, which will ensure that Windows is able to properly communicate with the modem.

Configure NowSMS to use this driver instead of the COM port.

VM environments add a lot of extra drivers to Windows, so going through a Windows modem driver instead of direct to COM port helps the VM better support the device as a modem.

3. Use NowSMS 2015.06.24 or later. http://www.nowsms.com/download-free-trial

4. Assuming you are using NowSMS 2015.06.24 or later, try editing SMSGW.INI, and add AltModemTimeouts=Yes to [SMSGW] section of SMSGW.INI. Restart the SMS service after adding this setting. If this setting does not improve the situation, remove it, as it is not recommended except for special circumstances.


--
Des
NowSMS Support
Ansar V M
New member
Username: Ansarvm

Post Number: 16
Registered: 06-2014
Posted on Thursday, November 26, 2015 - 11:16 am:   

Hi Des,

I have tried to install the Standard 33600 bps Modem in VM, but getting an error saying This device cannot start code 10.

Then i tried in a physical machine and installed the Standard 33600 bps modem driver, but when i open control panel it shows the modem not functioning properly.

Do you have any doc to refer the installation.

Regards
Ansar
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5517
Registered: 08-2008
Posted on Thursday, November 26, 2015 - 04:36 pm:   

Hi Ansar,

If Windows is having problems talking to the modem, then I would not expect NowSMS to be able to communicate with the modem, as NowSMS works through Windows.

As Wavecom is part of Sierra Wireless, I would suggest going there for updated drivers and documentation.

Most Fastrack modems do not natively support USB, but use a USB to serial cable from a 3rd party manufacturer. Drivers for some of those cables are unreliable. The Prolific chipset is a notable problem, but at least that manufacturer has updates. Refer to the 3rd to last message in one of our previous discussions where it was apparent you were using a USB cable with this chipset: http://support.nowsms.com/discus/messages/1/72456.html

The device cannot start message is most likely an issue with this device driver.

Other suggestions:

Stop the NowSMS services when running any modem tests in Windows to make sure there is no conflict.

Make sure that the Windows modem driver is associated with the correct port. The link to the other thread has info about using the Windows device manager which will show the COM port number assigned.

And as I have mentioned...using an Android device as a modem over WiFi can be a lot easier to work with.

--
Des
NowSMS Support

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