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

USSD SMPP integration

Hi, I am trying to use kannel for integrating with USSD GW using SMPP. My bind to USSD GW is ok. MO is ok and MT has some problem, msg is receiving in handset but if I send or cancel msg, it is is re-sending the same msg to my handset repetitively. I am using following parameters in