OK, we use group SMSC SMSC_ID=A only for receiving messages and the others are used for sending ONLY, SMSC_ID = B is for MO messages and SMSC_ID = C and SMSC_ID = D are for sending MT messages during the morning. We have already asked for a separate connexion to send the MT but we need to solve this issue meanwhile. When sending the MTs in the morning I make some tests sending SMS to our gateway and for my phone the delay is huge, also I receive several times the answer of my request which I send only one time (one sms = one answer) and theres no queue in SMSC_ID=B. Errors found: 2008-11-12 14:30:49 [3918] [6] ERROR: SMPP[A]: SMSC returned error code 0x00000014 (Message Queue Full) in response to submit_sm. 2008-11-12 14:30:49 [3918] [6] WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL. 2008-11-12 14:32:05 [3918] [6] WARNING: DLR[mysql]: DLR from SMSC<A> for DST<50240796989> not found. 2008-11-12 14:32:05 [3918] [6] ERROR: SMPP[A]: got DLR but could not find message or was not interested in it id<3904438898> dst<50240796989>, type<1> 2008-11-12 12:45:44 [3918] [8] ERROR: SMPP[C]: SMSC returned error code 0x00000058 (Throttling error) in response to submit_sm. Hope this might give you a better idea. Thanks Bernard Kannel bearerbox version Build `Nov 11 2008 07:54:56', compiler `4.1.2 20070925 (Red Hat 4.1.2-33)'. System Linux, release 2.6.23.1-42.fc8, version #1 SMP Tue Oct 30 13:18:33 EDT 2007, machine x86_64. Hostname kannelServer, IP 127.0.0.1. Libxml version 2.6.30. Using OpenSSL 0.9.8b 04 May 2006. Compiled with MySQL 5.0.45, using MySQL 5.0.45. Using native malloc.
group = core admin-port = 13000 #wapbox-port = 13002 smsbox-port = 13001 admin-password = bar wdp-interface-name = "*" log-file = "/var/log/kannel/core.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1;10.27.1.*,130.7.*.*,10.10.10.*" access-log = "/var/log/kannel/access.log" unified-prefix = "+502,00502,0;+,00" dlr-storage = mysql include = "/etc/kannel/smsbox.conf" group = smsc smsc-id= A smsc = smpp host=130.1.1.50 port = 5016 smsc-username= "AGLOBAL1" smsc-password= GLOBAL06 system-type= "SMSAGLOB" source-addr-ton= 0 source-addr-npi= 0 dest-addr-ton= 0 dest-addr-npi= 0 source-addr-autodetect = true transceiver-mode= true msg-id-type = 0x00 allowed-smsc-id = "A" denied-smsc-id = B;C;D" alt-charset = ISO-8859-1 group = smsc smsc-id= B smsc = smpp host= ****** port = 5016 smsc-username= ****** smsc-password= ****** system-type= "SMSAGLOB" source-addr-ton= 0 source-addr-npi= 0 dest-addr-ton= 0 dest-addr-npi= 0 transceiver-mode= false source-addr-autodetect = true receive-port = 0 msg-id-type = 0x00 allowed-smsc-id = "B" denied-smsc-id = "A;C;D" alt-charset = ISO-8859-1 group = smsc smsc-id= comcel3 smsc = smpp host= ****** port = 5016 smsc-username= ****** smsc-password= ****** system-type= "SMSAGLOB" source-addr-ton= 0 source-addr-npi= 0 dest-addr-ton= 0 dest-addr-npi= 0 source-addr-autodetect = true transceiver-mode= false receive-port = 0 msg-id-type = 0x00 allowed-smsc-id = "C" denied-smsc-id = "A;B;D" alt-charset = ISO-8859-1 group = smsc smsc-id= comcel4 smsc = smpp host= ****** port = 5016 smsc-username= ****** smsc-password= ****** system-type= "SMSAGLOB" source-addr-ton= 0 source-addr-npi= 0 dest-addr-ton= 0 dest-addr-npi= 0 transceiver-mode= false source-addr-autodetect = true receive-port = 0 msg-id-type = 0x00 allowed-smsc-id = "D" denied-smsc-id = "A;B;C" alt-charset = ISO-8859-1 group = mysql-connection id = mydlr host = localhost username = kannel password = kannel321 database = sms max-connections = 1 group = dlr-db id = mydlr table = dlr field-smsc = smsc field-timestamp = ts field-destination = destination field-source = source field-service = service field-url = url field-mask = mask field-status = status field-boxc-id = boxc -----Original Message----- From: Stipe Tolj [mailto:[EMAIL PROTECTED] Sent: miércoles, 12 de noviembre de 2008 11:06 Cc: [email protected] Subject: Re: Received SMS Delay Bernard Cotton schrieb: > Dear users: > > Its been a while since we have been experience a kind of delay when > receiving a SMS during a big load of MT messages sent from our Kannel to > the SMPP. The delay can be from 5 minutes to an hour and during this > time the message is received more then one time, I guess its trying > several times to access our gateway but our applications respond every > time. I checked the logs and theres no error, this delay is during the > morning when we send aprox. 15 000 MT SMS in 4 hours. After the load is > sent, the delay is still present but after a few hours the response > returns to normal. We have 1 SMMP connexion spitted in 4, the first one > is used to receive SMS only, and the second one is used to send MO > messages and the third and fourth is used to send MT messages during the > day. Is there anyway to control this delay? Or prevent receiving the > same message? which of the smsc groups is used for the MO part? What can be seen on various SMSCs is that concurrency between MT and MO on transceiver session is a problem. I.e. when bearerbox gets a huge MO load in the transceiver session, the concurrent MT stream towards the SMSC is decreasing. We surely need some more informations on the specific scenario you have here to have a better overall picture of what is happening. Can you describe the whole scenario a bit more in details and also describe on how you detect the delay and what log entries are suspicious to you? Stipe -- ------------------------------------------------------------------- Kölner Landstrasse 419 40589 Düsseldorf, NRW, Germany tolj.org system architecture Kannel Software Foundation (KSF) http://www.tolj.org/ http://www.kannel.org/ mailto:st_{at}_tolj.org mailto:stolj_{at}_kannel.org ------------------------------------------------------------------- -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
