Re: [PATCH] SMPP Optional Parameters
Hi, the warnings while compile are OK. When kannel segfaults? when compile or starting kannel? If when starting kannel please provide backtrace. Kyriacos Sakkas wrote: Minus attachments. Kyriacos Sakkas wrote: Hi, Trying to compile against cvs, I segfault. Diring compile the only error is: gw/meta_data.c: In function âmeta_data_set_valueâ: gw/meta_data.c:338: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c:340: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c:341: warning: passing argument 2 of âdict_getâ discards qualifiers from pointer target type gw/meta_data.c:343: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c: In function âmeta_data_get_valueâ: gw/meta_data.c:368: warning: passing argument 2 of âdict_removeâ discards qualifiers from pointer target type -- Thanks, Alex
Re: [PATCH] SMPP Optional Parameters
Hi Alexander, So us to be clear, me programing credential are not great, so I will give the backtrace a go, but if you thing some specials parameters to gdb would help, please let me know. Anyway the segfault is at run time, I will try and post a backtrace shortly. Kyriacos Sakkas Alexander Malysh wrote: Hi, the warnings while compile are OK. When kannel segfaults? when compile or starting kannel? If when starting kannel please provide backtrace. Kyriacos Sakkas wrote: Minus attachments. Kyriacos Sakkas wrote: Hi, Trying to compile against cvs, I segfault. Diring compile the only error is: gw/meta_data.c: In function âmeta_data_set_valueâ: gw/meta_data.c:338: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c:340: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c:341: warning: passing argument 2 of âdict_getâ discards qualifiers from pointer target type gw/meta_data.c:343: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c: In function âmeta_data_get_valueâ: gw/meta_data.c:368: warning: passing argument 2 of âdict_removeâ discards qualifiers from pointer target type -- 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] **
Re: [PATCH] SMPP Optional Parameters
Hi, I just recompiled, and it looks stable, the difference was that up to now I had been using --with-mysql on the configure, which to be honest I did not need in this instance, just a force of habit. Anyway I will now test and if anything comes up I will let you know, but it does look like the problem lies there. As soon as I have some time I will try and dig a bit more into this. Kyriacos Alexander Malysh wrote: Hi, the warnings while compile are OK. When kannel segfaults? when compile or starting kannel? If when starting kannel please provide backtrace. Kyriacos Sakkas wrote: Minus attachments. Kyriacos Sakkas wrote: Hi, Trying to compile against cvs, I segfault. Diring compile the only error is: gw/meta_data.c: In function âmeta_data_set_valueâ: gw/meta_data.c:338: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c:340: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c:341: warning: passing argument 2 of âdict_getâ discards qualifiers from pointer target type gw/meta_data.c:343: warning: passing argument 2 of âdict_putâ discards qualifiers from pointer target type gw/meta_data.c: In function âmeta_data_get_valueâ: gw/meta_data.c:368: warning: passing argument 2 of âdict_removeâ discards qualifiers from pointer target type -- 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] **
Re: [PATCH] SMPP Optional Parameters
If my packet capturing is correct, everything is parsed ok, but the TLVs do not get added to the PDU. Also my log file: 2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU 0x667eb0 dump: 2007-11-26 15:58:08 [4930] [6] DEBUG: type_name: enquire_link_resp 2007-11-26 15:58:08 [4930] [6] DEBUG: command_id: 2147483669 = 0x8015 2007-11-26 15:58:08 [4930] [6] DEBUG: command_status: 0 = 0x 2007-11-26 15:58:08 [4930] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU dump ends. 2007-11-26 15:58:13 [4930] [17] DEBUG: boxc_receiver: sms received 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced source addr ton = 3, source add npi = 9 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-26 15:58:13 [4930] [6] DEBUG: new group created `smpp-tlv' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBbilling' value=`sub' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBoperator' value=`31003' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBcontentType' value=`100' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBcommand' value=`START' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBsubDate' value=`1196085364000' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBserviceId' value=`' 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Sending PDU: 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump: 2007-11-26 15:58:13 [4930] [6] DEBUG: type_name: submit_sm 2007-11-26 15:58:13 [4930] [6] DEBUG: command_id: 4 = 0x0004 2007-11-26 15:58:13 [4930] [6] DEBUG: command_status: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: sequence_number: 6 = 0x0006 2007-11-26 15:58:13 [4930] [6] DEBUG: service_type: NULL 2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_npi: 9 = 0x0009 2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr: 28444 2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-26 15:58:13 [4930] [6] DEBUG: destination_addr: 1X 2007-11-26 15:58:13 [4930] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-26 15:58:13 [4930] [6] DEBUG: protocol_id: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: priority_flag: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: schedule_delivery_time: NULL 2007-11-26 15:58:13 [4930] [6] DEBUG: validity_period: NULL 2007-11-26 15:58:13 [4930] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-26 15:58:13 [4930] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: data_coding: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: sm_length: 8 = 0x0008 2007-11-26 15:58:13 [4930] [6] DEBUG: short_message: CONTENT0 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU dump ends. 2007-11-26 15:58:13 [4930] [17] DEBUG: send_msg: sending msg to boxc: smsc4 2007-11-26 15:58:13 [4930] [17] ERROR: Error reading from fd 46: 2007-11-26 15:58:13 [4930] [17] ERROR: System error 104: Connection reset by peer 2007-11-26 15:58:13 [4930] [17] ERROR: Connection to box 127.0.0.1 broke. 2007-11-26 15:58:13 [4930] [18] DEBUG: send_msg: sending msg to boxc: smsc4 2007-11-26 15:58:13 [4930] [18] ERROR: Error writing 16 octets to fd 46: 2007-11-26 15:58:13 [4930] [18] ERROR: System error 32: Broken pipe 2007-11-26 15:58:13 [4930] [18] ERROR: Couldn't write Msg to box 127.0.0.1, disconnecting 2007-11-26 15:58:13 [4930] [18] DEBUG: Thread 18 (gw/bb_boxc.c:boxc_sender) terminates. 2007-11-26 15:58:13 [4930] [17] ERROR: Error writing 16 octets to fd 46: 2007-11-26 15:58:13 [4930] [17] ERROR: System error 32: Broken pipe 2007-11-26 15:58:13 [4930] [17] DEBUG: Thread 17 (gw/bb_boxc.c:function) terminates. 2007-11-26 15:58:14 [4930] [6] WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL. 2007-11-26 15:58:14 [4930] [6] DEBUG: SMPP[mblox28444]: Got PDU: 2007-11-26 15:58:14 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump: 2007-11-26 15:58:14 [4930] [6] DEBUG: type_name: submit_sm_resp 2007-11-26 15:58:14 [4930] [6] DEBUG: command_id: 2147483652 = 0x8004 2007-11-26 15:58:14 [4930] [6] DEBUG: command_status: 1066 = 0x042a 2007-11-26 15:58:14 [4930] [6] DEBUG: sequence_number: 6 = 0x0006 2007-11-26 15:58:14 [4930] [6] DEBUG: message_id: NULL 2007-11-26 15:58:14 [4930] [6] DEBUG: SMPP PDU dump ends. 2007-11-26 15:58:14 [4930] [6] ERROR: SMPP[mblox28444]: SMSC returned error code 0x042a (Vendor-specific error, please refer to your SMPP provider) in response to submit_sm. 2007-11-26 15:58:14 [4930] [6] DEBUG: SMSC[mblox28444]: creating DLR message 2007-11-26 15:58:14 [4930] [6] DEBUG: SMSC[mblox28444]: DLR =
Re: [PATCH] SMPP Optional Parameters
Hi, I suppose you didn't defined TLVs in the config and group in meta_data named smpp instead of smpp-tlv. Example: In the config group = smpp-tlv name = MBbilling tag = 0x1601 type = integer|nulterminated|octetstring length = 4 meta_data=?smpp?MBbilling=XXX... Kyriacos Sakkas wrote: If my packet capturing is correct, everything is parsed ok, but the TLVs do not get added to the PDU. Also my log file: 2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU 0x667eb0 dump: 2007-11-26 15:58:08 [4930] [6] DEBUG: type_name: enquire_link_resp 2007-11-26 15:58:08 [4930] [6] DEBUG: command_id: 2147483669 = 0x8015 2007-11-26 15:58:08 [4930] [6] DEBUG: command_status: 0 = 0x 2007-11-26 15:58:08 [4930] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU dump ends. 2007-11-26 15:58:13 [4930] [17] DEBUG: boxc_receiver: sms received 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced source addr ton = 3, source add npi = 9 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-26 15:58:13 [4930] [6] DEBUG: new group created `smpp-tlv' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBbilling' value=`sub' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBoperator' value=`31003' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBcontentType' value=`100' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBcommand' value=`START' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBsubDate' value=`1196085364000' 2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBserviceId' value=`' 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Sending PDU: 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump: 2007-11-26 15:58:13 [4930] [6] DEBUG: type_name: submit_sm 2007-11-26 15:58:13 [4930] [6] DEBUG: command_id: 4 = 0x0004 2007-11-26 15:58:13 [4930] [6] DEBUG: command_status: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: sequence_number: 6 = 0x0006 2007-11-26 15:58:13 [4930] [6] DEBUG: service_type: NULL 2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_npi: 9 = 0x0009 2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr: 28444 2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-26 15:58:13 [4930] [6] DEBUG: destination_addr: 1X 2007-11-26 15:58:13 [4930] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-26 15:58:13 [4930] [6] DEBUG: protocol_id: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: priority_flag: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: schedule_delivery_time: NULL 2007-11-26 15:58:13 [4930] [6] DEBUG: validity_period: NULL 2007-11-26 15:58:13 [4930] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-26 15:58:13 [4930] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: data_coding: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-26 15:58:13 [4930] [6] DEBUG: sm_length: 8 = 0x0008 2007-11-26 15:58:13 [4930] [6] DEBUG: short_message: CONTENT0 2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU dump ends. 2007-11-26 15:58:13 [4930] [17] DEBUG: send_msg: sending msg to boxc: smsc4 2007-11-26 15:58:13 [4930] [17] ERROR: Error reading from fd 46: 2007-11-26 15:58:13 [4930] [17] ERROR: System error 104: Connection reset by peer 2007-11-26 15:58:13 [4930] [17] ERROR: Connection to box 127.0.0.1 broke. 2007-11-26 15:58:13 [4930] [18] DEBUG: send_msg: sending msg to boxc: smsc4 2007-11-26 15:58:13 [4930] [18] ERROR: Error writing 16 octets to fd 46: 2007-11-26 15:58:13 [4930] [18] ERROR: System error 32: Broken pipe 2007-11-26 15:58:13 [4930] [18] ERROR: Couldn't write Msg to box 127.0.0.1, disconnecting 2007-11-26 15:58:13 [4930] [18] DEBUG: Thread 18 (gw/bb_boxc.c:boxc_sender) terminates. 2007-11-26 15:58:13 [4930] [17] ERROR: Error writing 16 octets to fd 46: 2007-11-26 15:58:13 [4930] [17] ERROR: System error 32: Broken pipe 2007-11-26 15:58:13 [4930] [17] DEBUG: Thread 17 (gw/bb_boxc.c:function) terminates. 2007-11-26 15:58:14 [4930] [6] WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL. 2007-11-26 15:58:14 [4930] [6] DEBUG: SMPP[mblox28444]: Got PDU: 2007-11-26 15:58:14 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump: 2007-11-26 15:58:14 [4930] [6] DEBUG: type_name: submit_sm_resp 2007-11-26 15:58:14 [4930] [6] DEBUG: command_id: 2147483652 = 0x8004 2007-11-26 15:58:14 [4930] [6] DEBUG: command_status: 1066 = 0x042a 2007-11-26 15:58:14 [4930] [6] DEBUG: sequence_number: 6 = 0x0006 2007-11-26 15:58:14 [4930] [6] DEBUG: message_id: NULL 2007-11-26 15:58:14 [4930]
Re: [PATCH] SMPP Optional Parameters
Call: (Relevant values inserted of courser)
$post .= X-Kannel-Meta-Data:
?smpp-tlv?MBbilling=.$bill.MBoperator=.$operatorid.MBcontentType=100MBcommand=STARTMBsubDate=.date('U000').MBserviceId=XXX\r\n;
Definitions: (Had all as octstring, switched to nullterm for those with
no definite length)
group = smpp-tlv
name = MBoperator
tag = 0x1402
type = octetstring
length = 5
group = smpp-tlv
name = MBbilling
tag = 0x1403
type = octetstring
length = 5
group = smpp-tlv
name = MBsessionId
tag = 0x1404
type = nulterminated
length = 60
group = smpp-tlv
name = MBserviceDesc
tag = 0x1405
type = nulterminated
length = 10
group = smpp-tlv
name = MBcontentType
tag = 0x1406
type = nulterminated
length = 5
.
Alexander Malysh wrote:
Hi,
I suppose you didn't defined TLVs in the config and group in meta_data named
smpp instead of smpp-tlv. Example:
In the config
group = smpp-tlv
name = MBbilling
tag = 0x1601
type = integer|nulterminated|octetstring
length = 4
meta_data=?smpp?MBbilling=XXX...
Kyriacos Sakkas wrote:
If my packet capturing is correct, everything is parsed ok, but the TLVs
do not get added to the PDU.
Also my log file:
2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU 0x667eb0 dump:
2007-11-26 15:58:08 [4930] [6] DEBUG: type_name: enquire_link_resp
2007-11-26 15:58:08 [4930] [6] DEBUG: command_id: 2147483669 =
0x8015
2007-11-26 15:58:08 [4930] [6] DEBUG: command_status: 0 = 0x
2007-11-26 15:58:08 [4930] [6] DEBUG: sequence_number: 5 = 0x0005
2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU dump ends.
2007-11-26 15:58:13 [4930] [17] DEBUG: boxc_receiver: sms received
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced
source addr ton = 3, source add npi = 9
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced
dest addr ton = 1, dest add npi = 1
2007-11-26 15:58:13 [4930] [6] DEBUG: new group created `smpp-tlv'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBbilling'
value=`sub'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBoperator'
value=`31003'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv'
key=`MBcontentType' value=`100'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBcommand'
value=`START'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBsubDate'
value=`1196085364000'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBserviceId'
value=`'
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Sending PDU:
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump:
2007-11-26 15:58:13 [4930] [6] DEBUG: type_name: submit_sm
2007-11-26 15:58:13 [4930] [6] DEBUG: command_id: 4 = 0x0004
2007-11-26 15:58:13 [4930] [6] DEBUG: command_status: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sequence_number: 6 = 0x0006
2007-11-26 15:58:13 [4930] [6] DEBUG: service_type: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_ton: 3 = 0x0003
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_npi: 9 = 0x0009
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr: 28444
2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_ton: 1 = 0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_npi: 1 = 0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: destination_addr: 1X
2007-11-26 15:58:13 [4930] [6] DEBUG: esm_class: 3 = 0x0003
2007-11-26 15:58:13 [4930] [6] DEBUG: protocol_id: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: priority_flag: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: schedule_delivery_time: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: validity_period: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: registered_delivery: 1 =
0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: replace_if_present_flag: 0 =
0x
2007-11-26 15:58:13 [4930] [6] DEBUG: data_coding: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sm_default_msg_id: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sm_length: 8 = 0x0008
2007-11-26 15:58:13 [4930] [6] DEBUG: short_message: CONTENT0
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU dump ends.
2007-11-26 15:58:13 [4930] [17] DEBUG: send_msg: sending msg to boxc:
smsc4
2007-11-26 15:58:13 [4930] [17] ERROR: Error reading from fd 46:
2007-11-26 15:58:13 [4930] [17] ERROR: System error 104: Connection
reset by peer
2007-11-26 15:58:13 [4930] [17] ERROR: Connection to box 127.0.0.1
broke. 2007-11-26 15:58:13 [4930] [18] DEBUG: send_msg: sending msg to
boxc: smsc4
2007-11-26 15:58:13 [4930] [18] ERROR: Error writing 16 octets to fd 46:
2007-11-26 15:58:13 [4930] [18] ERROR: System error 32: Broken pipe
2007-11-26 15:58:13 [4930] [18] ERROR: Couldn't write Msg to box
127.0.0.1, disconnecting
2007-11-26 15:58:13 [4930] [18] DEBUG: Thread 18
(gw/bb_boxc.c:boxc_sender) terminates.
2007-11-26 15:58:13 [4930] [17] ERROR: Error writing 16 octets to fd 46:
2007-11-26
Re: [PATCH] SMPP Optional Parameters
That's what Alexandar just said...
You're using:
?smpp-tlv?MBbilling=
and it should be:
?smpp?MBbilling=
regards,
Juan
On Nov 26, 2007 12:33 PM, Kyriacos Sakkas [EMAIL PROTECTED] wrote:
Call: (Relevant values inserted of courser)
$post .= X-Kannel-Meta-Data:
?smpp-tlv?MBbilling=.$bill.MBoperator=.$operatorid.MBcontentType=100MBcommand=STARTMBsubDate=.date('U000').MBserviceId=XXX\r\n;
Definitions: (Had all as octstring, switched to nullterm for those with
no definite length)
group = smpp-tlv
name = MBoperator
tag = 0x1402
type = octetstring
length = 5
group = smpp-tlv
name = MBbilling
tag = 0x1403
type = octetstring
length = 5
group = smpp-tlv
name = MBsessionId
tag = 0x1404
type = nulterminated
length = 60
group = smpp-tlv
name = MBserviceDesc
tag = 0x1405
type = nulterminated
length = 10
group = smpp-tlv
name = MBcontentType
tag = 0x1406
type = nulterminated
length = 5
.
Alexander Malysh wrote:
Hi,
I suppose you didn't defined TLVs in the config and group in meta_data named
smpp instead of smpp-tlv. Example:
In the config
group = smpp-tlv
name = MBbilling
tag = 0x1601
type = integer|nulterminated|octetstring
length = 4
meta_data=?smpp?MBbilling=XXX...
Kyriacos Sakkas wrote:
If my packet capturing is correct, everything is parsed ok, but the TLVs
do not get added to the PDU.
Also my log file:
2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU 0x667eb0 dump:
2007-11-26 15:58:08 [4930] [6] DEBUG: type_name: enquire_link_resp
2007-11-26 15:58:08 [4930] [6] DEBUG: command_id: 2147483669 =
0x8015
2007-11-26 15:58:08 [4930] [6] DEBUG: command_status: 0 = 0x
2007-11-26 15:58:08 [4930] [6] DEBUG: sequence_number: 5 = 0x0005
2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU dump ends.
2007-11-26 15:58:13 [4930] [17] DEBUG: boxc_receiver: sms received
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced
source addr ton = 3, source add npi = 9
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced
dest addr ton = 1, dest add npi = 1
2007-11-26 15:58:13 [4930] [6] DEBUG: new group created `smpp-tlv'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBbilling'
value=`sub'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBoperator'
value=`31003'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv'
key=`MBcontentType' value=`100'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBcommand'
value=`START'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBsubDate'
value=`1196085364000'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBserviceId'
value=`'
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Sending PDU:
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump:
2007-11-26 15:58:13 [4930] [6] DEBUG: type_name: submit_sm
2007-11-26 15:58:13 [4930] [6] DEBUG: command_id: 4 = 0x0004
2007-11-26 15:58:13 [4930] [6] DEBUG: command_status: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sequence_number: 6 = 0x0006
2007-11-26 15:58:13 [4930] [6] DEBUG: service_type: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_ton: 3 = 0x0003
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_npi: 9 = 0x0009
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr: 28444
2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_ton: 1 = 0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_npi: 1 = 0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: destination_addr: 1X
2007-11-26 15:58:13 [4930] [6] DEBUG: esm_class: 3 = 0x0003
2007-11-26 15:58:13 [4930] [6] DEBUG: protocol_id: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: priority_flag: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: schedule_delivery_time: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: validity_period: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: registered_delivery: 1 =
0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: replace_if_present_flag: 0 =
0x
2007-11-26 15:58:13 [4930] [6] DEBUG: data_coding: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sm_default_msg_id: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sm_length: 8 = 0x0008
2007-11-26 15:58:13 [4930] [6] DEBUG: short_message: CONTENT0
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU dump ends.
2007-11-26 15:58:13 [4930] [17] DEBUG: send_msg: sending msg to boxc:
smsc4
2007-11-26 15:58:13 [4930] [17] ERROR: Error reading from fd 46:
2007-11-26 15:58:13 [4930] [17] ERROR: System error 104: Connection
reset by peer
2007-11-26 15:58:13 [4930] [17] ERROR: Connection to box 127.0.0.1
broke. 2007-11-26 15:58:13 [4930] [18] DEBUG: send_msg: sending msg to
boxc: smsc4
2007-11-26 15:58:13 [4930] [18] ERROR: Error writing 16 octets to fd 46:
2007-11-26 15:58:13 [4930]
Re: [PATCH] SMPP Optional Parameters
Please read carefully :)
Kyriacos Sakkas wrote:
Call: (Relevant values inserted of courser)
$post .= X-Kannel-Meta-Data:
?smpp-tlv?MBbilling=.$bill.MBoperator=.
^^ group should be ?smpp? instead if ?smpp-tlv?
$operatorid.MBcontentType=100MBcommand=STARTMBsubDate=.date('U000').MBserviceId=XXX\r\n;
Definitions: (Had all as octstring, switched to nullterm for those with
no definite length)
group = smpp-tlv
name = MBoperator
tag = 0x1402
type = octetstring
length = 5
group = smpp-tlv
name = MBbilling
tag = 0x1403
type = octetstring
length = 5
group = smpp-tlv
name = MBsessionId
tag = 0x1404
type = nulterminated
length = 60
group = smpp-tlv
name = MBserviceDesc
tag = 0x1405
type = nulterminated
length = 10
group = smpp-tlv
name = MBcontentType
tag = 0x1406
type = nulterminated
length = 5
.
Alexander Malysh wrote:
Hi,
I suppose you didn't defined TLVs in the config and group in meta_data
named smpp instead of smpp-tlv. Example:
In the config
group = smpp-tlv
name = MBbilling
tag = 0x1601
type = integer|nulterminated|octetstring
length = 4
meta_data=?smpp?MBbilling=XXX...
Kyriacos Sakkas wrote:
If my packet capturing is correct, everything is parsed ok, but the TLVs
do not get added to the PDU.
Also my log file:
2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU 0x667eb0 dump:
2007-11-26 15:58:08 [4930] [6] DEBUG: type_name: enquire_link_resp
2007-11-26 15:58:08 [4930] [6] DEBUG: command_id: 2147483669 =
0x8015
2007-11-26 15:58:08 [4930] [6] DEBUG: command_status: 0 = 0x
2007-11-26 15:58:08 [4930] [6] DEBUG: sequence_number: 5 = 0x0005
2007-11-26 15:58:08 [4930] [6] DEBUG: SMPP PDU dump ends.
2007-11-26 15:58:13 [4930] [17] DEBUG: boxc_receiver: sms received
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced
source addr ton = 3, source add npi = 9
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Manually forced
dest addr ton = 1, dest add npi = 1
2007-11-26 15:58:13 [4930] [6] DEBUG: new group created `smpp-tlv'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBbilling'
value=`sub'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBoperator'
value=`31003'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv'
key=`MBcontentType' value=`100'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBcommand'
value=`START'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBsubDate'
value=`1196085364000'
2007-11-26 15:58:13 [4930] [6] DEBUG: group=`smpp-tlv' key=`MBserviceId'
value=`'
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP[mblox28444]: Sending PDU:
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU 0x6804c0 dump:
2007-11-26 15:58:13 [4930] [6] DEBUG: type_name: submit_sm
2007-11-26 15:58:13 [4930] [6] DEBUG: command_id: 4 = 0x0004
2007-11-26 15:58:13 [4930] [6] DEBUG: command_status: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sequence_number: 6 = 0x0006
2007-11-26 15:58:13 [4930] [6] DEBUG: service_type: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_ton: 3 = 0x0003
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr_npi: 9 = 0x0009
2007-11-26 15:58:13 [4930] [6] DEBUG: source_addr: 28444
2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_ton: 1 = 0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: dest_addr_npi: 1 = 0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: destination_addr: 1X
2007-11-26 15:58:13 [4930] [6] DEBUG: esm_class: 3 = 0x0003
2007-11-26 15:58:13 [4930] [6] DEBUG: protocol_id: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: priority_flag: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: schedule_delivery_time: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: validity_period: NULL
2007-11-26 15:58:13 [4930] [6] DEBUG: registered_delivery: 1 =
0x0001
2007-11-26 15:58:13 [4930] [6] DEBUG: replace_if_present_flag: 0 =
0x
2007-11-26 15:58:13 [4930] [6] DEBUG: data_coding: 0 = 0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sm_default_msg_id: 0 =
0x
2007-11-26 15:58:13 [4930] [6] DEBUG: sm_length: 8 = 0x0008
2007-11-26 15:58:13 [4930] [6] DEBUG: short_message: CONTENT0
2007-11-26 15:58:13 [4930] [6] DEBUG: SMPP PDU dump ends.
2007-11-26 15:58:13 [4930] [17] DEBUG: send_msg: sending msg to boxc:
smsc4
2007-11-26 15:58:13 [4930] [17] ERROR: Error reading from fd 46:
2007-11-26 15:58:13 [4930] [17] ERROR: System error 104: Connection
reset by peer
2007-11-26 15:58:13 [4930] [17] ERROR: Connection to box 127.0.0.1
broke. 2007-11-26 15:58:13 [4930] [18] DEBUG: send_msg: sending msg to
boxc: smsc4
2007-11-26 15:58:13 [4930] [18] ERROR: Error writing 16 octets to fd 46:
2007-11-26 15:58:13 [4930] [18] ERROR: System error 32: Broken pipe
2007-11-26 15:58:13 [4930] [18] ERROR: Couldn't write Msg to box
127.0.0.1, disconnecting
2007-11-26 15:58:13
Re: [PATCH] SMPP Optional Parameters
hi All, That seems to have sorted the parameters missing from PDU error, but as seen below something dies after I submit one or two messages. looking into it, as I had some minor issues still pending here with some TLVs, but if something pops to mind please let me know 2007-11-26 16:46:33 [5137] [6] DEBUG: SMPP[mblox28444]: Got PDU: 2007-11-26 16:46:33 [5137] [6] DEBUG: SMPP PDU 0x66b1d0 dump: 2007-11-26 16:46:33 [5137] [6] DEBUG: type_name: enquire_link_resp 2007-11-26 16:46:33 [5137] [6] DEBUG: command_id: 2147483669 = 0x8015 2007-11-26 16:46:33 [5137] [6] DEBUG: command_status: 0 = 0x 2007-11-26 16:46:33 [5137] [6] DEBUG: sequence_number: 3 = 0x0003 2007-11-26 16:46:33 [5137] [6] DEBUG: SMPP PDU dump ends. 2007-11-26 16:46:35 [5137] [17] DEBUG: boxc_receiver: sms received 2007-11-26 16:46:35 [5137] [17] DEBUG: send_msg: sending msg to boxc: smsc4 2007-11-26 16:46:35 [5137] [6] DEBUG: SMPP[mblox28444]: Manually forced source addr ton = 3, source add npi = 9 2007-11-26 16:46:35 [5137] [6] DEBUG: SMPP[mblox28444]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-26 16:46:35 [5137] [6] DEBUG: new group created `smpp' 2007-11-26 16:46:35 [5137] [6] DEBUG: group=`smpp' key=`MBbilling' value=`sub' 2007-11-26 16:46:35 [5137] [6] DEBUG: group=`smpp' key=`MBoperator' value=`31003' 2007-11-26 16:46:35 [5137] [6] DEBUG: group=`smpp' key=`MBcontentType' value=`100' 2007-11-26 16:46:35 [5137] [6] DEBUG: group=`smpp' key=`MBcommand' value=`START' 2007-11-26 16:46:35 [5137] [6] DEBUG: group=`smpp' key=`MBsubDate' value=`1196088266000' 2007-11-26 16:46:35 [5137] [6] DEBUG: group=`smpp' key=`MBserviceId' value=`' 2007-11-26 16:46:35 [5137] [6] DEBUG: SMPP[mblox28444]: Sending PDU: 2007-11-26 16:46:35 [5137] [17] ERROR: Error reading from fd 46: 2007-11-26 16:46:35 [5137] [17] ERROR: System error 104: Connection reset by peer 2007-11-26 16:46:35 [5137] [6] DEBUG: SMPP PDU 0x668600 dump: 2007-11-26 16:46:35 [5137] [6] DEBUG: type_name: submit_sm 2007-11-26 16:46:35 [5137] [6] DEBUG: command_id: 4 = 0x0004 2007-11-26 16:46:35 [5137] [6] DEBUG: command_status: 0 = 0x 2007-11-26 16:46:35 [5137] [6] DEBUG: sequence_number: 4 = 0x0004 2007-11-26 16:46:35 [5137] [17] ERROR: Connection to box 127.0.0.1 broke. 2007-11-26 16:46:35 [5137] [6] DEBUG: service_type: NULL 2007-11-26 16:46:35 [5137] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-26 16:46:35 [5137] [18] DEBUG: send_msg: sending msg to boxc: smsc4 2007-11-26 16:46:35 [5137] [6] DEBUG: source_addr_npi: 9 = 0x0009 2007-11-26 16:46:35 [5137] [6] DEBUG: source_addr: 28444 2007-11-26 16:46:35 [5137] [18] ERROR: Error writing 16 octets to fd 46: 2007-11-26 16:46:35 [5137] [18] ERROR: System error 32: Broken pipe 2007-11-26 16:46:35 [5137] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-26 16:46:35 [5137] [18] ERROR: Couldn't write Msg to box 127.0.0.1, disconnecting 2007-11-26 16:46:35 [5137] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-26 16:46:35 [5137] [18] DEBUG: Thread 18 (gw/bb_boxc.c:boxc_sender) terminates. 2007-11-26 16:46:35 [5137] [6] DEBUG: destination_addr: 1X 2007-11-26 16:46:35 [5137] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-26 16:46:35 [5137] [6] DEBUG: protocol_id: 0 = 0x 2007-11-26 16:46:35 [5137] [6] DEBUG: priority_flag: 0 = 0x 2007-11-26 16:46:35 [5137] [6] DEBUG: schedule_delivery_time: NULL 2007-11-26 16:46:35 [5137] [17] ERROR: Error writing 16 octets to fd 46: 2007-11-26 16:46:35 [5137] [17] ERROR: System error 32: Broken pipe 2007-11-26 16:46:35 [5137] [6] DEBUG: validity_period: NULL 2007-11-26 16:46:35 [5137] [17] DEBUG: Thread 17 (gw/bb_boxc.c:function) terminates. 2007-11-26 16:46:35 [5137] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-26 16:46:35 [5137] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-26 16:46:35 [5137] [6] DEBUG: data_coding: 0 = 0x 2007-11-26 16:46:35 [5137] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-26 16:46:35 [5137] [6] DEBUG: sm_length: 8 = 0x0008 2007-11-26 16:46:35 [5137] [6] DEBUG: short_message: CONTENT0 2007-11-26 16:46:35 [5137] [6] DEBUG: MBsubDate: 1196088266000 2007-11-26 16:46:35 [5137] [6] DEBUG: MBcommand: START 2007-11-26 16:46:35 [5137] [6] DEBUG: MBbilling: sub 2007-11-26 16:46:35 [5137] [6] DEBUG: MBoperator: 31003 2007-11-26 16:46:35 [5137] [6] DEBUG: MBserviceId: 2007-11-26 16:46:35 [5137] [6] DEBUG: MBcontentType: 100 2007-11-26 16:46:35 [5137] [6] DEBUG: SMPP PDU dump ends. 2007-11-26 16:46:35 [5137] [6] ERROR: SMPP: Unknown TLV `MBsubDate', don't send. 2007-11-26 16:46:36 [5137] [6] WARNING: SMPP: PDU NULL terminated string (message_id) has no NULL. 2007-11-26 16:46:36 [5137] [6] DEBUG: SMPP[mblox28444]: Got PDU: 2007-11-26 16:46:36 [5137] [6] DEBUG: SMPP PDU 0x668600 dump: 2007-11-26 16:46:36 [5137] [6] DEBUG: type_name: submit_sm_resp 2007-11-26 16:46:36 [5137] [6] DEBUG: command_id: 2147483652 =
Re: [PATCH] SMPP Optional Parameters
any feedback on this?
thnx again!
Juan
On Nov 8, 2007 3:17 PM, Juan Nin [EMAIL PROTECTED] wrote:
Hi Alexander!
I've made some tests with your patch.
These are the Optional SMPP parameters I've configured:
# Specifies if message must or not be billed
group = smpp-tlv
name = charge_type
tag= 0x2151
type = integer
length = 1
# Specifies amount to be billed
group = smpp-tlv
name = charge_amount
tag= 0x2152
type = integer
length = 2
# Specifies the reason why the SMS is in it's current message state
group = smpp-tlv
name = reason_id
tag= 0x2153
type = integer
length = 2
I've used the first 2 ones, on MT sending, and I've been able to send
with this Premium messages
I used this sample code on PHP:
SNIP
$tlv = urlencode('?smpp?charge_type=1charge_amount=99');
$url =
http://127.0.0.1:13131/cgi-bin/sendsms?username=$send_sms_userpassword=$send_sms_passto=$phonefrom=$short_codesmsc=$smscdlr-mask=$dlr_maskdlr-url=$dlr_urltext=$message;;
if($tlv != '')
{
$url .= meta-data=$tlv;
}
/SNIP
This worked fine as you can see here:
007-11-08 09:54:01 [19112] [6] DEBUG: SMPP[om-1]: Manually forced dest
addr ton = 1, dest add npi = 1
2007-11-08 09:54:01 [19112] [6] DEBUG: new group created `smpp'
2007-11-08 09:54:01 [19112] [6] DEBUG: group=`smpp' key=`charge_type'
value=`1'
2007-11-08 09:54:01 [19112] [6] DEBUG: group=`smpp'
key=`charge_amount' value=`99'
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP[om-1]: Sending PDU:
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP PDU 0x1da7c4c0 dump:
2007-11-08 09:54:01 [19112] [6] DEBUG: type_name: submit_sm
2007-11-08 09:54:01 [19112] [6] DEBUG: command_id: 4 = 0x0004
2007-11-08 09:54:01 [19112] [6] DEBUG: command_status: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: sequence_number: 28 = 0x001c
2007-11-08 09:54:01 [19112] [6] DEBUG: service_type: NULL
2007-11-08 09:54:01 [19112] [6] DEBUG: source_addr_ton: 3 = 0x0003
2007-11-08 09:54:01 [19112] [6] DEBUG: source_addr_npi: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: source_addr: 12345
2007-11-08 09:54:01 [19112] [6] DEBUG: dest_addr_ton: 1 = 0x0001
2007-11-08 09:54:01 [19112] [6] DEBUG: dest_addr_npi: 1 = 0x0001
2007-11-08 09:54:01 [19112] [6] DEBUG: destination_addr: 11234567890
2007-11-08 09:54:01 [19112] [6] DEBUG: esm_class: 3 = 0x0003
2007-11-08 09:54:01 [19112] [6] DEBUG: protocol_id: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: priority_flag: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: schedule_delivery_time: NULL
2007-11-08 09:54:01 [19112] [6] DEBUG: validity_period: NULL
2007-11-08 09:54:01 [19112] [6] DEBUG: registered_delivery: 1 = 0x0001
2007-11-08 09:54:01 [19112] [6] DEBUG: replace_if_present_flag: 0 =
0x
2007-11-08 09:54:01 [19112] [6] DEBUG: data_coding: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: sm_default_msg_id: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: sm_length: 30 = 0x001e
2007-11-08 09:54:01 [19112] [6] DEBUG: short_message:
2007-11-08 09:54:01 [19112] [6] DEBUG:Octet string at 0x1da56910:
2007-11-08 09:54:01 [19112] [6] DEBUG: len: 30
2007-11-08 09:54:01 [19112] [6] DEBUG: size: 31
2007-11-08 09:54:01 [19112] [6] DEBUG: immutable: 0
2007-11-08 09:54:01 [19112] [6] DEBUG: data: 54 65 73 74 20 50 53
4d 53 20 66 72 6f 6d 20 4a Test PSMS from J
2007-11-08 09:54:01 [19112] [6] DEBUG: data: 75 61 6e 20 4e 69 6e
20 28 53 4d 50 50 29 uan Nin (SMPP)
2007-11-08 09:54:01 [19112] [6] DEBUG:Octet string dump ends.
2007-11-08 09:54:01 [19112] [6] DEBUG: charge_type: 1
2007-11-08 09:54:01 [19112] [6] DEBUG: charge_amount: 99
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP PDU dump ends.
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP[om-1]: Got PDU:
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP PDU 0x1da7c4c0 dump:
2007-11-08 09:54:01 [19112] [6] DEBUG: type_name: submit_sm_resp
2007-11-08 09:54:01 [19112] [6] DEBUG: command_id: 2147483652 = 0x8004
2007-11-08 09:54:01 [19112] [6] DEBUG: command_status: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: sequence_number: 28 = 0x001c
2007-11-08 09:54:01 [19112] [6] DEBUG: message_id:
2007-11-08 09:54:01 [19112] [6] DEBUG:Octet string at 0x1da64ea0:
2007-11-08 09:54:01 [19112] [6] DEBUG: len: 23
2007-11-08 09:54:01 [19112] [6] DEBUG: size: 24
2007-11-08 09:54:01 [19112] [6] DEBUG: immutable: 0
2007-11-08 09:54:01 [19112] [6] DEBUG: data: 30 31 30 37 48 2d 31
31 30 38 47 2d 30 39 35 34 0107H-1108G-0954
2007-11-08 09:54:01 [19112] [6] DEBUG: data: 44 2d 30 31 33 39 52
D-0139R
2007-11-08 09:54:01 [19112] [6] DEBUG:Octet string dump ends.
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP PDU dump ends.
Now, the third optional parameter I defined (reason_id) is sent by the
gateway when
Re: [PATCH] SMPP Optional Parameters
Hi, seems I just forgot about DLRs and data_sm :) Please try attached patch instead of previous one. Juan Nin wrote: any feedback on this? thnx again! Juan On Nov 8, 2007 3:17 PM, Juan Nin [EMAIL PROTECTED] wrote: Hi Alexander! I've made some tests with your patch. These are the Optional SMPP parameters I've configured: # Specifies if message must or not be billed group = smpp-tlv name = charge_type tag= 0x2151 type = integer length = 1 # Specifies amount to be billed group = smpp-tlv name = charge_amount tag= 0x2152 type = integer length = 2 # Specifies the reason why the SMS is in it's current message state group = smpp-tlv name = reason_id tag= 0x2153 type = integer length = 2 -- Thanks, Alex meta_data.diff.gz Description: GNU Zip compressed data
Re: [PATCH] SMPP Optional Parameters
On Nov 9, 2007 11:54 AM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, seems I just forgot about DLRs and data_sm :) Please try attached patch instead of previous one. cool! :) I just tried it, and now it's passing it! BUT, it's not passing back all of the received optional parameters :( it's only passing the vendor specific one there are 2 more that are coming, which are defined on the SMPP specs (receipted_message_id and message_state), that are not being passed in %D may be something yet missing? here's the definitions: # Specifies if message must or not be billed group = smpp-tlv name = charge_type tag= 0x2151 type = integer length = 1 # Specifies amount to be billed group = smpp-tlv name = charge_amount tag= 0x2152 type = integer length = 2 # Specifies the reason why the SMS is in its current message state group = smpp-tlv name = reason_id tag= 0x2153 type = integer length = 2 # Specifies the Message ID returned in the Submit_SM response packet group = smpp-tlv name = receipted_message_id tag= 0x001e type = octetstring length = 65 # Specifies the most up-to-date delivery state of the SMS group = smpp-tlv name = message_state tag= 0x0427 type = integer length = 1 here the smsc connection logs: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced source addr ton = 3, source add npi = 0 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-09 09:26:18 [4004] [6] DEBUG: new group created `smpp' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_type' value=`1' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_amount' value=`99' 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Sending PDU: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU 0xdeee5c0 dump: 2007-11-09 09:26:18 [4004] [6] DEBUG: type_name: submit_sm 2007-11-09 09:26:18 [4004] [6] DEBUG: command_id: 4 = 0x0004 2007-11-09 09:26:18 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-09 09:26:18 [4004] [6] DEBUG: service_type: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_npi: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr: 12345 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: destination_addr: 11234567890 2007-11-09 09:26:18 [4004] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: protocol_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: priority_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: schedule_delivery_time: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: validity_period: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: data_coding: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_length: 30 = 0x001e 2007-11-09 09:26:18 [4004] [6] DEBUG: short_message: 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string at 0xdec18e0: 2007-11-09 09:26:18 [4004] [6] DEBUG: len: 30 2007-11-09 09:26:18 [4004] [6] DEBUG: size: 31 2007-11-09 09:26:18 [4004] [6] DEBUG: immutable: 0 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 54 65 73 74 20 50 53 4d 53 20 66 72 6f 6d 20 4a Test PSMS from J 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 75 61 6e 20 4e 69 6e 20 28 53 4d 50 50 29 uan Nin (SMPP) 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string dump ends. 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_type: 1 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_amount: 99 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU dump ends. 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP[om-1]: Sending enquire link: 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP PDU 0xdec1580 dump: 2007-11-09 09:26:19 [4004] [6] DEBUG: type_name: enquire_link 2007-11-09 09:26:19 [4004] [6] DEBUG: command_id: 21 = 0x0015 2007-11-09 09:26:19 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:19 [4004] [6] DEBUG: sequence_number: 6 = 0x0006 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP PDU dump ends. 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP[om-1]: Got PDU: 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP PDU 0xdec1580 dump: 2007-11-09 09:26:19 [4004] [6] DEBUG: type_name: submit_sm_resp 2007-11-09 09:26:19 [4004] [6] DEBUG: command_id: 2147483652 = 0x8004 2007-11-09 09:26:19 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:19 [4004] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-09 09:26:19 [4004] [6] DEBUG: message_id: 2007-11-09 09:26:19 [4004] [6] DEBUG:
Re: [PATCH] SMPP Optional Parameters
Hi again, in metadata you will receive only vendor specific TLVs. It could be expanded to all TLVs if needed. Juan Nin wrote: On Nov 9, 2007 11:54 AM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, seems I just forgot about DLRs and data_sm :) Please try attached patch instead of previous one. cool! :) I just tried it, and now it's passing it! BUT, it's not passing back all of the received optional parameters :( it's only passing the vendor specific one there are 2 more that are coming, which are defined on the SMPP specs (receipted_message_id and message_state), that are not being passed in %D may be something yet missing? here's the definitions: # Specifies if message must or not be billed group = smpp-tlv name = charge_type tag= 0x2151 type = integer length = 1 # Specifies amount to be billed group = smpp-tlv name = charge_amount tag= 0x2152 type = integer length = 2 # Specifies the reason why the SMS is in its current message state group = smpp-tlv name = reason_id tag= 0x2153 type = integer length = 2 # Specifies the Message ID returned in the Submit_SM response packet group = smpp-tlv name = receipted_message_id tag= 0x001e type = octetstring length = 65 # Specifies the most up-to-date delivery state of the SMS group = smpp-tlv name = message_state tag= 0x0427 type = integer length = 1 here the smsc connection logs: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced source addr ton = 3, source add npi = 0 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-09 09:26:18 [4004] [6] DEBUG: new group created `smpp' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_type' value=`1' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_amount' value=`99' 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Sending PDU: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU 0xdeee5c0 dump: 2007-11-09 09:26:18 [4004] [6] DEBUG: type_name: submit_sm 2007-11-09 09:26:18 [4004] [6] DEBUG: command_id: 4 = 0x0004 2007-11-09 09:26:18 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-09 09:26:18 [4004] [6] DEBUG: service_type: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_npi: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr: 12345 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: destination_addr: 11234567890 2007-11-09 09:26:18 [4004] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: protocol_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: priority_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: schedule_delivery_time: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: validity_period: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: data_coding: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_length: 30 = 0x001e 2007-11-09 09:26:18 [4004] [6] DEBUG: short_message: 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string at 0xdec18e0: 2007-11-09 09:26:18 [4004] [6] DEBUG: len: 30 2007-11-09 09:26:18 [4004] [6] DEBUG: size: 31 2007-11-09 09:26:18 [4004] [6] DEBUG: immutable: 0 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 54 65 73 74 20 50 53 4d 53 20 66 72 6f 6d 20 4a Test PSMS from J 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 75 61 6e 20 4e 69 6e 20 28 53 4d 50 50 29 uan Nin (SMPP) 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string dump ends. 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_type: 1 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_amount: 99 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU dump ends. 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP[om-1]: Sending enquire link: 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP PDU 0xdec1580 dump: 2007-11-09 09:26:19 [4004] [6] DEBUG: type_name: enquire_link 2007-11-09 09:26:19 [4004] [6] DEBUG: command_id: 21 = 0x0015 2007-11-09 09:26:19 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:19 [4004] [6] DEBUG: sequence_number: 6 = 0x0006 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP PDU dump ends. 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP[om-1]: Got PDU: 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP PDU 0xdec1580 dump: 2007-11-09 09:26:19 [4004] [6] DEBUG: type_name: submit_sm_resp 2007-11-09 09:26:19 [4004] [6] DEBUG: command_id: 2147483652 =
Re: [PATCH] SMPP Optional Parameters
oks, can u give me any clue on how to expand it to all TLVs? not sure if I'll be able to do it, I'm not too much of a C programmer, but if not much has to be touched, maybe I can do it... thnx again! Juan On Nov 9, 2007 12:55 PM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi again, in metadata you will receive only vendor specific TLVs. It could be expanded to all TLVs if needed. Juan Nin wrote: On Nov 9, 2007 11:54 AM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, seems I just forgot about DLRs and data_sm :) Please try attached patch instead of previous one. cool! :) I just tried it, and now it's passing it! BUT, it's not passing back all of the received optional parameters :( it's only passing the vendor specific one there are 2 more that are coming, which are defined on the SMPP specs (receipted_message_id and message_state), that are not being passed in %D may be something yet missing? here's the definitions: # Specifies if message must or not be billed group = smpp-tlv name = charge_type tag= 0x2151 type = integer length = 1 # Specifies amount to be billed group = smpp-tlv name = charge_amount tag= 0x2152 type = integer length = 2 # Specifies the reason why the SMS is in its current message state group = smpp-tlv name = reason_id tag= 0x2153 type = integer length = 2 # Specifies the Message ID returned in the Submit_SM response packet group = smpp-tlv name = receipted_message_id tag= 0x001e type = octetstring length = 65 # Specifies the most up-to-date delivery state of the SMS group = smpp-tlv name = message_state tag= 0x0427 type = integer length = 1 here the smsc connection logs: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced source addr ton = 3, source add npi = 0 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-09 09:26:18 [4004] [6] DEBUG: new group created `smpp' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_type' value=`1' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_amount' value=`99' 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Sending PDU: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU 0xdeee5c0 dump: 2007-11-09 09:26:18 [4004] [6] DEBUG: type_name: submit_sm 2007-11-09 09:26:18 [4004] [6] DEBUG: command_id: 4 = 0x0004 2007-11-09 09:26:18 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-09 09:26:18 [4004] [6] DEBUG: service_type: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_npi: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr: 12345 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: destination_addr: 11234567890 2007-11-09 09:26:18 [4004] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: protocol_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: priority_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: schedule_delivery_time: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: validity_period: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: data_coding: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_length: 30 = 0x001e 2007-11-09 09:26:18 [4004] [6] DEBUG: short_message: 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string at 0xdec18e0: 2007-11-09 09:26:18 [4004] [6] DEBUG: len: 30 2007-11-09 09:26:18 [4004] [6] DEBUG: size: 31 2007-11-09 09:26:18 [4004] [6] DEBUG: immutable: 0 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 54 65 73 74 20 50 53 4d 53 20 66 72 6f 6d 20 4a Test PSMS from J 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 75 61 6e 20 4e 69 6e 20 28 53 4d 50 50 29 uan Nin (SMPP) 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string dump ends. 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_type: 1 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_amount: 99 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU dump ends. 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP[om-1]: Sending enquire link: 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP PDU 0xdec1580 dump: 2007-11-09 09:26:19 [4004] [6] DEBUG: type_name: enquire_link 2007-11-09 09:26:19 [4004] [6] DEBUG: command_id: 21 = 0x0015 2007-11-09 09:26:19 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09
Re: [PATCH] SMPP Optional Parameters
It's easier for me todo it myself instead of write how to do it :) Juan Nin wrote: oks, can u give me any clue on how to expand it to all TLVs? not sure if I'll be able to do it, I'm not too much of a C programmer, but if not much has to be touched, maybe I can do it... thnx again! Juan On Nov 9, 2007 12:55 PM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi again, in metadata you will receive only vendor specific TLVs. It could be expanded to all TLVs if needed. Juan Nin wrote: On Nov 9, 2007 11:54 AM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, seems I just forgot about DLRs and data_sm :) Please try attached patch instead of previous one. cool! :) I just tried it, and now it's passing it! BUT, it's not passing back all of the received optional parameters :( it's only passing the vendor specific one there are 2 more that are coming, which are defined on the SMPP specs (receipted_message_id and message_state), that are not being passed in %D may be something yet missing? here's the definitions: # Specifies if message must or not be billed group = smpp-tlv name = charge_type tag= 0x2151 type = integer length = 1 # Specifies amount to be billed group = smpp-tlv name = charge_amount tag= 0x2152 type = integer length = 2 # Specifies the reason why the SMS is in its current message state group = smpp-tlv name = reason_id tag= 0x2153 type = integer length = 2 # Specifies the Message ID returned in the Submit_SM response packet group = smpp-tlv name = receipted_message_id tag= 0x001e type = octetstring length = 65 # Specifies the most up-to-date delivery state of the SMS group = smpp-tlv name = message_state tag= 0x0427 type = integer length = 1 here the smsc connection logs: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced source addr ton = 3, source add npi = 0 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-09 09:26:18 [4004] [6] DEBUG: new group created `smpp' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_type' value=`1' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_amount' value=`99' 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Sending PDU: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU 0xdeee5c0 dump: 2007-11-09 09:26:18 [4004] [6] DEBUG: type_name: submit_sm 2007-11-09 09:26:18 [4004] [6] DEBUG: command_id: 4 = 0x0004 2007-11-09 09:26:18 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-09 09:26:18 [4004] [6] DEBUG: service_type: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_npi: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr: 12345 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: destination_addr: 11234567890 2007-11-09 09:26:18 [4004] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: protocol_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: priority_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: schedule_delivery_time: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: validity_period: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: data_coding: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_length: 30 = 0x001e 2007-11-09 09:26:18 [4004] [6] DEBUG: short_message: 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string at 0xdec18e0: 2007-11-09 09:26:18 [4004] [6] DEBUG: len: 30 2007-11-09 09:26:18 [4004] [6] DEBUG: size: 31 2007-11-09 09:26:18 [4004] [6] DEBUG: immutable: 0 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 54 65 73 74 20 50 53 4d 53 20 66 72 6f 6d 20 4a Test PSMS from J 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 75 61 6e 20 4e 69 6e 20 28 53 4d 50 50 29 uan Nin (SMPP) 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string dump ends. 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_type: 1 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_amount: 99 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU dump ends. 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP[om-1]: Sending enquire link: 2007-11-09 09:26:19 [4004] [6] DEBUG: SMPP PDU 0xdec1580 dump: 2007-11-09 09:26:19 [4004] [6] DEBUG: type_name: enquire_link 2007-11-09 09:26:19 [4004] [6] DEBUG: command_id: 21 =
Re: [PATCH] SMPP Optional Parameters
oks, great! :) to be able to plan my stuff, when do you think you can have some time to do it? thnx again On Nov 9, 2007 1:31 PM, Alexander Malysh [EMAIL PROTECTED] wrote: It's easier for me todo it myself instead of write how to do it :) Juan Nin wrote: oks, can u give me any clue on how to expand it to all TLVs? not sure if I'll be able to do it, I'm not too much of a C programmer, but if not much has to be touched, maybe I can do it... thnx again! Juan On Nov 9, 2007 12:55 PM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi again, in metadata you will receive only vendor specific TLVs. It could be expanded to all TLVs if needed. Juan Nin wrote: On Nov 9, 2007 11:54 AM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, seems I just forgot about DLRs and data_sm :) Please try attached patch instead of previous one. cool! :) I just tried it, and now it's passing it! BUT, it's not passing back all of the received optional parameters :( it's only passing the vendor specific one there are 2 more that are coming, which are defined on the SMPP specs (receipted_message_id and message_state), that are not being passed in %D may be something yet missing? here's the definitions: # Specifies if message must or not be billed group = smpp-tlv name = charge_type tag= 0x2151 type = integer length = 1 # Specifies amount to be billed group = smpp-tlv name = charge_amount tag= 0x2152 type = integer length = 2 # Specifies the reason why the SMS is in its current message state group = smpp-tlv name = reason_id tag= 0x2153 type = integer length = 2 # Specifies the Message ID returned in the Submit_SM response packet group = smpp-tlv name = receipted_message_id tag= 0x001e type = octetstring length = 65 # Specifies the most up-to-date delivery state of the SMS group = smpp-tlv name = message_state tag= 0x0427 type = integer length = 1 here the smsc connection logs: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced source addr ton = 3, source add npi = 0 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-09 09:26:18 [4004] [6] DEBUG: new group created `smpp' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_type' value=`1' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_amount' value=`99' 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Sending PDU: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU 0xdeee5c0 dump: 2007-11-09 09:26:18 [4004] [6] DEBUG: type_name: submit_sm 2007-11-09 09:26:18 [4004] [6] DEBUG: command_id: 4 = 0x0004 2007-11-09 09:26:18 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-09 09:26:18 [4004] [6] DEBUG: service_type: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_npi: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr: 12345 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: destination_addr: 11234567890 2007-11-09 09:26:18 [4004] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: protocol_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: priority_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: schedule_delivery_time: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: validity_period: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: data_coding: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_length: 30 = 0x001e 2007-11-09 09:26:18 [4004] [6] DEBUG: short_message: 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string at 0xdec18e0: 2007-11-09 09:26:18 [4004] [6] DEBUG: len: 30 2007-11-09 09:26:18 [4004] [6] DEBUG: size: 31 2007-11-09 09:26:18 [4004] [6] DEBUG: immutable: 0 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 54 65 73 74 20 50 53 4d 53 20 66 72 6f 6d 20 4a Test PSMS from J 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 75 61 6e 20 4e 69 6e 20 28 53 4d 50 50 29 uan Nin (SMPP) 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string dump ends. 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_type: 1 2007-11-09 09:26:18 [4004] [6] DEBUG: charge_amount: 99 2007-11-09 09:26:18 [4004]
Re: [PATCH] SMPP Optional Parameters
Hi, I will try to look into this when I have some spare time but it was not the intention of the patch. The patch was only to allow operator specific TLVs. TLVs from SMPP spec. should be handled by kannel on regular basis (IMHO). Juan Nin wrote: oks, great! :) to be able to plan my stuff, when do you think you can have some time to do it? thnx again On Nov 9, 2007 1:31 PM, Alexander Malysh [EMAIL PROTECTED] wrote: It's easier for me todo it myself instead of write how to do it :) Juan Nin wrote: oks, can u give me any clue on how to expand it to all TLVs? not sure if I'll be able to do it, I'm not too much of a C programmer, but if not much has to be touched, maybe I can do it... thnx again! Juan On Nov 9, 2007 12:55 PM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi again, in metadata you will receive only vendor specific TLVs. It could be expanded to all TLVs if needed. Juan Nin wrote: On Nov 9, 2007 11:54 AM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, seems I just forgot about DLRs and data_sm :) Please try attached patch instead of previous one. cool! :) I just tried it, and now it's passing it! BUT, it's not passing back all of the received optional parameters :( it's only passing the vendor specific one there are 2 more that are coming, which are defined on the SMPP specs (receipted_message_id and message_state), that are not being passed in %D may be something yet missing? here's the definitions: # Specifies if message must or not be billed group = smpp-tlv name = charge_type tag= 0x2151 type = integer length = 1 # Specifies amount to be billed group = smpp-tlv name = charge_amount tag= 0x2152 type = integer length = 2 # Specifies the reason why the SMS is in its current message state group = smpp-tlv name = reason_id tag= 0x2153 type = integer length = 2 # Specifies the Message ID returned in the Submit_SM response packet group = smpp-tlv name = receipted_message_id tag= 0x001e type = octetstring length = 65 # Specifies the most up-to-date delivery state of the SMS group = smpp-tlv name = message_state tag= 0x0427 type = integer length = 1 here the smsc connection logs: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced source addr ton = 3, source add npi = 0 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-09 09:26:18 [4004] [6] DEBUG: new group created `smpp' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_type' value=`1' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_amount' value=`99' 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Sending PDU: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU 0xdeee5c0 dump: 2007-11-09 09:26:18 [4004] [6] DEBUG: type_name: submit_sm 2007-11-09 09:26:18 [4004] [6] DEBUG: command_id: 4 = 0x0004 2007-11-09 09:26:18 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-09 09:26:18 [4004] [6] DEBUG: service_type: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_npi: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr: 12345 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: destination_addr: 11234567890 2007-11-09 09:26:18 [4004] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: protocol_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: priority_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: schedule_delivery_time: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: validity_period: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: data_coding: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_length: 30 = 0x001e 2007-11-09 09:26:18 [4004] [6] DEBUG: short_message: 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string at 0xdec18e0: 2007-11-09 09:26:18 [4004] [6] DEBUG: len: 30 2007-11-09 09:26:18 [4004] [6] DEBUG: size: 31 2007-11-09 09:26:18 [4004] [6] DEBUG: immutable: 0 2007-11-09 09:26:18 [4004] [6] DEBUG: data: 54 65 73 74 20 50 53 4d 53 20 66 72 6f 6d 20 4a Test PSMS from J 2007-11-09 09:26:18 [4004] [6] DEBUG:
Re: [PATCH] SMPP Optional Parameters
i agree doing it separately as to integrate it with the kannel regular code would be more difficult? On Nov 9, 2007 3:02 PM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, I will try to look into this when I have some spare time but it was not the intention of the patch. The patch was only to allow operator specific TLVs. TLVs from SMPP spec. should be handled by kannel on regular basis (IMHO). Juan Nin wrote: oks, great! :) to be able to plan my stuff, when do you think you can have some time to do it? thnx again On Nov 9, 2007 1:31 PM, Alexander Malysh [EMAIL PROTECTED] wrote: It's easier for me todo it myself instead of write how to do it :) Juan Nin wrote: oks, can u give me any clue on how to expand it to all TLVs? not sure if I'll be able to do it, I'm not too much of a C programmer, but if not much has to be touched, maybe I can do it... thnx again! Juan On Nov 9, 2007 12:55 PM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi again, in metadata you will receive only vendor specific TLVs. It could be expanded to all TLVs if needed. Juan Nin wrote: On Nov 9, 2007 11:54 AM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, seems I just forgot about DLRs and data_sm :) Please try attached patch instead of previous one. cool! :) I just tried it, and now it's passing it! BUT, it's not passing back all of the received optional parameters :( it's only passing the vendor specific one there are 2 more that are coming, which are defined on the SMPP specs (receipted_message_id and message_state), that are not being passed in %D may be something yet missing? here's the definitions: # Specifies if message must or not be billed group = smpp-tlv name = charge_type tag= 0x2151 type = integer length = 1 # Specifies amount to be billed group = smpp-tlv name = charge_amount tag= 0x2152 type = integer length = 2 # Specifies the reason why the SMS is in its current message state group = smpp-tlv name = reason_id tag= 0x2153 type = integer length = 2 # Specifies the Message ID returned in the Submit_SM response packet group = smpp-tlv name = receipted_message_id tag= 0x001e type = octetstring length = 65 # Specifies the most up-to-date delivery state of the SMS group = smpp-tlv name = message_state tag= 0x0427 type = integer length = 1 here the smsc connection logs: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced source addr ton = 3, source add npi = 0 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Manually forced dest addr ton = 1, dest add npi = 1 2007-11-09 09:26:18 [4004] [6] DEBUG: new group created `smpp' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_type' value=`1' 2007-11-09 09:26:18 [4004] [6] DEBUG: group=`smpp' key=`charge_amount' value=`99' 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP[om-1]: Sending PDU: 2007-11-09 09:26:18 [4004] [6] DEBUG: SMPP PDU 0xdeee5c0 dump: 2007-11-09 09:26:18 [4004] [6] DEBUG: type_name: submit_sm 2007-11-09 09:26:18 [4004] [6] DEBUG: command_id: 4 = 0x0004 2007-11-09 09:26:18 [4004] [6] DEBUG: command_status: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sequence_number: 5 = 0x0005 2007-11-09 09:26:18 [4004] [6] DEBUG: service_type: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_ton: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr_npi: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: source_addr: 12345 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_ton: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: dest_addr_npi: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: destination_addr: 11234567890 2007-11-09 09:26:18 [4004] [6] DEBUG: esm_class: 3 = 0x0003 2007-11-09 09:26:18 [4004] [6] DEBUG: protocol_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: priority_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: schedule_delivery_time: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: validity_period: NULL 2007-11-09 09:26:18 [4004] [6] DEBUG: registered_delivery: 1 = 0x0001 2007-11-09 09:26:18 [4004] [6] DEBUG: replace_if_present_flag: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: data_coding: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_default_msg_id: 0 = 0x 2007-11-09 09:26:18 [4004] [6] DEBUG: sm_length: 30 = 0x001e 2007-11-09 09:26:18 [4004] [6] DEBUG: short_message: 2007-11-09 09:26:18 [4004] [6] DEBUG:Octet string at 0xdec18e0: 2007-11-09 09:26:18 [4004]
Re: [PATCH] SMPP Optional Parameters
Hi Alexander!
I've made some tests with your patch.
These are the Optional SMPP parameters I've configured:
# Specifies if message must or not be billed
group = smpp-tlv
name = charge_type
tag= 0x2151
type = integer
length = 1
# Specifies amount to be billed
group = smpp-tlv
name = charge_amount
tag= 0x2152
type = integer
length = 2
# Specifies the reason why the SMS is in it's current message state
group = smpp-tlv
name = reason_id
tag= 0x2153
type = integer
length = 2
I've used the first 2 ones, on MT sending, and I've been able to send
with this Premium messages
I used this sample code on PHP:
SNIP
$tlv = urlencode('?smpp?charge_type=1charge_amount=99');
$url =
http://127.0.0.1:13131/cgi-bin/sendsms?username=$send_sms_userpassword=$send_sms_passto=$phonefrom=$short_codesmsc=$smscdlr-mask=$dlr_maskdlr-url=$dlr_urltext=$message;;
if($tlv != '')
{
$url .= meta-data=$tlv;
}
/SNIP
This worked fine as you can see here:
007-11-08 09:54:01 [19112] [6] DEBUG: SMPP[om-1]: Manually forced dest
addr ton = 1, dest add npi = 1
2007-11-08 09:54:01 [19112] [6] DEBUG: new group created `smpp'
2007-11-08 09:54:01 [19112] [6] DEBUG: group=`smpp' key=`charge_type' value=`1'
2007-11-08 09:54:01 [19112] [6] DEBUG: group=`smpp'
key=`charge_amount' value=`99'
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP[om-1]: Sending PDU:
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP PDU 0x1da7c4c0 dump:
2007-11-08 09:54:01 [19112] [6] DEBUG: type_name: submit_sm
2007-11-08 09:54:01 [19112] [6] DEBUG: command_id: 4 = 0x0004
2007-11-08 09:54:01 [19112] [6] DEBUG: command_status: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: sequence_number: 28 = 0x001c
2007-11-08 09:54:01 [19112] [6] DEBUG: service_type: NULL
2007-11-08 09:54:01 [19112] [6] DEBUG: source_addr_ton: 3 = 0x0003
2007-11-08 09:54:01 [19112] [6] DEBUG: source_addr_npi: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: source_addr: 12345
2007-11-08 09:54:01 [19112] [6] DEBUG: dest_addr_ton: 1 = 0x0001
2007-11-08 09:54:01 [19112] [6] DEBUG: dest_addr_npi: 1 = 0x0001
2007-11-08 09:54:01 [19112] [6] DEBUG: destination_addr: 11234567890
2007-11-08 09:54:01 [19112] [6] DEBUG: esm_class: 3 = 0x0003
2007-11-08 09:54:01 [19112] [6] DEBUG: protocol_id: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: priority_flag: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: schedule_delivery_time: NULL
2007-11-08 09:54:01 [19112] [6] DEBUG: validity_period: NULL
2007-11-08 09:54:01 [19112] [6] DEBUG: registered_delivery: 1 = 0x0001
2007-11-08 09:54:01 [19112] [6] DEBUG: replace_if_present_flag: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: data_coding: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: sm_default_msg_id: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: sm_length: 30 = 0x001e
2007-11-08 09:54:01 [19112] [6] DEBUG: short_message:
2007-11-08 09:54:01 [19112] [6] DEBUG:Octet string at 0x1da56910:
2007-11-08 09:54:01 [19112] [6] DEBUG: len: 30
2007-11-08 09:54:01 [19112] [6] DEBUG: size: 31
2007-11-08 09:54:01 [19112] [6] DEBUG: immutable: 0
2007-11-08 09:54:01 [19112] [6] DEBUG: data: 54 65 73 74 20 50 53
4d 53 20 66 72 6f 6d 20 4a Test PSMS from J
2007-11-08 09:54:01 [19112] [6] DEBUG: data: 75 61 6e 20 4e 69 6e
20 28 53 4d 50 50 29 uan Nin (SMPP)
2007-11-08 09:54:01 [19112] [6] DEBUG:Octet string dump ends.
2007-11-08 09:54:01 [19112] [6] DEBUG: charge_type: 1
2007-11-08 09:54:01 [19112] [6] DEBUG: charge_amount: 99
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP PDU dump ends.
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP[om-1]: Got PDU:
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP PDU 0x1da7c4c0 dump:
2007-11-08 09:54:01 [19112] [6] DEBUG: type_name: submit_sm_resp
2007-11-08 09:54:01 [19112] [6] DEBUG: command_id: 2147483652 = 0x8004
2007-11-08 09:54:01 [19112] [6] DEBUG: command_status: 0 = 0x
2007-11-08 09:54:01 [19112] [6] DEBUG: sequence_number: 28 = 0x001c
2007-11-08 09:54:01 [19112] [6] DEBUG: message_id:
2007-11-08 09:54:01 [19112] [6] DEBUG:Octet string at 0x1da64ea0:
2007-11-08 09:54:01 [19112] [6] DEBUG: len: 23
2007-11-08 09:54:01 [19112] [6] DEBUG: size: 24
2007-11-08 09:54:01 [19112] [6] DEBUG: immutable: 0
2007-11-08 09:54:01 [19112] [6] DEBUG: data: 30 31 30 37 48 2d 31
31 30 38 47 2d 30 39 35 34 0107H-1108G-0954
2007-11-08 09:54:01 [19112] [6] DEBUG: data: 44 2d 30 31 33 39 52
D-0139R
2007-11-08 09:54:01 [19112] [6] DEBUG:Octet string dump ends.
2007-11-08 09:54:01 [19112] [6] DEBUG: SMPP PDU dump ends.
Now, the third optional parameter I defined (reason_id) is sent by the
gateway when they send a DLR
I defined my dlr-url and dlr-mask like this:
$dlr_mask = '31';
$dlr_url =
urlencode(http://myHost.tld/dlr.php?smsc-id=%istatus=%danswer=%Ato=%Pfrom=%pts=%tmeta_data=%D;);
There
Re: [PATCH] SMPP Optional Parameters
Hi! 3 months have passed by, and just today I was able to start testing this!!! Haven't been able to test too much yet though I've sent some premium messages, making them billable and setting it's pricepoints via TLVs and everything went ok Tomorrow I'm going to make more tests, I want to test it also with TLVs on the DLRs PDUs, and then with SQLbox with Alejandro Guerrieri's patch I hope to be able to finish them tomorrow and post my results After that, I hope to be able to make the docs patch so we can get this into Kannel!!! Regards, Juan On Sep 27, 2007 1:02 PM, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, any progress on testing and userguide :)? Alejandro Guerrieri wrote: So far I've tested the sendsms - SMSC portion using Logica SMSC simulator and it works like a charm! Great job Alex! I've also made a patch for Sqlbox-standalone (already sent to dev list). I'll test the SMSC - Kannel portion as soon as I can get a hand on a SMSC and/or Simulator capable of sending TLV's (Logica cannot AFAIK, just displays the raw bytes when TLV's are received). We're just missing the userguide docs (coming after completing the tests). Regards, Alejandro On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump 'http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex -- Thanks, Alex
Re: [PATCH] SMPP Optional Parameters
Hi, yes, the format is OK. I'm not sure whether the value of HTTP header should be url-encoded? If it doesn't work post the whole debug log (smsbox + bearerbox). Kyriacos Sakkas wrote: Hi, Anybody has some extra info on how to us with post? (X-Kannel-Meta-Data). I am trying but not able it seems to get the proper format. Would this be considered ok? X-Kannel-Meta-Data: ?smpp?mytag=12 Definition is: group = smpp-tlv name = mytag tag = 0x1521 type = octetstring length = 32 Thanks, Kyriacos Alexander Malysh wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump 'http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex
Re: [PATCH] SMPP Optional Parameters
Hi, Anybody has some extra info on how to us with post? (X-Kannel-Meta-Data). I am trying but not able it seems to get the proper format. Would this be considered ok? X-Kannel-Meta-Data: ?smpp?mytag=12 Definition is: group = smpp-tlv name = mytag tag = 0x1521 type = octetstring length = 32 Thanks, Kyriacos Alexander Malysh wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump 'http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- 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] **
Re: [PATCH] SMPP Optional Parameters
Hi, If this is known to somebody, please tell: Will this patch work for capturing optional parameters presend in DLR messages ? That is can I use meta-data=%D in my DLR-URL? Thanks, Kyriacos Sakkas Alexander Malysh wrote: Hi, any progress on testing and userguide :)? Alejandro Guerrieri wrote: So far I've tested the sendsms - SMSC portion using Logica SMSC simulator and it works like a charm! Great job Alex! I've also made a patch for Sqlbox-standalone (already sent to dev list). I'll test the SMSC - Kannel portion as soon as I can get a hand on a SMSC and/or Simulator capable of sending TLV's (Logica cannot AFAIK, just displays the raw bytes when TLV's are received). We're just missing the userguide docs (coming after completing the tests). Regards, Alejandro On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump 'http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex -- 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] **
Re: [PATCH] SMPP Optional Parameters
Hi, any progress on testing and userguide :)? Alejandro Guerrieri wrote: So far I've tested the sendsms - SMSC portion using Logica SMSC simulator and it works like a charm! Great job Alex! I've also made a patch for Sqlbox-standalone (already sent to dev list). I'll test the SMSC - Kannel portion as soon as I can get a hand on a SMSC and/or Simulator capable of sending TLV's (Logica cannot AFAIK, just displays the raw bytes when TLV's are received). We're just missing the userguide docs (coming after completing the tests). Regards, Alejandro On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump 'http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex -- Thanks, Alex
Re: [PATCH] SMPP Optional Parameters
Hi Alex! Unfortunately I haven't been able to test it yet... :( I'm opening a new company, and starting this monday, so I've been very busy! Compiled Kannel with the patch with no problem On tuesday a partner of mine from the US is comming down here, so during the week I'll make tests with his phone and post the results Sorry for the delay!!! Juan On 9/27/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, any progress on testing and userguide :)? Alejandro Guerrieri wrote: So far I've tested the sendsms - SMSC portion using Logica SMSC simulator and it works like a charm! Great job Alex! I've also made a patch for Sqlbox-standalone (already sent to dev list). I'll test the SMSC - Kannel portion as soon as I can get a hand on a SMSC and/or Simulator capable of sending TLV's (Logica cannot AFAIK, just displays the raw bytes when TLV's are received). We're just missing the userguide docs (coming after completing the tests). Regards, Alejandro On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump 'http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex -- Thanks, Alex
[PATCH] SMPP Optional Parameters
Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump 'http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex smpp-tlv.patch.gz Description: GNU Zip compressed data
Re: [PATCH] SMPP Optional Parameters
Alexander. First of all, many many thanks for this :) Long awaited patch! I will be setting up a test SMPP connection with OpenMarket from the US, I hope this week, so I'll test it with them. Will let you know about the results!!! Question, will it compile against Kannel 1.4.1 or needs current form CVS? Regards, Juan On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump ' http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123 ' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex
Re: [PATCH] SMPP Optional Parameters
Hi, Juan Nin wrote: Alexander. First of all, many many thanks for this :) Long awaited patch! I will be setting up a test SMPP connection with OpenMarket from the US, I hope this week, so I'll test it with them. Will let you know about the results!!! Question, will it compile against Kannel 1.4.1 or needs current form CVS? don't know, but I would suggest to use current CVS. Regards, Juan On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump ' http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123 ' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex -- Thanks, Alex
Re: [PATCH] SMPP Optional Parameters
On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, Juan Nin wrote: Alexander. First of all, many many thanks for this :) Long awaited patch! I will be setting up a test SMPP connection with OpenMarket from the US, I hope this week, so I'll test it with them. Will let you know about the results!!! Question, will it compile against Kannel 1.4.1 or needs current form CVS? don't know, but I would suggest to use current CVS. oks, would also be cool to know if Martin Conte will apply patches for SQLbox to be able to work with this or if someone makes them, if he would like to add them to SQLbox. :) Juan
Re: [PATCH] SMPP Optional Parameters
I think I can do the mods if Martin is too busy. Alex, _great_ job and thanks a lot for making this a reality. Regards, Alejandro On 8/6/07, Juan Nin [EMAIL PROTECTED] wrote: On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hi, Juan Nin wrote: Alexander. First of all, many many thanks for this :) Long awaited patch! I will be setting up a test SMPP connection with OpenMarket from the US, I hope this week, so I'll test it with them. Will let you know about the results!!! Question, will it compile against Kannel 1.4.1 or needs current form CVS? don't know, but I would suggest to use current CVS. oks, would also be cool to know if Martin Conte will apply patches for SQLbox to be able to work with this or if someone makes them, if he would like to add them to SQLbox. :) Juan -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
Re: [PATCH] SMPP Optional Parameters
So far I've tested the sendsms - SMSC portion using Logica SMSC simulator and it works like a charm! Great job Alex! I've also made a patch for Sqlbox-standalone (already sent to dev list). I'll test the SMSC - Kannel portion as soon as I can get a hand on a SMSC and/or Simulator capable of sending TLV's (Logica cannot AFAIK, just displays the raw bytes when TLV's are received). We're just missing the userguide docs (coming after completing the tests). Regards, Alejandro On 8/6/07, Alexander Malysh [EMAIL PROTECTED] wrote: Hello all, as promised I rebased my SMPP TLV patch and post is here for review. Please anybody if possible, write a userguide because I don't have time to do it and without userguide this patch will not get into mainline. Short description... In the config group = smpp-tlv name = some-name tag = 0x1601 type = integer|nulterminated|octetstring length = 4 In the msg struct I added meta_data field that can contain any parameters not only for smpp. meta_data is formated as follows: meta_data = ?group?key=valuekey1=value1?smpp?some-name=ABC then SMPP module just set all TLVs that can be found in the smpp group of meta_data. With this approach it's possible to use this generic interface to put some extra functionality into any SMSC module. Example sendsms url: lynx -source -dump 'http://localhost:13013/cgi-bin/sendsms?username=testerpassword=foobarto=123from=456text=textmeta-data=%3Fsmpp%3Fsome-name%3D123' Example MO url: http://localhost:123/bla/...meta-data=%D;... or with Post: X-Kannel-Meta-Data or with xml: meta-datax/meta-data Please test it and let me know how it works. P.S. I don't like how smpp_pdu_init and smpp_pdu_shutdown functions called. They called from bb_smscconn.c but I have not found a better place to call these. This may change in future ;) -- Thanks, Alex -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/ LinkedIn: http://www.linkedin.com/in/aguerrieri
