Re: Re[2]: Couldnot parse DLR string sscanf way, fallback to old way. Please report
Try set system-type = "" So Far Express VPN still the fastest https://www.expressrefer.com/refer-friend?referrer_id=15939000&utm_campaign=referrals&utm_medium=copy_link&utm_source=referral_dashboard On Sun, Mar 25, 2018 at 5:46 PM Сергей Сергеевич Батманов < sergeybatma...@mail.ru> wrote: > I try to set msg-id-type = 0x01, 0x02, 0x03 and still not working. > > > Воскресенье, 25 марта 2018, 15:38 +05:00 от Willy Mularto < > sangpr...@gmail.com>: > > See how to set msg-id-type in user guide. > > > So Far Express VPN still the fastest > > https://www.expressrefer.com/refer-friend?referrer_id=15939000&utm_campaign=referrals&utm_medium=copy_link&utm_source=referral_dashboard > > > On Sun, Mar 25, 2018 at 5:30 PM Сергей Сергеевич Батманов < > sergeybatma...@mail.ru > <https://e.mail.ru/compose/?mailto=mailto%3asergeybatma...@mail.ru>> > wrote: > > Hi, there. > > I have a problem with incoming deliver_sm. > > Kannel can't parse DLR and gives error. The problem is that i don't send > submit_sm, this pdu deliver_sm is special notification from provider with > next short_message: > 20180325102847+PayDay+0+20180326103303+2.5+28766 > > Deliver_sm is not a delivery report and doesn't have message_id. > > 1. What I can do with this erorr and how can i save this deliver_sm to db? > > 2. I have another deliver_sm, that doesn't give same error, but kannel can't > decode short_message. > > I try change msg-id-type, alt-charset and it doesn't work. > > Any ideas? > > > It's the first deliver_sm. > > 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Got PDU: > 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU 0x7f23c80025b0 dump: > 2018-03-25 15:02:26 [2579] [6] DEBUG: type_name: deliver_sm > 2018-03-25 15:02:26 [2579] [6] DEBUG: command_id: 5 = 0x0005 > 2018-03-25 15:02:26 [2579] [6] DEBUG: command_status: 0 = 0x > 2018-03-25 15:02:26 [2579] [6] DEBUG: sequence_number: 1435116073 = > 0x558a2229 > 2018-03-25 15:02:26 [2579] [6] DEBUG: service_type: NULL > 2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr_ton: 1 = 0x0001 > 2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr_npi: 1 = 0x0001 > 2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr: "79519881890" > 2018-03-25 15:02:26 [2579] [6] DEBUG: dest_addr_ton: 1 = 0x0001 > 2018-03-25 15:02:26 [2579] [6] DEBUG: dest_addr_npi: 1 = 0x0001 > 2018-03-25 15:02:26 [2579] [6] DEBUG: destination_addr: "683" > 2018-03-25 15:02:26 [2579] [6] DEBUG: esm_class: 28 = 0x001c > 2018-03-25 15:02:26 [2579] [6] DEBUG: protocol_id: 0 = 0x > 2018-03-25 15:02:26 [2579] [6] DEBUG: priority_flag: 0 = 0x > 2018-03-25 15:02:26 [2579] [6] DEBUG: schedule_delivery_time: NULL > 2018-03-25 15:02:26 [2579] [6] DEBUG: validity_period: NULL > 2018-03-25 15:02:26 [2579] [6] DEBUG: registered_delivery: 0 = 0x > 2018-03-25 15:02:26 [2579] [6] DEBUG: replace_if_present_flag: 0 = > 0x > 2018-03-25 15:02:26 [2579] [6] DEBUG: data_coding: 0 = 0x > 2018-03-25 15:02:26 [2579] [6] DEBUG: sm_default_msg_id: 0 = 0x > 2018-03-25 15:02:26 [2579] [6] DEBUG: sm_length: 51 = 0x0033 > 2018-03-25 15:02:26 [2579] [6] DEBUG: short_message: > 2018-03-25 15:02:26 [2579] [6] DEBUG: Octet string at 0x7f23c8000b60: > 2018-03-25 15:02:26 [2579] [6] DEBUG: len: 51 > 2018-03-25 15:02:26 [2579] [6] DEBUG: size: 52 > 2018-03-25 15:02:26 [2579] [6] DEBUG: immutable: 0 > 2018-03-25 15:02:26 [2579] [6] DEBUG: data: 32 30 31 38 30 33 32 35 31 30 > 32 38 34 37 2b 50 20180325102847+P > 2018-03-25 15:02:26 [2579] [6] DEBUG: data: 61 79 44 61 79 2b 30 2b 32 30 > 31 38 30 33 32 36 ayDay+0+20180326 > 2018-03-25 15:02:26 [2579] [6] DEBUG: data: 31 30 33 33 30 33 2b 32 2e 35 > 2b 32 38 37 36 36 103303+2.5+28766 > 2018-03-25 15:02:26 [2579] [6] DEBUG: data: 31 33 32 132 > 2018-03-25 15:02:26 [2579] [6] DEBUG: Octet string dump ends. > 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU dump ends. > 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2] handle_pdu, got DLR > 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Couldnot parse DLR > string sscanf way,fallback to old way. Please report! > 2018-03-25 15:02:26 [2579] [6] ERROR: SMPP[smstele2]: got DLR but could > not find message or was not interested in it id<> dst<79519881890>, type<2> > 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Sending PDU: > 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU 0x7f23c8006890 dump: > 2018-03-25 15:02:26 [2579] [6] DEBUG: type_name: deliver_sm_resp > 2018-03-25 15:02:26 [2579] [6] DEBUG: command_id: 2147483653 = 0x8005 > 2018-03-25 15:02:26 [2579] [6] DEBUG: command
Re[4]: Couldnot parse DLR string sscanf way,fallback to old way. Please report
Thanks for your answer, but the same error. >Воскресенье, 25 марта 2018, 16:26 +05:00 от Willy Mularto >: > >Try set system-type = "" > > >So Far Express VPN still the fastest >https://www.expressrefer.com/refer-friend?referrer_id=15939000&utm_campaign=referrals&utm_medium=copy_link&utm_source=referral_dashboard > > >On Sun, Mar 25, 2018 at 5:46 PM Сергей Сергеевич Батманов < >sergeybatma...@mail.ru > wrote: >>I try to set msg-id-type = 0x01, 0x02, 0x03 and still not working. >> >> >>>Воскресенье, 25 марта 2018, 15:38 +05:00 от Willy Mularto < >>>sangpr...@gmail.com >: >>> >>>See how to set msg-id-type in user guide. >>> >>> >>>So Far Express VPN still the fastest >>>https://www.expressrefer.com/refer-friend?referrer_id=15939000&utm_campaign=referrals&utm_medium=copy_link&utm_source=referral_dashboard >>> >>> >>>On Sun, Mar 25, 2018 at 5:30 PM Сергей Сергеевич Батманов < >>>sergeybatma...@mail.ru > wrote: >>>>Hi, there. >>>> >>>>I have a problem with incoming deliver_sm. >>>> >>>>Kannel can't parse DLR and gives error. The problem is that i don't send >>>>submit_sm, this pdu deliver_sm is special notification from provider with >>>>next short_message: >>>>20180325102847+PayDay+0+20180326103303+2.5+28766 >>>> >>>>Deliver_sm is not a delivery report and doesn't have message_id. >>>> >>>>1. What I can do with this erorr and how can i save this deliver_sm to db? >>>> >>>>2. I have another deliver_sm, that doesn't give same error, but kannel >>>>can't decode short_message. >>>> >>>>I try change msg-id-type, alt-charset and it doesn't work. >>>> >>>>Any ideas? >>>> >>>> >>>>It's the first deliver_sm. >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Got PDU: >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU 0x7f23c80025b0 dump: >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: type_name: deliver_sm >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: command_id: 5 = 0x0005 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: command_status: 0 = 0x >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: sequence_number: 1435116073 = >>>>0x558a2229 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: service_type: NULL >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr_ton: 1 = 0x0001 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr_npi: 1 = 0x0001 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr: "79519881890" >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: dest_addr_ton: 1 = 0x0001 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: dest_addr_npi: 1 = 0x0001 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: destination_addr: "683" >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: esm_class: 28 = 0x001c >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: protocol_id: 0 = 0x >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: priority_flag: 0 = 0x >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: schedule_delivery_time: NULL >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: validity_period: NULL >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: registered_delivery: 0 = 0x >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: replace_if_present_flag: 0 = >>>>0x >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: data_coding: 0 = 0x >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: sm_default_msg_id: 0 = 0x >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: sm_length: 51 = 0x0033 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: short_message: >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: Octet string at 0x7f23c8000b60: >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: len: 51 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: size: 52 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: immutable: 0 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: data: 32 30 31 38 30 33 32 35 31 30 >>>>32 38 34 37 2b 50 20180325102847+P >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: data: 61 79 44 61 79 2b 30 2b 32 30 >>>>31 38 30 33 32 36 ayDay+0 +20180326 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: data: 31 30 33 33 30 33 2b 32 2e 35 >>>>2b 32 38 37 36 36 103303+2.5+28766 >>>>2018-03-25 15:02:26 [2579] [6] DEBUG: data: 31 33 32 132 >>>>2018-03-25 15:
Re[2]: Couldnot parse DLR string sscanf way,fallback to old way. Please report
I try to set msg-id-type = 0x01, 0x02, 0x03 and still not working. >Воскресенье, 25 марта 2018, 15:38 +05:00 от Willy Mularto >: > >See how to set msg-id-type in user guide. > > >So Far Express VPN still the fastest >https://www.expressrefer.com/refer-friend?referrer_id=15939000&utm_campaign=referrals&utm_medium=copy_link&utm_source=referral_dashboard > > >On Sun, Mar 25, 2018 at 5:30 PM Сергей Сергеевич Батманов < >sergeybatma...@mail.ru > wrote: >>Hi, there. >> >>I have a problem with incoming deliver_sm. >> >>Kannel can't parse DLR and gives error. The problem is that i don't send >>submit_sm, this pdu deliver_sm is special notification from provider with >>next short_message: >>20180325102847+PayDay+0+20180326103303+2.5+28766 >> >>Deliver_sm is not a delivery report and doesn't have message_id. >> >>1. What I can do with this erorr and how can i save this deliver_sm to db? >> >>2. I have another deliver_sm, that doesn't give same error, but kannel can't >>decode short_message. >> >>I try change msg-id-type, alt-charset and it doesn't work. >> >>Any ideas? >> >> >>It's the first deliver_sm. >>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Got PDU: >>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU 0x7f23c80025b0 dump: >>2018-03-25 15:02:26 [2579] [6] DEBUG: type_name: deliver_sm >>2018-03-25 15:02:26 [2579] [6] DEBUG: command_id: 5 = 0x0005 >>2018-03-25 15:02:26 [2579] [6] DEBUG: command_status: 0 = 0x >>2018-03-25 15:02:26 [2579] [6] DEBUG: sequence_number: 1435116073 = 0x558a2229 >>2018-03-25 15:02:26 [2579] [6] DEBUG: service_type: NULL >>2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr_ton: 1 = 0x0001 >>2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr_npi: 1 = 0x0001 >>2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr: "79519881890" >>2018-03-25 15:02:26 [2579] [6] DEBUG: dest_addr_ton: 1 = 0x0001 >>2018-03-25 15:02:26 [2579] [6] DEBUG: dest_addr_npi: 1 = 0x0001 >>2018-03-25 15:02:26 [2579] [6] DEBUG: destination_addr: "683" >>2018-03-25 15:02:26 [2579] [6] DEBUG: esm_class: 28 = 0x001c >>2018-03-25 15:02:26 [2579] [6] DEBUG: protocol_id: 0 = 0x >>2018-03-25 15:02:26 [2579] [6] DEBUG: priority_flag: 0 = 0x >>2018-03-25 15:02:26 [2579] [6] DEBUG: schedule_delivery_time: NULL >>2018-03-25 15:02:26 [2579] [6] DEBUG: validity_period: NULL >>2018-03-25 15:02:26 [2579] [6] DEBUG: registered_delivery: 0 = 0x >>2018-03-25 15:02:26 [2579] [6] DEBUG: replace_if_present_flag: 0 = 0x >>2018-03-25 15:02:26 [2579] [6] DEBUG: data_coding: 0 = 0x >>2018-03-25 15:02:26 [2579] [6] DEBUG: sm_default_msg_id: 0 = 0x >>2018-03-25 15:02:26 [2579] [6] DEBUG: sm_length: 51 = 0x0033 >>2018-03-25 15:02:26 [2579] [6] DEBUG: short_message: >>2018-03-25 15:02:26 [2579] [6] DEBUG: Octet string at 0x7f23c8000b60: >>2018-03-25 15:02:26 [2579] [6] DEBUG: len: 51 >>2018-03-25 15:02:26 [2579] [6] DEBUG: size: 52 >>2018-03-25 15:02:26 [2579] [6] DEBUG: immutable: 0 >>2018-03-25 15:02:26 [2579] [6] DEBUG: data: 32 30 31 38 30 33 32 35 31 30 32 >>38 34 37 2b 50 20180325102847+P >>2018-03-25 15:02:26 [2579] [6] DEBUG: data: 61 79 44 61 79 2b 30 2b 32 30 31 >>38 30 33 32 36 ayDay+0 +20180326 >>2018-03-25 15:02:26 [2579] [6] DEBUG: data: 31 30 33 33 30 33 2b 32 2e 35 2b >>32 38 37 36 36 103303+2.5+28766 >>2018-03-25 15:02:26 [2579] [6] DEBUG: data: 31 33 32 132 >>2018-03-25 15:02:26 [2579] [6] DEBUG: Octet string dump ends. >>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU dump ends. >>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2] handle_pdu, got DLR >>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Couldnot parse DLR >>string sscanf way,fallback to old way. Please report! >>2018-03-25 15:02:26 [2579] [6] ERROR: SMPP[smstele2]: got DLR but could not >>find message or was not interested in it id<> dst<79519881890>, type<2> >>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Sending PDU: >>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU 0x7f23c8006890 dump: >>2018-03-25 15:02:26 [2579] [6] DEBUG: type_name: deliver_sm_resp >>2018-03-25 15:02:26 [2579] [6] DEBUG: command_id: 2147483653 = 0x8005 >>2018-03-25 15:02:26 [2579] [6] DEBUG: command_status: 0 = 0x >>2018-03-25 15:02:26 [2579] [6] DEBUG: sequence_number: 1435116073 = 0x558a2229 >>2018-03-25 15:02:26 [2579] [6] DEBUG: message_id: NULL >>2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU dump ends. >>
Couldnot parse DLR string sscanf way,fallback to old way. Please report
Hi, there. I have a problem with incoming deliver_sm. Kannel can't parse DLR and gives error. The problem is that i don't send submit_sm, this pdu deliver_sm is special notification from provider with next short_message: 20180325102847+PayDay+0+20180326103303+2.5+28766 Deliver_sm is not a delivery report and doesn't have message_id. 1. What I can do with this erorr and how can i save this deliver_sm to db? 2. I have another deliver_sm, that doesn't give same error, but kannel can't decode short_message. I try change msg-id-type, alt-charset and it doesn't work. Any ideas? It's the first deliver_sm. 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Got PDU: 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU 0x7f23c80025b0 dump: 2018-03-25 15:02:26 [2579] [6] DEBUG: type_name: deliver_sm 2018-03-25 15:02:26 [2579] [6] DEBUG: command_id: 5 = 0x0005 2018-03-25 15:02:26 [2579] [6] DEBUG: command_status: 0 = 0x 2018-03-25 15:02:26 [2579] [6] DEBUG: sequence_number: 1435116073 = 0x558a2229 2018-03-25 15:02:26 [2579] [6] DEBUG: service_type: NULL 2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr_ton: 1 = 0x0001 2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr_npi: 1 = 0x0001 2018-03-25 15:02:26 [2579] [6] DEBUG: source_addr: "79519881890" 2018-03-25 15:02:26 [2579] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2018-03-25 15:02:26 [2579] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2018-03-25 15:02:26 [2579] [6] DEBUG: destination_addr: "683" 2018-03-25 15:02:26 [2579] [6] DEBUG: esm_class: 28 = 0x001c 2018-03-25 15:02:26 [2579] [6] DEBUG: protocol_id: 0 = 0x 2018-03-25 15:02:26 [2579] [6] DEBUG: priority_flag: 0 = 0x 2018-03-25 15:02:26 [2579] [6] DEBUG: schedule_delivery_time: NULL 2018-03-25 15:02:26 [2579] [6] DEBUG: validity_period: NULL 2018-03-25 15:02:26 [2579] [6] DEBUG: registered_delivery: 0 = 0x 2018-03-25 15:02:26 [2579] [6] DEBUG: replace_if_present_flag: 0 = 0x 2018-03-25 15:02:26 [2579] [6] DEBUG: data_coding: 0 = 0x 2018-03-25 15:02:26 [2579] [6] DEBUG: sm_default_msg_id: 0 = 0x 2018-03-25 15:02:26 [2579] [6] DEBUG: sm_length: 51 = 0x0033 2018-03-25 15:02:26 [2579] [6] DEBUG: short_message: 2018-03-25 15:02:26 [2579] [6] DEBUG: Octet string at 0x7f23c8000b60: 2018-03-25 15:02:26 [2579] [6] DEBUG: len: 51 2018-03-25 15:02:26 [2579] [6] DEBUG: size: 52 2018-03-25 15:02:26 [2579] [6] DEBUG: immutable: 0 2018-03-25 15:02:26 [2579] [6] DEBUG: data: 32 30 31 38 30 33 32 35 31 30 32 38 34 37 2b 50 20180325102847+P 2018-03-25 15:02:26 [2579] [6] DEBUG: data: 61 79 44 61 79 2b 30 2b 32 30 31 38 30 33 32 36 ayDay+0+20180326 2018-03-25 15:02:26 [2579] [6] DEBUG: data: 31 30 33 33 30 33 2b 32 2e 35 2b 32 38 37 36 36 103303+2.5+28766 2018-03-25 15:02:26 [2579] [6] DEBUG: data: 31 33 32 132 2018-03-25 15:02:26 [2579] [6] DEBUG: Octet string dump ends. 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU dump ends. 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2] handle_pdu, got DLR 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2018-03-25 15:02:26 [2579] [6] ERROR: SMPP[smstele2]: got DLR but could not find message or was not interested in it id<> dst<79519881890>, type<2> 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP[smstele2]: Sending PDU: 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU 0x7f23c8006890 dump: 2018-03-25 15:02:26 [2579] [6] DEBUG: type_name: deliver_sm_resp 2018-03-25 15:02:26 [2579] [6] DEBUG: command_id: 2147483653 = 0x8005 2018-03-25 15:02:26 [2579] [6] DEBUG: command_status: 0 = 0x 2018-03-25 15:02:26 [2579] [6] DEBUG: sequence_number: 1435116073 = 0x558a2229 2018-03-25 15:02:26 [2579] [6] DEBUG: message_id: NULL 2018-03-25 15:02:26 [2579] [6] DEBUG: SMPP PDU dump ends. And it's the second deliver_sm: 2018-03-25 05:35:04 [9914] [6] DEBUG: Optional parameter tag (0x0202) 2018-03-25 05:35:04 [9914] [6] DEBUG: Optional parameter length read as 12 2018-03-25 05:35:04 [9914] [6] DEBUG: Optional parameter tag (0x0204) 2018-03-25 05:35:04 [9914] [6] DEBUG: Optional parameter length read as 2 2018-03-25 05:35:04 [9914] [6] DEBUG: SMPP[smstele2]: Got PDU: 2018-03-25 05:35:04 [9914] [6] DEBUG: SMPP PDU 0x7f103c000a60 dump: 2018-03-25 05:35:04 [9914] [6] DEBUG: type_name: deliver_sm 2018-03-25 05:35:04 [9914] [6] DEBUG: command_id: 5 = 0x0005 2018-03-25 05:35:04 [9914] [6] DEBUG: command_status: 0 = 0x 2018-03-25 05:35:04 [9914] [6] DEBUG: sequence_number: 1232498810 = 0x4976707a 2018-03-25 05:35:04 [9914] [6] DEBUG: service_type: NULL 2018-03-25 05:35:04 [9914] [6] DEBUG: source_addr_ton: 1 = 0x0001 2018-03-25 05:35:04 [9914] [6] DEBUG: source_addr_npi: 1 = 0x0001 2018-03-25 05:35:04 [9914] [6] DEBUG: source_addr: "79524022709" 2018-03-25 05:35:04 [9914] [6] DEB
Re: Invalid DRL Couldnot parse DLR string sscanf way,fallback to old way. Please report!
Hi All, I have managed to contact MTC they had to make amendments and we had to split our TX and RX into seperate binds and set the message id type as 0x01 for both. Thanks again Jarratt On 09/17/2010 10:45 AM, "Mads N. Vestergaard – CoolSMS A/S" wrote: Hi Jarratt, For me it looks like your provider isn't following the official protocol. If we look at the message you are sending, they give it the msgid 31D44D55: > 2010-09-17 10:26:34 [16954] [12] DEBUG: message_id: "31D44D55" Later on you receive the DLR, but the ID is only given in the message_payload: > 2010-09-17 10:26:37 [16954] [13] DEBUG: message_payload: "31D44D55 201" And after the msgid, thay have, what for me looks like a return code: 201 This is out of standard, you provider might be able to solve this for you, if not you might need to create a patch for kannel, to support your provider.
Re: Invalid DRL Couldnot parse DLR string sscanf way,fallback to old way. Please report!
Hi Mads, Thanks for the response i though it would be as such, the provider is MTC Namibia in case anybody else has the same issue, I have asked them for a response but as usual in Africa Everybody is on African time :) If i get a response i will update the list Thanks Jarratt On 09/17/2010 10:45 AM, "Mads N. Vestergaard – CoolSMS A/S" wrote: Hi Jarratt, For me it looks like your provider isn't following the official protocol. If we look at the message you are sending, they give it the msgid 31D44D55: 2010-09-17 10:26:34 [16954] [12] DEBUG: message_id: "31D44D55" Later on you receive the DLR, but the ID is only given in the message_payload: 2010-09-17 10:26:37 [16954] [13] DEBUG: message_payload: "31D44D55 201" And after the msgid, thay have, what for me looks like a return code: 201 This is out of standard, you provider might be able to solve this for you, if not you might need to create a patch for kannel, to support your provider. If you mention what provider, somebody else on the list, might have further info for you, if they have been in the same situation. Den 17/09/2010 kl. 10.31 skrev Jarratt Ingram: Hi Guys, We have just connected to a Namibian Provider, We are sending message's correctly however we are getting the following error "Couldnot parse DLR string sscanf way,fallback to old way. Please report!", any ideas on how to process the DLR correctly Below is the full debug 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: throughput (1.00,5.00) 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: Got PDU: 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP PDU 0x7fd8a8002650 dump: 2010-09-17 10:26:34 [16954] [12] DEBUG: type_name: submit_sm_resp 2010-09-17 10:26:34 [16954] [12] DEBUG: command_id: 2147483652 = 0x8004 2010-09-17 10:26:34 [16954] [12] DEBUG: command_status: 0 = 0x 2010-09-17 10:26:34 [16954] [12] DEBUG: sequence_number: 87 = 0x0057 2010-09-17 10:26:34 [16954] [12] DEBUG: message_id: "31D44D55" 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP PDU dump ends. 2010-09-17 10:26:34 [16954] [12] DEBUG: DLR[mysql]: Adding DLR smsc=30, ts=835997013, src=081011, dst=264811229233, mask=1, boxc= 2010-09-17 10:26:34 [16954] [12] DEBUG: adding DLR entry into database 2010-09-17 10:26:34 [16954] [12] DEBUG: sql: INSERT INTO `dlr` (`smsc`, `ts`, `source`, `destination`, `service`, `url`, `mask`, `boxc`, `status`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 0) 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: throughput (1.00,5.00) 2010-09-17 10:26:37 [16954] [13] DEBUG: Optional parameter tag (0x0424) 2010-09-17 10:26:37 [16954] [13] DEBUG: Optional parameter length read as 12 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Got PDU: 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU 0x7fd89c001520 dump: 2010-09-17 10:26:37 [16954] [13] DEBUG: type_name: data_sm 2010-09-17 10:26:37 [16954] [13] DEBUG: command_id: 259 = 0x0103 2010-09-17 10:26:37 [16954] [13] DEBUG: command_status: 0 = 0x 2010-09-17 10:26:37 [16954] [13] DEBUG: sequence_number: 19 = 0x0013 2010-09-17 10:26:37 [16954] [13] DEBUG: service_type: NULL 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr_ton: 1 = 0x0001 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr_npi: 1 = 0x0001 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr: "264811229233" 2010-09-17 10:26:37 [16954] [13] DEBUG: dest_addr_ton: 2 = 0x0002 2010-09-17 10:26:37 [16954] [13] DEBUG: dest_addr_npi: 1 = 0x0001 2010-09-17 10:26:37 [16954] [13] DEBUG: destination_addr: "081011" 2010-09-17 10:26:37 [16954] [13] DEBUG: esm_class: 4 = 0x0004 2010-09-17 10:26:37 [16954] [13] DEBUG: registered_delivery: 0 = 0x 2010-09-17 10:26:37 [16954] [13] DEBUG: data_coding: 0 = 0x 2010-09-17 10:26:37 [16954] [13] DEBUG: message_payload: "31D44D55 201" 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU dump ends. 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30] handle_pdu, got DLR 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2010-09-17 10:26:37 [16954] [13] ERROR: SMPP[30]: got DLR but could not find message or was not interested in it id<> dst<264811229233>, type<2> 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Sending PDU: 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU 0x7fd89c0057a0 dump: 2010-09-17 10:26:37 [16954] [13] DEBUG: type_name: data_sm_resp 2010-09-17 10:26:37 [16954] [13] DEBUG: command_id: 2147483907 = 0x8103 2010-09-17 10:26:37 [16954] [13] DEBUG: command_status: 0 = 0x 2010-09-17 10:26:37 [16954] [13] DEBUG: sequence_number: 19 = 0x0013 2010-09-17 10:26:37 [16954] [13] DEBUG: message_id: NULL 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU dump ends. Regards Jarratt
Re: Invalid DRL Couldnot parse DLR string sscanf way, fallback to old way. Please report!
Hi Jarratt, For me it looks like your provider isn't following the official protocol. If we look at the message you are sending, they give it the msgid 31D44D55: > 2010-09-17 10:26:34 [16954] [12] DEBUG: message_id: "31D44D55" Later on you receive the DLR, but the ID is only given in the message_payload: > 2010-09-17 10:26:37 [16954] [13] DEBUG: message_payload: "31D44D55 201" And after the msgid, thay have, what for me looks like a return code: 201 This is out of standard, you provider might be able to solve this for you, if not you might need to create a patch for kannel, to support your provider. If you mention what provider, somebody else on the list, might have further info for you, if they have been in the same situation. Den 17/09/2010 kl. 10.31 skrev Jarratt Ingram: > Hi Guys, > > We have just connected to a Namibian Provider, We are sending message's > correctly however we are getting the following error "Couldnot parse DLR > string sscanf way,fallback to old way. Please report!", any ideas on how to > process the DLR correctly > > Below is the full debug > 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: throughput (1.00,5.00) > 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: Got PDU: > 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP PDU 0x7fd8a8002650 dump: > 2010-09-17 10:26:34 [16954] [12] DEBUG: type_name: submit_sm_resp > 2010-09-17 10:26:34 [16954] [12] DEBUG: command_id: 2147483652 = 0x8004 > 2010-09-17 10:26:34 [16954] [12] DEBUG: command_status: 0 = 0x > 2010-09-17 10:26:34 [16954] [12] DEBUG: sequence_number: 87 = 0x0057 > 2010-09-17 10:26:34 [16954] [12] DEBUG: message_id: "31D44D55" > 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP PDU dump ends. > 2010-09-17 10:26:34 [16954] [12] DEBUG: DLR[mysql]: Adding DLR smsc=30, > ts=835997013, src=081011, dst=264811229233, mask=1, boxc= > 2010-09-17 10:26:34 [16954] [12] DEBUG: adding DLR entry into database > 2010-09-17 10:26:34 [16954] [12] DEBUG: sql: INSERT INTO `dlr` (`smsc`, `ts`, > `source`, `destination`, `service`, `url`, `mask`, `boxc`, `status`) VALUES > (?, ?, ?, ?, ?, ?, ?, ?, 0) > 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: throughput (1.00,5.00) > 2010-09-17 10:26:37 [16954] [13] DEBUG: Optional parameter tag (0x0424) > 2010-09-17 10:26:37 [16954] [13] DEBUG: Optional parameter length read as 12 > 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Got PDU: > 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU 0x7fd89c001520 dump: > 2010-09-17 10:26:37 [16954] [13] DEBUG: type_name: data_sm > 2010-09-17 10:26:37 [16954] [13] DEBUG: command_id: 259 = 0x0103 > 2010-09-17 10:26:37 [16954] [13] DEBUG: command_status: 0 = 0x > 2010-09-17 10:26:37 [16954] [13] DEBUG: sequence_number: 19 = 0x0013 > 2010-09-17 10:26:37 [16954] [13] DEBUG: service_type: NULL > 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr_ton: 1 = 0x0001 > 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr_npi: 1 = 0x0001 > 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr: "264811229233" > 2010-09-17 10:26:37 [16954] [13] DEBUG: dest_addr_ton: 2 = 0x0002 > 2010-09-17 10:26:37 [16954] [13] DEBUG: dest_addr_npi: 1 = 0x0001 > 2010-09-17 10:26:37 [16954] [13] DEBUG: destination_addr: "081011" > 2010-09-17 10:26:37 [16954] [13] DEBUG: esm_class: 4 = 0x0004 > 2010-09-17 10:26:37 [16954] [13] DEBUG: registered_delivery: 0 = 0x > 2010-09-17 10:26:37 [16954] [13] DEBUG: data_coding: 0 = 0x > 2010-09-17 10:26:37 [16954] [13] DEBUG: message_payload: "31D44D55 201" > 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU dump ends. > 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30] handle_pdu, got DLR > 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Couldnot parse DLR string > sscanf way,fallback to old way. Please report! > 2010-09-17 10:26:37 [16954] [13] ERROR: SMPP[30]: got DLR but could not find > message or was not interested in it id<> dst<264811229233>, type<2> > 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Sending PDU: > 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU 0x7fd89c0057a0 dump: > 2010-09-17 10:26:37 [16954] [13] DEBUG: type_name: data_sm_resp > 2010-09-17 10:26:37 [16954] [13] DEBUG: command_id: 2147483907 = 0x8103 > 2010-09-17 10:26:37 [16954] [13] DEBUG: command_status: 0 = 0x > 2010-09-17 10:26:37 [16954] [13] DEBUG: sequence_number: 19 = 0x0013 > 2010-09-17 10:26:37 [16954] [13] DEBUG: message_id: NULL > 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU dump ends. > > Regards > Jarratt >
Invalid DRL Couldnot parse DLR string sscanf way,fallback to old way. Please report!
Hi Guys, We have just connected to a Namibian Provider, We are sending message's correctly however we are getting the following error "Couldnot parse DLR string sscanf way,fallback to old way. Please report!", any ideas on how to process the DLR correctly Below is the full debug 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: throughput (1.00,5.00) 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: Got PDU: 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP PDU 0x7fd8a8002650 dump: 2010-09-17 10:26:34 [16954] [12] DEBUG: type_name: submit_sm_resp 2010-09-17 10:26:34 [16954] [12] DEBUG: command_id: 2147483652 = 0x8004 2010-09-17 10:26:34 [16954] [12] DEBUG: command_status: 0 = 0x 2010-09-17 10:26:34 [16954] [12] DEBUG: sequence_number: 87 = 0x0057 2010-09-17 10:26:34 [16954] [12] DEBUG: message_id: "31D44D55" 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP PDU dump ends. 2010-09-17 10:26:34 [16954] [12] DEBUG: DLR[mysql]: Adding DLR smsc=30, ts=835997013, src=081011, dst=264811229233, mask=1, boxc= 2010-09-17 10:26:34 [16954] [12] DEBUG: adding DLR entry into database 2010-09-17 10:26:34 [16954] [12] DEBUG: sql: INSERT INTO `dlr` (`smsc`, `ts`, `source`, `destination`, `service`, `url`, `mask`, `boxc`, `status`) VALUES (?, ?, ?, ?, ?, ?, ?, ?, 0) 2010-09-17 10:26:34 [16954] [12] DEBUG: SMPP[30]: throughput (1.00,5.00) 2010-09-17 10:26:37 [16954] [13] DEBUG: Optional parameter tag (0x0424) 2010-09-17 10:26:37 [16954] [13] DEBUG: Optional parameter length read as 12 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Got PDU: 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU 0x7fd89c001520 dump: 2010-09-17 10:26:37 [16954] [13] DEBUG: type_name: data_sm 2010-09-17 10:26:37 [16954] [13] DEBUG: command_id: 259 = 0x0103 2010-09-17 10:26:37 [16954] [13] DEBUG: command_status: 0 = 0x 2010-09-17 10:26:37 [16954] [13] DEBUG: sequence_number: 19 = 0x0013 2010-09-17 10:26:37 [16954] [13] DEBUG: service_type: NULL 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr_ton: 1 = 0x0001 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr_npi: 1 = 0x0001 2010-09-17 10:26:37 [16954] [13] DEBUG: source_addr: "264811229233" 2010-09-17 10:26:37 [16954] [13] DEBUG: dest_addr_ton: 2 = 0x0002 2010-09-17 10:26:37 [16954] [13] DEBUG: dest_addr_npi: 1 = 0x0001 2010-09-17 10:26:37 [16954] [13] DEBUG: destination_addr: "081011" 2010-09-17 10:26:37 [16954] [13] DEBUG: esm_class: 4 = 0x0004 2010-09-17 10:26:37 [16954] [13] DEBUG: registered_delivery: 0 = 0x 2010-09-17 10:26:37 [16954] [13] DEBUG: data_coding: 0 = 0x 2010-09-17 10:26:37 [16954] [13] DEBUG: message_payload: "31D44D55 201" 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU dump ends. 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30] handle_pdu, got DLR 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2010-09-17 10:26:37 [16954] [13] ERROR: SMPP[30]: got DLR but could not find message or was not interested in it id<> dst<264811229233>, type<2> 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP[30]: Sending PDU: 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU 0x7fd89c0057a0 dump: 2010-09-17 10:26:37 [16954] [13] DEBUG: type_name: data_sm_resp 2010-09-17 10:26:37 [16954] [13] DEBUG: command_id: 2147483907 = 0x8103 2010-09-17 10:26:37 [16954] [13] DEBUG: command_status: 0 = 0x 2010-09-17 10:26:37 [16954] [13] DEBUG: sequence_number: 19 = 0x0013 2010-09-17 10:26:37 [16954] [13] DEBUG: message_id: NULL 2010-09-17 10:26:37 [16954] [13] DEBUG: SMPP PDU dump ends. Regards Jarratt
Re: Dlr warning: Couldnot parse DLR string sscanf way, fallback to old way. Please report!
39 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Got PDU: > > 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU 0xa5a03ad8 dump: > > 2009-03-04 10:02:39 [3044] [6] DEBUG: type_name: deliver_sm > > 2009-03-04 10:02:39 [3044] [6] DEBUG: command_id: 5 = 0x0005 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: command_status: 0 = 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: sequence_number: 1 = 0x0001 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: service_type: NULL > > 2009-03-04 10:02:39 [3044] [6] DEBUG: source_addr_ton: 5 = 0x0005 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: source_addr_npi: 0 = 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: source_addr: "MiSender" > > 2009-03-04 10:02:39 [3044] [6] DEBUG: dest_addr_ton: 1 = 0x0001 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: dest_addr_npi: 1 = 0x0001 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: destination_addr: "525513206766" > > 2009-03-04 10:02:39 [3044] [6] DEBUG: esm_class: 4 = 0x0004 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: protocol_id: 0 = 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: priority_flag: 0 = 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: schedule_delivery_time: NULL > > 2009-03-04 10:02:39 [3044] [6] DEBUG: validity_period: NULL > > 2009-03-04 10:02:39 [3044] [6] DEBUG: registered_delivery: 0 = 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: replace_if_present_flag: 0 = > > 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: data_coding: 0 = 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: sm_default_msg_id: 0 = 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: sm_length: 70 = 0x0046 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: short_message: > > 2009-03-04 10:02:39 [3044] [6] DEBUG:Octet string at 0xa5a3ac38: > > 2009-03-04 10:02:39 [3044] [6] DEBUG: len: 70 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: size: 71 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: immutable: 0 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 69 64 3a 31 32 33 36 > > 31 38 32 35 33 36 20 73 74 id:1236182536 st > > 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 61 74 3a 44 45 4c 49 > > 56 52 44 20 73 75 62 6d 69 at:DELIVRD submi > > 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 74 20 64 61 74 65 3a > > 30 39 30 33 30 34 31 30 30 t date:090304100 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 32 20 64 6f 6e 65 20 > > 64 61 74 65 3a 30 39 30 33 2 done date:0903 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 30 34 31 30 30 32 > > 041002 > > 2009-03-04 10:02:39 [3044] [6] DEBUG:Octet string dump ends. > > 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU dump ends. > > 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got > > DLR > > 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot > > parse DLR string sscanf way,fallback to old way. Please report! > > 2009-03-04 10:02:39 [3044] [6] DEBUG: DLR[mysql]: Looking for DLR > > smsc=telcel_sc3783, ts=1236182536, dst=MiSender, type=1 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: sql: SELECT mask, service, url, > > source, destination, boxc FROM tblkannel_dlr WHERE > > smsc='telcel_sc3783' AND ts='1236182536'; > > 2009-03-04 10:02:39 [3044] [6] DEBUG: Found entry, row[0]=31, > > row[1]=playsms, > > row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2860670&uid=10&smsc=%i&sender_id=MiSender, > > row[3]=0, row[4]=525513206766 row[5]= > > 2009-03-04 10:02:39 [3044] [6] DEBUG: DLR[mysql]: created DLR message > > for URL > > <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2860670&uid=10&smsc=%i&sender_id=MiSender> > > 2009-03-04 10:02:39 [3044] [6] DEBUG: removing DLR from database > > 2009-03-04 10:02:39 [3044] [6] DEBUG: sql: DELETE FROM tblkannel_dlr > > WHERE smsc='telcel_sc3783' AND ts='1236182536' LIMIT 1; > > 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: > > 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU 0xa5a99eb0 dump: > > 2009-03-04 10:02:39 [3044] [6] DEBUG: type_name: deliver_sm_resp > > 2009-03-04 10:02:39 [3044] [6] DEBUG: command_id: 2147483653 = 0x8005 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: command_status: 0 = 0x > > 2009-03-04 10:02:39 [3044] [6] DEBUG: sequence_number: 1 = 0x0001 > > 2009-03-04 10:02:39 [3044] [6] DEBUG: message_id: NULL > > 2009-03-04
Re: Dlr warning: Couldnot parse DLR string sscanf way, fallback to old way. Please report!
09-03-04 10:02:39 [3044] [6] DEBUG: destination_addr: "525513206766" 2009-03-04 10:02:39 [3044] [6] DEBUG: esm_class: 4 = 0x0004 2009-03-04 10:02:39 [3044] [6] DEBUG: protocol_id: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: priority_flag: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: schedule_delivery_time: NULL 2009-03-04 10:02:39 [3044] [6] DEBUG: validity_period: NULL 2009-03-04 10:02:39 [3044] [6] DEBUG: registered_delivery: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: replace_if_present_flag: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: data_coding: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: sm_length: 70 = 0x0046 2009-03-04 10:02:39 [3044] [6] DEBUG: short_message: 2009-03-04 10:02:39 [3044] [6] DEBUG:Octet string at 0xa5a3ac38: 2009-03-04 10:02:39 [3044] [6] DEBUG: len: 70 2009-03-04 10:02:39 [3044] [6] DEBUG: size: 71 2009-03-04 10:02:39 [3044] [6] DEBUG: immutable: 0 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 69 64 3a 31 32 33 36 31 38 32 35 33 36 20 73 74 id:1236182536 st 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 61 74 3a 44 45 4c 49 56 52 44 20 73 75 62 6d 69 at:DELIVRD submi 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 74 20 64 61 74 65 3a 30 39 30 33 30 34 31 30 30 t date:090304100 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 32 20 64 6f 6e 65 20 64 61 74 65 3a 30 39 30 33 2 done date:0903 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 30 34 31 30 30 32 041002 2009-03-04 10:02:39 [3044] [6] DEBUG:Octet string dump ends. 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU dump ends. 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got DLR 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2009-03-04 10:02:39 [3044] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=telcel_sc3783, ts=1236182536, dst=MiSender, type=1 2009-03-04 10:02:39 [3044] [6] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236182536'; 2009-03-04 10:02:39 [3044] [6] DEBUG: Found entry, row[0]=31, row[1]=playsms, row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2860670&uid=10&smsc=%i&sender_id=MiSender, row[3]=0, row[4]=525513206766 row[5]= 2009-03-04 10:02:39 [3044] [6] DEBUG: DLR[mysql]: created DLR message for URL <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2860670&uid=10&smsc=%i&sender_id=MiSender> 2009-03-04 10:02:39 [3044] [6] DEBUG: removing DLR from database 2009-03-04 10:02:39 [3044] [6] DEBUG: sql: DELETE FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236182536' LIMIT 1; 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU 0xa5a99eb0 dump: 2009-03-04 10:02:39 [3044] [6] DEBUG: type_name: deliver_sm_resp 2009-03-04 10:02:39 [3044] [6] DEBUG: command_id: 2147483653 = 0x8005 2009-03-04 10:02:39 [3044] [6] DEBUG: command_status: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: sequence_number: 1 = 0x0001 2009-03-04 10:02:39 [3044] [6] DEBUG: message_id: NULL 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU dump ends. 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Sending enquire link: 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP PDU 0xa5a03ad8 dump: 2009-03-04 10:02:45 [3044] [6] DEBUG: type_name: enquire_link 2009-03-04 10:02:45 [3044] [6] DEBUG: command_id: 21 = 0x0015 2009-03-04 10:02:45 [3044] [6] DEBUG: command_status: 0 = 0x 2009-03-04 10:02:45 [3044] [6] DEBUG: sequence_number: 2200 = 0x0898 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP PDU dump ends. 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Got PDU: 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP PDU 0xa5a03ad8 dump: 2009-03-04 10:02:45 [3044] [6] DEBUG: type_name: enquire_link_resp 2009-03-04 10:02:45 [3044] [6] DEBUG: command_id: 2147483669 = 0x8015 2009-03-04 10:02:45 [3044] [6] DEBUG: command_status: 0 = 0x 2009-03-04 10:02:45 [3044] [6] DEBUG: sequence_number: 2200 = 0x0898 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP PDU dump ends. |-| 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.NET www.smsglobal.com.mx y www.pravcom.com On Wed, Mar 4, 2009 at 10:46 AM, Alexander Malysh wrote: Please post deliver_sm for DLR coming from SMSC. Thanks, Alex Alvaro Cornejo schrieb: Hi Alex This is the code I use for
Re: Dlr warning: Couldnot parse DLR string sscanf way, fallback to old way. Please report!
0x 2009-03-04 10:02:39 [3044] [6] DEBUG: schedule_delivery_time: NULL 2009-03-04 10:02:39 [3044] [6] DEBUG: validity_period: NULL 2009-03-04 10:02:39 [3044] [6] DEBUG: registered_delivery: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: replace_if_present_flag: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: data_coding: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: sm_default_msg_id: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: sm_length: 70 = 0x0046 2009-03-04 10:02:39 [3044] [6] DEBUG: short_message: 2009-03-04 10:02:39 [3044] [6] DEBUG:Octet string at 0xa5a3ac38: 2009-03-04 10:02:39 [3044] [6] DEBUG: len: 70 2009-03-04 10:02:39 [3044] [6] DEBUG: size: 71 2009-03-04 10:02:39 [3044] [6] DEBUG: immutable: 0 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 69 64 3a 31 32 33 36 31 38 32 35 33 36 20 73 74 id:1236182536 st 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 61 74 3a 44 45 4c 49 56 52 44 20 73 75 62 6d 69 at:DELIVRD submi 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 74 20 64 61 74 65 3a 30 39 30 33 30 34 31 30 30 t date:090304100 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 32 20 64 6f 6e 65 20 64 61 74 65 3a 30 39 30 33 2 done date:0903 2009-03-04 10:02:39 [3044] [6] DEBUG: data: 30 34 31 30 30 32 041002 2009-03-04 10:02:39 [3044] [6] DEBUG:Octet string dump ends. 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU dump ends. 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got DLR 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2009-03-04 10:02:39 [3044] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=telcel_sc3783, ts=1236182536, dst=MiSender, type=1 2009-03-04 10:02:39 [3044] [6] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236182536'; 2009-03-04 10:02:39 [3044] [6] DEBUG: Found entry, row[0]=31, row[1]=playsms, row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2860670&uid=10&smsc=%i&sender_id=MiSender, row[3]=0, row[4]=525513206766 row[5]= 2009-03-04 10:02:39 [3044] [6] DEBUG: DLR[mysql]: created DLR message for URL <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2860670&uid=10&smsc=%i&sender_id=MiSender> 2009-03-04 10:02:39 [3044] [6] DEBUG: removing DLR from database 2009-03-04 10:02:39 [3044] [6] DEBUG: sql: DELETE FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236182536' LIMIT 1; 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU 0xa5a99eb0 dump: 2009-03-04 10:02:39 [3044] [6] DEBUG: type_name: deliver_sm_resp 2009-03-04 10:02:39 [3044] [6] DEBUG: command_id: 2147483653 = 0x8005 2009-03-04 10:02:39 [3044] [6] DEBUG: command_status: 0 = 0x 2009-03-04 10:02:39 [3044] [6] DEBUG: sequence_number: 1 = 0x0001 2009-03-04 10:02:39 [3044] [6] DEBUG: message_id: NULL 2009-03-04 10:02:39 [3044] [6] DEBUG: SMPP PDU dump ends. 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Sending enquire link: 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP PDU 0xa5a03ad8 dump: 2009-03-04 10:02:45 [3044] [6] DEBUG: type_name: enquire_link 2009-03-04 10:02:45 [3044] [6] DEBUG: command_id: 21 = 0x0015 2009-03-04 10:02:45 [3044] [6] DEBUG: command_status: 0 = 0x 2009-03-04 10:02:45 [3044] [6] DEBUG: sequence_number: 2200 = 0x0898 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP PDU dump ends. 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP[telcel_sc3783]: Got PDU: 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP PDU 0xa5a03ad8 dump: 2009-03-04 10:02:45 [3044] [6] DEBUG: type_name: enquire_link_resp 2009-03-04 10:02:45 [3044] [6] DEBUG: command_id: 2147483669 = 0x8015 2009-03-04 10:02:45 [3044] [6] DEBUG: command_status: 0 = 0x 2009-03-04 10:02:45 [3044] [6] DEBUG: sequence_number: 2200 = 0x0898 2009-03-04 10:02:45 [3044] [6] DEBUG: SMPP PDU dump ends. |-| 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.NET www.smsglobal.com.mx y www.pravcom.com On Wed, Mar 4, 2009 at 10:46 AM, Alexander Malysh wrote: > Please post deliver_sm for DLR coming from SMSC. > > Thanks, > Alex > > Alvaro Cornejo schrieb: >> >> Hi Alex >> >> This is the code I use for dlr: >> >> $dlr_URL = >> $dlr_mask."&dlr-url=".urlencode($kannel_param['playsms_web']."/gateway/kannel/dlr.php?type=%d&slid=$smslog_id&uid=$uid&smsc=%i&s
Re: Dlr warning: Couldnot parse DLR string sscanf way, fallback to old way. Please report!
Please post deliver_sm for DLR coming from SMSC. Thanks, Alex Alvaro Cornejo schrieb: Hi Alex This is the code I use for dlr: $dlr_URL = $dlr_mask."&dlr-url=".urlencode($kannel_param['playsms_web']."/gateway/kannel/dlr.php?type=%d&slid=$smslog_id&uid=$uid&smsc=%i&sender_id=$sms_from"); $dlr_URL .= "&mclass=$sms_type"; This is the url: /cgi-bin/sendsms?username=puser&password=ppass&from=%252B525587654321&to=%2B525535504776&text=ABANDONO+GRAL+1.46%25PRUEBA+SMS+&smsc=telcel&coding=0&mclass=2 and dlr part of url coded: &dlr-mask=24&dlr-url=http%3A%2F%2F127.0.0.1%2Fsms%2Fplugin%2Fgateway%2Fkannel%2Fdlr.php%3Ftype%3D%25d%26slid%3D2858203%26uid%3D277%26smsc%3D%25i%26sender_id%3D%252B525587654321 Hope help you help me ;) |-| 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.NET www.smsglobal.com.mx y www.pravcom.com On Wed, Mar 4, 2009 at 5:20 AM, Alexander Malysh wrote: Hi Alvaro, this is related to how DLR message is formated. Seems it's formated in different way as smpp spec suggest. Could you please post your DLR message, so I can look into it? Thanks, Alex Alvaro Cornejo schrieb: Hi I'm receiving the following error in my SMPP log: 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got DLR 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=telcel_sc3783, ts=1236113516, dst=MiSender, type=1 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236113516'; 2009-03-03 14:52:20 [6373] [6] DEBUG: Found entry, row[0]=31, row[1]=playsms, row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender, row[3]=0, row[4]=525527298936 row[5]= 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: created DLR message for URL <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender> 2009-03-03 14:52:20 [6373] [6] DEBUG: removing DLR from database 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: DELETE FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236113516' LIMIT 1; 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP PDU 0x9c54f10 dump: What is this? Regards Alvaro
Re: Dlr warning: Couldnot parse DLR string sscanf way, fallback to old way. Please report!
Hi Alex This is the code I use for dlr: $dlr_URL = $dlr_mask."&dlr-url=".urlencode($kannel_param['playsms_web']."/gateway/kannel/dlr.php?type=%d&slid=$smslog_id&uid=$uid&smsc=%i&sender_id=$sms_from"); $dlr_URL .= "&mclass=$sms_type"; This is the url: /cgi-bin/sendsms?username=puser&password=ppass&from=%252B525587654321&to=%2B525535504776&text=ABANDONO+GRAL+1.46%25PRUEBA+SMS+&smsc=telcel&coding=0&mclass=2 and dlr part of url coded: &dlr-mask=24&dlr-url=http%3A%2F%2F127.0.0.1%2Fsms%2Fplugin%2Fgateway%2Fkannel%2Fdlr.php%3Ftype%3D%25d%26slid%3D2858203%26uid%3D277%26smsc%3D%25i%26sender_id%3D%252B525587654321 Hope help you help me ;) |-| 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.NET www.smsglobal.com.mx y www.pravcom.com On Wed, Mar 4, 2009 at 5:20 AM, Alexander Malysh wrote: > Hi Alvaro, > > this is related to how DLR message is formated. Seems it's formated in > different way as smpp spec suggest. Could you please post your DLR message, > so I can look into it? > > Thanks, > Alex > > Alvaro Cornejo schrieb: >> >> Hi >> >> I'm receiving the following error in my SMPP log: >> >> 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got >> DLR >> 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot >> parse DLR string sscanf way,fallback to old way. Please report! >> 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: Looking for DLR >> smsc=telcel_sc3783, ts=1236113516, dst=MiSender, type=1 >> 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: SELECT mask, service, url, >> source, destination, boxc FROM tblkannel_dlr WHERE >> smsc='telcel_sc3783' AND ts='1236113516'; >> 2009-03-03 14:52:20 [6373] [6] DEBUG: Found entry, row[0]=31, >> row[1]=playsms, >> >> row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender, >> row[3]=0, row[4]=525527298936 row[5]= >> 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: created DLR message >> for URL >> <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender> >> 2009-03-03 14:52:20 [6373] [6] DEBUG: removing DLR from database >> 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: DELETE FROM tblkannel_dlr >> WHERE smsc='telcel_sc3783' AND ts='1236113516' LIMIT 1; >> 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: >> 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP PDU 0x9c54f10 dump: >> >> >> What is this? >> >> Regards >> >> Alvaro >> >> > > >
Re: Dlr warning: Couldnot parse DLR string sscanf way,fallback to old way. Please report!
Hi Alvaro, this is related to how DLR message is formated. Seems it's formated in different way as smpp spec suggest. Could you please post your DLR message, so I can look into it? Thanks, Alex Alvaro Cornejo schrieb: Hi I'm receiving the following error in my SMPP log: 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got DLR 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=telcel_sc3783, ts=1236113516, dst=MiSender, type=1 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236113516'; 2009-03-03 14:52:20 [6373] [6] DEBUG: Found entry, row[0]=31, row[1]=playsms, row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender, row[3]=0, row[4]=525527298936 row[5]= 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: created DLR message for URL <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender> 2009-03-03 14:52:20 [6373] [6] DEBUG: removing DLR from database 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: DELETE FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236113516' LIMIT 1; 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP PDU 0x9c54f10 dump: What is this? Regards Alvaro
Re: Dlr warning: Couldnot parse DLR string sscanf way,fallback to old way. Please report!
YES, you are right here, its not msg-id-type related, Could you paste the PDU data as well ? anyway, take a look at http://doxygen.kannel.org/de/dfe/smsc__smpp_8c.html line 01193 I assume the DLR string contains additional data, I have experienced similar behavior with the some customized SMSC DLR, may be like Clickatell SMSC usual DLR string looks like: r...@dl360-1.seikath.net:[Wed Mar 04 01:00:23]:[/opt/kannel/logs]$ tail access.log | sed '/Receive DLR/!d' | sed '$,$!d' 2009-03-04 01:00:32 Receive DLR [SMSC:sir] [SVC:SANTA] [ACT:] [BINF:] [from:1916] [to:+359885100407] [flags:-1:-1:-1:-1:1] [msg:122:id:0062034476 sub:001 dlvrd:001 submit date:0903040100 done date:0903040100 stat:DELIVRD err:000 text: ., 1 SMS ] [udh:0:] So, check the dlr string for additional data etc. but again, its not critical as yours DLR are being processed. Alvaro Cornejo wrote: > Hi > > This is my smpp setup. msg-type is set to 1 because I get msg id in Hex > and I send it in dec. So I think it is the correct value. > > group = smsc > smsc = smpp > smsc-id = telcel_sc3783 > host = a.b.c.d > port = 8808 > transceiver-mode= true > smsc-username = user > smsc-password = pass > ##throughput = 10 > msg-id-type = 1 > system-type = smpp > dest-addr-ton = 2 > dest-addr-npi = 1 > source-addr-ton = 2 > source-addr-npi = 1 > log-level = 0 > log-file= "/var/log/kannel/sc3783.log" > allowed-smsc-id = sc3783 > > Other ideas?? > > > > On Wed, 2009-03-04 at 00:32 +0200, seikath wrote: >> Hi, >> >> Its NOT a critical issue, >> i believe its something related to a particular smsc settings >> >> in case you have time and no critical DLR involved services, >> you may try to change msg-id-type value of this smsc account >> >> >> cheers >> >> >> Alvaro Cornejo wrote: >>> Hi >>> >>> I'm receiving the following error in my SMPP log: >>> >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got >>> DLR >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot >>> parse DLR string sscanf way,fallback to old way. Please report! >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: Looking for DLR >>> smsc=telcel_sc3783, ts=1236113516, dst=MiSender, type=1 >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: SELECT mask, service, url, >>> source, destination, boxc FROM tblkannel_dlr WHERE >>> smsc='telcel_sc3783' AND ts='1236113516'; >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: Found entry, row[0]=31, >>> row[1]=playsms, >>> row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender, >>> row[3]=0, row[4]=525527298936 row[5]= >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: created DLR message >>> for URL >>> <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender> >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: removing DLR from database >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: DELETE FROM tblkannel_dlr >>> WHERE smsc='telcel_sc3783' AND ts='1236113516' LIMIT 1; >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: >>> 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP PDU 0x9c54f10 dump: >>> >>> >>> What is this? >>> >>> Regards >>> >>> Alvaro >>> >>> > >
Re: Dlr warning: Couldnot parse DLR string sscanf way,fallback to old way. Please report!
Hi This is my smpp setup. msg-type is set to 1 because I get msg id in Hex and I send it in dec. So I think it is the correct value. group = smsc smsc = smpp smsc-id = telcel_sc3783 host = a.b.c.d port = 8808 transceiver-mode= true smsc-username = user smsc-password = pass ##throughput = 10 msg-id-type = 1 system-type = smpp dest-addr-ton = 2 dest-addr-npi = 1 source-addr-ton = 2 source-addr-npi = 1 log-level = 0 log-file= "/var/log/kannel/sc3783.log" allowed-smsc-id = sc3783 Other ideas?? On Wed, 2009-03-04 at 00:32 +0200, seikath wrote: > Hi, > > Its NOT a critical issue, > i believe its something related to a particular smsc settings > > in case you have time and no critical DLR involved services, > you may try to change msg-id-type value of this smsc account > > > cheers > > > Alvaro Cornejo wrote: > > Hi > > > > I'm receiving the following error in my SMPP log: > > > > 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got > > DLR > > 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot > > parse DLR string sscanf way,fallback to old way. Please report! > > 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: Looking for DLR > > smsc=telcel_sc3783, ts=1236113516, dst=MiSender, type=1 > > 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: SELECT mask, service, url, > > source, destination, boxc FROM tblkannel_dlr WHERE > > smsc='telcel_sc3783' AND ts='1236113516'; > > 2009-03-03 14:52:20 [6373] [6] DEBUG: Found entry, row[0]=31, > > row[1]=playsms, > > row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender, > > row[3]=0, row[4]=525527298936 row[5]= > > 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: created DLR message > > for URL > > <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender> > > 2009-03-03 14:52:20 [6373] [6] DEBUG: removing DLR from database > > 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: DELETE FROM tblkannel_dlr > > WHERE smsc='telcel_sc3783' AND ts='1236113516' LIMIT 1; > > 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: > > 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP PDU 0x9c54f10 dump: > > > > > > What is this? > > > > Regards > > > > Alvaro > > > >
Re: Dlr warning: Couldnot parse DLR string sscanf way,fallback to old way. Please report!
Hi, Its NOT a critical issue, i believe its something related to a particular smsc settings in case you have time and no critical DLR involved services, you may try to change msg-id-type value of this smsc account cheers Alvaro Cornejo wrote: > Hi > > I'm receiving the following error in my SMPP log: > > 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got DLR > 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot > parse DLR string sscanf way,fallback to old way. Please report! > 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: Looking for DLR > smsc=telcel_sc3783, ts=1236113516, dst=MiSender, type=1 > 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: SELECT mask, service, url, > source, destination, boxc FROM tblkannel_dlr WHERE > smsc='telcel_sc3783' AND ts='1236113516'; > 2009-03-03 14:52:20 [6373] [6] DEBUG: Found entry, row[0]=31, > row[1]=playsms, > row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender, > row[3]=0, row[4]=525527298936 row[5]= > 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: created DLR message > for URL > <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender> > 2009-03-03 14:52:20 [6373] [6] DEBUG: removing DLR from database > 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: DELETE FROM tblkannel_dlr > WHERE smsc='telcel_sc3783' AND ts='1236113516' LIMIT 1; > 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: > 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP PDU 0x9c54f10 dump: > > > What is this? > > Regards > > Alvaro > >
Dlr warning: Couldnot parse DLR string sscanf way,fallback to old way. Please report!
Hi I'm receiving the following error in my SMPP log: 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783] handle_pdu, got DLR 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=telcel_sc3783, ts=1236113516, dst=MiSender, type=1 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236113516'; 2009-03-03 14:52:20 [6373] [6] DEBUG: Found entry, row[0]=31, row[1]=playsms, row[2]=http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender, row[3]=0, row[4]=525527298936 row[5]= 2009-03-03 14:52:20 [6373] [6] DEBUG: DLR[mysql]: created DLR message for URL <http://127.0.0.1/sms/plugin/gateway/kannel/dlr.php?type=%d&slid=2854200&uid=10&smsc=%i&sender_id=MiSender> 2009-03-03 14:52:20 [6373] [6] DEBUG: removing DLR from database 2009-03-03 14:52:20 [6373] [6] DEBUG: sql: DELETE FROM tblkannel_dlr WHERE smsc='telcel_sc3783' AND ts='1236113516' LIMIT 1; 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP[telcel_sc3783]: Sending PDU: 2009-03-03 14:52:20 [6373] [6] DEBUG: SMPP PDU 0x9c54f10 dump: What is this? Regards Alvaro
Re: Couldnot parse DLR string sscanf way, fallback to old way. Please report!
I tried the latest CVS version, but this wouldn't fix the problem. Rolandow wrote: Hi guys, I am receiving this DLR error when my DLR comes in. In the example below, you can see from the string that the message is delivery succesfully. So it should return a type=2. Though, the parsing isn't correct, so I think that may be the reason why type is set to 2. I am running a cvs build of some time ago .. i'm not sure how I can check my exact version? Is this solved in the latest CVS version? Thanks in advance for your help. My logs: 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP[73299]: Got PDU: 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP PDU 0x81b4720 dump: 2008-11-10 15:15:56 [23865] [6] DEBUG: type_name: deliver_sm 2008-11-10 15:15:56 [23865] [6] DEBUG: command_id: 5 = 0x0005 2008-11-10 15:15:56 [23865] [6] DEBUG: command_status: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: sequence_number: 14 = 0x000e 2008-11-10 15:15:56 [23865] [6] DEBUG: service_type: NULL 2008-11-10 15:15:56 [23865] [6] DEBUG: source_addr_ton: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: source_addr_npi: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: source_addr: "3162945162" 2008-11-10 15:15:56 [23865] [6] DEBUG: dest_addr_ton: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: dest_addr_npi: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: destination_addr: "8090" 2008-11-10 15:15:56 [23865] [6] DEBUG: esm_class: 4 = 0x0004 2008-11-10 15:15:56 [23865] [6] DEBUG: protocol_id: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: priority_flag: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: schedule_delivery_time: NULL 2008-11-10 15:15:56 [23865] [6] DEBUG: validity_period: NULL 2008-11-10 15:15:56 [23865] [6] DEBUG: registered_delivery: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: replace_if_present_flag: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: data_coding: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: sm_default_msg_id: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: sm_length: 70 = 0x0046 2008-11-10 15:15:56 [23865] [6] DEBUG: short_message: 2008-11-10 15:15:56 [23865] [6] DEBUG:Octet string at 0x81b3bb8: 2008-11-10 15:15:56 [23865] [6] DEBUG: len: 70 2008-11-10 15:15:56 [23865] [6] DEBUG: size: 71 2008-11-10 15:15:56 [23865] [6] DEBUG: immutable: 0 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 69 64 3a 30 38 36 34 38 31 30 38 38 36 20 73 75 id:0864810886 su 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 62 6d 69 74 20 64 61 74 65 3a 30 38 31 31 31 30 bmit date:081110 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 30 39 31 35 20 64 6f 6e 65 20 64 61 74 65 3a 30 0915 done date:0 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 38 31 31 31 30 30 39 31 35 20 73 74 61 74 3a 44 811100915 stat:D 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 45 4c 49 56 52 44 ELIVRD 2008-11-10 15:15:56 [23865] [6] DEBUG:Octet string dump ends. 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP PDU dump ends. 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP[73299] handle_pdu, got DLR 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP[73299]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2008-11-10 15:15:56 [23865] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=73299, ts=864810886, dst=3162945162, type=2 2008-11-10 15:15:56 [23865] [6] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='73299' AND ts='864810886'; 2008-11-10 15:15:56 [23865] [6] DEBUG: Found entry, row[0]=31, row[1]=mbridges, row[2]=http://login.mobilebridges.com/sms/mo/quattromobile_smpp/DLR.php5?mtid=71341386&msgid=%I&smsc=%i&ts=%T&sender=%q&receiver=%Q&status=%d&application=qm_co_8090&answer=%A, row[3]=8090, row[4]=573162945162 row[5]= 2008-11-10 15:15:56 [23865] [6] DEBUG: DLR[mysql]: created DLR message for URL <http://login.mobilebridges.com/sms/mo/quattromobile_smpp/DLR.php5?mtid=71341386&msgid=%I&smsc=%i&ts=%T&sender=%q&receiver=%Q&status=%d&application=qm_co_8090&answer=%A> 2008-11-10 15:15:56 [23865] [6] DEBUG: removing DLR from database
Couldnot parse DLR string sscanf way,fallback to old way. Please report!
Hi guys, I am receiving this DLR error when my DLR comes in. In the example below, you can see from the string that the message is delivery succesfully. So it should return a type=2. Though, the parsing isn't correct, so I think that may be the reason why type is set to 2. I am running a cvs build of some time ago .. i'm not sure how I can check my exact version? Is this solved in the latest CVS version? Thanks in advance for your help. My logs: 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP[73299]: Got PDU: 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP PDU 0x81b4720 dump: 2008-11-10 15:15:56 [23865] [6] DEBUG: type_name: deliver_sm 2008-11-10 15:15:56 [23865] [6] DEBUG: command_id: 5 = 0x0005 2008-11-10 15:15:56 [23865] [6] DEBUG: command_status: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: sequence_number: 14 = 0x000e 2008-11-10 15:15:56 [23865] [6] DEBUG: service_type: NULL 2008-11-10 15:15:56 [23865] [6] DEBUG: source_addr_ton: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: source_addr_npi: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: source_addr: "3162945162" 2008-11-10 15:15:56 [23865] [6] DEBUG: dest_addr_ton: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: dest_addr_npi: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: destination_addr: "8090" 2008-11-10 15:15:56 [23865] [6] DEBUG: esm_class: 4 = 0x0004 2008-11-10 15:15:56 [23865] [6] DEBUG: protocol_id: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: priority_flag: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: schedule_delivery_time: NULL 2008-11-10 15:15:56 [23865] [6] DEBUG: validity_period: NULL 2008-11-10 15:15:56 [23865] [6] DEBUG: registered_delivery: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: replace_if_present_flag: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: data_coding: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: sm_default_msg_id: 0 = 0x 2008-11-10 15:15:56 [23865] [6] DEBUG: sm_length: 70 = 0x0046 2008-11-10 15:15:56 [23865] [6] DEBUG: short_message: 2008-11-10 15:15:56 [23865] [6] DEBUG:Octet string at 0x81b3bb8: 2008-11-10 15:15:56 [23865] [6] DEBUG: len: 70 2008-11-10 15:15:56 [23865] [6] DEBUG: size: 71 2008-11-10 15:15:56 [23865] [6] DEBUG: immutable: 0 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 69 64 3a 30 38 36 34 38 31 30 38 38 36 20 73 75 id:0864810886 su 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 62 6d 69 74 20 64 61 74 65 3a 30 38 31 31 31 30 bmit date:081110 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 30 39 31 35 20 64 6f 6e 65 20 64 61 74 65 3a 30 0915 done date:0 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 38 31 31 31 30 30 39 31 35 20 73 74 61 74 3a 44 811100915 stat:D 2008-11-10 15:15:56 [23865] [6] DEBUG: data: 45 4c 49 56 52 44 ELIVRD 2008-11-10 15:15:56 [23865] [6] DEBUG:Octet string dump ends. 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP PDU dump ends. 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP[73299] handle_pdu, got DLR 2008-11-10 15:15:56 [23865] [6] DEBUG: SMPP[73299]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2008-11-10 15:15:56 [23865] [6] DEBUG: DLR[mysql]: Looking for DLR smsc=73299, ts=864810886, dst=3162945162, type=2 2008-11-10 15:15:56 [23865] [6] DEBUG: sql: SELECT mask, service, url, source, destination, boxc FROM dlr WHERE smsc='73299' AND ts='864810886'; 2008-11-10 15:15:56 [23865] [6] DEBUG: Found entry, row[0]=31, row[1]=mbridges, row[2]=http://login.mobilebridges.com/sms/mo/quattromobile_smpp/DLR.php5?mtid=71341386&msgid=%I&smsc=%i&ts=%T&sender=%q&receiver=%Q&status=%d&application=qm_co_8090&answer=%A, row[3]=8090, row[4]=573162945162 row[5]= 2008-11-10 15:15:56 [23865] [6] DEBUG: DLR[mysql]: created DLR message for URL <http://login.mobilebridges.com/sms/mo/quattromobile_smpp/DLR.php5?mtid=71341386&msgid=%I&smsc=%i&ts=%T&sender=%q&receiver=%Q&status=%d&application=qm_co_8090&answer=%A> 2008-11-10 15:15:56 [23865] [6] DEBUG: removing DLR from database
Re: Couldnot parse DLR
On Fri, Oct 3, 2008 at 2:24 PM, Kyriacos Sakkas <[EMAIL PROTECTED]> wrote: > 2008-10-03 15:12:16 [6363] [20] ERROR: SMPP[SMSCID]: got DLR but could > not find message or was not interested in it id<> dst<3069">, > type<2> >From the logs I see that you're using sql as a DLR storage. The error that you are reporting usualy happens when kannel looses the track of the message (restarting kannel when using internal dlr storage or not inserting the dlr data in the database) First make sure that the drl data is wirtten to the database. Turn off the phone send a message, and check if the dlr is inserted in the database ;) > 2008-10-03 15:12:16 [6363] [20] DEBUG: SMPP[SMSCID]: Couldnot parse DLR > string sscanf way,fallback to old way. Please report! It seems to me that you are not receiving the complete DLR message from the operator or it is in some format that kannel doesn't know how to parse. Monitor your http traffic towards the SMSC and check if you are receiving complete DLR report from the operator and check its form. You can use wireshark (ethereal) [1] to monitor the traffic. here is a nice tutorial [2] how to do it. [1] http://www.wireshark.org/ [2] http://www.smssolutions.net/tutorials/smpp/smppmonitoring/ CHEERS, Jovan
Couldnot parse DLR
] DEBUG: sequence_number: 1611 = 0x064b 2008-10-03 15:12:16 [6363] [20] DEBUG: service_type: NULL 2008-10-03 15:12:16 [6363] [20] DEBUG: source_addr_ton: 1 = 0x0001 2008-10-03 15:12:16 [6363] [20] DEBUG: source_addr_npi: 1 = 0x0001 2008-10-03 15:12:16 [6363] [20] DEBUG: source_addr: "3069" 2008-10-03 15:12:16 [6363] [20] DEBUG: dest_addr_ton: 2 = 0x0002 2008-10-03 15:12:16 [6363] [20] DEBUG: dest_addr_npi: 1 = 0x0001 2008-10-03 15:12:16 [6363] [20] DEBUG: destination_addr: "5" 2008-10-03 15:12:16 [6363] [20] DEBUG: esm_class: 4 = 0x0004 2008-10-03 15:12:16 [6363] [20] DEBUG: protocol_id: 0 = 0x 2008-10-03 15:12:16 [6363] [20] DEBUG: priority_flag: 0 = 0x 2008-10-03 15:12:16 [6363] [20] DEBUG: schedule_delivery_time: NULL 2008-10-03 15:12:16 [6363] [20] DEBUG: validity_period: NULL 2008-10-03 15:12:16 [6363] [20] DEBUG: registered_delivery: 0 = 0x 2008-10-03 15:12:16 [6363] [20] DEBUG: replace_if_present_flag: 0 = 0x 2008-10-03 15:12:16 [6363] [20] DEBUG: data_coding: 0 = 0x 2008-10-03 15:12:16 [6363] [20] DEBUG: sm_default_msg_id: 0 = 0x 2008-10-03 15:12:16 [6363] [20] DEBUG: sm_length: 66 = 0x0042 2008-10-03 15:12:16 [6363] [20] DEBUG: short_message: 2008-10-03 15:12:16 [6363] [20] DEBUG:Octet string at 0x82018a8: 2008-10-03 15:12:16 [6363] [20] DEBUG: len: 66 2008-10-03 15:12:16 [6363] [20] DEBUG: size: 67 2008-10-03 15:12:16 [6363] [20] DEBUG: immutable: 0 2008-10-03 15:12:16 [6363] [20] DEBUG: data: 32 39 32 32 38 34 39 38 36 36 30 30 31 30 30 31 2922849866001001 2008-10-03 15:12:16 [6363] [20] DEBUG: data: 30 38 31 30 30 33 31 35 31 32 30 38 31 30 30 33 0810031512081003 2008-10-03 15:12:16 [6363] [20] DEBUG: data: 31 35 31 32 44 45 4c 49 56 52 44 30 30 30 54 45 1512DELIVRD000TE 2008-10-03 15:12:16 [6363] [20] DEBUG: data: 18 54 20 41 16 4f 3a 20 35 34 35 30 30 20 18 54 .T A.O: 5 .T 2008-10-03 15:12:16 [6363] [20] DEBUG: data: 4f 20 O 2008-10-03 15:12:16 [6363] [20] DEBUG: Octet string dump ends. 2008-10-03 15:12:16 [6363] [20] DEBUG: SMPP PDU dump ends. 2008-10-03 15:12:16 [6363] [20] DEBUG: SMPP[SMSCID] handle_pdu, got DLR 2008-10-03 15:12:16 [6363] [20] DEBUG: SMPP[SMSCID]: Couldnot parse DLR string sscanf way,fallback to old way. Please report! 2008-10-03 15:12:16 [6363] [20] ERROR: SMPP[SMSCID]: got DLR but could not find message or was not interested in it id<> dst<3069">, type<2> 2008-10-03 15:12:16 [6363] [20] DEBUG: SMPP[SMSCID]: Sending PDU: 2008-10-03 15:12:16 [6363] [20] DEBUG: SMPP PDU 0x81c9cb8 dump: 2008-10-03 15:12:16 [6363] [20] DEBUG: type_name: deliver_sm_resp 2008-10-03 15:12:16 [6363] [20] DEBUG: command_id: 2147483653 = 0x8005 2008-10-03 15:12:16 [6363] [20] DEBUG: command_status: 0 = 0x 2008-10-03 15:12:16 [6363] [20] DEBUG: sequence_number: 1611 = 0x064b 2008-10-03 15:12:16 [6363] [20] DEBUG: message_id: NULL 2008-10-03 15:12:16 [6363] [20] DEBUG: SMPP PDU dump ends. -- Kyriacos Sakkas Development Team Netsmart Tel: + 357 22 452565 Fax: + 357 22 452566 Email: [EMAIL PROTECTED] http://www.netsmart.com.cy Taking Business to a New Level! ** Confidentiality Notice: The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution, or copying of this email message is strictly prohibited. If you think that you have received this email message in error, please email the sender at [EMAIL PROTECTED] **
