Re: SMPP TLVs on bind_transceiver_resp and submit_sm_resp
Thank you Stipe! Will try it and reply to the devel list. Best regards, Paulo Correia On 21-01-2014 18:55, Stipe Tolj wrote: Am 20.01.2014 23:25, schrieb Paulo Correia: Hi! I'm trying to find out if there is a way to retrieve TLV data sent from a SMSC on the PDUs: * bind_transceiver_resp * submit_sm_resp I already defined the TLVs on the configuration and the log indicates kannel does receive the data, but how can I retrieve it to an external application? Here is an example from the log: 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x0210) 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 1 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x1401) 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 7 2014-01-20 18:26:42 [39688] [6] DEBUG: Found configured optional parameter `XXX_credit' 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU: 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU 0x7f893c001570 dump: 2014-01-20 18:26:42 [39688] [6] DEBUG: type_name: bind_transceiver_resp 2014-01-20 18:26:42 [39688] [6] DEBUG: command_id: 2147483657 = 0x8009 2014-01-20 18:26:42 [39688] [6] DEBUG: command_status: 0 = 0x 2014-01-20 18:26:42 [39688] [6] DEBUG: sequence_number: 1 = 0x0001 2014-01-20 18:26:42 [39688] [6] DEBUG: system_id: lnstsmpp 2014-01-20 18:26:42 [39688] [6] DEBUG: sc_interface_version: 52 = 0x0034 2014-01-20 18:26:42 [39688] [6] DEBUG: XXX_credit: 000 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU dump ends. ... 2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter tag (0x1401) 2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter length read as 7 2014-01-20 18:30:19 [39688] [6] DEBUG: Found configured optional parameter `XXX_credit' 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU: 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU 0x7f893c0014f0 dump: 2014-01-20 18:30:19 [39688] [6] DEBUG: type_name: submit_sm_resp 2014-01-20 18:30:19 [39688] [6] DEBUG: command_id: 2147483652 = 0x8004 2014-01-20 18:30:19 [39688] [6] DEBUG: command_status: 0 = 0x 2014-01-20 18:30:19 [39688] [6] DEBUG: sequence_number: 2 = 0x0002 2014-01-20 18:30:19 [39688] [6] DEBUG: message_id: 227b7cfd 2014-01-20 18:30:19 [39688] [6] DEBUG: XXX_credit: 10238900 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU dump ends. When the message that resulted on the submit_sm_resp was sent to kannel, I used a dlr-mask=31 and dlr-url with a parameter meta=%D but the first call to the URL, created by the submit_sm_resp (comes with the %A value as ACK/), came up with an empty meta value. I'm using kannel 1.5.0, svn r5065 on these tests and couldn't find any way that TLVs are processed on the given PDUs on the source code... this is NOT supported at the moment. The intermediate DLR SMSC SUCCESS does not handle any optional TVLs coming inside a submit_sm_resp PDU. I have submitted a patchset to the devel@ mailing list that supports this, at least for submit_sm_resp. I don't see a practical way to do it for the bind resp PDUs at the moment. See [Msg-Id: 52dec1f8.3090...@kannel.org] Please test the patchset and confirm in the mail thread on the devel@ mailing list. Moving the discussion to there, since it's development related. Stipe
Re: SMPP TLVs on bind_transceiver_resp and submit_sm_resp
Hi again, I missed to mention the TLV data I'm trying to get: * XXX_credit Best regards, Paulo Correia Em 20-01-2014 22:25, Paulo Correia escreveu: Hi! I'm trying to find out if there is a way to retrieve TLV data sent from a SMSC on the PDUs: * bind_transceiver_resp * submit_sm_resp I already defined the TLVs on the configuration and the log indicates kannel does receive the data, but how can I retrieve it to an external application? Here is an example from the log: 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x0210) 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 1 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x1401) 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 7 2014-01-20 18:26:42 [39688] [6] DEBUG: Found configured optional parameter `XXX_credit' 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU: 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU 0x7f893c001570 dump: 2014-01-20 18:26:42 [39688] [6] DEBUG: type_name: bind_transceiver_resp 2014-01-20 18:26:42 [39688] [6] DEBUG: command_id: 2147483657 = 0x8009 2014-01-20 18:26:42 [39688] [6] DEBUG: command_status: 0 = 0x 2014-01-20 18:26:42 [39688] [6] DEBUG: sequence_number: 1 = 0x0001 2014-01-20 18:26:42 [39688] [6] DEBUG: system_id: lnstsmpp 2014-01-20 18:26:42 [39688] [6] DEBUG: sc_interface_version: 52 = 0x0034 2014-01-20 18:26:42 [39688] [6] DEBUG: XXX_credit: 000 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU dump ends. ... 2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter tag (0x1401) 2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter length read as 7 2014-01-20 18:30:19 [39688] [6] DEBUG: Found configured optional parameter `XXX_credit' 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU: 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU 0x7f893c0014f0 dump: 2014-01-20 18:30:19 [39688] [6] DEBUG: type_name: submit_sm_resp 2014-01-20 18:30:19 [39688] [6] DEBUG: command_id: 2147483652 = 0x8004 2014-01-20 18:30:19 [39688] [6] DEBUG: command_status: 0 = 0x 2014-01-20 18:30:19 [39688] [6] DEBUG: sequence_number: 2 = 0x0002 2014-01-20 18:30:19 [39688] [6] DEBUG: message_id: 227b7cfd 2014-01-20 18:30:19 [39688] [6] DEBUG: XXX_credit: 10238900 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU dump ends. When the message that resulted on the submit_sm_resp was sent to kannel, I used a dlr-mask=31 and dlr-url with a parameter meta=%D but the first call to the URL, created by the submit_sm_resp (comes with the %A value as ACK/), came up with an empty meta value. I'm using kannel 1.5.0, svn r5065 on these tests and couldn't find any way that TLVs are processed on the given PDUs on the source code... Is there a way to retrieve these TLV values without a grep of the log files? Best regards, Paulo Correia
Re: SMPP TLVs on bind_transceiver_resp and submit_sm_resp
Am 20.01.2014 23:25, schrieb Paulo Correia: Hi! I'm trying to find out if there is a way to retrieve TLV data sent from a SMSC on the PDUs: * bind_transceiver_resp * submit_sm_resp I already defined the TLVs on the configuration and the log indicates kannel does receive the data, but how can I retrieve it to an external application? Here is an example from the log: 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x0210) 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 1 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x1401) 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 7 2014-01-20 18:26:42 [39688] [6] DEBUG: Found configured optional parameter `XXX_credit' 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU: 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU 0x7f893c001570 dump: 2014-01-20 18:26:42 [39688] [6] DEBUG: type_name: bind_transceiver_resp 2014-01-20 18:26:42 [39688] [6] DEBUG: command_id: 2147483657 = 0x8009 2014-01-20 18:26:42 [39688] [6] DEBUG: command_status: 0 = 0x 2014-01-20 18:26:42 [39688] [6] DEBUG: sequence_number: 1 = 0x0001 2014-01-20 18:26:42 [39688] [6] DEBUG: system_id: lnstsmpp 2014-01-20 18:26:42 [39688] [6] DEBUG: sc_interface_version: 52 = 0x0034 2014-01-20 18:26:42 [39688] [6] DEBUG: XXX_credit: 000 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU dump ends. ... 2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter tag (0x1401) 2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter length read as 7 2014-01-20 18:30:19 [39688] [6] DEBUG: Found configured optional parameter `XXX_credit' 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU: 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU 0x7f893c0014f0 dump: 2014-01-20 18:30:19 [39688] [6] DEBUG: type_name: submit_sm_resp 2014-01-20 18:30:19 [39688] [6] DEBUG: command_id: 2147483652 = 0x8004 2014-01-20 18:30:19 [39688] [6] DEBUG: command_status: 0 = 0x 2014-01-20 18:30:19 [39688] [6] DEBUG: sequence_number: 2 = 0x0002 2014-01-20 18:30:19 [39688] [6] DEBUG: message_id: 227b7cfd 2014-01-20 18:30:19 [39688] [6] DEBUG: XXX_credit: 10238900 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU dump ends. When the message that resulted on the submit_sm_resp was sent to kannel, I used a dlr-mask=31 and dlr-url with a parameter meta=%D but the first call to the URL, created by the submit_sm_resp (comes with the %A value as ACK/), came up with an empty meta value. I'm using kannel 1.5.0, svn r5065 on these tests and couldn't find any way that TLVs are processed on the given PDUs on the source code... this is NOT supported at the moment. The intermediate DLR SMSC SUCCESS does not handle any optional TVLs coming inside a submit_sm_resp PDU. I have submitted a patchset to the devel@ mailing list that supports this, at least for submit_sm_resp. I don't see a practical way to do it for the bind resp PDUs at the moment. See [Msg-Id: 52dec1f8.3090...@kannel.org] Please test the patchset and confirm in the mail thread on the devel@ mailing list. Moving the discussion to there, since it's development related. 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 ---
SMPP TLVs on bind_transceiver_resp and submit_sm_resp
Hi! I'm trying to find out if there is a way to retrieve TLV data sent from a SMSC on the PDUs: * bind_transceiver_resp * submit_sm_resp I already defined the TLVs on the configuration and the log indicates kannel does receive the data, but how can I retrieve it to an external application? Here is an example from the log: 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x0210) 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 1 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter tag (0x1401) 2014-01-20 18:26:42 [39688] [6] DEBUG: Optional parameter length read as 7 2014-01-20 18:26:42 [39688] [6] DEBUG: Found configured optional parameter `XXX_credit' 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU: 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU 0x7f893c001570 dump: 2014-01-20 18:26:42 [39688] [6] DEBUG: type_name: bind_transceiver_resp 2014-01-20 18:26:42 [39688] [6] DEBUG: command_id: 2147483657 = 0x8009 2014-01-20 18:26:42 [39688] [6] DEBUG: command_status: 0 = 0x 2014-01-20 18:26:42 [39688] [6] DEBUG: sequence_number: 1 = 0x0001 2014-01-20 18:26:42 [39688] [6] DEBUG: system_id: lnstsmpp 2014-01-20 18:26:42 [39688] [6] DEBUG: sc_interface_version: 52 = 0x0034 2014-01-20 18:26:42 [39688] [6] DEBUG: XXX_credit: 000 2014-01-20 18:26:42 [39688] [6] DEBUG: SMPP PDU dump ends. ... 2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter tag (0x1401) 2014-01-20 18:30:19 [39688] [6] DEBUG: Optional parameter length read as 7 2014-01-20 18:30:19 [39688] [6] DEBUG: Found configured optional parameter `XXX_credit' 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP[XXX-XX_001]: Got PDU: 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU 0x7f893c0014f0 dump: 2014-01-20 18:30:19 [39688] [6] DEBUG: type_name: submit_sm_resp 2014-01-20 18:30:19 [39688] [6] DEBUG: command_id: 2147483652 = 0x8004 2014-01-20 18:30:19 [39688] [6] DEBUG: command_status: 0 = 0x 2014-01-20 18:30:19 [39688] [6] DEBUG: sequence_number: 2 = 0x0002 2014-01-20 18:30:19 [39688] [6] DEBUG: message_id: 227b7cfd 2014-01-20 18:30:19 [39688] [6] DEBUG: XXX_credit: 10238900 2014-01-20 18:30:19 [39688] [6] DEBUG: SMPP PDU dump ends. When the message that resulted on the submit_sm_resp was sent to kannel, I used a dlr-mask=31 and dlr-url with a parameter meta=%D but the first call to the URL, created by the submit_sm_resp (comes with the %A value as ACK/), came up with an empty meta value. I'm using kannel 1.5.0, svn r5065 on these tests and couldn't find any way that TLVs are processed on the given PDUs on the source code... Is there a way to retrieve these TLV values without a grep of the log files? Best regards, Paulo Correia