Hello All,
Below is my bearerbox log.
My SMSC guy tells me I have to set the status report value( guess he
meant SMS-STATUS-REPORT) to 1 for me to receive delivery reports.
How do I do that with Kannel?
2009-10-20 12:43:40 [18380] [6] DEBUG: SMPP[smsc2]: Manually forced
source addr ton = 0, source add npi = 0
2009-10-20 12:43:40 [18380] [6] DEBUG: SMPP[smsc2]: Manually forced
dest addr ton = 0, dest add npi = 0
2009-10-20 12:43:40 [18380] [6] DEBUG: SMPP[smsc2]: Sending PDU:
2009-10-20 12:43:40 [18380] [6] DEBUG: SMPP PDU 0x794340 dump:
2009-10-20 12:43:40 [18380] [6] DEBUG: type_name: submit_sm
2009-10-20 12:43:40 [18380] [6] DEBUG: command_id: 4 = 0x00000004
2009-10-20 12:43:40 [18380] [6] DEBUG: command_status: 0 = 0x00000000
2009-10-20 12:43:40 [18380] [6] DEBUG: sequence_number: 2 = 0x00000002
2009-10-20 12:43:40 [18380] [6] DEBUG: service_type: NULL
2009-10-20 12:43:40 [18380] [6] DEBUG: source_addr_ton: 1 = 0x00000001
2009-10-20 12:43:40 [18380] [6] DEBUG: source_addr_npi: 1 = 0x00000001
2009-10-20 12:43:40 [18380] [6] DEBUG: source_addr: "****"
2009-10-20 12:43:40 [18380] [6] DEBUG: dest_addr_ton: 1 = 0x00000001
2009-10-20 12:43:40 [18380] [6] DEBUG: dest_addr_npi: 1 = 0x00000001
2009-10-20 12:43:40 [18380] [6] DEBUG: destination_addr:
"****************"
2009-10-20 12:43:40 [18380] [6] DEBUG: esm_class: 3 = 0x00000003
2009-10-20 12:43:40 [18380] [6] DEBUG: protocol_id: 0 = 0x00000000
2009-10-20 12:43:40 [18380] [6] DEBUG: priority_flag: 0 = 0x00000000
2009-10-20 12:43:40 [18380] [6] DEBUG: schedule_delivery_time: NULL
2009-10-20 12:43:40 [18380] [6] DEBUG: validity_period: NULL
2009-10-20 12:43:40 [18380] [6] DEBUG: registered_delivery: 1 =
0x00000001
2009-10-20 12:43:40 [18380] [6] DEBUG: replace_if_present_flag: 0 =
0x00000000
2009-10-20 12:43:40 [18380] [6] DEBUG: data_coding: 0 = 0x00000000
2009-10-20 12:43:40 [18380] [6] DEBUG: sm_default_msg_id: 0 =
0x00000000
2009-10-20 12:43:40 [18380] [6] DEBUG: sm_length: 11 = 0x0000000b
2009-10-20 12:43:40 [18380] [6] DEBUG: short_message: "Hello Peter"
2009-10-20 12:43:40 [18380] [6] DEBUG: SMPP PDU dump ends.
2009-10-20 12:43:41 [18380] [6] DEBUG: SMPP[smsc2]: Got PDU:
2009-10-20 12:43:41 [18380] [6] DEBUG: SMPP PDU 0x794340 dump:
2009-10-20 12:43:41 [18380] [6] DEBUG: type_name: submit_sm_resp
2009-10-20 12:43:41 [18380] [6] DEBUG: command_id: 2147483652 =
0x80000004
2009-10-20 12:43:41 [18380] [6] DEBUG: command_status: 0 = 0x00000000
2009-10-20 12:43:41 [18380] [6] DEBUG: sequence_number: 2 = 0x00000002
2009-10-20 12:43:41 [18380] [6] DEBUG: message_id:
2009-10-20 12:43:41 [18380] [6] DEBUG: Octet string at 0x79a410:
2009-10-20 12:43:41 [18380] [6] DEBUG: len: 36
2009-10-20 12:43:41 [18380] [6] DEBUG: size: 37
2009-10-20 12:43:41 [18380] [6] DEBUG: immutable: 0
2009-10-20 12:43:41 [18380] [6] DEBUG: data: 34 37 30 37 34 39 33
65 2d 34 34 37 66 2d 34 62 4707493e-447f-4b
2009-10-20 12:43:41 [18380] [6] DEBUG: data: 35 31 2d 38 66 66 61
2d 31 63 33 34 61 33 30 35 51-8ffa-1c34a305
2009-10-20 12:43:41 [18380] [6] DEBUG: data: 35 36 32
63 562c
2009-10-20 12:43:41 [18380] [6] DEBUG: Octet string dump ends.
2009-10-20 12:43:41 [18380] [6] DEBUG: SMPP PDU dump ends.
2009-10-20 12:43:41 [18380] [6] DEBUG: DLR[internal]: Adding DLR
smsc=smsc2, ts=1191659838, src=******, dst=**************,
mask=31, boxc=
2009-10-20 12:43:41 [18380] [6] DEBUG: SMSC[smsc2]: creating DLR message
2009-10-20 12:43:41 [18380] [6] DEBUG: SMSC[smsc2]: DLR = http://
**********
Thanks,
Peter.
On Sep 23, 2009, at 11:31 PM, Alan McNatty wrote:
Hi Peter,
Can you provide a full PDU dump (log-level = 0 bearerbox log) of
your submit request so we can see what SMSC driver you are using
(SMPP, etc, etc). Maybe my brain is not engaged correctly this
morning (half way through first cup) but I'm not familiar with
'SRR' (I only have experience with SMPP and AT drivers).
Cheers,
Alan
Otandeka Simon Peter wrote:
Hi List,
My SMSC guy tells I have to set the SRR flag to 1 and then it will
invoke the SMSC to send back a delivery report to the CP/SP.
Can someone explain to me how to do this?
Thanks,
P.
On Sep 22, 2009, at 8:28 PM, Otandeka Simon Peter wrote:
Thanks Nikos.
It was actually an SMSC issue after we analyzed a trace they sent
me.
The SMSC vendors are looking for a solution to the problem.
BR,
Peter.
On Sep 18, 2009, at 9:53 PM, Nikos Balkanas wrote:
Hi,
Since you are succefully getting DLRs, it couldn't be a msg-id-
type issue. It seems that it is an SMSc issues. Can they produce
logs from their end, that they:
1) Correctly receive and interpret DLR mask 31
2) They send to you DLRs 1 & 2
Just saying "there is no problem on our end" is not enough. There
should be able to prove it.
BR,
Nikos
----- Original Message -----
From: Otandeka Simon Peter
To: users@kannel.org User
Sent: Friday, September 18, 2009 7:56 PM
Subject: Problem with DLR's
Hi List,
I am getting a problem with receiving dlrs. I only receive type =
8 only even after setting dlr-mask = 31.
Have tried setting msg-id-type = 0x01 but have still failed to
get type = 1 (delivered) or type = 2 (undelivered) which I really
require. Tried changing the msg-id-type to 1 or 2 or 3 and still
failed.
When I check in the logs I see DLR rerouting for smsc id <smsc2>
disabled.
Further checking I see
2009-09-18 16:43:37 [10004] [6] DEBUG: DLR[internal]: Adding DLR
smsc=smsc2, ts=3199801508, src=555, dst=+25**********, mask=31,
boxc=
2009-09-18 16:43:37 [10004] [6] DEBUG: SMSC[smsc2]: creating DLR
message
2009-09-18 16:43:37 [10004] [6] DEBUG: SMSC[smsc2]: DLR = http://my.test.server/test/test.php?dlrvalue=
%d
The SMSC guy tells me there is no problem on his side.
Any help is welcome.
Cheers,
SPO.
