rtpengine

3.0 GiB

Tree: 541e2999a9

Author	SHA1	Message	Date
Frederic-Philippe Metz	541e2999a9	Implemented redis-notification base feature. Currently, every rtpengine will subscribe to redis-keyspace notification so it will receive a notification when an call is inserted. If the call is not already handeled by the rtpengine, the call will be restored. The reason for this is to have in-place redundancy. Imagine you have multiple rtpengines running, eachone will have all calls of the others. When one rtpengine fails somehow, infrastructure guys use BGP in order to 'move' the IP address from one rtpengine to another. Thisone can handle the new calls instantly since they're already recovered by redis-notification feature. Next step is internally identify those calls in order to prevent some timers to delete the calls where no RTP flows. Second will be something we call 'partitioning'. It means that the subscription to a redis notify will only be for the keyspace a dedicated rtpengine writes to. This leads to the point that you can make redundancy groups (partitions) of the rtpengines.	10 years ago
Lucian Balaceanu	41fa252d6b	Replacing redis hashkeys with -CALLID_IDX instead of -POINTER	10 years ago
smititelu	72cf55b6fb	Specific REDIS read and write databases Able to specify now, in the config, the redis databases from which rtpengine should read and write session information.	10 years ago
Richard Fuchs	dafde10571	MT#15157 integrate redis module into main code tree obsoletes the entire plugin/module system Change-Id: I6997b7e6e49dac568e844c3e132fa3756cf147cb	10 years ago
Richard Fuchs	05e429c610	C99 inlining rules	12 years ago
Richard Fuchs	a780cf7891	redis updates	13 years ago
Richard Fuchs	900f76a17e	make the callmaster struct private - also requires update to redis module	14 years ago
Richard Fuchs	dc7517121d	remove uuid helper code	14 years ago

8 Commits (541e2999a98997a52d30fa2b52020bf7fa5981b8)