Re: Problem with SMPP 3.3 SMSC in message delivery
Ritesh Shah wrote: The Kannel 1.0.3 version works fine, but the later versions give this error when the gw. receives the msg. (got DLR but could not find message or was not interested in it) This prob. is happening only with logica SMSC, I haven't faced this issue with any other SMSC. try the current cvs snapshot or the upcoming 1.3.1 version. It contains some fixes for the SMPP optional parameter parsing code. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Problem with SMPP 3.3 SMSC in message delivery
Thanks a lot, the CVS version solved the prob. Regards Ritesh - Original Message - From: Stipe Tolj [EMAIL PROTECTED] To: Ritesh Shah [EMAIL PROTECTED] Cc: Kannel [EMAIL PROTECTED] Sent: Friday, February 14, 2003 4:44 AM Subject: Re: Problem with SMPP 3.3 SMSC in message delivery Ritesh Shah wrote: The Kannel 1.0.3 version works fine, but the later versions give this error when the gw. receives the msg. (got DLR but could not find message or was not interested in it) This prob. is happening only with logica SMSC, I haven't faced this issue with any other SMSC. try the current cvs snapshot or the upcoming 1.3.1 version. It contains some fixes for the SMPP optional parameter parsing code. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Problem with SMPP 3.3 SMSC in message delivery
Hi , The Kannel 1.0.3 version works fine, but the later versions give this error when the gw. receives the msg. (got DLR but could not find message or was not interested in it) This prob. is happening only with logica SMSC, I haven't faced this issue with any other SMSC. 2003-02-12 01:00:55 [5] DEBUG: SMPP PDU 0x811eb20 dump:2003-02-12 01:00:55 [5] DEBUG: type_name: deliver_sm2003-02-12 01:00:55 [5] DEBUG: command_id: 5 = 0x00052003-02-12 01:00:55 [5] DEBUG: command_status: 0 = 0x2003-02-12 01:00:55 [5] DEBUG: sequence_number: 3 = 0x00032003-02-12 01:00:55 [5] DEBUG: service_type: NULL2003-02-12 01:00:55 [5] DEBUG: source_addr_ton: 1 = 0x00012003-02-12 01:00:55 [5] DEBUG: source_addr_npi: 1 = 0x00012003-02-12 01:00:55 [5] DEBUG: source_addr: "12323434344"2003-02-12 01:00:55 [5] DEBUG: dest_addr_ton: 1 = 0x00012003-02-12 01:00:55 [5] DEBUG: dest_addr_npi: 1 = 0x00012003-02-12 01:00:55 [5] DEBUG: destination_addr: "1234567892"2003-02-12 01:00:55 [5] DEBUG: esm_class: 2 = 0x00022003-02-12 01:00:55 [5] DEBUG: protocol_id: 0 = 0x2003-02-12 01:00:55 [5] DEBUG: priority_flag: 0 = 0x2003-02-12 01:00:55 [5] DEBUG: schedule_delivery_time: NULL2003-02-12 01:00:55 [5] DEBUG: validity_period: NULL2003-02-12 01:00:55 [5] DEBUG: registered_delivery: 0 = 0x2003-02-12 01:00:55 [5] DEBUG: replace_if_present_flag: 0 = 0x2003-02-12 01:00:55 [5] DEBUG: data_coding: 0 = 0x2003-02-12 01:00:55 [5] DEBUG: sm_default_msg_id: 0 = 0x2003-02-12 01:00:55 [5] DEBUG: sm_length: 15 = 0x000f2003-02-12 01:00:55 [5] DEBUG: short_message: "another message"2003-02-12 01:00:55 [5] DEBUG: SMPP PDU dump ends.2003-02-12 01:00:55 [5] DEBUG: SMPP[tt] handle_pdu, got DLR2003-02-12 01:00:55 [5] ERROR: SMPP[tt]: got DLR but could not find message or was not interested in it2003-02-12 01:00:55 [5] DEBUG: SMPP[tt]: Sending PDU:2003-02-12 01:00:55 [5] DEBUG: SMPP PDU 0x811ecc0 dump:2003-02-12 01:00:55 [5] DEBUG: type_name: deliver_sm_resp2003-02-12 01:00:55 [5] DEBUG: command_id: 2147483653 = 0x80052003-02-12 01:00:55 [5] DEBUG: command_status: 0 = 0x2003-02-12 01:00:55 [5] DEBUG: sequence_number: 3 = 0x00032003-02-12 01:00:55 [5] DEBUG: message_id: NULL2003-02-12 01:00:55 [5] DEBUG: SMPP PDU dump ends.2003-02-12 01:01:03 [5] DEBUG: SMPP[tt]: Sending enquire link:2003-02-12 01:01:03 [5] DEBUG: SMPP PDU 0x811ecc0 dump:2003-02-12 01:01:03 [5] DEBUG: type_name: enquire_link2003-02-12 01:01:03 [5] DEBUG: command_id: 21 = 0x00152003-02-12 01:01:03 [5] DEBUG: command_status: 0 = 0x2003-02-12 01:01:03 [5] DEBUG: sequence_number: 24 = 0x00182003-02-12 01:01:03 [5] DEBUG: SMPP PDU dump ends. Regards Ritesh
Problem with SMPP 3.3 SMSC in message delivery
Hi YJ, How did u solved the prob. of Incomplete replies I am trying to connect with logica smsc. I am also getting the same prob. which The Kannel bearer's log text indicated that it: SMPP handle_pdu Got DELIVER REPORTBut then it followed up with ERROR:Got DELIV REPORT but couldnt find messageor was not interested in it For deliver_sm I am getting service_type "NOREP" (No Reply), We have defined the system-type = Ext. ###deliver_sm dump 2003-01-09 19:44:28 [6] DEBUG: type_name: deliver_sm2003-01-09 19:44:28 [6] DEBUG: command_id: 5 = 0x00052003-01-09 19:44:28 [6] DEBUG: command_status: 0 = 0x2003-01-09 19:44:28 [6] DEBUG: sequence_number: 3 = 0x00032003-01-09 19:44:28 [6] DEBUG: service_type: "NOREP"2003-01-09 19:44:28 [6] DEBUG: source_addr_ton: 1 = 0x00012003-01-09 19:44:28 [6] DEBUG: source_addr_npi: 1 = 0x00012003-01-09 19:44:28 [6] DEBUG: source_addr: "919029392923"2003-01-09 19:44:28 [6] DEBUG: dest_addr_ton: 0 = 0x2003-01-09 19:44:28 [6] DEBUG: dest_addr_npi: 1 = 0x00012003-01-09 19:44:28 [6] DEBUG: destination_addr: "1234"## and then there is no submit_sm for this msg. following is the dump of bind_transmitter and bind_receiver ## 2003-01-09 17:37:41 [5] DEBUG: type_name: bind_transmitter2003-01-09 17:37:41 [5] DEBUG: command_id: 2 = 0x00022003-01-09 17:37:41 [5] DEBUG: command_status: 0 = 0x2003-01-09 17:37:41 [5] DEBUG: sequence_number: 0 = 0x2003-01-09 17:37:41 [5] DEBUG: system_id: "test"2003-01-09 17:37:41 [5] DEBUG: password: "test"2003-01-09 17:37:41 [5] DEBUG: system_type: "Ext"2003-01-09 17:37:41 [5] DEBUG: interface_version: 51 = 0x00332003-01-09 17:37:41 [5] DEBUG: addr_ton: 0 = 0x2003-01-09 17:37:41 [5] DEBUG: addr_npi: 1 = 0x00012003-01-09 17:37:41 [5] DEBUG: address_range: "^1234" 2003-01-09 17:37:41 [6] DEBUG: type_name: bind_receiver2003-01-09 17:37:41 [6] DEBUG: command_id: 1 = 0x00012003-01-09 17:37:41 [6] DEBUG: command_status: 0 = 0x2003-01-09 17:37:41 [6] DEBUG: sequence_number: 1 = 0x00012003-01-09 17:37:41 [6] DEBUG: system_id: "test"2003-01-09 17:37:41 [6] DEBUG: password: "test"2003-01-09 17:37:41 [6] DEBUG: system_type: "Ext"2003-01-09 17:37:41 [6] DEBUG: interface_version: 51 = 0x00332003-01-09 17:37:41 [6] DEBUG: addr_ton: 1 = 0x00012003-01-09 17:37:41 [6] DEBUG: addr_npi: 1 = 0x00012003-01-09 17:37:41 [6] DEBUG: address_range: "^1234" # This prob. is only coming with logica smsc, there was no prob. connecting with other types of SMSC's. RegardsRitesh Shah
Re: Problem with SMPP 3.3 SMSC in message delivery
Hi please give more of the log file, we need to see the full deliver_sm PDU dump nisan At 12:09 AM 1/10/03 +0530, Ritesh Shah wrote: Hi YJ, How did u solved the prob. of Incomplete replies I am trying to connect with logica smsc. I am also getting the same prob. which The Kannel bearer's log text indicated that it: SMPP handle_pdu Got DELIVER REPORT But then it followed up with ERROR: Got DELIV REPORT but couldnt find message or was not interested in it For deliver_sm I am getting service_type NOREP (No Reply), We have defined the system-type = Ext. ###deliver_sm dump 2003-01-09 19:44:28 [6] DEBUG: type_name: deliver_sm 2003-01-09 19:44:28 [6] DEBUG: command_id: 5 = 0x0005 2003-01-09 19:44:28 [6] DEBUG: command_status: 0 = 0x 2003-01-09 19:44:28 [6] DEBUG: sequence_number: 3 = 0x0003 2003-01-09 19:44:28 [6] DEBUG: service_type: NOREP 2003-01-09 19:44:28 [6] DEBUG: source_addr_ton: 1 = 0x0001 2003-01-09 19:44:28 [6] DEBUG: source_addr_npi: 1 = 0x0001 2003-01-09 19:44:28 [6] DEBUG: source_addr: 919029392923 2003-01-09 19:44:28 [6] DEBUG: dest_addr_ton: 0 = 0x 2003-01-09 19:44:28 [6] DEBUG: dest_addr_npi: 1 = 0x0001 2003-01-09 19:44:28 [6] DEBUG: destination_addr: 1234 ## and then there is no submit_sm for this msg. following is the dump of bind_transmitter and bind_receiver ## 2003-01-09 17:37:41 [5] DEBUG: type_name: bind_transmitter 2003-01-09 17:37:41 [5] DEBUG: command_id: 2 = 0x0002 2003-01-09 17:37:41 [5] DEBUG: command_status: 0 = 0x 2003-01-09 17:37:41 [5] DEBUG: sequence_number: 0 = 0x 2003-01-09 17:37:41 [5] DEBUG: system_id: test 2003-01-09 17:37:41 [5] DEBUG: password: test 2003-01-09 17:37:41 [5] DEBUG: system_type: Ext 2003-01-09 17:37:41 [5] DEBUG: interface_version: 51 = 0x0033 2003-01-09 17:37:41 [5] DEBUG: addr_ton: 0 = 0x 2003-01-09 17:37:41 [5] DEBUG: addr_npi: 1 = 0x0001 2003-01-09 17:37:41 [5] DEBUG: address_range: ^1234 2003-01-09 17:37:41 [6] DEBUG: type_name: bind_receiver 2003-01-09 17:37:41 [6] DEBUG: command_id: 1 = 0x0001 2003-01-09 17:37:41 [6] DEBUG: command_status: 0 = 0x 2003-01-09 17:37:41 [6] DEBUG: sequence_number: 1 = 0x0001 2003-01-09 17:37:41 [6] DEBUG: system_id: test 2003-01-09 17:37:41 [6] DEBUG: password: test 2003-01-09 17:37:41 [6] DEBUG: system_type: Ext 2003-01-09 17:37:41 [6] DEBUG: interface_version: 51 = 0x0033 2003-01-09 17:37:41 [6] DEBUG: addr_ton: 1 = 0x0001 2003-01-09 17:37:41 [6] DEBUG: addr_npi: 1 = 0x0001 2003-01-09 17:37:41 [6] DEBUG: address_range: ^1234 # This prob. is only coming with logica smsc, there was no prob. connecting with other types of SMSC's. Regards Ritesh Shah
