Ok then if you thing so. Nothing we can help here then. AFAIK XL mention this on their documentation. I have been connected to XL since 2005 and no DLR missed between millions of MT. On 19 Jun 2016 8:58 a.m., "Fajar" <bebas...@yahoo.com> wrote:
> hello, > > i delete msg-id-type because msgid number is beyond limit in XL. i read by > removing it, now it becomes string type, and we don't have a problem > running that... we have set TLV number.., but for matching DLR, kannel > doesn't need tx_id, it uses foreign id/message id and msisdn... > > > ------------------------------ > *From:* Willy Mularto <sangpr...@gmail.com> > *To:* Fajar <bebas...@yahoo.com> > *Cc:* "kannel users@kannel.org" <users@kannel.org> > *Sent:* Sunday, 19 June 2016, 4:52 > *Subject:* Re: Can't find DLR, eventhough msgid is exist > > That's dlr-mask, what I mean is msg-id-type, it should be 0x01 for XL. And > also have you set the TLV TX_ID parameter? With correct configuration you > will never miss the DLR. > On 19 Jun 2016 4:12 a.m., "Fajar" <bebas...@yahoo.com> wrote: > > hello, > > i'm setting up mask with 3, both dlr type 2 and 1 can go to not mapped > situation. instead of increasing the push to smsc... i'm reducing the > amount of push to kannel to 2500/s. but the problem still happen. like i > said.. i have 2 service, both has same amount of users.. but one can be > less not mapped DLR. both use same configuration. > > ------------------------------ > * From: * Willy Mularto <sangpr...@gmail.com>; > * To: * Fajar <bebas...@yahoo.com>; > * Cc: * kannel users@kannel.org <users@kannel.org>; > * Subject: * Re: Can't find DLR, eventhough msgid is exist > * Sent: * Sat, Jun 18, 2016 3:48:52 PM > > Hi, > I believe this is more about the configuration. And regarding the DLR > issue are you sure you have the same DLR Type with XL, also please check > the TLV. The throttle limit is configurable. Re read the user guide and you > will find how to do it. > On 18 Jun 2016 9:56 p.m., "Fajar" <bebas...@yahoo.com> wrote: > > hello, > > i'm sending SMS bulk, with usually 10k messages in a minute to kannel, but > the kannel to SMSC only limit 20 messages/s, so it will cause queue in > kannel, instead in my database..., the problem is DLR. sometimes there are > 3000 messages can't be mapped, eventhough kannel received the DLR.., here > is snip log...:(i'm currently testing using redis, with max-connection=40 > and idle_timeout=10) > > [root@App YYYY]# cat /opt/kannel/logs/xl/XLMTXLSDP.log | grep XXXXXXXX > 2016-06-17 21:21:46 [28347] [7] DEBUG: destination_addr: "XXXXXXXX" > 2016-06-17 21:21:46 [28347] [7] DEBUG: DLR[redis]: Adding DLR > smsc=XLMOMTXLSDP, ts=100001200101160617142146064421, src=9922806, > dst=XXXXXXXX, mask=3, boxc= > > [root@App YYYY]# cat /opt/kannel/logs/xl/XLMOXLSDP.log | grep > 100001200101160617142146064421 > 2016-06-17 21:21:46 [28347] [6] DEBUG: DLR[redis]: Looking for DLR > smsc=XLMOMTXLSDP, ts=100001200101160617142146064421, dst=XXXXXXXX, type=2 > 2016-06-17 21:21:46 [28347] [6] ERROR: SMPP[XLMOMTXLSDP]: got DLR but > could not find message or was not interested in it > id<100001200101160617142146064421> dst<XXXXXXXX>, type<2> > > while in redis database itself... > 127.0.0.1:6379[2]> keys *100001200101160617142146064421 > 1) "dlr:XLMOMTXLSDP:100001200101160617142146064421" > > the keys still in there..., i don't know why kannel can't find it... > > the default DLR storage is internal DLR, but i'm trying to use redis > database to see if it makes different.., but it doesn't help at all... > > is there anyplace that i need to tweak more? > > thank you > > fajar > > > >
