We do not use a proper mount unit because that requires the mount point
to be encoded in the filename which is variable and depends on the value
coming from config.yml.
Change-Id: Ibb637c533c94bc3db119111460ca647a50a205af
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.
Split out the debugging symbols from the main packages into
one single package named ngcp-mediaproxy-ng-dbg
Closes: https://bugtracker.sipwise.com/view.php?id=1825
From: Michael Prokop <mprokop@sipwise.com>
The default file is provided by templates. We
won't have questions regarding changed config
files on upgrades.
The init script will be provided via lsb-scripts.
Guillem Jover
Richard Fuchs
Victor Seva
Stefan Mititelu
Frederic-Philippe Metz
Jon Bonilla
Michael Prokop