We have encountered this very situation. The solution I settled on has
multiple kannel servers configured with transmit binds. So a load balancer
can hit any instance for sending MT messages. However, only ONE instance is
configured with receive binds. My logic was that the SMSC will queue MO and
On Sunday 29 March 2020 at 18:42:12, Alexander Malysh wrote:
> Hi,
>
> unfortunately you mixed two things together.
Very probably. I didn't find the documentation too clear on this topic.
> 1. Store support.
> It’s a snapshot of messages that Kannel has in his memory (RAM) stored
>
Hi,
unfortunately you mixed two things together.
1. Store support.
It’s a snapshot of messages that Kannel has in his memory (RAM) stored
either on disk (spool, file) or in Redis.
This store is used for a case if Kannel crashes, then messages are not
lost.
This is _NOT_
On Sunday 29 March 2020 at 05:37:25, Arun wrote:
> Hello Friends
> I am reading the document Kannel Architecture
> $Revision: 1.20 $
> Is this the latest document
It appears that it is.
However, see https://www.kannel.org/arch.shtml (which has several links which
do not work), which contains
