Kaspars Foigts
2005-02-28 13:22:46 UTC
Still noone bothered answering my mail about DLR's. Anyone, one more
question. This time about source/dest_addr_ton/npi PDU parameters
and delivery reports (again).
On delivery reports - is it possible to request delivery reports, if
incoming short message is processed by kannel? For example:
group = sms-service
keyword = info
keyword-regex = ^(info|i)$
text = "Information"
faked-sender = "123456701"
I would like to know, if this message is delivered to user, but
kannel does not set registered_delivery PDU parameter. I guess this
could be related to my first mail about DLR's not being processed.
Why it is not possible to modify source-addr-ton/npi and
destination-addr-ton/npi? I'm trying to set them in configuration
file:
group = smsc
smsc = smpp
smsc-id = MyOperator
system-type = "VMA"
host = xxx.xxx.xxx.xxx
port = xxxx
smsc-username = xxxxxxxx
smsc-password = xxxxxxxx
source-addr-autodetect = no
msg-id-type = 0x00
# source-addr-ton = 2
source-addr-ton = 23
dest-addr-ton = 1
log-file = /var/log/kannel/smsc-myoperator.log
No matter, what I set, Kannel submits sm with its own TON/NPI's
2005-02-28 15:11:44 [1264] [7] DEBUG: source_addr_ton: 2 = 0x00000002
2005-02-28 15:11:44 [1264] [7] DEBUG: source_addr_npi: 1 = 0x00000001
2005-02-28 15:11:44 [1264] [7] DEBUG: source_addr: "1234567890123456701"
2005-02-28 15:11:44 [1264] [7] DEBUG: dest_addr_ton: 2 = 0x00000002
2005-02-28 15:11:44 [1264] [7] DEBUG: dest_addr_npi: 1 = 0x00000001
2005-02-28 15:11:44 [1264] [7] DEBUG: destination_addr: "3711234567"
Probably related question - if/when will it be available to
configure these parameters? For example, one of our operators uses some
non-standard ton/npi settings. If they do not correspond to
operator's preferences, message is not accepted.
question. This time about source/dest_addr_ton/npi PDU parameters
and delivery reports (again).
On delivery reports - is it possible to request delivery reports, if
incoming short message is processed by kannel? For example:
group = sms-service
keyword = info
keyword-regex = ^(info|i)$
text = "Information"
faked-sender = "123456701"
I would like to know, if this message is delivered to user, but
kannel does not set registered_delivery PDU parameter. I guess this
could be related to my first mail about DLR's not being processed.
Why it is not possible to modify source-addr-ton/npi and
destination-addr-ton/npi? I'm trying to set them in configuration
file:
group = smsc
smsc = smpp
smsc-id = MyOperator
system-type = "VMA"
host = xxx.xxx.xxx.xxx
port = xxxx
smsc-username = xxxxxxxx
smsc-password = xxxxxxxx
source-addr-autodetect = no
msg-id-type = 0x00
# source-addr-ton = 2
source-addr-ton = 23
dest-addr-ton = 1
log-file = /var/log/kannel/smsc-myoperator.log
No matter, what I set, Kannel submits sm with its own TON/NPI's
2005-02-28 15:11:44 [1264] [7] DEBUG: source_addr_ton: 2 = 0x00000002
2005-02-28 15:11:44 [1264] [7] DEBUG: source_addr_npi: 1 = 0x00000001
2005-02-28 15:11:44 [1264] [7] DEBUG: source_addr: "1234567890123456701"
2005-02-28 15:11:44 [1264] [7] DEBUG: dest_addr_ton: 2 = 0x00000002
2005-02-28 15:11:44 [1264] [7] DEBUG: dest_addr_npi: 1 = 0x00000001
2005-02-28 15:11:44 [1264] [7] DEBUG: destination_addr: "3711234567"
Probably related question - if/when will it be available to
configure these parameters? For example, one of our operators uses some
non-standard ton/npi settings. If they do not correspond to
operator's preferences, message is not accepted.
--
Kaspars
http://laacz.lv/
Kaspars
http://laacz.lv/