Hello,

it is not the problem about TLV, because we are running kannel from cvs
branch. It is the problem with proprietary PDU's..

regards,
Martynas

> You can checkout the cvs version of kannel which is able to handle
> customized TLVs on smpp...
>
> Julien
>
> 2009/6/9 V <[email protected]>:
>> Hello,
>>
>> Yes, we already run kannel with meta-data/tlv support (cvs branch). But,
>> it's strange, why LMT use some PDU, that are non standart.
>>
>> On what conditions we could get that patch?
>>
>> regards,
>> Martynas
>>
>>> Hi,
>>>
>>> LMT uses SMPP meta-data optional parameters, its easy to implement it
>>> using meta-data build.
>>> LMT additionally uses two specific PDU's (LMT_REPORT and
>>> LMT_REPORT_RESP) what must be
>>> programmed directly into Kannel (those are actually LMT specific DLR
>>> PDU's and can be mapped to
>>> DLR requests in Kannel)
>>>
>>> We are using cvs-meta-data build with LMT patch, works correctly.
>>>
>>> Illimar
>>>> Hi,
>>>>
>>>> without their Spec is this impossible to say if Kannel can handle
>>>> this...
>>>>
>>>> Please provide Spec.
>>>>
>>>> Thanks,
>>>> Alex
>>>>
>>>> Am 09.06.2009 um 10:11 schrieb V:
>>>>
>>>>> Hello,
>>>>>
>>>>> Any have some experience with connection to LMT operator in Latvia
>>>>> with
>>>>> proprietary SMPP extensions for DLR and billing reports?
>>>>> I found previous thread about it, but with no decisions..:(
>>>>>
>>>>> Kind regards,
>>>>> Martynas
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> Hi,
>>>>>
>>>>> Am I right that LMT uses reserved command ids there?
>>>>>
>>>>> If yes, then in my opinion it may be useful to implement some API for
>>>>> adding vendor specific SMPP commands processing as DSO and after this
>>>>> LMT extension as such DSO :-)
>>>>>
>>>>>
>>>>> Illimar Reinbusch - Telejazz.com wrote:
>>>>>> LMT uses SMPP procol with some additions to it for billing and DLR
>>>>>> purpose.
>>>>>> *
>>>>>> *For example:*
>>>>>>
>>>>>> * **LMT_REPORT – Contains information regarding the result of the
>>>>>> processing and execution of the SUBMIT_SM command;*
>>>>>> *LMT_GEN_CODE_RESP – Contains information regarding the result of
>>>>>> the
>>>>>> processing and execution of the LMT_GEN_CODE command**
>>>>>> LMT_VERIFY_CODE_RESP – Contains information regarding the result
>>>>>> of
>>>>>> the
>>>>>> processing and execution of the LMT_ VERIFY_CODE command;
>>>>>> *
>>>>>> *LMT_REPORT_RESP – contains information regarding the results of
>>>>>> the
>>>>>> LMT_REPORT command’s execution;*
>>>>>> *LMT_GEN_CODE – requests to generate access information for the
>>>>>> Service
>>>>>> provider’s public resource, if authorization is made according to
>>>>>> the
>>>>>> procedure outlined in Art.3.7. and 3.8. of the Addendum No.2 to this
>>>>>> Contract;*
>>>>>> *LMT_VERIFY_CODE – requests to verify the access information
>>>>>> provided by
>>>>>> the Client for the public resource;
>>>>>>
>>>>>> Illimar
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> what is LMT extention? Could you please provide some links?
>>>>>>>
>>>>>>> Illimar Reinbusch - Telejazz.com wrote:
>>>>>>>
>>>>>>>
>>>>>>>> Have somebody implemented it or its new to Kannel. Would Kannel be
>>>>>>>> interested adding support for it to Kannel if someone (me) would
>>>>>>>> write it?
>>>>>>>>
>>>>>>>> Illimar
>>>>>>>>
>>>>>>>> Jurijs Cerepanovs wrote:
>>>>>>>>
>>>>>>>>> Illimar Reinbusch - Telejazz.com wrote:
>>>>>>>>> Current implementation needs patch for kannel - it's simply to
>>>>>>>>> rewrite
>>>>>>>>> smpp connector for understanding LMT_REPORT e.t.c proprietary
>>>>>>>>> packets.
>>>>>>>>>
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> Has anybody implemented or added new protocol to support Latvia
>>>>>>>>>> LMT
>>>>>>>>>> operator
>>>>>>>>>> SMPP protocol with LMT extentsions?
>>>>>>>>>>
>>>>>>>>>> Would u suggest adding to to current SMPP development or add new
>>>>>>>>>> protocol
>>>>>>>>>> based on SMPP implementation?
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Illimar
>>>>>
>>>>>
>>>>> --
>>>>> Michael Bochkaryov
>>>>> www.netstyle.com.ua
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
> --
> Julien Buratto
>



Reply via email to