Hello, 1. in the dlr you need only to specify ONE unique ID of yours in a view to match the DLR report with the MT message. 2. -1 means its not set. 3. if you set proper dlr-mask value, you will get the proper state of the MT message, if your SMSC is an usual one.
its all written in the manual. and there are tons of examples in this mailing list, it worth to search it. or Google a bit with proper search string BeCauet wrote: > Hello, > > 1) > In the dlr-url is a pity not being able to specify: > > - source_addr_ton > - source_addr_npi > - dest_addr_ton > - dest_addr_npi > - esm_class > - protocol_id > - priority_flag > - schedule_delivery_time > - validity_period > - registered_delivery > - replace_if_present_flag > - network_error_code (PDU) > - receipted_message_id > > -------- > 2) > > data_coding and my log says: > > data_coding: 0 = 0x00000000 > > And kannel transfert: > > "-1" > > 3) > > And delivery report is a pity we do not know directly the value of > "message_state" ... > > message_state: 2 = 0x00000002 > > And kannel transfert: > > %d the delivery report value > > If you know how ... > thank you > >
