Thank you all. It worked with the DLR Storage in same database.
- Mahesh
On Sat, Aug 4, 2018 at 12:56 PM, Денис Давыдов wrote:
> Manesh,
>
> See msg-id-type in the User Guide. Also I suggest you to enable debug mode
> to smsc group (log_level=0) to see how your provider work with a message ID
Manesh,
See msg-id-type in the User Guide. Also I suggest you to enable debug mode
to smsc group (log_level=0) to see how your provider work with a message ID
numbers.
--
Regards,
Denis
пт, 3 авг. 2018 г. в 9:38, mahesh Lavanam :
> Hi,
>
> Please help me in resolving the DLR issue
>
> I have a
use database with same DLR table, each kannel database has its own timestamp
table store, so it is normal respond when DLR received in another kannel box...
On Friday, 3 August 2018, 5:13:55 PM GMT+7, mahesh Lavanam
wrote:
But, this error I'm seeing at kannel.log file. I think as it
But, this error I'm seeing at kannel.log file. I think as it is not
identifying it, it does not store into database.
Thanks,
Mahesh
On Fri, Aug 3, 2018 at 2:12 PM, wrote:
> Hi,
>
> do both Kannel share the same database and table ? they have to share DLR
> database.
>
> Alex
>
>
> Am
Hi,
do both Kannel share the same database and table ? they have to share DLR
database.
Alex
> Am 03.08.2018 um 08:37 schrieb mahesh Lavanam :
>
> Hi,
>
> Please help me in resolving the DLR issue
>
> I have a SMS Port with 2 TX & 2 RX sessions enabled.
>
> I have configured these
Hi,
Please help me in resolving the DLR issue
I have a SMS Port with 2 TX & 2 RX sessions enabled.
I have configured these sessions in two kannel configurations with same
smsc id
*kannel1.conf - 1TX & 1RX(SMSbox1 & Bearerbox1) *
#1st tx connection
group = smsc
smsc = smpp
smsc-id = tran
host