Juan is correct. With repect to version I would with any recent 1.4.3 svn,
latest is safest. I am not sure that 1.5.0 is production ready.
BR,
Nikos
----- Original Message -----
From: "Juan Nin" <[email protected]>
To: <[email protected]>
Sent: Saturday, October 30, 2010 7:10 AM
Subject: Re: Optional / Extra TLV in Delivery Report (DeliverySM) - HLR
The TLVs you define can work for all: MOs, MTs and DLRs.
So if your provider sends TLVs on the DLR just define the TLVs and
then capture them accordingly
Regards
On Fri, Oct 29, 2010 at 4:29 PM, Blast SMS Team <[email protected]> wrote:
Hi Nikos,
You are talking about the Development Release 1.5?
IS this the correct part of the UG?
http://www.kannel.org/download/1.5.0/userguide-1.5.0/userguide.html#META-DATA
The UG talks about SMPP TLVs, is that going to pass to the DLR ? Or do
I have to assign it to the DLR somehow?
Regards,
J
2010/10/29 Nikos Balkanas <[email protected]>:
Yes. Latest kannel supports SMPP TLV data. UG has some excellent
configuration examples.
BR,
Nikos
----- Original Message ----- From: "Blast SMS Team" <[email protected]>
To: <[email protected]>
Sent: Friday, October 29, 2010 2:33 PM
Subject: Optional / Extra TLV in Delivery Report (DeliverySM) - HLR
Hi
I am wondering if Kannel can, or if there is a patch available to get
optional TLVs sent through on the delivery report (DeliverySM).
These extra parameters are actually HLR Lookup results.
Regards,
J
