I already talked to my provider but they dont find a valid reason, they say ., I suspect that the HLR bans the modem thinking that its span due to high traffic volume, I have noticed that this has happened during high volume traffic, my final thought is they dont care too much.
Thanks for the explanation, Ill read about the allowed/denied to check with my setup to improve it, what I need is to reroute the sms when a modem is stopped. Maybe, if you have a little time, read my kannel configuration below and give some orientation or recommendation about it, Ill appreciate it very much. Regards. From: Alvaro Cornejo [mailto:[email protected]] Sent: Wednesday, August 13, 2014 2:03 PM To: Vinicio Cruz Cc: users Subject: Re: Modem discard messages instead error Hi Vinicio Interesting thing the disconnects. Might try to talk to your provider to track the issue and at least know its cause. About your new question: - Messages are stored in kannel store location you defined in core part of setup. - If they stay on queue or are rerouted to other smsc's it will depend on your setup. - If you have more than one smsc with the same smsc-id or use/share smsc-id with allowed-smsc/denied-smsc; then messages are rerouted to those shared smsc. - If you use unique smsc-id, then it will stay queued until smsc comes up again or message validity ends. 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 On Wed, Aug 13, 2014 at 11:21 AM, Vinicio Cruz <[email protected]> wrote: I agree with you Alvaro, I have found anything else on my research and getting to your conclusion too, I made changes in my parse application to handle this as an error. Disconnecting problems are not in my hands, I checked signal with AT cmd in minicom and is very good, I think its some problem with the operator happening time to time, anyway I have to live with that Maybe you can help me with other question, in the latest version you can stop an SMSC even if it is sending messages, what happened with those messages?, are they rerouted to the others SMSC, they wait until the SMSC is restarted, or other?. Thank you very much for sharing your expertise. Regards. From: Alvaro Cornejo [mailto:[email protected]] Sent: Tuesday, August 12, 2014 12:50 PM To: Vinicio Cruz Cc: users Subject: Re: Modem discard messages instead error Hi Vinicio I think this change is just a change of error name. You might want to check the code or kannel changes log for the error condition that triggers those errors. It is syntactically more correct to say that the message was discarded after n retries than failed to send it since actually kannel never "tried" to send the message because modem was disconnected from network. Therefore it shouldn't matter if the actual issue is reported as fail or discard message; unless you do parse logs for something. If this is the case, you can adapt your parser accordingly. There is nothing in your config that you can do but maybe retries setup (number and time interval). BTW why do your modems disconnect ? If you do have a low signal you should try to relocate them in a better place. Also some modems support external antennas; that might enhance reception and lower its disconnections. 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 On Tue, Aug 12, 2014 at 12:08 PM, Vinicio Cruz <[email protected]> wrote: Thanks for your response Alvaro, Ill try to explain my self better. >From time to time modems disconnects from network and are not able to send messages, in version 1.4.1 when kannel try to send an sms thru a disconnected modem and after the maximum retries is reached, the sms was marked as FAILED SEND SMS, in latest version and same symptom the sms Is marked DISCARDED SMS in the bearerbox.access. Ive read the latest manual to find some new configuration in order to mark the sms FAILED instead DISCARDED but no success, Im using exactly the same configuration file used in 1.4.1. May be you can check my modem configuration and guide me with it if there is something wrong or new, Ill appreciate very much. group = core smsbox-port = 1302 group = smsbox bearerbox-host = localhost bearerbox-port = 1301 sendsms-port = 1303 log-file = /kannel/log/smsbox.log log-level = 1 access-log = /kannel/log/smsbox.access group = sms-service keyword = default text = "" get-url = "http://localhost:8080/sms/EntradaSMS?id=%I <http://localhost:8080/sms/EntradaSMS?id=%25I&hora=%25t&smsc=%25i&fuente=%25 p&destino=%25P&codif=%25c&texto=%25b> &hora=%t&smsc=%i&fuente=%p&destino=%P&codif=%c&texto=%b" omit-empty = true group = sendsms-user username = xxxx password = xxxx user-allow-ip = 192.168.1.20 group = core admin-port = 1300 admin-password = xxxx admin-allow-ip = 192.168.1.* smsbox-port = 1301 log-file = /kannel/log/bearerbox.log log-level = 1 store-file = /kannel/log/bearerbox-store.dat access-log = /kannel/log/bearerbox.access access-log-clean = yes access-log-format = "%I","%t","%l","%i","%n","%A","%p","%P","%c",%b $$## box-allow-ip = 127.0.0.1 dlr-storage = internal sms-incoming-queue-limit = 0 sms-resend-retry = 0 group = smsbox group = modems id = multi-modem-serial sendline-sleep = 500 no-pin = yes keepalive-cmd = "AT+CMGD=1,2" reset-string = AT+CFUN=1 init-string = "AT+CMEE=1;+CGSMS=1" message-storage = "SM" #************************************** modems ******************************* group = smsc smsc-id = modem-1 smsc = at modemtype = multi-modem-serial device = /dev/ttyUSB0 keepalive = 60 max-error-count = 1 log-file = /kannel/log/modem-1.log log-level = 0 preferred-smsc-id = "modem-1" validityperiod = 0 speed = 57600 sim-buffering = true group = smsc smsc-id = modem-2 smsc = at modemtype = multi-modem-serial device = /dev/ttyUSB1 keepalive = 60 max-error-count = 1 log-file = /kannel/log/modem-2.log log-level = 0 preferred-smsc-id = "modem-" validityperiod = 0 speed = 57600 sim-buffering = true And so on 8 modems more From: Alvaro Cornejo [mailto:[email protected]] Sent: Tuesday, August 12, 2014 8:05 AM To: Vinicio Cruz Cc: users Subject: Re: Modem discard messages instead error Can you explain further your issue? The log shows error 512. You get a discard response of the message since it reached the maximum number of retries. Check user guide on how to increase the number of retries as well as its time interval. 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 On Mon, Aug 11, 2014 at 5:31 PM, Vinicio Cruz <[email protected]> wrote: Hi everyone, last weekend Updated kannel from 1.4.1 to latest svn svn-r5104'. Im facing a extrange behavior as follows, when modem is not connected to the network, try to send an sms and gets to the maximum retries, the sms gets a DISCARD status, In version 1.4.1 the sms used to get an ERROR status. Can anyone help me please . Vinicio Cruz Kannel bearerbox version `svn-r5104'. Build `Aug 9 2014 10:14:10', compiler `4.4.7 20120313 (Red Hat 4.4.7-4)'. System Linux, release 2.6.39-400.211.1.el6uek.i686, version #1 SMP Fri Nov 15 13:38:12 PST 2013, machine i686. Hostname localhost, IP 127.0.0.1. Libxml version 2.7.6. Using OpenSSL 1.0.1e-fips 11 Feb 2013. Using native malloc. 2014-08-11 16:06:33 [8778] [21] DEBUG: AT2[rack-4-telca]: TP-Validity-Period: 5 minutes 2014-08-11 16:06:33 [8778] [21] DEBUG: AT2[rack-4-telca]: --> AT+CMGS=30^M 2014-08-11 16:06:33 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- > 2014-08-11 16:06:33 [8778] [21] DEBUG: AT2[rack-4-telca]: send command status: 1 2014-08-11 16:06:33 [8778] [21] DEBUG: AT2[rack-4-telca]: --> 001100088145101268000000145079BD2C0E83C66F37A8CC06C9C3E3358806 2014-08-11 16:06:33 [8778] [21] DEBUG: AT2[rack-4-telca]: --> ^Z 2014-08-11 16:06:34 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- > 2014-08-11 16:06:34 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- +CMS ERROR: 512 2014-08-11 16:06:34 [8778] [21] ERROR: AT2[rack-4-telca]: +CMS ERROR: +CMS ERROR: 512 2014-08-11 16:06:34 [8778] [21] ERROR: AT2[rack-4-telca]: +CMS ERROR: User abort or MM establishment failure (SMS) (512) 2014-08-11 16:06:34 [8778] [21] DEBUG: AT2[rack-4-telca]: send command status: 1 2014-08-11 16:07:22 [8778] [21] DEBUG: AT2[rack-4-telca]: --> AT+CPMS?^M 2014-08-11 16:07:22 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- +CPMS: "SM",0,35,"SM",0,35,"SM",0,35 2014-08-11 16:07:22 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- OK 2014-08-11 16:07:34 [8778] [21] DEBUG: AT2[rack-4-telca]: TP-Validity-Period: 5 minutes 2014-08-11 16:07:34 [8778] [21] DEBUG: AT2[rack-4-telca]: --> AT+CMGS=30^M 2014-08-11 16:07:34 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- > 2014-08-11 16:07:34 [8778] [21] DEBUG: AT2[rack-4-telca]: send command status: 1 2014-08-11 16:07:34 [8778] [21] DEBUG: AT2[rack-4-telca]: --> 001100088145101268000000145079BD2C0E83C66F37A8CC06C9C3E3358806 2014-08-11 16:07:35 [8778] [21] DEBUG: AT2[rack-4-telca]: --> ^Z 2014-08-11 16:07:35 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- > 2014-08-11 16:07:35 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- +CMS ERROR: 512 2014-08-11 16:07:35 [8778] [21] ERROR: AT2[rack-4-telca]: +CMS ERROR: +CMS ERROR: 512 2014-08-11 16:07:35 [8778] [21] ERROR: AT2[rack-4-telca]: +CMS ERROR: User abort or MM establishment failure (SMS) (512) 2014-08-11 16:07:35 [8778] [21] DEBUG: AT2[rack-4-telca]: send command status: 1 2014-08-11 16:07:35 [8778] [21] WARNING: Maximum retries for message exceeded, discarding it! 2014-08-11 16:08:24 [8778] [21] DEBUG: AT2[rack-4-telca]: --> AT+CPMS?^M 2014-08-11 16:08:24 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- +CPMS: "SM",0,35,"SM",0,35,"SM",0,35 2014-08-11 16:08:24 [8778] [21] DEBUG: AT2[rack-4-telca]: <-- OK 2014-08-11 16:08:36 [8778] [21] DEBUG: AT2[rack-4-telca]: --> AT+CMGD=1,2^M Vinicio.
