On 25.05.2008, at 19:31, sangprabv wrote:
Hi,
What I mean here is, currently Kannel support 1,2,4,8,16 as DLR value.
My telco send back the DLR with 17 as the value which means
insufficient
balance via HTTP SMSC (http://host:port/?dlr=17).
You are mixing up what kannel uses as dlrmask and what external
suppliers use as dlrmask.
Those values are independent.
I have patched smsc_http.c to grab this value. But since this value
is not a standard
one for Kannel, then Kannel doesn't destroy this dlr mask.
Destroy? How you want to destroy a DLR mask? It's an integer used
internally.
What Im trying to do also is how to destroy this dlr mask. TIA.
Regards,
Willy
On Sun, 2008-05-25 at 15:12 +0200, Andreas Fink wrote:
what you mean by "custom" dlr mask?
DLR mask is a field which is internal to kannel. Its a bitfield. so
0x17 would give you 0x10 + 0x4 + 0x2 + 0x1 type of messages back.
Depending on which bits are set, certain reports from the SMSC are
sent back or not. Some SMSC's dont support all of those. For example
SMPP doesnt have a message called "Buffered" like this is in EMI/UCP.
On 25.05.2008, at 10:33, sangprabv wrote:
Hi,
I have a situation where I need to implement a custom dlr mask. I
have
read dlr.h, and I found some definitions for each dlr mask.
My question is if I need to implement let say 17 as a custom dlr
mask.
Will it be:
#define DLR_CUSTOM 0x17?
And also how to make Kannel automatically destroy this custom dlr
mask?
TIA
Regards,
Willy
--
[sangprabv]
http://www.sangprabv.web.id
