222 Commits (1238d2f3c23f68304562ad4138a830ce64249d7e)

Author	SHA1	Message	Date
Richard Fuchs	725638bccb	remove redis-role redundancy ... Change-Id: Id5a39d008169d4b01cd33a7d82bb0896983e47bc	9 years ago
Frederic-Philippe Metz	1ca0cc5a52	Implemented session limitation logic ... The session limit is only for calls an rtpengine is responsible for. Foreign calls (coming in via redis notification) are not counted as long as the rtpengine is not responsible for those calls. At least that means that the limit may exceed if the calls the rtpengine is responsible for plus the former foreign calls are greater than the limit. This will happen suddenly when the rtpengine becomes responsible for the foreign calls.	9 years ago
Frederic-Philippe Metz	637d1f4cce	Locked redis context on redis notification	9 years ago
Frederic-Philippe Metz	5af1d8fcca	redis operations on the keyspace are now related to the keyspace they belong to	9 years ago
Frederic-Philippe Metz	fd3e2342c1	Implemented redis notification according to RTPENGINE-64 ... Thoughts on that topic so far: There's one thing to keep also in mind. What do we do if the call changes (streams) and the backup node is notified ? Currently we only know (by subscribing to the 'notifier-' prefix that in fact it has changed, but we don't know what has changed in detail. Subscribing to everything would lead to the problem that we have to take care about synchronising the the new streams with the old ones. Without having a look at the code that might be a lot of effort and ... I guess that's why richard likes to ... have clean states of the calls. Synchronizing is always a mess. Easier to delete and setup new. I thought about the following solution for makes things more abstract and easier to understand: 1. Whenever that call on a backup node (foreign call) has seen a packet (also timers are started then), we do not process any notification by a redis notification for this call (caus' the RTP-IP has already been switched). More precise and abstract that means: If a node has taken over the responsibility for that call (by having seen a packet), it assumes that notifications from the former node to be dropped. The call will be deleted when either the timer fires or (for other companies) the control channel address has also been switched and via that channel the call is deleted. 2. If a call has not seen a packet (inactive call on the backup node, seen as not responsible for that call but could become so), we accept all commands for that call on the backup node in the same way as on the original node. That means also deletions in-between and so on. I mean if the original node does it, why not accepting to do the same way on the backup node ?	9 years ago
Frederic-Philippe Metz	bf38f151ba	Fix for restoring notified call from own redis db	9 years ago
Frederic-Philippe Metz	48543b4c4e	Intermediate State: Notifications enabled by cli	9 years ago
Frederic-Philippe Metz	d7ca576ba2	Fixed issues with terminating event_loop	10 years ago
Frederic-Philippe Metz	447148b73f	Stop event loop on shutdown	10 years ago
Frederic-Philippe Metz	1ee88db282	Fixed SEGFAULT for RTPENGINE-64	10 years ago
Frederic-Philippe Metz	28a43e4f11	Merge remote-tracking branch 'origin/master' into dev-fmetz-redis-notification ... Conflicts: daemon/call.c daemon/main.c daemon/redis.c	10 years ago
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
Richard Fuchs	cd34dde934	fix missing redis expiry times ... Change-Id: Id38d3760f2eb0bcbf6c8912be244662c5ce11855	10 years ago
Richard Fuchs	6d3865b971	Mass update - manual merge of rfuchs/socket-rework branch ... This brings master up to date with branch `rfuchs/socket-rework` at commit `b1bcc096b7`. The branches have diverged too much for a proper merge, so this is a manual (squashed) merge. The old master before this merge can be found in branch `old-master-before-socket-rework` (commit `82199216b2`). This is a complete rewrite of all socket handling routines. The most important functional change is that sockets aren't indiscriminately bound to INADDR_ANY (or rather in6addr_any), but instead are always bound to their respective local interface address and with the correct address family. Side effects of this are that in multi-homed environments, multiple sockets must be opened (one per interface address and family) which must be taken into account when considering RLIMIT_NOFILE values. As a benefit, this change allows rtpengine to utilize the full UDP port space per interface address, instead of just one port space per machine. The socket abstraction also makes it possible to support RTP over TCP in the future. Change-Id: If6cf4f42136229490186d2d2482fb4fc140c2b53	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	83ebe70e81	clean up payload_types-X before populating it	10 years ago
smititelu	2ed14aa86e	Solve packet errors due to payload type ... The payload types are not saved and retrieved from redis. Used a hash to store the payload types in the form (0, payload_value0), (1, payload_value1) for every media.	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	a780cf7891	redis updates	12 years ago
Richard Fuchs	900f76a17e	make the callmaster struct private - also requires update to redis module	13 years ago
Richard Fuchs	dc7517121d	remove uuid helper code	13 years ago