Wavecom Fastrack WMODT

Wavecom Fastrack WMODT SearchSearch
Author Message
Anonymous
Posted on Saturday, December 14, 2002 - 04:36 am:   

Hi!
I am trying to connect the Wavecom fastrack gsm modem using XP. I cannot locate an XP driver and when I try to add it I only have the option to add it on COM1, but the software reports an initialisation error "error waiting for initialisation response from modem" I would greatly appreciate some help in getting this connected. Thanks!
Marshal
(Sydney, Australia)
Bryce Norwood - NowSMS Support (Bryce)
Posted on Saturday, December 14, 2002 - 07:56 pm:   

Marshal,

I'm trying to figure out the best way to troubleshoot this, so let me ask a question ...

Does the error come back very quickly after you click OK ... or does it take about 2 minutes?

Also, here's an idea that just might get it working.

Go into the Control Panel ... Phone and Modem Options ... and Add a modem. Use the modem driver titled "Generic 9600 bps modem" under "(Standard Modem Types)".

After you add the modem, select Properties/Diagnostics, and Query Modem ... just to make sure that the driver is talking to the modem.

Then go back and instead of trying COM1 in our software, try "Generic 9600 bps modem".

-bn
Anonymous
Posted on Tuesday, December 17, 2002 - 10:44 pm:   

Dear Bryce
Thanks for the rapid response to my question! Your software is great. I tried your solution and it worked. I have another question. We need to be able to send commands for sending MMS messages to the gateway securely via the internet. We are afraid a hacker could intrude and send messages from the gateway. Is it possible to configure the software with SSL encryption so we can send the commands securely over the internet to the server? Is it as simple as specifying an SSL port in the web setup page? Is this the correct solution?
Thanks and Regards
Marshal
(Sydney, Australia)
Bryce Norwood - NowSMS Support (Bryce)
Posted on Tuesday, December 17, 2002 - 11:20 pm:   

Marshal,

Cool. I'm glad that worked. I've got someone else that is having the same problem, and I made the same suggestion via e-mail, but haven't heard back from them yet.

We don't have an SSL interface. But I think we're going to get that sorted out by the start of the new year. We just have to link in some additional libraries.

In the meantime, I would suggest that you use the capability to limit the addresses that connections to the web interface are accepted from. On the web page, just define the IP addresses that you want to allow connections from, and everything else will be assumed "blocked".

-bn