Re: Kannel Redis - can I force the destination in the key name?

Thanks for the clarification. Turned out that in my case, some of the message IDs would get recycled given enough time and volume. So in order to generate unique redis keys, I still had to include the destination. In case anyone is interested, I ended up making a local change to

Re: Kannel Redis - can I force the destination in the key name?

Ts is just the old variable name, the remote message id is used for that field, not a time stamp. So as long as your supplier provides a unique message ID you won't have collisions On Tuesday, 01 November 2016, Robert Chen wrote: > Hi, I'm trying to set up

Kannel Redis - can I force the destination in the key name?

Hi, I'm trying to set up Kannel with Redis. My concern is that some DLRs would be lost due to timestamp collisions. And my question is whether hard-coding dlr_redis_add to use the destination (at least for my personal installation) is the best approach. dlr_redis.c: Changing: if (entry->use_dst