I wrote a tutorial a while back for extracting TLV's using the meta data
feature of the latest CVS Kannel. You can see it here:

http://www.ddj.co.za/archives/69/extracting-meta-data-from-smpp-tlvs-with-kannel

Hope that helps you.

Cheers,
Donald

2009/9/27 Juan Nin <[email protected]>

> As Alejandro already said, you need to use TLVs, and for that you
> should use the latest CVS version and not 1.4.3
>
> This is probably not the latest mBlox SMPP specs, it's from 2007, but
> I guess this part has not changed.
> According to
> http://data.getafreelancer.com/project/283852/mBlox%20SMPP%20Interface%20Technical%20Manual_v2.3.pdf
>
> the operator ID comes on the "mblox_operator" optional parameter (TLV).
> On page 23 of that document you got it's description, but you better
> check the latest mBlox specs just in case.
>
> So, first of all download latest CVS snapshot, and read the SMPP
> optional parameters configuration section.
> Then check the latest mBlox SMPP specs, and configure all the needed
> optional parameters accordingly.
>
> Regards,
>
> Juan
>
>
>
>
> On Sun, Sep 27, 2009 at 12:25 PM, Alejandro Guerrieri
> <[email protected]> wrote:
> > Using the meta-data functionality. You need to configure the TLV's and
> > they'll be available as meta-data.
> > You need to use latest CVS, though. 1.4.3 won't cut it.
> > Regards,
> > Alejandro
> >
> > On Sun, Sep 27, 2009 at 2:00 PM, Karan Zaveri <[email protected]>
> wrote:
> >>
> >> Yes I am using mBlox as our aggregator. How do you catch the TLV coming
> >> from the aggregator? I am 100%
> >>
> >> sure mBlox sends that information as I mentioned earlier I was able to
> >> catch that using a script we wrote to
> >> test…
> >>
> >>
> >>
> >> From: Alejandro Guerrieri [mailto:[email protected]]
> >> Sent: Saturday, September 26, 2009 2:54 PM
> >> To: Karan Zaveri
> >> Cc: Nikos Balkanas; [email protected]
> >>
> >> Subject: Re: Incorrect Operator ID returned
> >>
> >>
> >>
> >> You're using an aggregator right? Maybe they use a TLV to send you the
> >> carrier id? Check the documentation or ask your SMSC provider about it.
> >>
> >>
> >>
> >> Regards,
> >>
> >>
> >>
> >> Alejandro
> >>
> >> On Sat, Sep 26, 2009 at 7:13 PM, Karan Zaveri <[email protected]>
> wrote:
> >>
> >> Thanks Nikos,
> >>
> >>
> >>
> >> I tried that but it didn’t work. What I really need is the message
> >> sender’s Operator’s ID which is a number
> >> identifying who the operator is like Sprint = 31005, Cingular = 31002
> >>  etc. The %o returns the system-type
> >> variable from the config file and the %i returns the SMPP hostname which
> >> is not what I am looking for.
> >>
> >> I am not sure if this is a bug in Kannel or some other setting that I
> need
> >> to do.
> >>
> >>
> >>
> >> Appreciate your help.
> >>
> >>
> >>
> >> Thanks
> >>
> >> Karan
> >>
> >>
> >>
> >> From: Nikos Balkanas [mailto:[email protected]]
> >> Sent: Saturday, September 26, 2009 11:50 AM
> >> To: Karan Zaveri; [email protected]
> >> Subject: Re: Incorrect Operator ID returned
> >>
> >>
> >>
> >> Hi,
> >>
> >>
> >>
> >> Try %i to get the smsc-id.
> >>
> >>
> >>
> >> BR,
> >>
> >> Nikos
> >>
> >> ----- Original Message -----
> >>
> >> From: Karan Zaveri
> >>
> >> To: [email protected]
> >>
> >> Sent: Saturday, September 26, 2009 4:12 PM
> >>
> >> Subject: Incorrect Operator ID returned
> >>
> >>
> >>
> >> Hi All,
> >>
> >>
> >>
> >> I have been trying to integrate Kannel with our SMS application and so
> far
> >> have had success receiving
> >> messages however, I am having a bit of hard time trying to get Kannel
> >> return the operator id of the message.
> >>
> >> Based on the documentation I set the %o value in the response URL but
> >> instead of sending a numeric operator
> >> ID Kannel returns the smsc-username value. I am not sure if there is any
> >> additional setting that would need
> >> to be done in order to get the original operator id of the sender. Any
> >> help would be appreciated.
> >>
> >>
> >>
> >> Attached is my config file.
> >>
> >>
> >>
> >> Thanks
> >>
> >> Karan
> >>
> >> No virus found in this incoming message.
> >> Checked by AVG - www.avg.com
> >> Version: 8.5.409 / Virus Database: 270.13.112/2390 - Release Date:
> >> 09/26/09 05:51:00
> >>
> >>
> >>
> >> No virus found in this incoming message.
> >> Checked by AVG - www.avg.com
> >> Version: 8.5.409 / Virus Database: 270.13.112/2390 - Release Date:
> >> 09/26/09 05:51:00
> >
>
>
>
> --
> Juan Nin
> 3Cinteractive / Mobilizing Great Brands
> http://www.3cinteractive.com
>
>


-- 
Donald Jackson
http://www.thearchitech.com
donald(a)thearchitech.com

Reply via email to