Re: Incorrect DLR mapping in kannel 1.5.0

Am 24.11.2014 11:11, schrieb Tanja Kipreska:
> First 3 DLRs were with status=1(DELIVERED) and the 4th DLR was with
> status=2 (EXPIRED). Here are access.log details for the MSISDN I've
> tested with:
> 2014-11-20 11:21:11 Sent SMS [SMSC:smsc4.7] [SVC:bulk] [ACT:] [BINF:]
> [FID:9223372036854775807] [META:] [from:ONE] [to:076514006]
> [flags:1:0:-1:-1:3] [msg:15:Test za DLR ONE]                  [udh:0:]
> 2014-11-20 11:23:17 Receive DLR [SMSC:smsc4.7] [SVC:bulk] [ACT:vasgw]
> [BINF:] [FID:9223372036854775807] [META:?smpp?dlr_err=%03%00%00&]
> [from:ONE] [to:076514006] [flags:-1:-1:                 -1:-1:1]
> [msg:126:id:ffffff02553314cb sub:001 dlvrd:001 submit date:1411201123
> done date:1411201123 stat:DELIVRD err:0 text:message Pocituvani t] [udh:0:]

your 'msg-id-type' in the 'group = smsc' is messed up. As we see the 
foreign ID we got back from the submit_sm is 9223372036854775807, which 
is exactly the "upper max value" of the int64_t type, hence the long 
value we use to store if submit_sm_resp.message_id is interpreted as 
integer.

Please review what msg ID type you get back in 
submit_sm_resp.mesage_status. If it is the SAME as in the deliver_sm 
(DLR) PDUs, then you have obviously set some 'msg-id-type' that messes 
things up.

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
-------------------------------------------------------------------