|
I think I got the answer. When I was reading the numbers from the
text file line by line I think I was also getting the ‘\0’ or ‘\n’
at the end of the line which was causing kannel receive the number wrong. Although the data entered in the database
looked fine I think it was not actually right. I am still confused about this
but at least it is working now. So if you are reading numbers from a text
file to send as bulk, make sure that the number you are getting is just the
number and not the ‘\n’ or ‘\0’ included at the end. Regards, Cavit Dolgun From: Cavit Dolgun
[mailto:[EMAIL PROTECTED] Hi, I am sending sms using sqlbox and kannel cvs-20061026 on
FC4. When I send a single sms using my php script it is ok
but when I insert more than one number using my php script to send bulk the
submit_sm pdu for all numbers except the last number is 2006-11-07 12:37:47 [29281] [6] DEBUG: SMPP PDU 0x846e1a8
dump: 2006-11-07 12:37:47 [29281] [6] DEBUG:
type_name: submit_sm 2006-11-07 12:37:47 [29281] [6] DEBUG:
command_id: 4 = 0x00000004 2006-11-07 12:37:47 [29281] [6] DEBUG:
command_status: 0 = 0x00000000 2006-11-07 12:37:47 [29281] [6] DEBUG:
sequence_number: 62 = 0x0000003e 2006-11-07 12:37:47 [29281] [6] DEBUG: service_type:
NULL 2006-11-07 12:37:47 [29281] [6] DEBUG:
source_addr_ton: 5 = 0x00000005 2006-11-07 12:37:47 [29281] [6] DEBUG:
source_addr_npi: 0 = 0x00000000 2006-11-07 12:37:47 [29281] [6] DEBUG:
source_addr: "test" 2006-11-07 12:37:47 [29281] [6] DEBUG:
dest_addr_ton: 2 = 0x00000002 2006-11-07 12:37:47 [29281] [6] DEBUG:
dest_addr_npi: 1 = 0x00000001 2006-11-07 12:37:47 [29281] [6]
DEBUG: destination_addr: 2006-11-07 12:37:47 [29281] [6]
DEBUG: Octet string at 0x8472fe0: 2006-11-07 12:37:47 [29281] [6]
DEBUG: len: 14 2006-11-07 12:37:47 [29281] [6]
DEBUG: size: 15 2006-11-07 12:37:47 [29281] [6]
DEBUG: immutable: 0 2006-11-07 12:37:47 [29281] [6]
DEBUG: data: 39 36 36 35 30 38 38 38 32 33 31 31
0d 0a
966508882311.. ß- this number is
different for each submit 2006-11-07 12:37:47 [29281] [6]
DEBUG: Octet string dump ends. 2006-11-07 12:37:47 [29281] [6] DEBUG:
esm_class: 3 = 0x00000003 2006-11-07 12:37:47 [29281] [6] DEBUG:
protocol_id: 0 = 0x00000000 2006-11-07 12:37:47 [29281] [6] DEBUG:
priority_flag: 0 = 0x00000000 2006-11-07 12:37:47 [29281] [6] DEBUG:
schedule_delivery_time: NULL 2006-11-07 12:37:47 [29281] [6] DEBUG:
validity_period: NULL 2006-11-07 12:37:47 [29281] [6] DEBUG:
registered_delivery: 1 = 0x00000001 2006-11-07 12:37:47 [29281] [6] DEBUG:
replace_if_present_flag: 0 = 0x00000000 2006-11-07 12:37:47 [29281] [6] DEBUG:
data_coding: 0 = 0x00000000 2006-11-07 12:37:47 [29281] [6] DEBUG:
sm_default_msg_id: 0 = 0x00000000 2006-11-07 12:37:47 [29281] [6] DEBUG:
sm_length: 7 = 0x00000007 2006-11-07 12:37:47 [29281] [6] DEBUG:
short_message: "testing" 2006-11-07 12:37:47 [29281] [6] DEBUG: SMPP PDU dump ends. Which then returns and invalid destination error from the
smsc. A normal pdu should look like 2006-11-07 12:37:47 [29281] [6]
DEBUG: destination_addr: 966508882311 I get the normal pdu for the last number that is submitted. I checked the database the data entered in the sqlbox db is
ok. Any ideas what may cause this kind of behaviour? Thanks, Cavit Dolgun |
- Weird submit_sm in kannel logs Cavit Dolgun
- RE: Weird submit_sm in kannel logs Cavit Dolgun
