Wavecom WMDO2 problem

Wavecom WMDO2 problem SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through October 19, 2005 » Wavecom WMDO2 problem « Previous || Next »
Author Message
Simon Hudson
New member
Username: Sliktrik

Post Number: 7
Registered: 08-2005
Posted on Wednesday, September 28, 2005 - 05:49 pm:   

I am trying to use a wavecom wmod2 modem to send/receive text/binary sms's - problem is I keep the following error in the log

2005-09-28 20:24:53,433AD81D.req,xxx.xxx.xxx.xxx,xxxxxxxxxxx,Retry Pending - ERROR - Modem Response (2): ERROR -- COM1:

nowsms can test and initialise the modem and I can see and query the modem via windows

Any ideas?

ashot shahbazian
New member
Username: Animatele

Post Number: 49
Registered: 06-2004
Posted on Thursday, September 29, 2005 - 06:01 pm:   

It appears that instead of setting up the modem in NowSMS you've set up its corresponding port, which it would allow you to do. However, with this type of setup the sending is slow and results are unpredictable.

I'd suggest that you remove your modem definition, then add it under the name as it was recognised by Windows and restart the service.

If it cannot initialise the modem it may be because the TAPI service on your computer is disabled. Enable and set it to Auto Start in control panel -- administration -- services
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5058
Registered: 10-2002
Posted on Wednesday, October 05, 2005 - 05:27 pm:   

Hi Simon,

If Ashot's suggestion doesn't help, I'd like to see an SMSDEBUG.LOG from your system, showing these sending attempts. Enable the SMSDEBUG.LOG from the "Serial #" page of the configuration.

From the sound of things, it sounds as if the modem is returning "ERROR" every time you attempt to send a message.

Try updating to the latest patch of NowSMS (http://www.nowsms.com/download/latestpatch.zip), which sends some extra initialisation commands to the modem to encourage it to respond with more detailed error information, and let's see if we then get a more detailed error message. We should get a "CMS ERROR xxx" message, where the "xxx" code is one of the values on the following list:


Beyond that, my initial suggestion would be to put the SIM into a phone, and verify that you can send an SMS using the phone ... and that there isn't something wrong with the SIM.

The next issue would be a question of whether or not the modem is actually able to receive a signal. Make sure your signal strength is good where the modem is installed.

ashot shahbazian
New member
Username: Animatele

Post Number: 50
Registered: 06-2004
Posted on Wednesday, October 05, 2005 - 05:49 pm:   

I would add, remove the SIM card PIN code before inserting the SIM into the modem

to check signal strength, issue at+csq

if the result is above 18, the reception's good

Wavecoms often misbehave if the Open AT interface isn't disabled (you don't need it for sending/receiving SMS) To disable it, issue at+wopen=0

To reboot the modem without unplugging the power cord, issue at+cfun=1

If you manage to begin sending but then the modem stops doing it for no apparent reason, try this:


Make sure the modem isn't set to send in wrong mode (CSD or GPRS) If SMS over GPRS isn't supported by your network, add:


IF SMS over GPRS is supported by the network and your version of the modem, replace it with:


These modems also freeze if they're nor properly grounded or if a low-quality DC power supply (such as that for a PC) is used.

Add a configuration option to have the modem pause 5 seconds (5000 ms) after unsuccessful send attempt. It is the optimal pause for Wavecom modems. You can find the relevant setting on this forum.
ashot shahbazian
Frequent Contributor
Username: Animatele

Post Number: 51
Registered: 06-2004
Posted on Wednesday, October 05, 2005 - 06:07 pm:   

Also, Wavecom modems freeze if there's significant inbound traffic, or the outgoing messages have DR request flag on. If that's the case my suggestion is to use Siemens MC35 instead.

Question to Bryce: is there a setting to override the DR request flag? I remember seeing a string, something like "DisableDeliveryReceiptFlag=" while I tried to start smsgws.exe in console mode, but that was a long time ago and I don't remember which version was it. It would be great to have it, as if the incoming traffic contains the DR requests and the modem works at near full capacity it would decrease the error rate.

Another interesting option would be if the DR-s generated by modems could have been sent downstream to the user's SMPP connection in a format recognisable by the user's SMPP server. Not easy to implement given the limited information received from the SMSC, but there must be some mechanism, as most handsets would correlate the receipts somehow.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5080
Registered: 10-2002
Posted on Thursday, October 06, 2005 - 07:34 pm:   

Hi Ashot,

There is a "DisableDeliveryReceipt=Yes" setting, but it only disables the delivery receipt request flag for messages sent out via SMPP connections. You put this setting under a section header titled [SMPP].

This setting was primarily for before the TrackSMPPReceipt=Yes setting became available. It allowed you to stop users from requesting receipts.

I'll have to investigate to see if we could do this in the future on a per SMSC basis. Or it would also be useful to do it on a per "SMS Users" basis to specify whether or not accounts were allowed to request receipts.

Making the GSM modem receipts match the SMPP format is one of the items on our todo list. Basically, it looks like support for it is going to be network and modem dependent. It's still going to be awhile longer before we get the specifics worked out, but potentially this looks promising.

ashot shahbazian
Frequent Contributor
Username: Animatele

Post Number: 52
Registered: 06-2004
Posted on Thursday, October 06, 2005 - 08:50 pm:   

Hi Bryce!

It would be nice to have that both ways, for an SMSC definition (i.e., to enable it for an uplink to a modem gateway.) It may also be helpful if the opposite setting, deliveryreceiptflag=1 or receiptrequested=yes, can be specified for each SMPP uplink individually.

For a user account, such setting may be useful if the user is requesting the DR-s but not retrieving them (which is quite common, i.e., an aggregator connected as tx and submitting someone else's traffic with the DR flags.) This would prevent queues of DR-s accumulating on the server, especially so with NowSMS where it'd add too many files and slow down the server if left unattended.

It would be interesting to hear about the modem DR-->SMPP DR development. Should you be interested in testing it with different networks/different types of real SMSC-s please advise, we can set up modems with SIM-s for different nets and give you remote access to the server.


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