Re: CIMD DLRs, reading field 062

Hi Kyriaco,

Such issues are best addressed to devel group. Please do not x-post, people 
are sensitive here about keeping mail low.

This is a change that affects only the CIMD2 driver. I see no problem with 
it, as long as the rest of the CIMD2 users agree with it. Personally I use 
only SMPP so I vote OK, but my vote shouldn't count :-)

BR,
Nikos
----- Original Message ----- 
From: "Kyriacos Sakkas" <[email protected]>
To: <[email protected]>; "Kannel Devel" <[email protected]>
Sent: Monday, April 12, 2010 5:47 PM
Subject: Re: CIMD DLRs, reading field 062


>I have taken this live and it seems to be working ok.
>
> Kyriacos
>
> On 12/04/2010 16:36, Kyriacos Sakkas wrote:
>> This should be a bit better :)
>>
>> Kyriacos
>>
>> On 12/04/2010 16:26, Kyriacos Sakkas wrote:
>>
>>> What do you think of this? I will try it, but wondering if anyone things
>>> this will not work. I know this is not a proper solution, but it should
>>> be OK.
>>>
>>> Kyriacos
>>>
>>> On 12/04/2010 16:01, Kyriacos Sakkas wrote:
>>>
>>>
>>>> Hi All,
>>>>
>>>> This question has been posted before, but I have not seen any 
>>>> solutions.
>>>> I need to receive CIMD2 field 062 in my DLR urls. None of the %* 
>>>> options
>>>> seems to return it, even embedded in other info.
>>>> As far as I understand the meta-data TLV system is SMPP only, and will
>>>> not provide a solution.
>>>> >From my system %A returns field 061 and %d the SMPP? 
>>>> >mapping/equivalent
>>>> of field 061.
>>>> Could some small change alter this so that %A returns 062 which is to 
>>>> my
>>>> understanding closer to the extra error info returned in SMPP DLRs.
>>>>
>>>> Thanks in advance,
>>>>
>>>> Kyriacos Sakkas
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
> -- 
> Kyriacos Sakkas
> Development Team
> Netsmart
> Tel: + 357 22 452565
> Fax: + 357 22 452566
> Email: [email protected]
> http://www.netsmart.com.cy
>
> Taking Business to a New Level!
>
> ** Confidentiality Notice: The information contained in this email
> message may be privileged, confidential and protected from disclosure.
> If you are not the intended recipient, any dissemination, distribution,
> or copying of this  email message is strictly prohibited.
> If you think that you have received this email message in error, please
> email the sender at [email protected] **
>