Modem bank problem

Modem bank problem SearchSearch
Author Message
Andrej Silin
New member
Username: Asilin

Post Number: 4
Registered: 11-2011
Posted on Monday, November 26, 2012 - 03:01 pm:   

Hello,

I have a Wavecom modem bank which is correctly recognised by NowSMS (it's a COM to USB modem bank). I was able to send SMS, but MMS connection does not work: even though my modem is recognised, it does not appear in "Network connection" drop-box as a connection type choice.

My modem bank is GPRS capable and both SIM cards installed on COM20 and COM11 are MMS enabled. I've tested Free and SFR, bot none of them works (probably because the connection does not go through the COM modem). Please advise.

Modem bank with two modems configured

Activity window using SFR

Activity window using Free Mobile

MMS Outbound Routing
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4219
Registered: 08-2008
Posted on Monday, November 26, 2012 - 06:26 pm:   

Hi,


You need to associate a Windows modem driver with the COM port in order to enable MMS capability.

If the manufacturer does not supply a Windows modem driver (such as Wavecom), we recommend you manually define the “Standard 33600 bps Modem” driver for the modem.

--
Des
NowSMS Support
Andrej Silin
New member
Username: Asilin

Post Number: 5
Registered: 11-2011
Posted on Tuesday, January 15, 2013 - 11:26 am:   

Hello,

I did this, but it didn't work. When I try to add the newly created modem to NowSMS, it says OK at first :

Modem - OK

Then it does something and fails with an error :

Modem - Error

If I try testing the connection without adding the modem, I get the following error :

MMS Routing Error

However, when I do Modem Diagnostic, it's OK :

Modem Windows

Do you have any idea why NowSMS is not working ?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8043
Registered: 10-2002
Posted on Tuesday, January 15, 2013 - 01:26 pm:   

Hi,

Something appears to be fundamentally wrong. Is this a real old modem by any chance? If so, how old?

Des suggested using “Standard 33600 bps Modem” (which actually talks to the modem at 115200 or higher), yet you appear to be using a 9600 bps driver.

In the context in which NowSMS displays "Initialised modem at 9600bps", it means that there are problems initialising the modem driver, so NowSMS is trying to reset the modem. As part of this process, NowSMS tries to talk to the modem at higher speeds, but finds that it can only successfully talk to the modem at 9600bps. It then tries the Windows modem driver, but that fails.

I am concerned because if the modem only supports 9600 bps, that suggests it is very old (approx 10 years), and it won't work very well for MMS at that speed even if you get past this issue.

It is odd that the Diagnostics is successful for the modem, but I think I've seen this before.

I seem to recall an incident where some other software had sent a configuration command to a modem to lock it to 9600bps, and similar problems happened. Windows diagnostics were OK for the modem, but no application could open the modem using the Windows modem driver.

The solution was to connect to the modem using a terminal program (like HyperTerminal or WinPuTTY) and send the following commands:

AT+IPR=0

AT&W

AT+IPR=0 sets the modem to autodetect the speed, and AT&W saves it.

Try that, and use “Standard 33600 bps Modem” because it does not try to fix the speed like the other "Standard" modem drivers do.

-bn

Bryce Norwood
NowSMS/MMS Support
Andrej Silin
New member
Username: Asilin

Post Number: 6
Registered: 11-2011
Posted on Tuesday, January 15, 2013 - 04:02 pm:   

Hello,

I did everything you asked above. The Windows modem diagnostics still work fine. As for NowSMS it still initialises the mode (with a different speed setting): "Initialised modem at 115200bps". Then it fails with Error 80000048 (same as above).
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8046
Registered: 10-2002
Posted on Tuesday, January 15, 2013 - 04:33 pm:   

Hi Andrej,

Is the "Afficher le journal" ("View Log") button in the modem diagnostics always greyed out?

That log might help us out. I think you have to enable "Change Settings" on the General page to enable viewing the log.

When you test the modem in NowSMS, Windows should append information to this log. It tells what actions the Windows modem driver is taking with the modem. And it should tell us what step is failing, or at least provide a clue.

-bn

Bryce Norwood
NowSMS/MMS Support
Andrej Silin
New member
Username: Asilin

Post Number: 7
Registered: 11-2011
Posted on Tuesday, April 16, 2013 - 11:08 am:   

Hi.

This is a Wavecom Q2406 gsm gprs modem bank. It works fine for sending receiving SMS. However, at this point I'm starting to wonder if it is compatible with MMS.

text/plainModem log
ModemLog_Standard 33600 bps Modem.txt (2.0 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 4405
Registered: 08-2008
Posted on Tuesday, April 16, 2013 - 06:43 pm:   

Hi Andrej,

I'm not sure what else to try.

Looking back over this discussion thread, there is one thing that I do want to make sure of. You're not configuring NowSMS to talk directly to the COM port and to the modem driver at the same time, are you? Make sure that the direct COM port reference is not in that SMSC list before you try to add the Windows modem driver. (Normally you would see different errors in this scenario, but I mention this just in case.)

Looking at your modem log, these entries show when NowSMS tries to open the modem via the Windows TAPI:

04-16-2013 12:01:19.781 - Opening Modem
04-16-2013 12:01:19.781 - 115200,8,N,1, ctsfl=1, rtsctl=2
04-16-2013 12:01:19.781 - Initializing modem.
04-16-2013 12:01:19.781 - DSR is low while initializing the modem. Verify modem is turned on.
04-16-2013 12:01:19.781 - CTS is low while initializing modem.
04-16-2013 12:01:19.781 - TSP(0000): LINEEVENT: LINE_CLOSE

The messages about DSR and CTS are normal with many modems.

What is odd is that this LINEEVENT: LINE_CLOSE event is triggered immediately. Not even a millisecond passes and Windows does not even attempt to send any commands to the modem.

Normally, there would be an attempt by Windows to try to send some initialisation commands to the modem. But there is no attempt shown in your log.

I am assuming that something is going wrong with the hardware handshaking. If this were a serial connection, I'd replace the cable or try a different port.

What is odd is that NowSMS appears to have no problem talking to the modem via the COM port directly ... and Windows diagnostics for the modem are OK.

My only other suggestions would be this.

1.) For a different modem issue, we produced a test version of SMSGW.EXE. Based upon the error you are seeing, I do not expect this version to make a difference. But maybe it will. The update is at http://www.nowsms.com/download/test20130415.zip. It contains only an updated SMSGW.EXE. Use it to replace the existing version and test if it allows the modem to be added.

2.) Check for new USB drivers for your modem bank.

--
Des
NowSMS Support