Hi Mira

I've the same issue and the only workaround we have is the same as you.
Monitor the ports and when this happens soft reset the modem. Also in the
second error, reading messages from memory, before reseting we manually
delete the message in the affected memory slot.

We were unable to find the cause, but we asume it is some kind of overflow
in the modem firmware.

Regards,

Alvaro

|-----------------------------------------------------------------------------------------------------------------|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS
y GPRS online
              Visitenos en www.perusms.com

2017-09-08 11:22 GMT-05:00 Mira Chlastak <m...@chlastak.cz>:

> Hello,
>
> I have a gsm pool with 8 slots (with wavecom Q2406 chipset). Slots are
> connected via serial IC port to serial/usb switch (in case) and this pool
> is connected to PC via USB interface. Every slot is representing by serial
> port.
>
> I am sending/receiving sms, receiving DLR. Everything work's fine, but
> sometimes (at some of days in month) are slots (not all) re-connecting or
> are in "stuck" state. This causes, that the sms are not sending and
> sometimes are the received sms "pushed" to the receiving URL manytimes.
>
> In kannel.log are log records like this one (only for "stuck" slot -
> others slot sending sms normaly):
>
> 2017-09-08 17:27:12 [10868] [6] DEBUG: AT2[1]: TP-Validity-Period: 24.0
> hours
> 2017-09-08 17:27:12 [10868] [6] DEBUG: AT2[1]: --> AT+CMGS=147^M
> 2017-09-08 17:27:12 [10868] [6] DEBUG: AT2[1]: <-- >
> 2017-09-08 17:27:12 [10868] [6] DEBUG: AT2[1]: send command status: 1
> 2017-09-08 17:27:12 [10868] [6] DEBUG: AT2[1]: -->
> 0051000C912460408793620000A797050003EE0202EAEAF4380D82CBC3E3
> B7DD9D0691CB6E1708B47CB7EBEEF4FA6D0FD34173903BDC4E83DA757D99
> 5E06BDC9F0B7BD4C4E83DC6110BD4E7F83A6CD29C85D16BF41EE30A8DC6A
> 87D3EC3A28ED36BF01EDBAD9EC1AEB5D206B7A5C06A5DDE637C81D06DDEF
> 7757BB6E36BBC67A17C81A9E839A55A311240D8FD3EE33885A0EB701
> 2017-09-08 17:27:12 [10868] [6] DEBUG: AT2[1]: --> ^Z
> 2017-09-08 17:27:12 [10868] [6] DEBUG: AT2[1]: <-- >
> 2017-09-08 17:27:12 [10868] [6] DEBUG: AT2[1]: <-- ERROR
> 2017-09-08 17:27:12 [10868] [6] ERROR: AT2[1]: Generic error: ERROR
>
>
> And this log records are in kannel.log when is received messaged "pushed"
> to receiving url manytimes:
>
> 2017-09-08 01:14:09 [10868] [6] DEBUG: AT2[1]: 3 messages waiting in memory
> 2017-09-08 01:14:09 [10868] [6] DEBUG: AT2[1]: --> AT+CMGR=1^M
> 2017-09-08 01:14:09 [10868] [6] DEBUG: AT2[1]: <-- +CMGR: "REC
> READ","+XXXXXXXXX",,"17/09/07,23:18:39+08"
> 2017-09-08 01:14:09 [10868] [6] DEBUG: AT2[1]: <-- V patek budu na
> Komenskeho 159.Zaslete hod.dodani..J.V.
> 2017-09-08 01:14:09 [10868] [6] ERROR: AT2[1]: got +CMT but pdu_extract
> failed
> 2017-09-08 01:14:09 [10868] [6] DEBUG: AT2[1]: <-- OK
> 2017-09-08 01:14:09 [10868] [6] DEBUG: AT2[1]: not deleted.
>
>
> To solve the problem is enough (very often) connecting to this slot via
> terminal (e.g. cu -l /dev/cuaU0 -s 115200) and enter command "AT" (that
> return "OK") and then close connection to this serial port. Sometimes
> solved this problem only restart of kannel.
>
>
>
> Part of kannel config (version of kannel is 1.4.4):
>
> ...
> group = smsc
> smsc = at
> device = /dev/cuaU0
> speed = 115200
> connect-allow-ip = "127.0.0.1"
> transceiver-mode = true
> smsc-id = 1
> allowed-smsc-id = 1
> sim-buffering=true
>
> group = modems
> id = GSMbox
> name = "wavecom"
> detect-string = "WAVECOM"
> speed = 115200
> need-sleep = false
> #
> init-string = "AT+CNMI=0,2,0,1,0;+CMEE=1"
> reset-string = "AT+CFUN=1"
> keepalive-cmd = "AT+CSQ"
> enable-hwhs = "AT+IFC=2,2"
> broken = false
> message-storage = "SM"
>
> group = sms-service
> keyword = default
> catch-all = yes
> max-messages = 0
> get-url = "http://x.x.x.x:6100/sms/received?sender=%p&text=%a";
> ...
>
>
> What can cause these problems?
>
> --
> Mira
>
>

Reply via email to