Hello,
what I have unederstood is that TLVs allow to catch additional meta-data
from a SMSC when encapsulated into a SMPP request.
Configure them is quite easy: contact your smsc and ask for docs, they will
basically tell what additional meta-data they add that you can use and they
will also tell the lenght/type for each TLV, so it's a matter or adding it
to my conf file in kannel.
Now my issue comes when I need to make use of those TLVs.
My SMSC does not use a unique id for each SMS ("field-timestamp" in the
mysql DLR storage), so kannel gets crazy when receiving DLRs.
For instance, the SMSC sets the field-timestamp with a friendly "0" or "1",
so when the DLRs comes back, there is no guarantee that the correct SMS
gets the delivered status because kannel makes use of that timestamp to map
the DLR with the SMS (and yes, also the recipient number if remember
correctly).
In my case, my SMSC inserts its unique ID into the meta-data, so I'm
wondering how to tell Kannel to use that info stored in the meta-data as
the sms unique id.
Any suggestion ?
Thanks to all!
--
Julien Buratto
Linkas SRL
Tel. 0230321419
PS: Some time ago, another guy went into this and made a patch for its
1.4.3 version. That works very well. Alejandro suggested to use TLVs but I
suppose that guy made its own way without TLVs. I would be very interested
to see how to solve that issue with TLVs instead of patching.
