Hi Ravi,
Had same problem when cinfiguring with mysql enabled, without mysql,
worked fine.
Kyriacos Sakkas
Ravi Bhalotia wrote:
> Thanks Juan. I did find that patch, and patched it against a cvs version of
> kannel. It compiled and installed fine, but it segfaults whenever I try to
> send a message. So, am not sure if I missed anything during the patch,
> though the patch command worked fine and reported everything succeeded.
>
> Regards,
> Ravi
>
> -----Original Message-----
> From: Juan Nin [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 26, 2007 7:12 AM
> To: Ravi Bhalotia
> Cc: [email protected]
> Subject: Re: optional vendor specific DLR TLV
>
> check out this threads:
>
> http://www.kannel.org/pipermail/devel/2007-August/001148.html
> http://www.kannel.org/pipermail/devel/2007-August/001156.html
>
> Regards,
>
> Juan
>
> On Nov 25, 2007 7:36 PM, Ravi Bhalotia
> <[EMAIL PROTECTED]> wrote:
>
>> Hello,
>> We are running kannel 1.4.1 to connect to a smsc that is sending
>>
> additional
>
>> information about a status of the message as an optional DLR TLV. I have
>> patched various files so that I can see that the bearerbox is recognizing
>> it, but when smsbox calls the dlr url it does not include the optional
>>
> TLV.
>
>> Can someone please point me to any patches or any information to achieve
>> this? Basically, the optional TLV is at 0x1521 and I need the ability to
>> include this in the dlr-url when smsbox calls it. All other parameters are
>> being successfully called, except the optional one. Please let me know if
>> anybody can provide any feedback on how to achieve this.
>>
>> Regards,
>> Ravi Bhalotia
>>
>>
>>
>>
>>
>
>
>
--
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] **
