Hi Gerardo,
I'm very curious about the effect of WOPEN=3 as well so if you get brave
enough to try it please post the results! I couldn't find any specific
references to WOPEN=3 either, but if you look at page 49 of this
(http://www.icenet.cz/ftp/EG_WS0008_CL_020_UK.pdf) reference manual
(section 2.17.2.1), they seem to suggest that WOPEN=3 is a normal part
of re-initializing a modem. The modem in question is different than the
one we're using, but it would be weird for it to work too differently.
While looking back through the AT command reference, I also noticed that
there's an AT+WRST command that "resets" the modem. My reference does
not specify what reset means, but perhaps it's worth a shot.
Nathan
Gerardo Segura wrote:
Yes, I've used minicom a couple times. Unfortunately that tip didn't
work.
In the past few day I have restarted the machine several times, even
unplugged
the modem an tried using it with other applications on a windows box
without success so far.
But I'm intrigued about the +WOPEN=3 effect, what would be
erased? the modem will remain functional? I can not find info in google
about this command. The modem's manual description for this command
sounds as tautological as it could be.
I'm afraid in a few more days I'm gonna go mad enough to enter that
+WOPEN=3 even if it melts down the modem :P
Anyway thanks for the help Nathan, really appreciate it.
Gerardo.
Nathan Ferris wrote:
Hi Gerardo,
I'm using multitech gprs modems as well. Every once in a while my
modems gets "stuck" and won't send out any more sms messages either.
My logs look similar to yours when this happens. As a first step,
you should try resetting the modems using minicom. Here's the basic
process:
1. make sure that Kannel has been shut down. If you reset the modem
while Kannel is using it then kannel and the modem will wind up
getting confused
2. using minicom, send the following reset strings to the modem:
AT+WOPEN=0 followed by AT+WOPEN=1
3. exit minicom
4. restart Kannel
Are you familiar with minicom?
Nathan
Gerardo Segura wrote:
In order to determine if the problem is wrong smsc number
I do set sms-center and no-smsc with either true and false values,
but the PDU stills doesn't include the SMSC number.
Here is relevant part of kannel.conf:
group = smsc
smsc = at
smsc-id = mt_modem
modemtype = wavecom
device = /dev/ttyUSB0
speed = 115200
sms-center = +5294100001410
my-number = +52XXXXXXX
group = modems
id = wavecom
name = Wavecom
detect-string = "WAVECOM"
#I've tried with true but still no smsc number included in PDU
no-smsc = false
Here is an example of PDU generated, notice no SMSC number included
-----------------------------------------------------
DEBUG: AT2[mt_modem]: --> AT+CMGS=17^M
DEBUG: AT2[mt_modem]: <-- >
DEBUG: AT2[mt_modem]: send command status: 1
DEBUG: AT2[mt_modem]: --> 0011000A8155739073740000A704F4F29C0E
DEBUG: AT2[mt_modem]: --> ^Z
DEBUG: AT2[mt_modem]: <-- >
DEBUG: AT2[mt_modem]: <-- ERROR
ERROR: AT2[mt_modem]: Generic error: ERROR
new question:
Is it possible to make kannel generate PDU with smsc number?
regards,
Gerardo
PS: yes, I know kannel is using default smsc number, also I can see
at beggining of log:
DEBUG: AT2[mt_modem]: --> AT+CSCA="+5294100001410"^M
DEBUG: AT2[mt_modem]: <-- OK
but, since I don't see any other place to look for error I first
want to make sure
the pdu gets all info needed in itself.
